A few months back I watched one of our customers run a real product launch through Arkweaver, start to finish, over MCP. It mostly worked, which was the good news. The bad news was the places it didn't: a one-pager came back two sentences long, it quoted a sales rep as if he were a customer, a deck printed "Brand guidelines" as the company logo, and a product-line request got forced through the nearest prompt that happened to exist. None of that is the kind of thing you catch in a demo. You only catch it when someone you respect is trying to ship with it on a deadline.
So a lot of this window was spent closing those gaps. We shipped the Launch Hub, rebuilt how deliverables are sourced and printed, and gave chat and MCP the ability to actually do the things the buttons do, not just talk about them.
TL;DR
Arkweaver now has a Launch Hub that groups related features into a named launch with dates, a shared launch context, an editable plan, and two-way Notion sync. Deliverables are rebuilt to lead with outcomes, quote only verified customers (never reps), print as branded PDFs, and use your team's own pitch language pulled from Gong calls. Chat, Slack, and MCP can now send deliverables to teammates, file requests into Jira or Linear, record feature interest by hand, approve and edit drafts, and send customer announcements behind a confirm-before-send guard. Launch emails can include a screenshot and a demo link, and a new rep coverage report shows who isn't pitching what. If you connect a PDF of your best one-pager, Arkweaver reads its brand and prints future deliverables to match.
What is the Arkweaver Launch Hub and how does it work?
The Launch Hub lets you group related features into a single named launch with optional dated stages, a plan of deliverables and owners, and a shared context every deliverable is written from. You find it under Launches. A launch is just a folder of features that ship together, like a "Catalight rollout" on one date moving to "General availability" a week later, and its status follows from the dates rather than being something you set by hand.
The part I think matters most is the launch context. It's one plain-language page covering what it is, what's shipping, what's coming, who it's for, and a short always/never list for the copy. Arkweaver drafts it the first time you open the launch, pulling from the feature descriptions, the Linear tickets that are done or in progress, and the customers who asked. Every deliverable for that launch is then written from that one page, so you're not re-explaining the scope and the standing fixes in every single request.
The plan itself is an editable table: deliverable, audience, owners, status, due dates, and a done checkbox. Owners show their real names now (synced from Slack and Google Workspace) instead of the front of their email address, which is a small thing that was quietly annoying everyone who looked at it. Rows that hand work to Arkweaver draft themselves. Close-the-loop rows read real sends and tick themselves when the emails actually go out.
You can mirror the whole plan into Notion as a two-way synced table. A change on either side copies across, a row added in Notion joins the plan, and if both sides edit the same cell the later edit wins. It syncs on page open and on demand, not on a timer, so don't expect it to be instant. There's a green Launch button on each feature card that drops you into the new-launch flow with that feature already picked.
Why do Arkweaver's deliverables now lead with outcomes and real quotes?
Because the old defaults produced marketing copy that read like a feature list and sometimes quoted the wrong person entirely. We rebuilt how deliverables are sourced, written, and printed so they need fewer notes before they're usable.
The default one-pager now opens on the outcome and the benefit, then a customer quote, then a short "what it replaces" contrast, then how it delivers, then the call to action. That outcome-first rule applies to every Marketing template, including blog posts, LinkedIn posts, and newsletters, so they all lead with the result rather than the problem. A deterministic style check runs after writing and catches banned words, dashes, and internal wording that leaked into customer copy ("evidence pack" and the like). If it finds any, one rewrite runs, and a rewrite that drops source links or most of the document is thrown out.
Quotes were the bigger fix. Deliverables now use only verified customer quotes, each labelled as rep or customer, with the account name attached. Wording a rep said is never presented as a customer saying it. We also started capturing "it worked" quotes, where a customer describes the result after actually using a feature, and those rank first in one-pager quote picking and get marked "(after using it)." On Frontera's data, one real one-pager went from 2 quotes reaching the writer to 14 once we fixed the fact that Gong calls carry no account field and every quote was being capped as "unknown account."
There's also a pitch-language pass. For each feature, Arkweaver reads its most recent linked Gong calls, pulls the wording your team actually uses (the one-liner, how they explain it, how they handle pushback), and ranks it by how customers reacted. Only phrases staff said word for word are kept. So the copy sounds like your team, not like a generic AI draft.
How do I turn deliverables into branded PDFs and match my own design?
Deliverables whose template prints are now produced as a branded US Letter PDF drawn from their text, and if you upload a PDF of your best example, Arkweaver reads its brand and prints future deliverables to match. The text stays the deliverable. You still edit and revise the words, and the page is reprinted from whatever it currently says.
Printing is on by default for the Marketing one-pager and the Enablement sales battlecard. Each markdown section becomes a block (hero, cards, quote, numbered steps, a live-today/coming-soon status list, a table, a call to action), recognised by its shape rather than its heading, so reordering the text reorders the page. A two-page PDF example prints as a branded two-page PDF instead of being squeezed and auto-shortened to one.
When you connect a PDF golden example, Arkweaver reads its colors, fonts, and logo on upload and prints in that brand by default. You can also opt in to copying the example's layout, not just its brand. One real problem we hit and fixed here: list items were getting cut during print fitting (whole steps and bullets vanishing), and fitting ran after the job already reported done, so approval saw different text than the draft. Fitting now finishes before completion and refuses any shortened version that drops a list item, a heading, or a quote.
Can chat and MCP actually send, file, and approve things now?
Yes. This was a big push: chat, Slack, and MCP can now do the things the buttons do, each calling the same underlying function the page action calls, so permissions and behaviour match everywhere.
A few of the ones people will use most:
- Send any deliverable to teammates, not just a feature's. "Make a 1-pager and send it to Oliver and Zara" used to fail for product-line and general deliverables and then cover the failure with an approval step that didn't exist. Now one path sends every deliverable type over each colleague's own channel, Slack falling back to email, and it's claimed so a retry never double-sends.
- File requests into Jira, Linear, or Shortcut by hand: "file everything with 5+ customers and $250K+ ARR in Jira." The first call files nothing, it lists what qualifies and isn't filed yet, and it only files when you confirm that exact list.
- Record feature interest when no call shows it: "mark Northshore Dermatology as interested in AI Prior Authorization, they asked Sam last week." It saves a stand-in record and refreshes the feature's customer count and value.
- Approve and edit drafts. edit_deliverable swaps exact text in the newest version so changing one sentence doesn't mean regenerating the whole thing, and any edit clears the approval so you have to re-approve.
- Send customer announcements, behind a confirm-before-send guard enforced in code. send_announcements never sends on the first call. It returns who would get the email, who was already sent to, and who it'll skip, and only sends when you call again with the recipient count it gave you back. Drafting from chat or MCP always holds for review.
There's a find_quote tool shared across all three channels that searches quotes already extracted from your calls by a few words, by speaker, or both, and returns the exact wording, who said it, the call and date, and a link that opens the call at that quote. MCP callers can also read a deliverable and write it into their own design file, so someone's Claude can put Arkweaver's words into a Figma one-pager.
What else shipped: coverage reports, demo links, and the quieter fixes
Two things worth calling out beyond the big three.
Launch emails can now include a screenshot and a demo link. There's an optional demo URL field on each feature (YouTube, Loom, whatever), and a new email-rules checkbox, off by default because screenshots have been private until now. Turn it on and drafts get a "Watch the demo" link, emails attach the screenshot as a PNG, and internal Slack DMs upload it into the thread.
We also added a rep coverage and missed-pitch report. It shows who is and isn't pitching each product line, and which accounts voiced a need for a line that nobody pitched them in the window. It's read-only for now, with no new AI calls, because we wanted the numbers to be credible before we build battlecards and alerts on top of them. To be honest, that one's deliberately held back until we trust it.
Under the hood, the Deliverables page got faster and stops crashing when its feed can't render, deliverables created together are now grouped into a set with a single "N deliverables are ready" notification instead of one per deliverable, and chat shows a plain-language progress label for each step ("Searching calls," "Reading your example") instead of just saying "Thinking" the whole time. Product-line deliverables that finish after the MCP wait expires now actually reach the person who asked, instead of completing with nobody told.
The shift in thinking for us this window was simple. We stopped treating "it generated a deliverable" as the finish line and started treating "someone could ship this without rewriting it" as the bar. Watching a real launch go through the product is a much harsher reviewer than any test suite, and most of what's above came straight out of that.
FAQ
What is the Arkweaver Launch Hub?
The Launch Hub groups related features into a single named launch with optional dated stages, an editable plan of deliverables and owners, and a shared launch context every deliverable for that launch is written from. Its status (Planning, Launching, Launched) follows from the dates rather than being set by hand. You can mirror the plan into Notion as a two-way synced table.
Do Arkweaver deliverables quote sales reps as customers?
No. Deliverables now use only verified quotes, each labelled rep or customer, with the account attached. Wording a rep said is never presented as a customer quote. Arkweaver also captures "it worked" quotes where a customer describes the result after using a feature, and ranks those first in one-pager quote picking.
Can I send deliverables and customer announcements from chat or MCP?
Yes. Chat, Slack, and MCP can send any deliverable to teammates over their own channel, file requests into Jira, Linear, or Shortcut, record feature interest, and approve or edit drafts. Sending customer announcements is gated by a confirm-before-send guard: the first call only previews recipients, and it sends only when you confirm the exact count it returned.
How do I make Arkweaver deliverables match my brand?
Upload a PDF of your best example (a one-pager, say) and Arkweaver reads its colors, fonts, and logo, then prints future deliverables in that brand by default. You can also opt in to copying the example's layout. Printing is on by default for the Marketing one-pager and Enablement sales battlecard, and two-page examples print as branded two-page PDFs.
Can launch emails include a demo video?
Yes. Each feature has an optional demo URL field for a YouTube or Loom link, and a new email-rules checkbox (off by default) adds a "Watch the demo" link and attaches the feature screenshot to launch emails. It applies only to launch emails, not status-change emails or internal shares.
