What you'll get
- 2 copy-ready blocks
- 5 min read
Discovery call vs demo is an order question, and the default order is discovery first. Not because process is sacred, but because a demo built on nothing answers questions nobody asked, shown to one person who may not matter, judged on first impressions. This page gives the default, the four real exceptions and what to say when the buyer wants the demo now.
Why discovery first, in one paragraph
A demo is an argument: your product, arranged to prove it solves their problem. Before discovery you do not know their problem, their words for it, their current workaround or who will judge the answer. Discovery buys the demo its script, its audience and its yardstick. Thirty minutes of listening routinely doubles what the same demo achieves, because the demo stops being a tour and becomes an answer. The agenda for those thirty minutes is the discovery call agenda and notes sheet.
The four cases where demo-first wins
1. Self-evident product The demo IS the explanation: a tool a user
can judge in two minutes. Delay looks evasive.
2. Technical gatekeeper An engineer must verify it is real before
anyone senior spends time. Demo to them is
discovery, if you treat their questions as data.
3. Competitive bake-off The format is fixed and refusing it removes
you. Fight for a 15-minute call first, then
comply.
4. A warm, educated buyer They used it at a previous company, or your
champion already sold it inside. Discovery
happened without you; skipping to the demo
respects that.If none of these four applies, the ask for a demo first is usually a politeness: easier to accept a screen share than a conversation. Treat it as the objection it is.
What to say when the buyer insists
"Happy to demo, and I will keep it short. Can I take 15 minutes first
to hear how this shows up at [company]? Otherwise I will show you the
generic tour, and you will have to translate it yourself. If after 15
minutes you want the full demo there and then, we do it on the spot."It concedes the demo, prices the skipped discovery honestly and offers a same-call bridge. Buyers who want a real answer usually take the 15 minutes; the ones who refuse have told you something about the account too.
The demo-first survival rules
When one of the four cases puts the demo first, protect the discovery that has not happened yet:
- Open with two questions anyway. "What made you want to look at this?" and "what would make this 30 minutes worth it?" turn the first five minutes into miniature discovery.
- Show one path, not the map. Pick the likeliest problem and demo that; a full tour is a feature reading.
- Treat every question as a notes field. What they ask is what they care about; it is the discovery arriving sideways.
- Close for the real conversation. The demo-first meeting's next step is discovery with the wider group, booked in the room.
The pre-call checks for either order are the demo prep checklist.
Worked example (illustrative, not a real company)
Pellow and Rook's IT manager emails Tessaro Analytics: "send a demo link, no need for a call." Case 2 applies: he is a technical gatekeeper. Dana Whitfield demos to him directly, shows one integration path and treats his eleven questions as the notes sheet. His verdict upward earns the real meeting: discovery with the operations director and finance lead, where the eleven questions become the agenda's first part. Demo first, but discovery still happened before anyone senior saw a screen. All names are invented.
Five mistakes to avoid
- Demoing to whoever asked. The asker is not always the audience. Ask who else should see it and offer to wait a week for them.
- Punishing the buyer with process. "We never demo before discovery" said rigidly costs accounts case 1 to 4 would have saved. The default has exceptions; know them.
- Running the generic tour and calling it a demo. Without discovery, cut scope, not corners: one problem path beats the full map.
- Letting the demo end the thread. Either order, the meeting's last five minutes book the next one. A demo with no next step is a video they could have watched.
- Mistaking a demo request for buying intent. Sometimes it is a junior researcher filling a spreadsheet. Two discovery questions at the top tell you which meeting you are actually in.
Why this works on named accounts
Common questions
Should a discovery call come before a demo?
By default, yes: discovery gives the demo its script (their problem in their words), its audience (the roles who will judge it) and its yardstick (what good looks like). Skip it only for a self-evident product, a technical gatekeeper, a fixed bake-off format or a buyer whose discovery effectively happened already.
Can you do discovery and a demo in the same call?
On smaller deals, yes: 15 minutes of questions, then a demo scoped to what you just heard, then a close. The mistake is blending them; run them as two labelled halves, or the demo swallows the questions.
What if a prospect refuses a discovery call?
Offer the 15-minute version with the demo on the spot afterwards. If they still refuse, demo one problem path, harvest their questions as discovery and close for the wider-group conversation. A buyer who refuses every conversation around the demo is telling you how the account will treat you after the sale too.
More from the Academy
Discovery Call Agenda and Notes Sheet
For sellers who run discovery on instinct and lose what they heard.
You leave with a five-part 30-minute agenda, a notes sheet whose fields feed the account plan and a list of the six things to leave the call holding.
Demo Prep Checklist
For anyone who has watched a demo die from an unshared screen or an unknown audience.
You leave with a three-part checklist: the account facts to hold, the setup checks and the first-minute questions.
Discovery Call Question Bank by Function
For sellers whose first call with a new stakeholder sounds like the last one.
You leave with a call plan, 36 questions for 6 functions, 4 closing questions, a notes header and one plan filled in.
Want this in your inbox?
Optional. We use your email only to send you this, nothing else.