---
name: demo-design-saas
slug: demo-design-saas
description: This skill should be used when the user asks to "design a SaaS demo", "build a product demo", "structure a demo call", "improve demo conversion", "create a demo script", "design the demo experience", "build a demo flow", "improve our demo", "structure a 30-minute demo", or any variation of designing, structuring, or improving the product demo for B2B SaaS sales.
category: general
---

# Demo Design for SaaS

A demo is not a product tour. It's a conversation about how your product solves the prospect's specific problem. The best demos show 20% of the product. The worst demos show 100%. A prospect who sees 3 features that solve their exact problem buys. A prospect who sees 40 features without context feels overwhelmed and says "let me think about it."

The principle: the demo is tailored to the discovery. If discovery surfaced 2 key pain points, the demo shows 2 solutions. Not 10 features. Not a pre-built slide deck that covers everything. Two things, shown deeply, connected to their specific situation.

## The Demo Structure

### The 30-minute demo framework

| Phase | Minutes | Purpose | Who talks |
|-------|---------|---------|-----------|
| 1. Recap and confirm | 0-3 | Summarize what you learned in discovery. Confirm priorities haven't changed | Rep 70%, prospect 30% |
| 2. Agenda set | 3-5 | Tell them what you'll show and why. Set expectations | Rep 90% |
| 3. Core demo (pain point 1) | 5-15 | Show how the product solves their #1 pain. Their workflow, their data, their scenario | Rep 60%, prospect 40% |
| 4. Core demo (pain point 2) | 15-22 | Show the second capability. Different angle, different value | Rep 60%, prospect 40% |
| 5. Q&A | 22-26 | Answer questions that came up during the demo | Prospect-led |
| 6. Close | 26-30 | Propose next steps. Confirm mutual interest. Schedule follow-up | Rep 60%, prospect 40% |

### Phase-by-phase guide

**Phase 1: Recap and confirm (3 minutes)**

```
"Before I show you the product, I want to make sure I have
the right focus. From our last conversation, the two things
you care most about are:

1. [Pain point 1 in their words]
2. [Pain point 2 in their words]

Is that still right? Anything else that's come up since we
talked?"
```

**Recap rules:**
- Summarize their pain in their words, not your marketing language. They said "our SDRs waste half their day on research." Don't say "manual prospecting inefficiency." Say what they said
- Ask if priorities changed. Between discovery and demo, a week may have passed. New priorities may have emerged. A 10-second check prevents showing the wrong thing for 25 minutes
- If they add a new pain point, adjust the demo on the fly. Show the new priority instead of the pre-planned item. Flexibility > script

**Phase 2: Agenda set (2 minutes)**

```
"Great. Here's what I'll show you today:

First, I'll walk through how we handle [pain point 1]. I'll
use a scenario similar to what you described.

Then, I'll show you how [pain point 2] works and how it
connects to [pain point 1].

I'll leave time for questions at the end, but feel free to
stop me anytime if something doesn't make sense or if you
want to go deeper.

Sound good?"
```

**Agenda rules:**
- Tell them the plan. Demos without an agenda feel like aimless product tours. "First X, then Y, then questions" gives them a mental map
- "Feel free to stop me anytime" is critical. It gives the prospect permission to interrupt. Interruptions during a demo are positive signals. They mean the prospect is engaged. Welcome them
- Two items only. "I'll show you 6 things" means you'll rush through all 6. Two things, shown deeply, with space for questions

**Phase 3-4: Core demo (17 minutes total)**

This is the product in action. Two pain points, each getting 7-10 minutes of focused demonstration.

**Demo showing rules:**

| Rule | Why |
|------|-----|
| Show their workflow, not your feature set | "Here's how your SDR team would do this" is 10x more impactful than "Here's our sequencing feature" |
| Use their data if possible | Demo with their company name, their industry, their prospect type. Not "Acme Corp" from a generic sandbox |
| Start with the outcome, then show the how | "This is what your team's dashboard would look like after a week. Here's how it gets there" (outcome first) |
| 3 clicks, not 30 | Show the shortest path to value. Don't navigate through settings, admin panels, and edge cases. Show the happy path |
| Pause after each feature and ask | "Does this address what you described about [pain point]?" Pauses create dialogue. Monologues create glazed eyes |
| Show the integration (if relevant) | "This data flows directly into your HubSpot. No CSV export" If integration is a decision criterion, show it working |

**Phase 5: Q&A (4 minutes)**

Let the prospect drive. Their questions reveal what they care about most and what objections they're forming.

**Q&A rules:**
- Don't rush through Q&A to get to the close. If questions run long, that's a good sign. Extend Q&A and shorten the close
- "I don't know, but I'll find out by tomorrow" is better than a guess. Wrong answers create trust debt. Honest uncertainty maintains trust
- If the question is about a feature you don't have, be honest: "We don't do that today. Here's how teams work around it." Then pivot: "But let me show you what we do for [related thing]"

**Phase 6: Close (4 minutes)**

