Launch Narrative

🧠Customer Pain

Open on a specific pain in the customer's words, not a feature

Open the launch copy on the pain in the customer's own words, not your product. Use phrases lifted verbatim from support tickets, sales calls, and reviews; name the exact moment the pain bites (the trigger scene), then quantify its cost — hours wasted, money, or the workaround they hate. One sharp pain converts better than three vague ones.

✨Promise Shift

Promise the before→after state change in one sentence

Stop listing features and rewrite the before→after state change as a promise. Compress it into one 'from X to Y' sentence, where the verb describes the customer's new reality, not your product's capability. The promise must be the exact inverse of the pain in node 2, and a believable specific ('30-minute reconciliation down to 3') beats a superlative like 'the best.'

📦Offer Stack

Not one product, but a bundle that makes 'buy now' rational

The offer is the bundle that makes 'buy now' the rational choice — core product + bonuses + guarantee + a reason to act today. Stack 2–3 concrete deliverables (a template, an onboarding call, lifetime updates), state the risk reversal (refund, no-card trial), and add real launch-window scarcity (price rises after day X, a first-100 bonus). Give each item its own standalone value so the sum reads as a no-brainer.

Demo Script

Not a feature tour — one outcome reached in under 3 minutes

Script the demo to reach one outcome fast, not to tour every menu. Open in the painful before-state, do the single highest-value job end to end in under 3 minutes, then close on the visible after-state. Cut setup and config — start mid-task with data already loaded. The viewer should be able to repeat exactly what they saw; show the path, not the feature catalog.

Pricing Anchor

Price only looks cheap beside an anchor

Price reads as cheap only beside an anchor. Anchor against the cost of the pain (the manual workaround, the agency quote, the lost hours), then show your price as a fraction of it. In a 3-tier layout, design the middle tier as the intended pick (decoy effect), and state the anchor before the price — never after. A struck-through 'original' price only works if that price was ever real.

📈Proof Layer

Every claim gets a proof object beside it — data, demo, or quote

Put a proof object next to every claim — a number, a live demo, or a named testimonial. Match the proof type to the claim: a performance claim earns a metric or benchmark, an ease claim earns a 20-second demo GIF, a trust claim earns a quote with a real name and company. Place the strongest proof right after the promise (node 3), not at the page bottom where nobody scrolls.

Case Quotes

Quote a result, not an adjective

Quote results, not adjectives. The strongest testimonial names a number and a timeframe ('cut our close from 6 weeks to 9 days'), attaches a real name + role + company, and ideally a face. Pull the one sentence that states the transformation and drop the 'great team, love it' filler. A single specific quote from a recognizable peer beats ten anonymous five-stars.

⏱️Launch Beats

Don't fire it in one day — build tension across a multi-day cadence

A launch is a multi-day cadence, not a single 'it's live' post. Spread it across beats: teaser → pain story → demo reveal → proof and social wave → offer opens → scarcity close → last call. Each beat is one focused message on one channel, reusing the same internal narrative to stay coherent. The dip after day one is normal — the last-call beat usually drives a second spike of conversions.

Launch Sequence

Pin the beats to dates — who, when, and on which channel

Pin the beats to actual dates and owners. A typical 7-day grid: D-3 teaser, D-1 pain story, D-0 demo + offer opens, D+1 proof wave, D+2 objection-handling FAQ, D+3 scarcity reminder, D+4 last call / close. Each row names the channel, the asset, and the owner; pre-write everything so launch week is execution, not authoring. Hold the close date firm — a deadline that slips trains people to ignore the next one.