Discovery vs Demo: Why Doing Both at Once Kills Deals
- No invented stats
- Written for UK readers
- 5 min read
- Published 28 September 2026
The combined discovery-and-demo call is one of the most reliably damaging habits in B2B sales, and it persists because it feels efficient. One meeting instead of two, the prospect sees the product sooner, momentum maintained. What actually happens is that you spend ten minutes on shallow questions, then deliver a demo built on guesses, and the prospect leaves with a positive impression and no reason to act.
What goes wrong mechanically
Three failures compound in a combined call.
Discovery gets compressed into a formality. When you know a demo is coming, you ask enough questions to justify starting it. Six or seven minutes, surface answers accepted, no follow-ups. You learn "they want better reporting" rather than "the monthly board pack takes the FD two days and she's threatened to outsource it."
The demo becomes the standard demo. You cannot meaningfully restructure a product walkthrough live, on ten minutes of thin information. So you run the one you always run, which covers everything and therefore emphasises nothing. The prospect sees eleven features, needs two, and can't tell which two you think matter.
You lose the second meeting. This is the real cost. Once they've seen the product, the obvious next step is a proposal — but you don't know enough to write a good one. So you write a generic proposal, send it, and join the long queue of suppliers waiting for a reply that doesn't come.
Separating them buys three things
- A demo aimed at something. With real discovery behind you, the demo shows three things they told you they needed, using their language and, where possible, their data or their scenario. That is a fundamentally different experience for the buyer.
- A second commitment. Agreeing to a demo is a small but genuine act of investment. Each one makes the next easier, and a buyer who has spent time on you is more likely to spend money.
- A reason to widen the room. "Who else should see this?" is an easy ask between a discovery call and a demo, and a much harder one after a combined call where everyone relevant has already missed it.
That last point alone justifies the split. Demos with three people in the room progress differently from demos with one, and the gap between calls is your best opportunity to bring in the people who can actually decide — see how to find the real decision maker.
How to hold the line when they ask to see it
Prospects will often ask for a demo up front. You don't need to refuse — you need to reframe, and it helps to be honest about why.
"Happy to show you, and I will. Can I do twenty minutes first to understand how you work at the moment? Otherwise I'll end up showing you the full tour, most of which won't be relevant to you, and we'll both have wasted an hour. Twenty minutes now means the demo is only the parts you'd actually use."
Almost nobody argues with that, because it's obviously in their interest. If someone insists — and occasionally they will, usually because they're comparing suppliers quickly — then give them a short demo, but ask questions throughout and treat it as discovery with visuals rather than a pitch.
A compromise that works: the shape-of-it walkthrough
If you genuinely need to give a sense of the product on the first call, show five minutes and no more, framed explicitly as a preview:
"Let me show you the one screen that matters for what you've just described, so you've got a picture in your head. I'm deliberately not doing the full walkthrough today — that's the next conversation, once I know what to point at."
This satisfies the curiosity without burning the demo. The key is naming what you're doing, so the short version reads as deliberate rather than underprepared.
What each call should contain
The discovery call should establish how things work today, what specifically goes wrong, what it costs, what they've tried before, who else is affected, and how a decision would get made. Twenty to thirty minutes is usually enough if you follow up properly on vague answers — the question set in discovery call questions that uncover real problems is a reasonable starting point.
It should end with an explicitly agreed next step: a date, a named list of attendees, and a stated purpose. "I'll send some times" is not a next step.
The demo should open by replaying what you heard, so they know you listened and can correct you before you start. Then show the smallest number of things that address it. Then stop, and ask what they'd want to know more about.
Most demos are far too long, cover far too much and put the prospect into passive viewing mode — there's more on that in your demo is too long.
When combining them is the right call
This advice has clear limits, and applying it rigidly costs deals.
- Low deal value, short cycle. If your average sale is a few hundred pounds a month and closes in a fortnight, insisting on two calls adds friction the deal can't absorb. Do a short combined call and accept the trade-off.
- Self-serve-adjacent products. If the buyer could sign up online without talking to anyone, making them sit through a discovery call before seeing the product is an obstacle, not a process.
- Late-stage competitive evaluations. If the prospect has already done their own discovery, written requirements and shortlisted three suppliers, they don't need you to run discovery from scratch. Ask about their criteria, then demo against them.
- Genuinely one-shot access. A senior person with one hour and no appetite for a second meeting. Take the hour.
The rule of thumb: separate the calls when the cost of a mis-aimed demo is higher than the cost of an extra meeting. That threshold arrives earlier than most reps think, but it isn't at zero.
The measurement that settles the argument
If your team disagrees about this, run it as a comparison rather than an opinion. Track two things across a quarter: the proportion of demos that produce an agreed next step with a date, and the proportion that lead to a proposal being requested rather than offered. Split by whether discovery happened separately.
Use your own numbers, not anyone's published benchmarks — your buyers, deal size and product are specific to you, and that's exactly the kind of thing a pipeline review meeting should be examining rather than relitigating each week from memory.
One last habit
Between the discovery call and the demo, send a short summary of what you understood, in their words, and ask them to correct it. It takes five minutes, it demonstrates you listened, it surfaces misunderstandings before you build the demo on them, and it gives your contact something they can forward internally to justify inviting colleagues. It is, deal for deal, one of the highest-return five minutes in the job.
Spotted a mistake or a number we can't back up? Tell us and we'll fix it.