---
name: demo-script-builder
description: Build structured, value-driven product demonstrations with scenario-based narratives, demo environment preparation, audience-specific adaptations, conversion tracking, and post-demo follow-up sequences. Use when creating demo scripts for new products, personalizing demos for specific prospects, preparing demo environments, coaching reps on demo delivery, or analyzing demo conversion rates. Triggers on phrases like "demo script", "product demo", "sales demo", "demo presentation", "demo planning", "demo narrative", "demo environment", "interactive demo", "demo conversion rate", "personalized demo", "demo follow-up", "demo best practices".
---

# Demo Script Builder

Create structured product demonstrations that consistently convert prospects by aligning demo narratives to buyer needs, preparing realistic demo data, and driving clear next steps.

## Demo Planning & Context Gathering

```
PRE-DEMO PREPARATION CHECKLIST
═══════════════════════════════════════════════════════════

Step 1 — Prospect Intelligence (30 minutes):
  → Discovery call notes review: Top 3 pain points, quantified impact, timeline
  → Company research: Industry, size, revenue, tech stack, recent news
  → Stakeholder mapping: Who will attend? What are their roles and priorities?
     - Economic buyer (CFO/VP): Cares about ROI, total cost, risk
     - Technical evaluator (CTO/IT): Cares about integration, security, architecture
     - End user (Manager/IC): Cares about usability, time savings, workflow fit
     - Champion (Director): Cares about success metrics, internal buy-in
  → Competitor intelligence: Who else are they evaluating? What's their perception?
  → Buying stage: Early evaluation (educational demo) vs. Final selection (comparative demo)
  → Must-cover topics: Topics champion says "they really care about"

Step 2 — Demo Objective Setting (10 minutes):
  Primary objective (ONE):
    → Early stage: "Get buy-in to move to technical deep-dive"
    → Mid stage: "Validate solution fit and build executive sponsor"
    → Late stage: "Confirm value and drive toward proposal/signature"
  Secondary objective:
    → Identify additional stakeholders to engage
    → Uncover budget and timeline specifics
    → Address specific competitive concerns
  Success criteria:
    → "Prospect confirms [X feature] solves [Y pain]"
    → "Prospect names economic buyer and agrees to intro"
    → "Prospect commits to [specific next step] by [date]"

Step 3 — Demo Environment Setup (20 minutes):
  → Demo instance preparation:
     - Load sample data matching prospect's industry and scale
     - Use prospect's company name in demo (personalization effect)
     - Pre-configure workflows relevant to prospect's use case
     - Clear any generic/sample content not relevant to prospect
  → Test all features:
     - Click through entire demo flow (no dead links, broken features)
     - Test on prospect's browser/device if known (Chrome, Safari, mobile)
     - Verify screen sharing works (test 10 minutes before call)
     - Prepare backup: Screen recording of demo in case of technical issues
  → Tools:
     - DemoTools / Navattic: Isolated demo environment with custom data — $500–$5,000/year
     - Your own sandbox: Free, but requires manual data setup
     - BrowserIncognito mode: Clean slate (no personal data visible)

Step 4 — Script Finalization (15 minutes):
  → Write talking points (not word-for-word script — natural delivery):
     - Opening hook (personalized to prospect)
     - 3 use case scenarios (aligned to prospect's top 3 pains)
     - Transition phrases between scenarios
     - Check-in questions after each scenario
     - ROI summary with prospect-specific numbers
     - Next step proposal
  → Time allocation:
     - Opening: 5 minutes
     - Problem restatement: 5 minutes
     - Demo (3 scenarios): 25–30 minutes
     - Proof and validation: 5–10 minutes
     - Next steps and Q&A: 5–10 minutes
     - Total: 45–60 minutes (leave 10-minute buffer)
  → Practice: Run through demo once (self-record, check timing, refine transitions)
```

## Demo Script Framework