```
"Based on what you've seen, does this feel like it could
solve [pain point 1] and [pain point 2]?

If so, here's what I'd suggest for next steps:
- [Specific next step with specific date]
  Examples:
  - "I'll send over pricing options by Friday"
  - "Let's set up a technical deep-dive with your engineering
    lead next week"
  - "Can I put together a pilot plan for your team to test
    for 2 weeks?"

Who else on your team should see this before you can move
forward?"
```

**Close rules:**
- Ask for a reaction before proposing next steps. "Does this feel right?" gauges interest. If they say "not really," you learn something. If they say "yes, this is great," you have momentum for the next step
- Propose a specific next step with a date. Not "let's stay in touch." A specific action, assigned to a specific person, on a specific date
- Always ask who else needs to see it. This identifies the buying committee members you haven't met yet and creates the opening for multi-threading

---

## Demo Tailoring by Audience

### Demo adjustments by role in the room

| Audience | Demo emphasis | Tone | What to show | What to skip |
|----------|-------------|------|-------------|-------------|
| Champion (Manager/Director) | Day-to-day workflow. How their team uses it | Tactical. "Here's what your Monday morning looks like" | The daily workflow. The specific screens they'd use | Admin settings, pricing, implementation timeline |
| Economic buyer (VP/C-level) | Business outcome. ROI. Strategic value | Strategic. Numbers. Impact | Dashboard/reporting view. ROI calculation. Peer results | Step-by-step feature walkthrough. They don't care how it works internally |
| Technical evaluator (Eng/IT/Ops) | Architecture. Integration. Security. Data model | Technical. Specific. Detailed | API docs, integration flow, data schema, security overview | Sales-focused value props. Business case. They want specs |
| End user (IC/SDR/rep) | Ease of use. Speed. How it makes their life easier | Practical. Hands-on. "Try this" | The product in action. Let them click buttons. Guided trial | Strategy, ROI, architecture |
| Mixed audience (multiple roles) | Lead with outcome, then briefly show the path | Balanced. Start strategic, go tactical, offer technical | 60% champion view, 30% EB view, 10% technical acknowledge | Don't try to satisfy everyone deeply. Offer follow-up deep-dives per role |

### Multi-stakeholder demo rules

- **Know who's in the room before the demo starts.** Ask the champion: "Who will be joining? What are their roles and what do they care about?" Adjust the demo accordingly
- **Open with the EB's priority, not the champion's.** If the VP is on the call, the first 5 minutes should address their concern (ROI, strategic fit). Then go into the champion's workflow. The EB won't stay for 30 minutes if the first 10 don't speak to them
- **Address each person by name during the demo.** "Sarah, this is the part I think matters most for your team." "Mark, this is how the integration with your Salesforce instance would work." Name-drops show you prepared for each person
- **Offer role-specific follow-ups.** "Mark, I can send you the API documentation afterward. Sarah, I'll include the ROI calculator in the follow-up." Tailored follow-ups per role

---

## Demo Preparation

### Pre-demo checklist (15-20 minutes before the demo)

- [ ] Discovery notes reviewed. Top 2 pain points identified
- [ ] Demo environment loaded with relevant data (their industry, their company type, their use case)
- [ ] Demo script adjusted for this specific prospect (not the generic flow)
- [ ] Attendee list confirmed with champion. Know who's in the room
- [ ] Integration demo ready (if integration is a decision criterion)
- [ ] Competitor positioning ready (if they mentioned evaluating alternatives)
- [ ] Pricing range ready to share (if likely to come up)
- [ ] Backup plan for technical issues (screenshots, recorded demo as fallback)
- [ ] Calendar link or time slots ready for next-step proposal

### Demo environment rules

- **Custom data > generic data.** A demo with their company name, their industry's terminology, and their workflow produces 2x the "aha" moments as a generic demo. Invest 10 minutes in customization
- **Pre-load the demo environment before the call.** Don't spend the first 3 minutes logging in, navigating to the right screen, and loading data. Have the first screen ready when you share
- **Have a backup.** Internet drops. Demo environments crash. Integrations fail live. Have screenshots or a recorded backup ready. "Let me show you this recorded walkthrough while we sort out the connection" is professional. A 5-minute awkward silence is not

---

## Demo Mistakes

### The 7 deadly demo mistakes

| Mistake | What it looks like | Impact | Fix |
|---------|-------------------|--------|-----|
| Feature tour | "And this button does X. And this tab shows Y. And over here we have Z" | Prospect drowns in features. Can't identify what matters for them | Show 2-3 features that solve their stated pain. Not the feature catalog |
| No discovery before demo | "I'll just show you everything and you tell me what's interesting" | Generic demo. No tailoring. Low conversion | Always run discovery before demo. If combined, spend the first 10 minutes on discovery before showing anything |
| Showing admin/settings | "Let me show you the admin panel and all the configuration options" | Boring. Irrelevant to most audiences. Eats clock | Show the user experience, not the admin experience. Save admin for technical deep-dive |
| Monologue demo | Rep talks for 25 minutes straight. Prospect is silent | No engagement. No feedback. No idea if the prospect cares | Pause every 3-5 minutes and ask: "Does this address what you described?" |
| Showing broken things | Feature fails during demo. Integration throws an error | Trust drops. "If it breaks in a demo, what happens in production?" | Test every feature path before the call. Have a backup ready |
| Ignoring questions | Prospect asks a question. Rep says "I'll get to that later" | Prospect feels unheard. Frustration builds. Trust drops | Answer the question now. Then return to the agenda. Their question > your script |
| No close | Demo ends with "great, let me know if you have any questions!" | No next step. The deal enters limbo. Follow-up becomes "just checking in" | Always propose a specific next step with a date |

