How to Write a Demo Script (Template + Examples)
How to write a demo script that keeps a product demo tight and persuasive — a reusable structure, what to say at each beat, the lines to cut, and a template you can fill in for your own product.
To write a demo script: open with the prospect's problem, map the whole demo to one outcome they care about, write value-driven talking points (not a word-for-word screenplay) for three to five beats that build to it, pre-empt the likely objection, and end with a specific next step. Keep it tight — if it runs to ten sections it's a feature tour, not a demo. The script's real job is to stop you from showing everything and keep you on one persuasive story. Here's the structure and a fill-in template.
Start with the problem, not the product
The opening line decides whether anyone leans in. Don't start with "Let me show you our platform." Start where the buyer already is: "You said your reps rebuild the same report every week — let me show you how that becomes three clicks." You've named their pain and promised a payoff in one sentence. Everything after earns attention by paying that off.
Map the demo to one outcome
Before writing a single beat, decide the one thing this demo will prove. Not "show the analytics suite" — "show that they'll catch a revenue dip a week sooner." Every beat either moves toward that outcome or gets cut. This single decision is what separates a demo people finish from a tour they tune out.
Write beats, not a screenplay
Structure the body as three to five beats, each a step toward the outcome. For each beat, write:
- What's on screen — the action you'll take.
- The value line — why this matters to them, not what you're clicking.
- The transition — the sentence that leads to the next beat.
For every beat, write the value line before the action. If you can't say why a step matters to this buyer, cut the step. That one rule eliminates most demo bloat.
A fill-in template
Hook: "You mentioned [problem]. Here's how [product] makes that [better outcome]." Outcome this demo proves: [one sentence] Beat 1 — [action]: Value line: "[why it matters to them]." Beat 2 — [action]: Value line: "[…]." Beat 3 — [action]: Value line: "[…]." Objection pre-empt: "You might be wondering [objection] — [answer]." Call to action: "[specific next step]."
Copy that, fill it in, and you have a complete, focused demo script.
Narrate value, not clicks
The most common scripting mistake is narrating mechanics — "now I click the dropdown, then this panel opens." That teaches the UI and sells nothing. Narrate the why. This applies whether you're delivering live or recording a sales demo to send async, and it's the same discipline behind a good product demo video.
Pair the script with something they can replay
A script is for the live moment — but the buyer rarely decides alone, and your delivery isn't in the room when the demo gets forwarded to the rest of the buying committee. Pair the scripted demo with an interactive version they can drive themselves afterward:
That way the script wins the live moment and the interactive demo keeps selling after it. To learn the delivery side, see how to give a product demo.
Frequently asked questions
How do I write a demo script?
Open with the prospect's problem, not your company. Map the demo to one outcome they care about, write talking points (not a word-for-word screenplay) for each step that explain the value rather than the clicks, and end with a clear next step. Keep it tight enough to deliver in a few minutes. The script's job is to keep you on the story and stop you from touring every feature.
What should a demo script include?
A hook tied to the prospect's problem, the one outcome the demo will prove, three to five value-driven beats that build to it, proactive answers to the most likely objection, and a specific call to action. Write talking points rather than a full script so it sounds natural — the structure keeps you focused, the looseness keeps you human.
How long should a demo script be?
Long enough to hit one clear outcome and no longer. For most software demos that's three to five beats covering a few minutes of actual product time. If your script has ten sections, it's a feature tour, not a demo — cut to the single story that moves this specific buyer.
Should I read a demo script word for word?
No. Write talking points and the key value lines, then deliver them conversationally. Reading verbatim sounds robotic and makes it hard to react to the prospect. The script is a map, not a teleprompter — it keeps you on the route while letting you respond to what the buyer actually says.