Create a product launch narrative kit for sales, website, ads, and email

Create a Google Drive folder and Google Doc for the launch source brief. Include the product update, target audience, use cases, screenshots, demo notes, release timing, pricing or packaging changes, differentiators, roadmap context, competitive context, customer proof, sales feedback, known limitations, and claims that are already approved. Label each input as approved, needs confirmation, background only, or do not use. Add links to source files instead of pasting scattered notes into multiple chats. The goal is to give Claude one clean source of truth while keeping uncertain material out of draft generation.

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. Add fields for source, owner, approval status, risk level, allowed wording, channels where it can be used, and reviewer. Use Claude to suggest the first version from the source brief, but require PMM or product to confirm anything factual. This separates persuasive writing from claim approval so teams do not accidentally publish unsupported promises. The claim ledger becomes the guardrail for every website, email, ad, and sales asset that follows.

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.