Demo script

What is a demo script?

A demo script is the documented flow a sales rep follows during a product demonstration — covering which features to show, in what order, with what narrative arc, and what to say at each step. A well-designed demo script is not a feature parade (showing everything the product can do). It's a pain-to-solution narrative that mirrors the prospect's own discovery conversation back to them: 'You told me X is a problem. Here's exactly how we solve that.'

The term 'script' is slightly misleading — a good demo script is a flow and a set of talking points, not a word-for-word monologue. Reps who read a script verbatim sound robotic; reps who internalize the flow and deliver it naturally close more. The script is the backbone that ensures every demo covers the critical sections in the right order, not a teleprompter.

For an AE running 8–15 demos a week, a demo script is consistency infrastructure. Without it, each rep runs a different demo that emphasizes different features for different reasons — and there's no way to identify why some demos convert and others don't. With a script, the demo is A/B testable: change one section, measure the conversion impact.

What a complete demo script contains

An effective demo script has five phases, each with a defined purpose.

• Opening (3–5 min) — restate the discovery findings. 'Based on what you told me, the three problems you're trying to solve are [X], [Y], [Z]. Today I'm going to show you exactly how we address each one.' Sets expectations and signals the demo is personalized.
• Pain-to-feature mapping (15–20 min) — show only the capabilities that address the stated pains. Walk through each pain, show the specific product section that solves it, state the outcome. Do not show features that don't map to a stated pain.
• Social proof injection (3–5 min) — insert one customer story or proof point per pain section. 'A company in your exact situation — similar stage, similar team size — used this to reduce their admin time from 4 hours to 45 minutes. Here's what that looks like in practice.'
• Objection checkpoint (3–5 min) — pause before the close and check for concerns. 'Before I walk through pricing and next steps, what questions do you have? Anything you'd like to see differently?' Surface concerns before they become post-demo ghosts.
• Close (5 min) — propose a specific next step with a named date. Not 'let's stay in touch.' 'The natural next step would be to get your IT lead on a call this week to run through the security questions — does Thursday work?'

How to build a demo script

1. Start with the top 5 pains your ICP identifies in discovery. The demo script is built around solving those pains — not around showcasing every product feature.

2. Map each pain to the minimal feature set that demonstrates the solution. One pain, one or two screens, one customer quote. Don't show the advanced configuration; show the outcome.

3. Write the exact narrative for each pain section. 'You mentioned [pain]. The problem most teams run into is [root cause]. Here's how we solve that...' Having the narrative written prevents reps from ad-libbing into a feature dump.

4. Define what to skip. A demo script includes an explicit 'do not show unless asked' list. The admin settings panel. The API documentation. The reporting module unless the prospect specifically asked. Less is more.

5. Test it in 5 real demos. Record, watch, and measure the conversion rate. Find the section where prospects disengage and fix it. A demo script is a hypothesis; only field testing proves it.

Common demo mistakes

1. Starting with the product instead of the pain. The first 2 minutes of a demo that opens with a feature tour loses the prospect's attention. Open with what you heard in discovery.

2. Showing too much. Every additional feature beyond the stated pain reduces the signal-to-noise ratio and invites 'well, do you also have X?' questions that derail the conversation.

3. Not pausing for questions. Reps who sprint through the demo and ask 'any questions?' at the end get 'looks good, we'll follow up.' Reps who pause after each pain section get real objections while they can still address them.

4. No specific next step. A demo that ends without a named next action and date produces a ghost rate of 60–70%. Always close with a specific, named, dated next step.

How Gangly helps reps run pain-led demos

Gangly's Call Prep Engine generates a pre-demo brief that lists the prospect's stated pains from the discovery call — in their exact language — and maps each pain to the relevant demo section. The rep opens the call already knowing which three features to lead with and what proof point to pair with each one.

Live Call Coach watches the demo in real time and surfaces a prompt when the rep has been in one section for more than 8 minutes without a natural pause — the signal that the demo has drifted into a feature dump.

See how Call Prep Engine works →

Frequently asked questions