Analyst for Launch Narrative Drafting

The average launch narrative goes through eleven drafts before the CMO signs off, and most of that revision is structural — the argument is wrong, the order is wrong, the category noun shifts twice between the deck and the blog post. Almost none of it is prose polish. A positioning analyst doesn't write a better sentence than your senior PMM. It reorders the argument before anyone wastes a Tuesday on word-level edits.

That's the whole pitch. The rest of this piece is how to actually do it.

Why launch drafts spiral

Pull the version history on any failed launch narrative and you'll see the same shape: drafts one through four argue about the what (which feature is the hero), drafts five through eight argue about the who (which segment leads the story), and drafts nine through eleven argue about the why-now (the wedge against the alternative). Each of those is a positioning question, not a copy question. But because the document looks like prose, every reviewer treats it as prose and lands their edits in tracked changes instead of in a margin comment that says "the argument is wrong."

The analyst's job is to surface the structural disagreement before the prose exists. You feed it the positioning brief, the competitive context, and the audience. It hands you back three structurally different narrative spines. You pick one. Then — and only then — does anyone open Google Docs.

The four-prompt sequence

A launch narrative has four structural decisions, in order: the frame (what change in the world makes this launch matter), the category (the noun the buyer files you under), the contrast (what alternative you're displacing), and the proof (what evidence shifts a skeptic). Drafting in that order, with a discrete prompt at each gate, is what cuts the cycle.

Each gate produces a one-page artifact. The four artifacts together are the narrative spine. A senior PMM can write the actual launch document from that spine in two drafts, not eleven.

What good prompting looks like

The thing that breaks this workflow is treating the analyst like a copywriter. If your prompt is "write me a launch narrative for our new analytics product," you get a generic launch narrative for a generic analytics product. The structural decisions are still buried in prose, and you're back to draft eleven by Friday.

The prompts that work share three properties. They name the artifact ("a one-paragraph why-now frame"), they name the constraint ("under 60 words, no jargon, no hedging"), and they ask for variants instead of a single answer. Asking for one answer collapses the disagreement into a single document; asking for three forces a choice.

Where the analyst doesn't help

Two cases. The first: when the positioning brief itself is wrong or stale, no amount of narrative drafting fixes it. The analyst will faithfully amplify the bad frame. If three independent frames all feel weak, the brief is the problem — go fix the brief, then come back.

The second: when the disagreement is political, not structural. If the head of product wants the AI feature to be the hero and the CMO wants the workflow redesign to be the hero, the analyst can show you that those are different launches with different buyers. It can't tell you which executive to side with. That's a meeting, not a prompt.

What the cycle looks like when it works

A working analyst-assisted launch narrative cycle looks something like this on the calendar:

Five working days, three drafts, one approval cycle. Compare that to the eleven-draft, three-week version most teams ship now, and the math on whether the four-prompt overhead is worth it answers itself.

What to do Monday

Pull the last launch narrative your team shipped. Open the version history. Count the drafts where the structural argument changed — where the category noun moved, where the hero feature shifted, where the why-now reframed. That number, minus two, is roughly how many drafts the four-prompt sequence would have removed from the next launch. Run the prompts on the next launch's brief this week, before anyone opens a doc.