```
DEMO SCRIPT TEMPLATE (45–60 minutes)
═══════════════════════════════════════════════════════════

PHASE 1 — Opening & Alignment (5 minutes):
  Opening (personalized, not generic):
    "Hi [Name], great to meet everyone. For those I haven't met, I'm [Name],
    [Title] at [Company]. I'm excited to show you how we can help [Company]
    solve [specific pain from discovery]."

  Agenda confirmation:
    "Here's what I'd like to cover today:
    1. Quick recap of the challenges you shared
    2. Walk through 3 scenarios that match your situation
    3. Show you the results [similar company] achieved
    4. Answer your questions and agree on next steps
    We have about 45 minutes — does that work?"

  Set expectations:
    "I want this to be interactive — please interrupt me anytime if something
    isn't clear or if I should go deeper on something."

  Context check:
    "Before we dive in — from our last conversation, your top priorities are
    [priority 1], [priority 2], and [priority 3]. Is that still accurate,
    or has anything shifted?"

PHASE 2 — Problem Statement (5 minutes):
  Restate challenges (shows you listened, builds credibility):
    "From what you've shared, your team is dealing with:
    → [Pain 1]: [Specific detail] — costing approximately [quantified impact]
    → [Pain 2]: [Specific detail] — impacting [business outcome]
    → [Pain 3]: [Specific detail] — creating [operational risk]
    Did I capture that accurately?"

  Cost of inaction (creates urgency):
    "Based on our work with similar companies, organizations that don't address
    [pain category] typically lose [quantified cost: $200K/year, 15 hours/week, 25% errors]
    over the next 12 months. That's why I know timing matters."

  Transition to solution:
    "Let me show you exactly how [Product] addresses each of these."

PHASE 3 — Solution Demonstration (25–30 minutes):
  Scenario 1 — Primary Use Case (10 minutes):
    → Context: "Let me walk through how your team currently handles [process],
       and how [Product] changes that."
    → Before state: "Today, this likely involves [X steps], taking [Y time],
       with [Z pain points]."
    → Demo (live, not slides): Walk through the feature
       "Here's [Product] — notice how [key action] happens automatically here..."
       "Your team would [specific action] — and this is what you'd see..."
    → After state: "So instead of [X steps], it's [Y steps]. Instead of
       [Z time], it's [A time] — that's a [B%] improvement."
    → Check-in: "How does this compare to your current process?
       Does this feel like it would work for your team?"
    → Engagement read:
       If prospect nods/agrees: Continue
       If prospect looks confused: "Let me walk through that step again..."
       If prospect asks question: Answer, then continue

  Scenario 2 — Secondary Use Case (8 minutes):
    → Context: "You also mentioned [Pain 2] — let me show you how we handle that."
    → Demo: Live walkthrough
    → Result: Quantified benefit
    → Check-in: "Does this address the [specific concern] you raised?"

  Scenario 3 — Advanced Use Case (7 minutes):
    → Context: "One thing our customers love — [advanced feature that drives ROI]."
    → Demo: Live walkthrough
    → Result: "Teams using this feature see [quantified benefit: 30% more X, $Y saved]."
    → Check-in: "This isn't critical day one, but it's a key reason customers
       renew and expand."

  Demo delivery principles:
    → Show, don't tell: 80% live product, 20% slides/screens
    → 3 scenarios maximum (depth over breadth — don't rush)
    → Use prospect's language: "You mentioned [pain] — here's how we solve that"
    → Pause every 3–5 minutes: "Questions so far?" (keeps engagement)
    → Handle objections immediately: Don't defer — address on the spot
    → Avoid: Feature dumping, reading slides, ignoring prospect signals

PHASE 4 — Proof & Validation (5–10 minutes):
  Social proof (industry-specific):
    "[Similar company in same industry, same size] was in your exact situation:
    [Before state] → Implemented [Product] → [After state] in [timeframe].
    Here's their testimonial: '[Direct quote].'"

  ROI calculation (prospect-specific):
    "Based on what you've shared:
    → Current state: [X cost/hours per month]
    → With [Product]: [Y cost/hours per month]
    → Savings: [Z% reduction] = [$A,XXX per month] = [$B,XXX per year]
    → Payback period: [C months]
    This aligns with what [similar company] experienced in their first 90 days."

  Competitive differentiation (if competitor mentioned):
    "You mentioned you're also looking at [Competitor]. Here's where we differ:
    → [Competitor] does [X] well, but we [Y better]
    → [Competitor] charges [Z], but we include [additional value]
    → [Competitor] requires [long implementation], we go live in [shorter time]
    Here's a case study of a company that chose us over [Competitor]: [reference]."

  Risk mitigation:
    "I know implementation can be a concern. Here's what that looks like:
    → Week 1: Setup and data migration (our team handles this)
    → Week 2: Training (2 live sessions + recorded materials)
    → Week 3: Go-live with dedicated support
    → Average time to value: 14 days (not months)"

PHASE 5 — Next Steps & Close (5 minutes):
  Summary (3 key takeaways):
    "To recap, [Product] would help you:
    → [Result 1]: [Quantified benefit]
    → [Result 2]: [Quantified benefit]
    → [Result 3]: [Quantified benefit]"

  Alignment check:
    "Does this address the priorities you mentioned at the start?
    Is there anything we covered that resonated more than others?"

  Next step proposal (specific, not vague):
    "The next logical step is [specific action]:
    → [Technical deep-dive with your engineering team]
    → [Executive briefing with [Economic Buyer]]
    → [Pilot program — 30 days, full access]
    I'll send a calendar invite for [date/time]. Does that work for everyone?"

  Open floor:
    "Before we wrap, is there anything else you'd like to see,
    or any questions I haven't addressed?"

  Calendar invite: Send BEFORE ending the call (not after)
```

