Best for
- PMMs preparing launches across multiple channels
- B2B teams that struggle with inconsistent launch messaging
- Sales teams that need clear talk tracks before a product release
Turn launch inputs into a PMM-approved narrative system that keeps website, sales, ads, email, customer, and support messaging consistent.
A launch narrative kit with positioning, audience-specific message blocks, claim guardrails, FAQs, channel copy, approval status, and post-launch message learnings.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
6 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Launches get messy when every channel rewrites the product story separately and every stakeholder reviews from a different version of the truth. A narrative kit gives teams one approved source for who the launch is for, why it matters, which claims are safe, and how the value should be explained. AI speeds up synthesis and first drafts, but the workflow forces claim review, owner assignment, and post-launch learning before the message becomes permanent positioning.
Expected results
Launch assets produced
6-10 channel-ready assets
A narrative kit can support website, email, ads, sales, customer, support, and internal assets without requiring every team to rewrite from scratch.
Time saved
8-12 hours per launch
AI accelerates synthesis, persona blocks, FAQs, and first drafts while PMM still owns narrative quality and claim approval.
Message consistency
One approved source of truth
The source brief, claim ledger, and persona blocks give every channel the same narrative, proof, CTA logic, and guardrails.
Launch readiness
Role-reviewed claims and FAQs
Product, sales, support, brand, legal, and PMM review the parts they are responsible for before assets reach buyers.
Step-by-step workflow
The first 2 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
45-60 min
45-60 min
Create a Google Drive folder and Google Doc for the launch source brief. Work in google docs and airtable and capture the concrete operating details: source links, buyer context, audience, claims, proof points, owner, review status, and the final deliverable link. Keep the work narrow: complete step 1, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that every claim has a source, every assumption is labeled, and unsupported claims are removed; the expected handoff is Launch source brief with product facts, audience, proof, limitations, source links, and approval status for each input.
Launch source brief with product facts, audience, proof, limitations, source links, and approval status for each input.
Include limitations early. Launch messaging becomes risky when teams only document the upside and leave sales or support to discover caveats later.
45-60 min
45-60 min
In Airtable, create a claim ledger with one row per product claim, proof point, stat, integration, customer reference, roadmap statement, pricing note, or competitive statement. Work in airtable, claude, and google docs and capture the concrete operating details: campaign name, audience, channel, offer, message angle, asset URL, performance baseline, owner, and approval status. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that every claim has a source, every assumption is labeled, and unsupported claims are removed; the expected handoff is Claim ledger with approved, pending, restricted, and prohibited launch claims mapped to owners and sources.
Claim ledger with approved, pending, restricted, and prohibited launch claims mapped to owners and sources.
Separate copy approval from claim approval. A sentence can sound good and still be unsupported, risky, or not ready for a public launch.
Pro workflow preview
Previewing 2 of 8 steps
Get the remaining 6 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Create a launch claim ledger from this source brief.
Launch source brief:
{{launch_source_brief}}
Known claims or proof points:
{{known_claims}}
Risk rules:
{{risk_rules}}
For each claim, output:
1. Claim or proof point
2. Source document or evidence
3. Claim type: product, customer, integration, roadmap, pricing, competitive, performance, or legal
4. Risk level
5. Allowed wording
6. Wording to avoid
7. Required reviewer
8. Approval status recommendation
9. Channels where the claim can be used
Do not invent claims. Mark uncertain items as needs confirmation.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
A reusable employee advocacy kit with post variations, personalization prompts, visual assets, and simple distribution instructions.
A scalable executive ghostwriting system with voice profiles, idea intake, draft generation, approvals, and performance feedback by executive.
Build a competitor messaging map with repeated claims, proof gaps, overused language, and sharper positioning opportunities for your brand.