Sales Demo Script

Before you start

Gather the following from the user. If anything is missing, ask before proceeding:

1. What product or feature are you demoing? (Full product, specific module, new capability)
2. Who is the audience? (Job title, technical depth, decision-making authority)
3. What problem does the audience care about? (In their language, not your feature names)
4. What is the current alternative? (Competitor, manual process, internal tool)
5. What are the top 3 objections you hear? (Price, switching cost, security, "build it ourselves")
6. What is the desired next step? (Free trial, POC, procurement, technical deep-dive)
7. How long is the demo slot? (15, 30, or 45 minutes — determines scope)

Demo script template

1. Opening (2-3 minutes)

Set context before touching the product.

"Before I show you anything — from our conversation, I understand
[specific pain point]. You're using [current process/tool] and the
main challenge is [consequence]. Still accurate?"

"I'll show you three things:
1. How [product] handles [pain point 1]
2. How it compares to [alternative] for [pain point 2]
3. [Unique differentiator]
Then we'll talk next steps."

Always confirm the problem before demoing. If the audience corrects you, adapt on the spot.

2. Discovery Questions (3-5 minutes)

If discovery was not done in a prior call, embed these before the walkthrough:

• Current state: "Walk me through how your team handles [process] today."
• Pain: "What breaks first when volume increases?"
• Impact: "When [problem] happens, what does that cost in time/revenue?"
• Decision criteria: "What would success look like in the first 30 days?"
• Stakeholders: "Who else would need to evaluate this?"
• Timeline: "Is there a deadline driving the timing?"

Listen more than you talk. Answers determine which features to emphasize and which to skip.

3. Product Walkthrough (15-25 minutes)

Structure the walkthrough as a story, not a feature tour. Each section follows the pattern: Problem > Solution > Proof.

Section 1: [Primary pain point]
  Problem:  "You mentioned [specific pain from discovery]."
  Solution: [Show the feature — click, don't describe]
  Proof:    "Customer X saw [specific result] solving the same issue."

Section 2: [Secondary pain point]
  Problem:  "Another thing you raised was [second pain]."
  Solution: [Demo the workflow with realistic data]
  Proof:    "This saves teams [metric] per [period]."

Section 3: [Differentiator]
  Problem:  "Most tools in this space [limitation]."
  Solution: [Show what only your product does]
  Proof:    "This is why [customer] chose us over [competitor]."

Rules: Use realistic data matching the prospect's industry. Click through real workflows — screenshots signal the product is not ready. Pause after each section to confirm relevance. Skip features the audience did not ask about.

4. Objection Handling

Prepare responses for top objections using the Acknowledge > Reframe > Evidence pattern.

Objection: "This seems expensive compared to [competitor]."
  Acknowledge: "Pricing is important to get right."
  Reframe:     "The real comparison is TCO — implementation, maintenance, productivity."
  Evidence:    "Customer Y found [product] was X% less over 12 months."

Objection: "We could build this internally."
  Acknowledge: "Your engineering team is clearly strong."
  Reframe:     "Is building [category] the best use of their time vs. [core work]?"
  Evidence:    "Customer Z estimated 3 months — still maintaining 18 months later."

Objection: "We need to think about it."
  Acknowledge: "Absolutely — important decision."
  Reframe:     "What specific questions does your team need answered?"

5. Close and Next Steps (2-3 minutes)

End with a clear, specific ask — not "let me know if you have questions."

"Based on what we covered, [product] addresses [pain 1] and [pain 2].
Here's what I'd suggest: [Choose ONE]
- Trial: "14-day trial with your data."
- POC: "2-week POC focused on [use case]."
- Expand: "Technical deep-dive with [their engineer]."
Does [specific date] work to get started?"

Always propose a specific date. "I'll follow up next week" has a close rate near zero.

Quality checklist

Before delivering a demo script, verify:

• Opening confirms the prospect's problem before showing the product
• Discovery questions are included as a section or recap prompts
• Walkthrough follows Problem > Solution > Proof per section
• Demo uses realistic data relevant to the prospect's industry
• Top 3 objections have prepared Acknowledge > Reframe > Evidence responses
• Close proposes one specific next step with a date
• Script length fits the time slot with room for questions

Common mistakes to avoid

• Starting with your company history. Nobody cares about founding stories during a demo. Start with their problem.
• Showing every feature. Show 3 things well, not 15 things briefly. A feature tour signals you do not understand priorities.
• Using fake data. "Acme Corp" test data tells prospects you did not prepare. Mirror their industry and scale.
• Ignoring audience reactions. If they lean in on feature X, spend more time there. If they disengage, skip ahead.
• No objection preparation. The same 3-5 objections come up in 90% of demos — script responses for all of them.
• Ending without a next step. Propose a specific action with a specific date, not "I'll send materials."