## Demo Conversion Tracking & Benchmarks

```
DEMO PERFORMANCE METRICS
═══════════════════════════════════════════════════════════

DEMO CONVERSION FUNNEL:
  ┌────────────────────────────────┬──────────┬──────────────────┐
  │ Stage                          │ Target   │ Notes            │
  ├────────────────────────────────┼──────────┼──────────────────┤
  │ Meetings booked → Demos shown  │ 70%      │ 30% no-show rate │
  │ Demo → Next step committed     │ 50%      │ Key conversion   │
  │ Next step → Proposal sent      │ 60%      │                  │
  │ Proposal → Closed-won          │ 35%      │                  │
  │ Overall: Meeting → Closed-won  │ 8.6%     │ Benchmark        │
  └────────────────────────────────┴──────────┴──────────────────┘

DEMO QUALITY SCORECARD:
  → Rep demo score (self-assessment + manager review):
     - Opening personalization: 1–5
     - Problem alignment: 1–5
     - Demo relevance (not generic): 1–5
     - Engagement level (prospect talking): 1–5
     - Objection handling: 1–5
     - Clear next steps: 1–5
     - Total: ___ / 30
  → Target: 25+/30 for demos that convert >50%
  → Track: Correlate demo scores with conversion rates monthly

DEMO CONVERSION BY AUDIENCE TYPE:
  ┌────────────────────┬────────────┬────────────┬──────────────────┐
  │ Audience           │ Demo Length│ Next Step  │ Win Rate Post    │
  │ Type               │            │ Commitment │ Demo             │
  ├────────────────────┼────────────┼────────────┼──────────────────┤
  │ Technical eval     │ 45–60 min  │ 55%        │ 30%              │
  │ Executive briefing │ 20–30 min  │ 40%        │ 25%              │
  │ Mixed committee    │ 45–60 min  │ 45%        │ 35%              │
  │ Champion only      │ 30–45 min  │ 50%        │ 20%              │
  │ Multi-stakeholder  │ 60 min     │ 60%        │ 40%              │
  └────────────────────┴────────────┴────────────┴──────────────────┘
  → Multi-stakeholder demos have highest conversion (but hardest to schedule)
  → Executive-only demos need to be shorter and outcome-focused
  → Champion-only demos have lowest win rate (need economic buyer engagement)
```

## Post-Demo Follow-Up