---

## Demo Types

### Discovery + demo combo (45 minutes)

For prospects who requested a demo and won't sit for a separate discovery call.

```
Minutes 0-12: Discovery (compressed)
  - 3 min: agenda + what brought them here
  - 7 min: current state + pain + priorities
  - 2 min: confirm what to show

Minutes 12-35: Tailored demo
  - Show the 2-3 things that map to their stated pain
  - Pause for questions throughout

Minutes 35-42: Q&A

Minutes 42-45: Close + next steps
```

**Combo rules:**
- Don't skip discovery. Even in a combo call, spend 10-12 minutes understanding their situation before showing anything. The demo quality depends on it
- Be explicit about the format: "I'd love to spend the first 10 minutes understanding your situation, then tailor the demo to what matters most. Sound good?"

### Technical deep-dive (60 minutes)

For technical evaluators (engineering, IT, security) after the initial demo.

```
Minutes 0-5: Recap from initial demo. Confirm technical priorities

Minutes 5-30: Architecture walkthrough
  - Data model and schema
  - API overview + live API call
  - Integration flow with their stack
  - Security: SOC 2, encryption, data residency

Minutes 30-50: Hands-on
  - Sandbox access for the technical evaluator
  - Walk through a real integration setup
  - Test edge cases they're concerned about

Minutes 50-55: Q&A (technical)

Minutes 55-60: Next steps (POC, security review, procurement)
```

### Executive briefing (15-20 minutes)

For economic buyers who won't sit through a full demo.

```
Minutes 0-2: Context. "Your team has been evaluating us for [problem]"
Minutes 2-8: Business case. ROI. Peer results. Strategic alignment
Minutes 8-15: Product overview (dashboard/reporting view only. No feature walkthrough)
Minutes 15-18: Q&A
Minutes 18-20: Decision support: "What do you need to feel confident moving forward?"
```

**Executive briefing rules:**
- No feature walkthrough. Show the outcome (dashboard, report, result), not the process
- Lead with the business case: "Teams like yours see [X] improvement in [metric]. Here's how"
- 20 minutes max. Executives will give you 20 minutes. Not 45. Design the entire experience for that window

---

## Measurement

| Metric | Definition | Target | Frequency |
|--------|-----------|--------|-----------|
| Demo-to-next-step rate | % of demos where a next step was booked on the call | > 70% | Weekly |
| Demo-to-opportunity rate | % of demos that result in an opportunity | > 50% | Monthly |
| Demo-to-closed-won rate | % of demos that eventually close | 15-25% | Quarterly |
| Average demo duration | How long demos actually run | 28-35 min (for 30-min demos) | Monthly |
| Prospect talk ratio during demo | % of time the prospect speaks | 35-45% | Per demo (via Gong/Chorus) |
| Questions asked by prospect during demo | Number of questions | > 3 (engagement signal) | Per demo |
| Next-meeting attendee expansion | % of next meetings that include a new stakeholder | > 40% | Monthly |
| Demo NPS or feedback | Post-demo survey score | > 4.0/5.0 | Per demo (optional) |

---

## Anti-Pattern Check

- Feature tour disguised as a demo. 30 features in 30 minutes. No tailoring. No questions. The prospect leaves knowing everything the product does and nothing about how it solves their problem. Show 2-3 features mapped to their pain, not the entire product
- No discovery before the demo. "Just show me the product" leads to a generic demo that shows everything and resonates with nothing. Even 10 minutes of compressed discovery dramatically improves demo relevance
- Rep talks 90% of the time. The demo is a monologue. The prospect is passive. No engagement = no buy-in = no next step. Pause every 3-5 minutes. Ask questions. The prospect should talk 35-45% of the time
- Generic demo environment. "Here's the Acme Corp account in our sandbox." The prospect's company is not Acme Corp. Spend 10 minutes customizing the demo with their company type, their industry terms, their workflow. It's the difference between "interesting" and "this is exactly what we need"
- Showing admin panels and configuration. The economic buyer doesn't care about settings. The champion doesn't care about API configuration. Show the user experience for most audiences. Save admin for the technical deep-dive
- No close at the end. "Great demo! Let me know if you have questions." This is not a close. This is a dead end. Propose a specific next step with a specific date and specific attendees
- Ignoring live questions. "Great question. I'll cover that later." Later never comes. The prospect's question was a buying signal. Answer it now. Their question > your script
- Same demo for every audience. The VP sees the same demo as the SDR Manager as the Engineer. Each role needs a different emphasis, different depth, and different outcome framing. Tailor per audience