A discovery call gets the buyer to state their problem, what it costs and how they will decide. A demo shows how the product meets the specific parts of that problem the buyer said matter. Discovery comes first because a demo is only as good as the buyer's words it is built from.
Our discovery call guide covers discovery in full, and how to run a discovery call is the minute-by-minute version. This page is about the line between discovery and the demo, and the handoff from one to the other.
The difference
The two calls produce opposite things. Discovery produces evidence from the buyer: their problem in their words, a cost they stated, the names of the people who decide. A demo spends that evidence. Every screen in a good demo answers something the buyer said, and the buyer can tell.
When the order flips, the demo has nothing to spend. The rep shows the features they like best and the buyer nods at the familiar ones. The call ends with "send me a deck." Nobody learned what the buyer needed. Feature dumping is usually a discovery problem that shows up in the demo.
Side by side
| Discovery call | Demo | |
|---|---|---|
| Purpose | Get the buyer's account of the problem, cost and decision | Show how the product meets the parts of the problem the buyer named |
| Who talks most | The buyer | The rep, in short turns, checking back often |
| Output | Buyer quotes on problem, cost, owner and decision; a dated next step | The buyer saying which part solves which problem; agreement on next steps toward a decision |
| What good looks like | Two or three pieces of evidence moved from guessed to stated by the buyer | The buyer asks a "how would that work for us" question you did not prompt |
| The usual failure | The rep pitches when the buyer mentions a pain | The rep shows everything, in product order |
| How to score it | Which evidence moved; skills such as framing and gaining commitment | Whether each segment traced to a buyer quote; whether the buyer committed to a next step |
| Typical length | 30 minutes, one buyer | 45 to 60 minutes, often with more of the committee |
The handoff rule
Move from discovery to demo when the buyer has said three things in their own words: the problem, what it costs, and what they want instead. The signal is usually a buyer question: "So how would that work for us?" That question, asked after the buyer has described their situation, means they are ready to see something.
- 01The problemIn the buyer's own words
- 02What it costs
- 03What they want instead
- 04"So how would that work for us?"The buyer's signal
- 05Demo
If those three are missing, the demo has nothing to aim at. If the buyer asks to see the product before they have said them, there is a script for that below.
Three handoff cases, with scripts
Case 1: The buyer asks for a demo in minute three
Agree, then ask two questions so the demo can be specific.
Say: "Happy to. So I show you the right part and skip the rest, can I ask two things first? What's happening today that made this worth a look, and what does it cost you when it goes wrong?"
Most buyers accept, because the offer is a shorter, more relevant demo. If they insist, show a short slice around whatever problem they named on the booking form, then return to the cost question.
Case 2: Discovery and demo on one call
Many teams run both in one 45 or 60 minute call. That works if the rep holds the order: the first half is discovery, and the switch happens on the buyer's sentence.
Say (at the switch): "You said renewals slip past notice dates and two did last year. Let me show you the one part that's about that, and you tell me if it would have caught them."
Show one part, then check: "Would that have caught them?" Then decide together whether to show more.
Case 3: A separate demo call
Open the demo by reading back the discovery in the buyer's words, and ask what has changed.
Say: "Last time, Dan, you said contracts sit nine days before legal looks at them, and Ruth signs anything new. Is that still the picture? Anything to add before I show you?"
Good looks like a correction. A buyer who corrects your summary is engaged with the problem, and the demo now aims at their corrected version. Give each segment a buyer quote as its title.
One call or two
Use two calls when the buyer has given you little to go on, the decision involves several people, or the product does many things and a demo needs choosing. A separate discovery call leaves time to find out which parts matter, and the demo can then bring in the people those parts affect.
One call works when the buyer owns the decision alone, already knows roughly what the product does and booked the meeting to see it. Holding the order is the hard part. Tell the buyer the shape at the start: "I'd like to spend the first part understanding what's going on, then show you the pieces that fit. Does that work?" Most buyers say yes, and the agreement makes it easier to keep asking when the urge to share a screen arrives.
Whichever you choose, ask about next steps early. Near the start of the call, say what usually happens after a call like this and ask whether that would suit them. The buyer then knows where the call is heading, and the close at the end becomes a confirmation.
Worked example (illustrative)
This deal is invented to show the handoff. Aisha sells a customer support platform. Her discovery call with Ben, head of support at a 250-person software firm, produced three quotes:
- "New agents take six weeks to get useful, and two seniors spend half their time shadowing."
- "We lost a renewal last quarter partly because the same bug got three different answers."
- "Our VP signs anything over our tooling budget, and she'll want to see time saved."
Her demo has three segments, in that order, each titled with a quote. Segment one shows how new agents get suggested answers drawn from resolved tickets. Segment two shows how a fix gets attached to a known issue so every agent gives the same answer. Segment three is a one-slide estimate of senior agents' shadowing time, built with Ben's figures.
At the start Aisha reads the three quotes back. Ben corrects one: it was two renewals, both partly the inconsistent answers. She moves segment two to the front. Twenty minutes in, Ben asks, "Could the VP see segment three with our real ticket data?" That question is the commitment: a meeting with the approver, on the buyer's numbers. Aisha did not show the reporting module, the integrations page or the mobile app. Ben never mentioned them.
What to send between discovery and the demo
When discovery and demo are separate calls, the email in between does most of the bridging. Send it the same day, while the buyer still remembers what they said. It has three jobs: play back the problem in the buyer's words, propose the demo agenda built from those words, and confirm who should attend.
A template, using Aisha and Ben's deal from above:
Subject: Your three points from today, and the demo agenda
Ben, thanks for the time. What I heard:
- New agents take six weeks to get useful, and two seniors spend half their time shadowing.
- You lost a renewal last quarter partly because the same bug got three different answers.
- Your VP signs anything over the tooling budget and will want to see time saved.
For Thursday I'd show one part of the product for each, in that order, and nothing else. Did I get any of these wrong, and is there anyone who should see point 3 with you?
Keep it short enough to read on a phone. If the buyer replies with a correction, that is the best outcome the email can produce: the demo now aims at their corrected version, and you have days to change the plan.
If they do not reply, open the demo by reading the three points back, as in Case 3 above.
Building the demo from discovery notes
A demo built from discovery takes less time to prepare than a full product tour, because most of the product is left out. A simple order:
- Pull the quotes. Copy the buyer's own sentences about the problem, the cost and the decision from your notes or the recording. Use the buyer's sentences; a paraphrase drifts toward what you wanted them to say.
- Rank them by the buyer's priority. Use what the buyer said mattered most, or what they returned to more than once.
- Give each quote one segment. Decide the single part of the product that answers it, and title the segment with the quote.
- Write the check line for each segment. One question that asks whether this would have handled the situation they described.
- List what you will not show. Anything that answers no quote stays out, unless the buyer asks.
- Prepare the ask. Decide which next step you will propose if the demo lands, and who needs to be in it.
If step one turns up fewer than three quotes, treat the demo as a second discovery call with a screen available.
Where teams get it wrong
Treating the demo as the first call. Some teams book demos from inbound forms and skip discovery. Every demo then starts cold, and the rep guesses what matters. Booking a short discovery call first, or opening the demo with ten minutes of discovery, fixes it.
Demoing in product order. The rep walks the navigation from left to right because that is how they learned it. The buyer's order is the order of their problems.
Missing the switch. The buyer asks "how would that work?" and the rep keeps asking questions from a list. That costs momentum. The buyer's question is the switch.
Scoring the demo on delivery alone. A smooth demo of the wrong features scores well on presence and loses the deal. Score whether each segment traced to something the buyer said.
Coaching both calls
Discovery and demo get coached differently. Discovery needs a brief before the call (which evidence is missing, what to ask) and a debrief after (what moved). The demo needs a build: which buyer quotes become which segments, in what order. Both happen before the call, and both take a manager's time that most managers do not have.
With Replicate Labs, the rep calls an AI sales expert such as Caty after discovery and talks through what the buyer said; the expert helps turn the quotes into a demo outline, and the rep practices the switch line and the opening read-back out loud with it. After the demo, the rep debriefs with the expert, who records what the buyer committed to against the deal, in the team's own method: Caty for MEDDPICC (metrics and decision criteria before the demo) or your own playbook, or Keenan for Gap Selling (current state before future state). Typing works when the rep cannot talk.
To have a discovery recording scored, talk to us. See preparing for sales conversations for the prep, and discovery call questions for what to ask before the switch. If the buyer pushes back during the demo, objection handling covers it.
Before your next demo, write down the three buyer quotes it is built on. If you cannot find three, the call you need is another discovery call, and we can show you how our coach helps plan it: talk to us.
FAQ
What is the difference between a discovery call and a demo?
A discovery call gets the buyer to describe their problem, its cost and how they will decide. A demo shows how the product meets the parts of that problem the buyer named. Discovery comes first, because a demo built without the buyer's own words tends to show features the buyer has not said they need.
Should discovery and demo be on the same call?
Discovery and demo can share one call if the rep holds the order. Spend the first half on discovery, and switch to the demo when the buyer has stated the problem, its cost and what they want, usually signaled by a question like "how would that work for us?" Then show one relevant part and check before showing more.
What do you do if a prospect wants a demo before discovery?
Agree, and ask two questions first so you can show the right part: what is happening today that made this worth a look, and what it costs when it goes wrong. Most buyers accept a shorter, more relevant demo. If they insist, show a short slice tied to the problem they named, then return to cost.
How do you know when to move from discovery to demo?
Move when the buyer has said, in their own words, what the problem is, what it costs and what they want instead. The clearest signal is the buyer asking how your product would handle their situation. If you are still guessing at the cost or the outcome, keep asking.
How should you start a demo after a discovery call?
Read back the buyer's words from discovery, attributed, and ask whether anything has changed. Then structure the demo as one segment per buyer problem, in the order of what matters most to them. A buyer who corrects your summary is engaged, and the demo should aim at the corrected version.
Can you skip discovery if the buyer has done their own research?
You can shorten it, but keep it. A buyer who has read your site knows what the product does; they have not told you what the problem costs them or who signs. Ten minutes at the start of the demo, asking those two things, keeps the demo aimed at their situation.
How long should a discovery call and a demo be?
A discovery call usually runs about 30 minutes with one buyer, and a demo 45 to 60 minutes, often with more of the buying committee. Length matters less than order. A combined call needs the longer slot, with the first half kept for discovery.
Who should be on the demo after discovery?
Invite the people whose problems the demo answers, plus the approver if the buyer will bring them. Use the discovery notes to decide: if the buyer named a colleague who feels the problem every day, that person should see the segment about it. Ask the buyer to confirm the list before you send the invite, so nobody arrives without knowing why they are there.