```
POST-DEMO FOLLOW-UP SEQUENCE (5 touches over 7 days)
═══════════════════════════════════════════════════════════

Touch 1 — Within 2 hours (Email):
  Subject: "Recap: [Product] demo for [Company]"
  Body:
    "Hi [Name], great conversation today. Here's what we covered:
    → [Topic 1]: [Key takeaway + quantified benefit]
    → [Topic 2]: [Key takeaway + quantified benefit]
    → [Topic 3]: [Key takeaway + quantified benefit]
    Next steps we agreed on:
    → [Action 1]: [Owner] by [Date]
    → [Action 2]: [Owner] by [Date]
    I've attached [relevant resource: case study, ROI calculator, pricing].
    Calendar invite for [next meeting] is sent.
    Best, [Name]"
  Expected response: Acknowledgment, additional questions

Touch 2 — Within 24 hours (LinkedIn or phone):
  "Hi [Name], just wanted to make sure you got the recap and resources
  from our demo. Did your team have any questions I can address?"
  Purpose: Stay top-of-mind, surface objections early

Touch 3 — Day 3 (Value-add email):
  Subject: "[Relevant resource] — thought of our conversation"
  Body:
    "Hi [Name], [relevant case study / industry report / customer testimonial]
    that aligns with what we discussed on [topic].
    [Link + 2-sentence summary of why it's relevant]
    Looking forward to [next step] on [date]."
  Purpose: Reinforce value without asking for anything

Touch 4 — Day 5 (Check-in call):
  "Hi [Name], checking in on [next step]. Has your team had a chance
  to review [resource/demo recap]? Any questions I can help with?"
  Purpose: Surface blockers, maintain momentum

Touch 5 — Day 7 (Escalation, if no progress):
  If next step is stalled:
  "Hi [Name], I want to make sure we're not missing anything.
  Is [next step] still on track, or has the priority shifted?
  Happy to adjust timeline or approach based on what makes sense for you."
  Purpose: Get honest status, either re-engage or disqualify
```

## Edge Cases

- **Technical audience** (engineers, IT, architects):
  → Demo length: 60–90 minutes (they want depth)
  → Focus areas: API documentation, security architecture, integration capabilities, data privacy, uptime SLAs
  → Preparation: Have technical documentation ready (PDFs, architecture diagrams, API references)
  → Q&A: Expect 20+ minutes of technical questions — be prepared
  → Demo environment: Show sandbox with real API calls, not mock data
  → Follow-up: Send technical documentation packet within 2 hours
  → Red flag: If engineer raises technical objection, address immediately — don't promise "we'll look into it"

- **Executive audience** (CEO, CFO, VP):
  → Demo length: 15–20 minutes maximum (they value time)
  → Focus areas: Business outcomes, ROI, competitive advantage, risk mitigation
  → Structure: Problem → Solution (high-level) → Results (numbers) → Next steps
  → Skip: Feature details, technical deep-dives, click-through demos
  → Alternative: Use slides with product screenshots, not live demo
  → Must include: Competitive comparison, implementation timeline, pricing range
  → Closing: "What would you need to see to feel comfortable moving forward?"

- **Multi-stakeholder demo** (5+ attendees, mixed roles):
  → Pre-demo: Get attendee list and roles from champion (critical!)
  → Opening: Acknowledge each person and their role
  → Navigation: "For the technical team, I'll dive into [X]. For the leadership team, I'll highlight [Y]."
  → Balance: Address both technical and business concerns in each scenario
  → Engagement: Direct questions to specific roles ("[Name], as the technical lead, would this integration work for your stack?")
  → Follow-up: Send personalized follow-up to each stakeholder based on their role

- **Competitive demo** (prospect is comparing vendors):
  → Preparation: Know exactly which competitor(s) are in play
  → Differentiation: Lead with "Here's where we differ from [Competitor]"
  → Battle cards: Reference specific competitive advantages (prepare in advance)
  → Avoid: Bad-mouthing competitor — focus on your strengths instead
  → Social proof: Share case study of customer who chose you over same competitor
  → Objection prep: Pre-load responses to known competitive objections

- **Self-serve / product-led demo** (prospect exploring independently):
  → Interactive sandbox: Pre-configured demo environment (Navattic, DemoTools)
  → In-product guidance: Walkthrough tooltips, guided tours (WalkMe, UserGuiding)
  → Video demos: Library of use-case-specific demo videos (Loom, Vimeo)
  → Conversion tracking: Monitor sandbox engagement (pages visited, features clicked, time spent)
  → Follow-up trigger: Auto-trigger outreach when prospect reaches key demo milestone
  → Conversion target: 5–10% of sandbox visitors book demo with rep

- **Demo technical failure** (product crashes, screen share fails):
  → Backup plan: Pre-recorded demo video (always have one ready)
  → Response: Stay calm, apologize briefly, pivot to backup immediately
  → Never: Blame technology, spend >2 minutes fixing, reschedule without backup
  → Script: "It looks like we have a technical hiccup — I have a recorded version
     we can watch together, and I can walk through the key points."
  → Follow-up: Send live demo link + offer rescheduled live demo
  → Prevention: Test all tech 15 minutes before every demo