Demo Scripting

Generate detailed demo scripts that match prospect priorities and competitive situation — with screen-by-screen walkthroughs, talking points, anticipated objections, and strategic moments that position your product as the clear choice.

Pre-Work Framework

Before creating a demo script, gather this context:

1. Who is the primary audience for this demo, and what is their role? (VP of Sales, frontline rep, ops manager, technical buyer, procurement) — A 30-minute demo for a VP of Sales is fundamentally different from a 45-minute demo for end-user teams. Executives want business outcomes; practitioners want to see how the product actually works.

2. What is the time allocation, and what's the meeting context? (Discovery call follow-up, competitive evaluation, proof-of-concept kickoff, product tour) — The demo length and depth changes based on where you are in the sales process. A 15-minute discovery follow-up is a different script from a 60-minute competitive evaluation.

3. What specific pain points has the prospect validated as high priority? (If they mentioned, "We waste 40% of rep time on manual updates," that's your opening. If they didn't explicitly mention pain, you need to validate your hypothesis before demoing) — The worst demos start with "Let me show you our product." Great demos start with "Based on our conversation, your biggest challenge is X. Let me show you how we address X."

4. Are they evaluating competitors, and if so, which ones? (This informs whether you need competitive differentiation moments woven into the demo) — If they're comparing you to Gong, your demo needs to address what Gong is strong at and where you're different, but not in a "vs." format. Weave differentiation naturally.

5. What is their evaluation criteria? (Ease of use, integration capability, specific features, cost, time-to-value) — This tells you which features to prioritize and how deep to go on technical capability vs. user experience.

6. Who will be in the demo, and what does each person care about? (End-user wants ease of use, manager wants coaching capability, IT wants integrations, finance wants ROI) — Multi-persona demos need parallel messaging that satisfies different perspectives without creating conflict.

Core Principles

Principle 1: No Demo Without Discovery

Rule: Never deliver a product-focused demo without first validating the prospect's top 2-3 pain points or priorities. If you haven't done discovery, your demo is generic.

Rationale: A demo without discovery context is a feature tour that the prospect could watch yourself on YouTube. Discovery is what makes a demo consultative. You need to know: What problem are you solving for them? Is it the problem they care most about? Are you showing the right features to their priorities? Without discovery, you're making these assumptions, and 60% of demos are about features the prospect doesn't care about.

Principle 2: Pain Before Product, Always

Rule: Open every demo by referencing a specific pain point the prospect mentioned or validated, not by introducing your product. Your opening hook should be about their problem, with your product as the answer, not the subject.

Rationale: Prospects already know you have a product. What they're testing in the demo is whether you understand their problem and whether your solution is relevant. If you open with "Let me show you our platform," you've positioned the demo as about you. If you open with "You mentioned your reps spend 45 minutes after every call updating the CRM — let me show you what happens when that updates automatically," you've positioned the demo as about them.

Principle 3: Ruthlessly Prioritize Features

Rule: Show a maximum of 3-5 features in a 30-minute demo, 5-7 features in a 60-minute demo. More than that creates cognitive overload and dilutes the impact of each feature.

Rationale: Research shows that prospects retain details about 2-3 things they see in a demo. If you show 12 features, they remember none. If you show 3 features connected to their pain, they remember all three. Choose features that map directly to their stated priorities, not features that are "cool" or that your product team wants highlighted.

Principle 4: Interactive Checkpoints Drive Engagement

Rule: Every 5-7 minutes of demo, build in a checkpoint question: "Does this match what your team needs?" or "How does your team handle this today?" Checkpoints serve two purposes: they validate you're showing relevant content, and they give the prospect ownership of the demo direction.

Rationale: A demo without checkpoints is a monologue. The prospect is passive. Checkpoints create dialogue and signal that you're customizing based on their feedback, not running a canned script. Checkpoints also surface objections or priorities you didn't anticipate, so you can adjust the remaining demo.

Principle 5: Competitive Differentiation is Woven, Not Bolted On

Rule: If the prospect is evaluating alternatives, differentiation points should be integrated naturally into the demo, not a separate "Why We're Better" slide. When you demonstrate a feature that's a competitive advantage, add a talking point that contextualizes the advantage without naming the competitor.

Rationale: A "vs. Gong" slide signals insecurity. Talking about Gong directly also makes the prospect feel like you're defensive. Instead, when showing a feature that's a key advantage, add nuance: "One thing our customers in your space tell us they value is that this happens in real-time during the call, not just in a post-call summary." The prospect draws the comparison themselves.

