Product launches usually stumble on distribution, not on the announcement itself. The blog post lands but the social thread contradicts it; the customer email uses different copy than the sales team memorized; the changelog says something the marketing site doesn't. This workflow makes the whole kit at once, from one source of truth — the ship-day artifact set is aligned, voice-consistent, and lets you push everything within the same hour. It's the pattern that separates 'we shipped' from 'we launched'.
Write the source-of-truth brief
Goal: One document that every downstream artifact draws from. If this is right, everything else falls into place.
I'm launching [feature/product] on [date]. Write the source-of-truth brief (~400 words) with: (1) the one-sentence positioning, (2) the problem this solves (the specific pain, not 'inefficiency'), (3) how it works (3-4 bullets, technical enough that a curious user can picture using it), (4) who it's for and who it's not for (be specific about the non-fit), (5) the ONE metric or specific thing we care about launch-day (impression? try? sign-up? conversion? we don't chase all of them), (6) what this ISN'T (the closest adjacent thing this might get confused with).
Blog post + changelog entry
Goal: Two artifacts, same information, different lengths.
From the brief above, draft (1) a 500-word blog post for the /blog page in the voice of the founder — first-person, specific, no hype, ends with a specific ask, and (2) a 3-sentence changelog entry for /changelog. Blog post opens with the specific pain we heard from customers, not with 'today we're excited to announce'.
Social threads (X, LinkedIn) + customer email
Goal: Distribution surfaces, adapted to each channel's shape, still saying one thing.
Draft: (1) a 6-tweet thread for X — first tweet is the hook (specific pain, not the announcement), (2) a 1-post LinkedIn version — 4 short paragraphs, professional register, (3) a customer email — 100 words to all existing business subscribers, opens with 'the statement drops next Friday'.
Sales / support enablement one-pager
Goal: The internal doc that keeps the go-to-market team saying the same thing as the public artifacts.
Draft the internal enablement one-pager for sales and support: (1) the elevator pitch (1 paragraph), (2) top 5 questions customers will ask + our answers, (3) the honest 'when this is NOT a good fit' framing so the team doesn't overpromise, (4) links to all published artifacts (blog, changelog, social, /business/impact-reporting).
Handoff: Enablement one-pager to internal Notion. Blog post + changelog scheduled for ship-day publication (ideally 8am ET). Social + customer email queued for the same window. Ship-day: one person watches responses across all channels; keeps consistent voice in replies.
Repeatability, not cleverness.
What lives where when the workflow finishes.
Brief → the source-of-truth doc in your marketing Notion. All artifacts publish within a 4-hour window on ship day. Follow-up: 3 days after launch, review which artifact drove the metric named in Step 1 (typically the blog + LinkedIn perform strongest for our business); use that data to weight the next launch's distribution.
The same shape, different jobs.
- Public product launch — add a press embargo + reviewer outreach kit as Step 5.
- Feature update (small) — collapse Steps 2-4 into one artifact set; blog post becomes a short update note.
- Big-name partner announcement — add a joint-approval loop; social and press require partner sign-off before Step 3.
- Silent launch / beta — Steps 3 and 4 skipped; only the customer email goes to a curated list; feature stays undocumented until GA.
Prompts: three headlines then choose · one pager from messy thread
Try this workflow once. Then decide if it earns a recurring slot.
The value compounds after the third run, not the first.