Most discovery advice is a list of questions. The better starting point is what you already know. By the time someone replies to outreach, their company size, technologies, open roles and the message they answered are all on record. Below: what to have before the call, how many questions to ask, how executives differ, and what decides a second meeting.
What is a discovery call for?
A discovery call is for deciding, on both sides, whether to keep talking. The seller needs to learn whether there is a real problem, who feels it, what it costs and how the company buys. The prospect needs to learn whether the seller understands their situation well enough to be worth another hour.
What it is not: a demo, a price discussion or a closing attempt. If the seller talks more than the prospect, the call has turned into a pitch, and the information it was meant to gather never arrives.
What should you know before the call starts?
You should know everything that data can tell you, so the call is spent only on what data cannot. Most of the context exists before the call: it comes from enrichment, from signals and from the reply itself.
- Company size: headcount and the size of the relevant team.
- Industry and market: what they sell and to whom.
- Technologies: the tools they run now, including any competitor of yours.
- Open roles: what they are hiring for, and in which team.
- Recent change: funding, a new leader, an expansion or a restructure.
- The person: role, seniority and how long they have been in it.
- Buying group: who else is likely to be involved.
- Existing relationship: earlier conversations, trials or lost deals in your CRM.
- The reply: exactly what they wrote, and their tone.
- The trigger step: which message they answered, and what it said.
The first eight come from enrichment and signals; the last two come from the reply. With these in hand, you can open with what you know and ask them to correct it, which is faster and more respectful than asking them to describe their own company.
Two vendor analyses and one classic study underpin this page. Gong's Mastering Sales Discovery Calls (2017, more than 519,000 calls) gives the eleven to fourteen question range, and Selling to the C-Suite (2018, 39,105 deals) gives the executive figure. Both are vendor data from recorded calls. Neil Rackham's SPIN Selling (1988), based on more than 35,000 sales calls, is the source of the question order.
How many questions, and which?
Ask about eleven to fourteen targeted questions, spread across the call rather than fired at the start. That is the range Gong associated with successful discovery calls in its 2017 analysis of more than 519,000 recorded calls (vendor data). Fewer questions leaves gaps; many more turns the call into an interrogation.
Order them the way Neil Rackham's SPIN Selling, built on research into more than 35,000 sales calls, suggests: situation, problem, implication, need-payoff. Keep situation questions short, because data has already answered most of them.
- Situation. I saw you are hiring two SDRs. Is that a new team or growth of an existing one?
- Situation. How do new leads reach your sellers today?
- Situation. Who else is involved when you change how the team works?
- Problem. What part of that process takes the most time?
- Problem. Where do good leads get lost?
- Problem. What have you already tried to fix it?
- Implication. What happens to the quarter if that stays as it is?
- Implication. How does it affect the new hires while they ramp?
- Implication. Who notices first when it goes wrong?
- Need-payoff. If that were solved, what would the team do with the time?
- Need-payoff. How would you know it was working?
- Next step. Who should be in the next conversation, and when?
How does discovery differ for executives?
With executives, ask fewer questions and bring more insight. Gong's 2018 analysis of 39,105 deals found that successful meetings with C-level buyers involved about four questions on average. Executives expect you to have done the situation work already. Use the call for one or two problem and implication questions, a point of view on their situation, and a clear proposed next step.
What decides whether there is a second meeting?
A second meeting follows when three things are true by the end of the call: the prospect has named a problem in their own words, they agree it is worth solving now, and a concrete next step is in the calendar with the right people invited. If any one is missing, say so plainly and ask what would need to change. A clear no at this stage saves both sides weeks.
When someone replies to a sequence, Leadspicker can create a task in the CRM for the rep who owns that reply, so they can call the number from the signature while the reply is still warm.
Frequently asked questions
How long should a discovery call be?
Long enough to cover problem, impact and next step without rushing, which for most B2B calls means a standard meeting slot. Agree the length at the start and keep to it.
What is the difference between a discovery call and a demo?
Discovery is for learning about the prospect's problem; a demo shows how the product solves it. Doing discovery first lets the demo show only what matters to that buyer.
Should you use a script for a discovery call?
Use a question list, not a script. Know the areas you must cover and a few strong questions for each, then follow the conversation. A script makes it sound like an interview.
