Discovery Call
A discovery call is an early sales conversation where buyer and seller figure out whether there's a reason to keep talking. It isn't a pitch. The seller is there to learn what problem the buyer has, what that problem costs, who else is involved in solving it and whether a real project with a timeline exists.
Account executives and SDRs run this conversation before any demo, proposal or trial. A good first call ends one of two ways. Either both sides agree on a next step with a date attached, or they honestly conclude the fit isn't there. Both outcomes protect the buyer's time as much as the seller's.
What Is a Discovery Call in Sales?
Discovery works in both directions. The seller checks whether the buyer has a problem worth solving, and the buyer checks whether the seller understands it well enough to help. A Gartner survey of 632 B2B buyers found buyers prefer self-service for general information but want seller input on context-heavy tasks like judging product fit.
Gartner's March 2026 survey found 67% of B2B buyers prefer a rep-free experience. So the calls that do happen have to earn their time. The call feeds the lead qualification decision. Discovery is the conversation. Qualification is the verdict.
What a Good Discovery Call Covers
Most productive calls touch five areas:
- The problem. What's broken, and what the buyer has already tried.
- The impact. What it costs and why it matters now.
- The process. How they buy, from evaluation and trials to security review and procurement.
- The people. Who uses, influences and signs, typically the economic buyer alongside the wider buying committee.
- The next step. A specific action agreed before you hang up.
That group of people can be big. Forrester's 2026 State of Business Buying research found a typical purchase involves 13 internal stakeholders and nine external influencers, with procurement making decisions in 53% of buying cycles. The BANT framework can give the conversation structure without turning it into a script.
Discovery Call Questions That Work
Good questions are open, specific and grouped by what they uncover.
| What it uncovers | Example questions |
|---|---|
| The problem | "What made you take this call now?" "What have you tried, and where did it break?" |
| The impact | "What happens if this isn't fixed this quarter?" |
| The process | "Where do security review and procurement come in?" |
| The people | "Who else needs to be convinced?" "Who owns the budget for this?" |
The best follow-up comes from the buyer's last answer, not a checklist. Strong sellers also share what's worked elsewhere.
Discovery Call vs. Demo
| Discovery | Demo | |
|---|---|---|
| Goal | Understand the problem, check fit | Show how the product solves it |
| Who talks most | Buyer | Seller |
| Output | Decision to continue or stop, plus context for a tailored demo | Buyer evaluation, often leading to a trial |
A demo that follows discovery targets the buyer's own problem instead of generic features. Use discovery to define what trial success looks like, too. Forrester's 2026 research found more than 60% of buyers run one.
Running Discovery with Technical Buyers
With technical buyers, asking things you could have found in public information burns trust fast. Do the research first: their stack, open roles, public repositories and what they said in technical communities. Engineers will check your claims against your docs. Gartner's June 2025 survey found 69% of buyers saw inconsistencies between seller websites and what reps told them.
The Stack Overflow 2025 Developer Survey found 48% of developers endorsed or influenced a new technology purchase. It helps to understand developer-focused sales personas before the call.
For deeper calls, bring a technical colleague, like a sales engineer or solutions architect. Don't know an answer? Say so, then follow up.
FAQ
What is the purpose of a discovery call?
A discovery call lets buyer and seller decide whether to keep going. The seller learns the problem, its business impact, the people involved and how the organization buys. It should end with an agreed next step or an honest decision that there's no fit.
What questions should you ask on a discovery call?
Group your questions by what they uncover: the problem ("What made you take this call now?"), the impact ("What happens if this isn't fixed?"), the process ("How did you evaluate your last tool?") and the people ("Who else needs to be convinced?"). Skip anything public research already answers.
What is the difference between a discovery call and a demo?
Discovery is about understanding the buyer's problem and checking fit, so the buyer does most of the talking. A demo shows how the product solves that problem, so the seller talks more. Discovery comes first, which lets the seller tailor the demo instead of showing generic features.
How long should a discovery call be?
There's no standard length. It depends on deal complexity and how much context the seller already has. Simple purchases might need only a short conversation. Technical evaluations often need a longer session or a second call with a sales engineer covering architecture, integrations and security.
Who should run a discovery call, an SDR or an AE?
It depends on the sales model. In many teams, SDRs run the first qualifying conversation and hand off to AEs, who lead deeper discovery on impact, process and stakeholders. On technical deals, bringing in a sales engineer early helps answer detailed questions credibly.