Running a great demo
Discovery first, demo second
By the wpdailylive editorial team · Part of Go-to-market strategy, the complete guide
Key takeaways
- Discovery first: Spend five minutes confirming the problem before showing anything.
- Three workflows: Show only what solves their stated problem, not every feature.
- Confirm the agenda: Agree time and goals at the start.
- Handle questions: Leave room for objections and answer them directly.
- Book the next step: End with a specific next step and a date.
- 01Confirm agenda and time30 minutes, outcome agreed.
- 02DiscoveryTheir process, pain and cost.
- 03Show the fixTwo or three workflows using their language.
- 04Handle questionsWrite down objections.
- 05Agree next stepCalendar invite before you hang up.
- TRIGGERMinute 0: agenda and goal
- STEPMinutes 2–10: discovery
- STEPMinutes 10–22: show 3 workflows
- STEPMinutes 22–28: questions
- GOALMinutes 28–30: book next step
Discovery
Demo
Questions
Next step
Key terms
DiscoveryLearning the buyer’s situation before pitching.
Next stepA specific, dated action both sides agree.
A 30-minute demo agenda
| MINUTES | SECTION |
|---|---|
| 0–3 | Agenda and goals |
| 3–10 | Discovery: confirm problems and priorities |
| 10–22 | Show 2–3 workflows that solve those problems |
| 22–27 | Questions and objections |
| 27–30 | Agree next step with a date |
Demo hygiene
- •Use realistic sample data, ideally from their industry
- •Close notifications and unrelated tabs
- •Have a backup recording in case of tech issues
- •Send a recap within an hour with the next step
Discovery call questions before the demo
- 1.Walk me through how you handle this today.
- 2.What’s the most frustrating part?
- 3.What have you tried already?
- 4.What would a great outcome look like?
- 5.Who else should see the demo?
SaaS demo script outline
| MINUTE | SECTION | TIP |
|---|---|---|
| 0–3 | Recap their goals and agree the agenda | Use their words |
| 3–8 | Show the outcome first | The finished report, not the settings |
| 8–20 | Walk through their top 2–3 use cases | Skip features they don’t need |
| 20–25 | Questions and objections | Ask “what would stop you?” |
| 25–30 | Next steps | Book the follow-up before you hang up |
Sales demo tips
- •Use a demo account with realistic data from their industry
- •Pause every few minutes to ask how it compares with today
- •Stop showing once you’ve proved the point
- •Send a short recap and recording within an hour
Common mistakes to avoid
✕ Feature toursFocus on their use cases.
✕ Demo without discoveryAsk first, show second.
✕ No next stepBook it before hanging up.
PEOPLE ALSO ASK
How do I give a good sales demo?
Run discovery first, recap their goals, show the outcome, cover only their key use cases, handle objections and agree next steps.
What should a demo script include?
Agenda and goals, the outcome, two or three use cases, questions and objections, and next steps.
What are good discovery call questions?
How they handle it today, what’s frustrating, what they’ve tried, what success looks like and who else should be involved.
How long should a sales demo be?
About 30 minutes, with most of the time on the prospect’s use cases.
Should I send a demo recording?
Yes, with a short recap so the prospect can share it with colleagues.
Tools we recommend for this stage
Some links are partner links: we may earn a commission at no cost to you. It never changes what we recommend. How we make money


















