Discovery calls are important because every later step in a deal, from the demo to the business case to the forecast, runs on what the buyer said in discovery, and a deal built on the rep's guesses stalls when it reaches someone who has to approve it.
The short version
Most sales content gives reasons that apply to any first meeting, like building rapport and qualifying the lead. Those are true of discovery too. What makes discovery different is that it produces the deal's evidence: the buyer's account of the problem, what it costs, who decides and by when. Nothing later in the cycle can produce that evidence as cheaply. A demo can confirm it and a business case can put numbers on it, but both need it first.
- The problemIn the buyer's account of it
- What it costs
- Who decides
- By when
- The problemIn the buyer's account of it
- What it costs
- Who decides
- By when
A good discovery call finds out what the buyer needs fixed and whether anyone above them wants it fixed too. Reps skip the second part, and it is the part that decides whether a deal closes. Our discovery call guide covers how to get both.
What runs on discovery
| Later step | What it needs from discovery | What happens without it |
|---|---|---|
| Demo | The problems the buyer named, in their order | Features shown in product order |
| Business case | A cost the buyer stated | The rep's estimate, which the approver discounts |
| Meeting the approver | The approver's name, from the buyer | A late surprise in procurement |
| Forecast | Buyer statements behind each stage | A stage set by the rep's hopes |
| Deal review | Quotes the manager can test | A conversation about how the call felt |
Example: two deals in the same pipeline review (illustrative)
These deals are invented. A manager runs a deal review call with two reps, each with a deal marked "discovery complete".
Rep A says the buyer was engaged, the call ran long, and they loved the product. The manager asks what the problem costs the buyer. Rep A does not know. Who signs? "Probably the VP." The deal is at the stage it is because the call went well.
Rep B reads two buyer quotes: "We lost a renewal last quarter because support gave three answers to the same bug," and "Our CFO signs anything over the tooling budget and will want to see time saved." The deal has a cost and an approver, in the buyer's words. The manager's coaching for Rep B is about the CFO meeting. For Rep A it is about going back to discovery before the demo.
Same stage on the CRM, very different deals, and the difference was made on the discovery call.
What thorough discovery covers
After a thorough discovery call, the rep can repeat five things in the buyer's own words: the problem, what it costs, what happens if nothing changes, who decides, and the agreed next step. A quick check after the call:
- Write each of the five as a quote, with who said it.
- Mark any that are the rep's inference.
- For each marked item, write the question that would turn it into a quote on the next call.
The length of the call and the number of questions say little about thoroughness: a 25-minute call that ends with a quoted cost and the approver's name has covered more than an hour on the roadmap that leaves both blank.
Why discovery matters to the buyer
A good discovery call is useful to the buyer even if they never buy. Many buyers have never described their problem out loud in one sitting, with someone asking what it costs and who would have to agree to fix it. By the end of the call they have a clearer version of the problem than they walked in with, and often a sentence they can reuse with their own boss.
That is also why buyers keep taking discovery calls from some reps and dodge them from others. A call made of situation questions the rep could have answered from the website feels like filling in a form. A call that starts from what the rep already knows and asks about the last time the problem bit feels like help, and the buyer gives better answers because the call is worth their time.
Two habits make the difference on the call:
- The rep has done the homework, so the first question is about this buyer's situation. How to prepare for a discovery call covers that.
- The rep plays back what the buyer said, in the buyer's words, before asking the next question. Buyers correct a playback, and the correction often tells the rep something new.
Discovery tells you when to walk away
Discovery is a cheap place to find out there is no deal. A rep who learns on the first call that the problem is minor, that nobody owns it, or that a budget freeze runs to next year has spent half an hour. A rep who learns it in procurement has spent a quarter, a solutions engineer's time, and a slot in the forecast that a real deal could have had.
Reps resist this because a disqualified deal looks like a lost one. In practice, a pipeline where every deal has buyer evidence behind it is one a manager can forecast and coach. The signs that a deal is not there yet are usually audible on the first call:
- The buyer cannot describe a recent example of the problem.
- Asked what it costs, the buyer calls it "more of a nice to have."
- Nobody above the buyer has asked about it.
- The only next step the buyer offers is "send me something."
One of these on its own does not end a deal. Two or three together, after a call where the rep asked the right questions, are a reason to say so to the buyer and agree to talk again when something changes. How to qualify out a deal has that conversation.
Why discovery decides the forecast
A forecast can only be as good as the evidence behind each deal's stage, and most of that evidence is created in discovery. When a manager asks why a deal is in commit, the answer should point to things the buyer said: the cost they named, the approver they named, the date they agreed to. If the answer points to how the call felt, the number is a guess.
This is where weak discovery does its damage. It rarely shows up as a lost deal on the day. It shows up weeks later as a deal that slips a quarter, then another, because nobody knew the CFO had to sign or that the buyer's priority had moved to a different project. By then the rep has made a forecast commitment that rests on it.
One rule keeps the two connected: a deal moves past discovery in the CRM only when the cost and the approver are written down as buyer quotes. Applying it usually shrinks the pipeline on paper. What is left can be forecast from what buyers said. Why sales forecasts are wrong goes further.
Worked example: one deal from discovery to signature (illustrative)
This deal is invented. Jordan sells route-planning software. Robin is director of operations at Tallowbrook Freight, a regional carrier with about 200 trucks.
Discovery. Jordan opens with something from research: Tallowbrook opened a second depot this year. Robin describes the last bad week: drivers running out of hours before their final drop, three late deliveries to the largest customer, and a dispatcher rebuilding routes by hand at 6 a.m. Asked what that costs, Robin says overtime is up and the largest customer has started asking for credits on late loads. Asked who signs, Robin says Morgan, the CFO, signs anything outside this year's budget and will want to see the overtime number.
What Jordan writes after the call. Problem: "We rebuild routes by hand every morning since the second depot opened." Cost: overtime, plus credits to the largest customer, with figures to come from Robin. Approver: Morgan, CFO, because the spend is outside the budget. Next step: Robin sends three months of overtime figures by Friday, and a 45-minute call is booked with Robin and the lead dispatcher.
The demo. Jordan shows the morning re-plan across two depots and leaves the rest of the product alone. The dispatcher asks how it handles driver hours, which is the question that matters to the person who would use it every day.
The business case. It uses Robin's overtime figures and the credits the customer asked for. Jordan adds no productivity estimate, because Morgan would discount a number Robin never gave.
The approver meeting. Morgan asks one question: what happens if they wait for next year's budget. Robin answers it with the line from discovery about the largest customer. The deal closes on the timeline Robin set.
Every step after the first call reused something Robin said on it. Had Jordan skipped the cost question, the business case would have been built on Jordan's numbers and Morgan's question would have had no answer.
Discovery does not stop after the first call
The first discovery call starts discovery and rarely finishes it. It usually captures one person's view of the problem. Larger deals need the same questions asked of the approver, the people who would use the product and whoever owns the budget, and their answers often differ. A finance lead may care about what the problem costs while the dispatcher cares about the 6 a.m. scramble.
Good reps keep asking through the rest of the sale. A demo is a chance to test whether the problems named on the first call are still the priority. A proposal review is a chance to check that the cost figure still holds. When a deal goes quiet after a strong first call, the cause is often something discovery did not reach: a new priority, a stakeholder nobody met, or a cost the buyer never confirmed. Why deals stall after good discovery covers the patterns, and how to run discovery with a buying committee covers talking to several people at once.
The follow-up that proves discovery happened
Send a short recap the same day. Its job is to put the buyer's words in writing and give them the chance to correct anything wrong. A template, using the Tallowbrook deal:
Subject: Recap of today and next steps
Thanks for the time today, Robin. Here is what I heard, so you can correct anything I got wrong:
- The problem: routes are rebuilt by hand every morning since the second depot opened.
- What it costs: overtime, and credits to your largest customer for late loads. You'll send three months of overtime figures by Friday.
- Who else is involved: Morgan approves anything outside this year's budget and will want the overtime number.
- Next step: Tuesday at 10 with you and your lead dispatcher, to walk through two-depot planning.
Did I miss anything?
A buyer who replies with a correction has just given you more discovery. A buyer who does not reply at all is worth noting before the deal goes into the forecast.
What the rest of the company gets from discovery
Buyer quotes from discovery are useful well beyond the deal, and most of them stay in reps' notes. Marketing can use the problems buyers name, in their words, for messaging. Product can see which problems come up again and again, and which ones the product does not solve. Enablement can see which questions reps skip. None of this needs a new process. If each deal record holds the buyer's quotes for the problem, the cost and the approver, anyone can read them across fifty deals.
Where to go next
Start with the discovery call guide, which covers preparation and the common mistakes, and the discovery call questions for what to ask. Managers checking whether discovery happened can use the discovery call scorecard template and how to score a discovery call. Deals with several stakeholders need discovery with each of them, covered in how to run discovery with a buying committee. To find out whether your pipeline looks more like Rep A or Rep B, talk to us.
FAQ
What is the main purpose of a discovery call?
The main purpose is to get the buyer to describe their problem, what it costs and how they will decide, in their own words. That tells the rep whether there is a deal, and gives every later call (demo, business case, approver meeting) something specific to build on.
What happens if you skip discovery?
If you skip discovery, the deal runs on guesses. The demo shows features the buyer has not said they need, the business case uses the rep's numbers, and the approver often appears late. Deals that skip discovery tend to stall at the point where someone has to justify the spend.
How do you know discovery is complete?
Discovery is complete when the buyer has stated the problem, its cost, who decides and what happens next, and agreed to a dated next step. If any of those are the rep's assumption, discovery is still open, whatever the CRM stage says.
How long should a discovery call be?
A first discovery call with one buyer usually fits in 30 minutes. Complex deals with several stakeholders need more than one call, and each can still run 30 to 45 minutes. Length matters less than whether the call ended with the cost, the approver and a dated next step in the buyer's words.
Is a discovery call the same as a qualification call?
A discovery call is not the same as a qualification call, though the two overlap. Qualification asks whether a deal is worth pursuing, and discovery gathers the evidence that answers that question and that every later step reuses. A good discovery call qualifies the deal along the way. A qualification call that only checks budget and timing leaves the rep without the buyer's account of the problem.
How is a discovery call different from a cold call?
A discovery call happens after the buyer has agreed to talk, usually because something in their business has made the problem worth discussing. A cold call is unsolicited, and its job is to earn that meeting. Discovery can go deeper because the buyer has already set aside the time. Discovery call vs sales call covers the wider distinction.
Who should run a discovery call?
The account executive who will own the deal runs it, because the buyer's words need to reach every later call without a handoff losing them. A manager or solutions engineer can join a later discovery call when the deal needs it. The manager's main part is the brief before the call and the debrief after.