Write a product demo script that tells a value story instead

Sales Demo Script Skill

Write a demo that makes a buyer feel their problem being solved — a value story, not a click-through of every screen. The best demos show the shortest path to the "aha," anchored in the pain the buyer already told you about.

What This Skill Produces

• A demo objective and the one thing the buyer should feel by the end
• Discovery hooks to tailor the demo live
• A scene-by-scene flow tied to buyer pain, with talk track
• Clearly marked "aha" moments and clean transitions
• A close with a concrete next step

Required Inputs

Ask for these if not provided:

• Product and the persona/buyer you're demoing to
• Their pain — what problem they're trying to solve (from discovery)
• The value story — the outcome the product delivers
• Key capabilities to show (and which to skip)
• Proof — data, before/after, or a realistic demo dataset
• Meeting context — first demo, technical deep-dive, competitive bake-off; time available

Use realistic sample data; don't imply results or claims you can't back — mark [to confirm].

Process

1. Set the objective — the single feeling/decision the demo should produce.
2. Open with their world — restate the pain; get agreement before showing anything.
3. Design the shortest path — pick the 2–4 scenes that prove the value; cut the rest.
4. Script talk track per scene — say the value, then show the feature as evidence.
5. Mark the "aha" — the moment the payoff lands; slow down there.
6. Write transitions — connect scenes with the buyer's logic, not the menu structure.
7. Close — recap value in their words and ask for the specific next step.

Output Format

---

Demo Script — [Product] for [Persona]

Objective: [the one thing they should feel/decide] · Time: [minutes] · Context: [first demo / deep-dive]

Open (restate their world)

• Say: "[Restate the pain and the outcome they want]"
• Confirm: [question to get a yes before showing anything]

Discovery Hooks (tailor live)

• If they care about [X] → emphasize [scene]
• If they mention [Y] → show [capability]

Scene Flow

Scene 1 — [Buyer outcome, not feature name]

• Setup: [the before state / realistic data]
• Say: [value-led talk track]
• Show: [the specific action]
• ✨ Aha: [the payoff moment — slow down]

Scene 2 — [Buyer outcome]

• Transition: "[connect from Scene 1 in buyer logic]"
• Say / Show / Aha: [...]

Handle Live Questions

• [Likely question] → [crisp answer, then return to the story]

Close

• Recap: "[value in the buyer's words]"
• Next step: [the specific ask — trial, technical eval, mutual plan]

---

Quality Checks

• The demo opens with the buyer's pain, not the product
• It shows the shortest path to the payoff, not every feature
• Each scene leads with value; the feature is the evidence
• "Aha" moments are explicitly marked
• Transitions follow buyer logic, not menu structure
• The close asks for a specific, concrete next step

Anti-Patterns

• Do not do a feature tour or "let me show you the settings"
• Do not start clicking before confirming the pain
• Do not demo on empty or unrealistic data
• Do not rush the "aha" — that's the moment that sells
• Do not end with "any questions?" — end with a next step

Example Trigger Phrases

• "Write a demo script for [product] to a [persona]"
• "Turn this feature list into a value-story demo"
• "Structure a 20-minute demo that leads with buyer pain"
• "Script the talk track and aha moments for our product demo"