The Process

Phase 1: Pre-Demo Intelligence Gathering

Entry criteria: You have a demo scheduled, and you have initial context about the prospect's role, company size, and stated priorities.

Actions:

• Review all discovery context: notes from previous calls, emails the prospect sent (tone, priorities they mentioned), any RFP or requirements they shared
• If discovery was light or nonexistent, send the prospect a pre-demo email: "Excited for our demo tomorrow. To make sure we focus on what matters to you, I wanted to confirm — are these your top 3 priorities: [Hypothesis 1], [Hypothesis 2], [Hypothesis 3]? Or should we focus on something different?" This forces a clarifying conversation.
• Research the prospect's company: headcount, industry, recent news (funding, hiring surge, competitive pressures), known sales processes or tools they currently use
• Identify what competitive alternatives they're evaluating, if any. Prepare talking points for natural differentiation, not defensive arguments.
• Map the demo attendees: Who will be in the room? What does each person care about? Does your opening hook address all of them, or just the primary audience?
• Determine your time budget for each section: Opening (2-3 min), features (20-30 min for a 30-min demo, accounting for checkpoints), closing (3-5 min). If your planned walkthrough exceeds this, cut features.

Output: Pre-demo brief with:

• Top 3 prospect priorities (validated or hypothesized)
• Key talking points for each feature
• 2-3 competitive talking points (if applicable)
• Time budget for each section
• List of anticipated objections and prepared responses

Exit criteria: You're ready to open the demo with confidence about what matters to the prospect.

Phase 2: Opening Hook (First 2-3 Minutes)

Entry criteria: Demo is live; you're on the call with prospect.

Actions:

• Start with a pain statement tied to their discovery context: "You mentioned that your reps spend 45 minutes after every call updating the CRM. Let me show you what that looks like when it happens automatically." Or, if discovery was limited: "Most VP of Sales tell us their biggest pain is forecast accuracy. Is that true for your team, or should we focus on something different?"
• This opening serves two purposes: (1) it signals you've listened, and (2) it reframes the demo as being about them, not your product
• Do not open with: company history, mission statement, team slide, customer logos, or product overview. The prospect agreed to a demo to see the product working, not to hear your origin story.
• If you're demoing to a mixed group (some executives, some practitioners), open with an outcome statement that resonates with all: "Over the next 30 minutes, I want to show you three specific capabilities that solve the three things you're evaluating us on. Sound good?"
• Confirm you have 30 (or whatever time) uninterrupted: "To respect your time, I want to make sure we're focused and don't run over. Is 30 minutes still good?"

Output: Hook delivered; prospect is engaged and knows the demo is about their priorities, not your features.

Exit criteria: Prospect has nodded or agreed that your understanding of their priority is correct.

Phase 3: Feature Sequence (Core of Demo)

Entry criteria: Hook is delivered; prospect has confirmed the priority is accurate.

Actions:

• Order features by relevance to prospect's priorities, not by your product's navigation menu. If their top pain is adoption, lead with ease-of-use features. If ROI is the priority, lead with features that drive efficiency or speed.

• For each feature, follow this structure:

  (a) Pain/Context (1 sentence): Restate the pain or use case this feature addresses, tied back to discovery.

  (b) Feature in Action (click path): Walk through 2-4 screens showing the feature working. Narrate your click path clearly: "I'm going to start by creating a [object]. Then I'll [action], and you'll see [result]." Go slowly enough that they can follow; fast enough that you don't lose momentum.

  (c) Business Outcome (1-2 sentences): Connect the feature to a business outcome: "This gets the data updated without manual work, so your reps spend that 45 minutes on selling, not data entry. On a team of 40, that's roughly 1,800 hours saved per year, or about one full-time headcount."

  (d) Anticipated Question Handling (prepared response): If you know a question will come up (like "Does this work with Salesforce?" or "What if we need custom fields?"), address it proactively. "I'm sure you're wondering how we handle custom fields — let me show you that in a moment, but first let me finish walking through the core flow."

• Build in checkpoints every 5-7 minutes: "Does this match what you're looking for?" or "How does your team handle this today, before you'd use our tool?" Checkpoints do two things: they validate engagement and they surface objections or new priorities you should account for in the remaining demo.

