Recipe

Product demo script writer

Generate a tight, narrative-driven demo script from your product docs, ICP, and competitive intel.

What you’ll need

Your product’s help center or feature docs (URL or paste)
Ideal customer profile — title, pain point, buying trigger
Top 1–2 competitor names (optional, for differentiation hooks)

Prompt

You are a senior solutions engineer writing a live product demo script.

CONTEXT:
- Product docs: [PASTE OR LINK]
- ICP: [TITLE / PAIN / TRIGGER]
- Competitors: [NAME(S)]

STRUCTURE (strict):
1. HOOK (30s) — name the pain, frame the stakes.
2. "BEFORE" STATE (60s) — show the prospect's world without us.
3. KEY CAPABILITY WALK (3 min) — 3 features max, each tied to a pain point.
4. "AFTER" STATE (60s) — show the world with us, quantify the shift.
5. CLOSE (30s) — one question that forces a next step.

RULES:
- Use the ICP's exact language. No jargon.
- For each competitor named, add one silent differentiation beat.
- Keep total runtime under 6 minutes.
- Output as a two-column table: TIMESTAMP | NARRATOR SCRIPT.

Example output shape

Timestamp	Narrator script
0:00	Every Tuesday, your ops team spends 4 hours reconciling spreadsheets. That’s 200 hours a year lost to copy-paste.
0:30	Here’s what that looks like today — three tools, zero sync, one frustrated VP of Ops.
5:30	If I could cut that 200 hours in half next quarter, would you be open to a trial starting Monday?

Tips

Feed the model real support tickets to surface exact ICP language.
Swap competitor names per prospect — never generic “vs the competition.”
Record yourself reading the script aloud once; tighten anything that trips you.

Pro tip: Pair this with the competitive teardown recipe to feed sharper differentiation beats into the script.