Discovery call
diss-KUV-uh-ree kawl
The first structured sales conversation where a rep qualifies the prospect by understanding their problem, timeline, and buying process.
A discovery call is the first real conversation between a salesperson and a prospect. Not a demo. Not a pitch. A conversation designed to understand whether this prospect has a problem worth solving, urgency to solve it, and the ability to buy.
Good discovery follows a framework. MEDDIC, BANT, or something custom. The rep asks about the prospect's current situation, the pain they are experiencing, what happens if they do nothing, who else is involved in the decision, and what their timeline looks like. The answers determine whether this opportunity is real.
The biggest mistake in discovery is talking too much. Reps who spend 70% of the call presenting and 30% listening close at half the rate of reps who flip that ratio. Discovery is about the prospect, not your product. Your product comes later, shaped by what you learned.
Examples
A BDR books a discovery call for an AE.
The BDR confirms the prospect matches the ICP and has expressed interest. The AE prepares by researching the company, identifying potential pain points, and preparing open-ended questions. The call lasts 30 minutes.
A discovery call reveals the deal is not real.
The prospect says they are 'just exploring options' with no budget, no timeline, and no defined problem. The rep politely disqualifies the opportunity and moves them to a nurture sequence instead of wasting everyone's time.
Discovery uncovers a bigger opportunity.
The prospect called about a single team's problem. During discovery, the rep learns that three other teams have the same issue. The opportunity expands from a $20k deal to a $100k company-wide deployment.
In practice
Discovery call question framework
SITUATION 1. What does your company do? Who are your customers? 2. How big is your team? How is it structured? 3. What tools/systems do you use today? PROBLEM 4. What prompted you to look for a solution now? 5. How are you handling this today? What breaks? 6. What happens if you do nothing for the next 12 months? IMPACT 7. How much time/money does this cost you per month? 8. Who else is affected by this problem? 9. Is this a priority for your leadership team? DECISION 10. Who else needs to be involved in this decision? 11. What does your evaluation process look like? 12. What is your timeline for making a change? 13. Do you have budget allocated for this?
Read more on the blog
Frequently asked questions
What questions should you ask on a discovery call?
Focus on four areas:
- Situation: what does the current process look like?
- Pain: what is not working and what does it cost?
- Impact: what happens if they do nothing?
- Decision: who is involved, what is the timeline, and is there budget?
Tailor your questions to your specific product and buyer.
How long should a discovery call be?
25 to 45 minutes. Shorter than that and you did not dig deep enough. Longer and you are probably pitching instead of asking. The prospect should talk at least 60% of the time.
Related terms
The average time from first contact with a prospect to closed-won deal. Longer for enterprise, shorter for self-serve.
An internal advocate at the prospect's company who wants your solution to win and actively sells on your behalf inside their organization.
A sales qualification framework: Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion.
A lead qualification framework: Budget, Authority, Need, Timeline. The simplest way to determine if a prospect is worth pursuing.
A lead that a salesperson has vetted and confirmed has real buying intent, budget, and authority.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.