• If a prospect asks a question that would derail the flow, acknowledge it and park it: "Great question — that's definitely something we should cover. Let me finish this feature, and then I'll come back to that."

• If a prospect indicates low interest in a feature, cut it: "I could walk through [Feature 5], but based on what you've said, it sounds like [Feature 1-3] are more relevant. Should we skip that and focus on questions you have about what we covered?"

Output: 3-5 features demonstrated, each with context, walkthrough, business outcome, and checkpoint for feedback.

Exit criteria: You've shown features that directly address top priorities; prospect has confirmed engagement at checkpoints.

Phase 4: Handling Competitive Context

Entry criteria: You're aware prospect is evaluating alternatives; you're at a moment where your product has a meaningful advantage.

Actions:

• Do not lead with "vs. Competitor X." Instead, weave competitive positioning into feature narration.
• When demonstrating a feature where you have an advantage, add a contextual talking point: "One thing our customers tell us they value about this is that it happens in real-time, so you're coaching during the call when behavior can still change — that's different from some tools that only show you post-call summaries."
• If the prospect directly asks "How does this compare to Gong?" or names a competitor, answer directly but positively: "Great question. The main difference is that Gong's strength is in call recording and analysis, where they're really strong. Our focus is on real-time guidance during calls, so reps get coached while they're still on the call. That's a different philosophy about when coaching matters. What would be most valuable for your team?"
• Do not go negative about competitors. Explain the genuine difference in approach or capability, then let the prospect decide what matters more.
• Use soft positioning language: "We see this differently" rather than "That tool can't..." or "We're better because..."

Output: Competitive advantages woven naturally into the demo without defensiveness.

Exit criteria: Prospect understands what you do well vs. alternatives, without feeling you're trashing competitors.

Phase 5: Closing and Next Steps (Last 3-5 Minutes)

Entry criteria: You've covered the core features; time is running down.

Actions:

• Summarize the 2-3 most impactful features you showed, tied back to their specific priorities: "We covered three things today: (1) real-time rep coaching during calls, which addresses your goal of improving deal velocity; (2) forecast accuracy through live pipeline visibility, which solves the forecast unpredictability you mentioned; and (3) ease of adoption, which matters because your team is stretched thin on onboarding time."
• Confirm the takeaway: "Based on what we covered, do you see how this could address the priorities you shared?"
• Propose a specific next step, not an open question: Do not say "What do you think?" or "Should we talk about next steps?" Instead: "Based on what we've covered, the logical next step would be a technical deep-dive with your team to see integrations with Salesforce and how the data flows. Can we get that on the calendar for next week?" or "Would it make sense for you to trial this with a small pilot group next month? If so, let me connect you with our implementation team to outline the timeline."
• If objections have surfaced during the demo, address them briefly in the close: "I know you had a question about implementation time — we can dive deeper on that in the technical session, but the average deployment is 3-4 weeks for teams your size. Does that timeframe work for you?"
• Provide a clear follow-up action: "I'm going to send you a summary of what we covered plus the technical specs we discussed, and I'll include Sarah from our team, who'll be running the technical review if you want to move forward. Sound good?"

Output: Clear summary of value + specific proposed next step + confirmation from prospect about timeline and format of next step.

Exit criteria: Prospect has committed to (or declined) next step; there is no ambiguity about what happens next.

Anti-Patterns

Anti-Pattern 1: The Feature Tour

Before: You show every feature your product has because "they might find something they like." You demonstrate workflow automation, analytics, reporting, integrations, mobile app, admin dashboard, and API capabilities. By the end, the prospect is overwhelmed and remembers nothing.

Problem: More features = less retention. If you show 12 things, they remember zero. If you show 3 things, they remember three.

After: You identify the 3 features that map to their stated priorities and demonstrate only those. You cut everything else. If they ask about a feature you didn't show, you say: "That's a great capability, and we have it — I focused on the priorities we discussed, but we can dive into that in the next session if it's relevant."

Why it works: Focused demonstrations are more persuasive.

Anti-Pattern 2: Skipping Discovery

Before: You haven't spoken to the prospect about their priorities or challenges. You show up to the demo and run a standard product tour. Halfway through, they say, "Actually, we don't care about that feature. The thing we really need is X." You've wasted 20 minutes on irrelevant features.

Problem: Generic demos without discovery context feel like sales demos, not consultative demos.

After: Before the demo, you send a pre-demo email: "I want to make sure we focus on what matters to you. Are your top priorities [3 hypotheses based on company size/industry]? Or is there something else we should focus on?" Or you spend the first 5 minutes of the demo clarifying priorities before showing anything.

Why it works: You're customizing based on their actual priorities, not assumptions.

Anti-Pattern 3: Demo Running Over Time

Before: You plan for 30 minutes but the demo goes 50 minutes because you showed too many features and took every tangent question. The prospect has another meeting in 5 minutes and is clearly distracted. They leave without committing to next steps.

Problem: Demos that run over signal poor preparation and disrespect for the prospect's time.

After: You have a hard time budget: opening (2 min), 3 features (25 min, with checkpoints), close (3 min). If a question would take more than 2 minutes to answer, you park it: "Great question — that's worth a deep dive. Let me note that down and we can cover it in the technical session." You end at 29 minutes, leaving room for them to schedule next steps without rushing.

Why it works: You respect their time and they respect your professionalism.

Anti-Pattern 4: Ignoring Engagement Signals

Before: A prospect nods along through the first two features but then their energy drops. They start looking at their phone. You push through and show the remaining three features anyway because that's your script.

Problem: You're not reading the room. The prospect has checked out.

After: You notice the engagement drop and you adjust: "I'm sensing this isn't hitting as much as the first couple of things — should we focus on something specific, or do you have questions about what we've covered so far?" You give them control of the direction instead of bulldozing through your script.

Why it works: Adaptive demos that respond to engagement signals are more effective.

Anti-Pattern 5: Competitive Defensiveness

Before: Prospect mentions they're evaluating Competitor X. You spend 10 minutes explaining why Competitor X is inferior and why you're better. Prospect feels attacked and loses trust.

Problem: Defensive positioning feels insecure and makes the prospect uncomfortable.

After: Prospect mentions they're evaluating Competitor X. You say: "They're a strong tool in this space. The main difference is how we think about [specific capability]. We focus on [your philosophy], which works well for teams that [your target profile]. What's most important to your evaluation criteria?" You acknowledge the competitor's strength while positioning your approach, then let the prospect decide.

Why it works: You're confident enough not to trash competitors, which makes you more credible.

Output Format

A complete demo script generates:

DEMO SCRIPT: [Prospect Name] [Prospect Role]
Meeting Length: 30 minutes
Primary Audience: [Role]
Secondary Audience: [Other roles, if applicable]
Context: [Discovery call follow-up / Competitive evaluation / POC kickoff]

PROSPECT PRIORITIES (Validated)
1. [Priority 1]: [Specific statement they made]
2. [Priority 2]: [Specific statement they made]
3. [Priority 3]: [Specific statement they made]

OPENING HOOK (2-3 minutes)
[Full script of opening, including pain statement and reframe]

FEATURE SEQUENCE

Feature 1: [Feature Name]
- Pain/Context: [How it addresses their priority]
- Click Path: [Step-by-step walkthrough]
- Business Outcome: [Why it matters to them]
- Checkpoint: [Engagement question]
- Anticipated Question: [If applicable]

[Repeat for Features 2-3 (or 5)]

COMPETITIVE POSITIONING (if applicable)
[Integrated talking points where differentiation appears]

CLOSING (3-5 minutes)
[Summary of 2-3 key features + specific next step proposal]

TIME BUDGET
Opening: 2 min
Feature 1: 8 min (including checkpoint)
Feature 2: 8 min (including checkpoint)
Feature 3: 8 min (including checkpoint)
Closing: 4 min
Total: 30 min

ANTICIPATED QUESTIONS & RESPONSES
[Question]: [Prepared response]

TALKING POINTS (if multi-persona)
Executive Perspective: [2-3 talking points]
Practitioner Perspective: [2-3 talking points]
Technical/IT Perspective: [2-3 talking points]

Task-Specific Questions

For Role-Specific Demos

1. What is the title/role of the primary audience, and what does that person care about most (business metrics, ease of use, technical capability, cost)?
2. Are there secondary audiences in the demo, and what do they care about? (If a VP of Sales is bringing a manager and an end-user, each cares about different things)
3. What business outcome would matter most to each role?

For Competitive Evaluation Demos

1. Which competitors are they evaluating, and what is each competitor's primary strength?
2. What is your competitive advantage over the top 1-2 competitors?
3. Where is the prospect's decision likely to be made (on feature capability, ease of use, integrations, cost, vendor reliability)?

For Proof-of-Concept or Trial Demos

1. What is the specific use case or workflow they want to test?
2. What metrics would define a successful proof-of-concept (time savings, accuracy improvement, adoption rate)?
3. What is the timeline for the POC, and what does implementation look like?

Quality Checklist

Before delivering a demo, verify:

1. Opening hook references a specific pain point or priority the prospect mentioned or validated. (Not "Let me show you our platform" but "You mentioned that your reps struggle with forecast accuracy — let me show you how we address that")

2. You are showing 3-5 features, maximum. (Count the features you plan to demonstrate. If it's more than 5, cut something.)

3. Each feature has a clear pain-to-outcome connection. (You can articulate why this feature matters to their specific business, not just why it's cool)

4. Checkpoints are built in every 5-7 minutes. (You have 3-4 places in the demo where you ask "Does this match what you need?" or "How do you handle this today?")

5. Time budget is realistic and accounts for talking, checkpoints, and questions. (Your detailed walkthrough should fit within the allocated time, leaving room for prospect engagement)

6. Closing includes a specific, proposed next step, not an open question. (Not "What do you think?" but "The next step would be a technical review with your team on integrations. Can we get that on the calendar for next week?")

7. If demoing competitively, you have 2-3 natural positioning points woven in, not a "vs." slide. (You've identified moments where differentiation appears naturally, not forced)

8. If multi-persona, you have parallel talking points for different roles. (Executive hears about ROI and business impact; practitioner hears about ease of use; IT hears about security and integrations)

Related Skills

When building and delivering demo scripts, you'll often need:

• Discovery — How to gather the intelligence that informs what to show in the demo
• Competitive Intelligence — How to understand competitor positioning and prepare differentiation
• Meeting Prep — How to prepare beyond the script (logistics, tech setup, anticipating objections)
• Objection Handling — How to respond when a prospect raises concerns during the demo

Example Prompts

1. Role-Specific Demo for Executive "I have a 30-minute demo with a VP of Sales tomorrow at a mid-market SaaS company. They care about coaching capability and forecast visibility. Their team is 25 people and they're evaluating three platforms. The main objection they've mentioned is implementation time. Build a demo script that leads with coaching and forecast, addresses implementation, and closes with a strong next step."

Expected output: Demo script that opens with a statistic about coaching impact, shows 3 features (coaching capability, forecast dashboard, implementation tooling), weaves in a soft competitive angle about implementation speed, and closes with a specific technical deep-dive proposal.

2. Proof-of-Concept Kickoff Demo "I'm demoing to an end-user team (10-15 reps) who are evaluating our product for a 30-day trial. They want to test our real-time call guidance capability. There will be a manager and a rep in the call. Build a demo that's both executive-friendly and practical for the reps to understand how they'd use this daily."

Expected output: Demo script with opening that addresses manager's ROI concerns and rep's ease-of-use concerns. Feature sequence shows the guidance system in action on a real call scenario. Closing proposes specific trial timeline and metrics to track during POC.

3. Competitive Evaluation Demo Against Gong "I'm demoing against Gong. They're evaluating for a sales coaching program. We're different because our approach is real-time coaching during the call, while Gong is post-call analysis. I have 45 minutes with the VP of Sales. Build a script that positions our real-time philosophy as a strategic advantage without trashing Gong."

Expected output: Demo script that opens by acknowledging Gong's strength in post-call analysis, then pivots to real-time coaching philosophy. Feature sequence shows real-time guidance in action. Competitive positioning is woven naturally (e.g., "Our customers tell us behavior changes during the call when they get real-time coaching, vs. after the call when it's too late to adjust"). Closing proposes trial with specific metrics around coaching timing.

4. Complex Multi-Persona Demo "I'm demoing to 4 people: VP of Sales (cares about coaching and ROI), Sales Operations Manager (cares about integrations and ease of setup), IT Security officer (cares about data security and compliance), and a frontline rep (cares about ease of use). All on one 45-minute call. Help me build a script that addresses all four perspectives without feeling fragmented."

Expected output: Demo script that opens with an outcome that all four care about (improved sales effectiveness). Feature sequence is structured with: (1) coaching capability with ROI numbers (for VP), (2) integration walkthrough showing Salesforce integration (for ops), (3) security/compliance in feature setup (for IT), (4) ease-of-use demonstration (for rep). Checkpoints are designed to let each role engage with their concern. Closing proposes a post-demo summary call with IT to address security questions separately.