Cold-call discovery qualifies a prospect enough to justify a meeting. Discovery-meeting discovery gathers enough understanding to build a proposal.1 Treating the call like a full audit can produce a 14-question interrogation, leave the prospect feeling audited, and end with a polite request for information.2 Keep questions narrow, follow the prospect's words, and stop when you know whether another conversation has a clear purpose.
Set the guardrails
Control the size of the job. Get enough detail to decide whether a useful next conversation exists, then leave room for the prospect to do most of the talking.
A cold call that ends in a booked meeting runs 3 to 7 minutes.3 On those calls, talk for 40 to 45 percent of the time and spend the rest asking and listening.4 Keep discovery to 6 to 9 questions maximum.5 Build the questions around one thread: why they took the call, how they handle the situation, what creates difficulty, and whether further discussion makes sense. Let each answer choose the next question instead of running a checklist.
Start with the reason
Give the prospect room to describe the situation in their own words. Ask, "why'd you take this call with me?"6 Asking what specifically prompted the call usually reveals a situation or problem.7 Listen for the prospect's wording and use it in the next question. Move on when they have given you something concrete to explore.
Confirm the current state
Once the prospect gives you a reason, establish how the situation works today. This gives the later questions a clear target.
The focus at this stage is the prospect's current state.8 Before asking about problems, confirm and build on your pre-call work with short questions about the business, the team, and the current situation.9 Ask about the process instead of requesting a broad tour. For a systems workflow, ask, "Does your phone system integrate into your CRM?"10
Listen for what exists and how the prospect describes it. If the answer is vague, ask for the next concrete part of the process. Move on when you understand the current approach well enough to ask about its limits.
Isolate the problem
Stay with the first problem signal until the prospect can describe the gap in their own operation. Explaining your offering too soon cuts off information that should shape the rest of the call.
A cold call only needs two problem-based questions.11 Start with "What problem are you attempting to solve?"12 Then ask how that problem appears in the current process or what happens when it remains. Keep the questions narrow. The aim is to expose one weakness or problem in the current operation.13
Move on when the prospect has described the problem and its effect in terms you can repeat accurately. If they cannot describe a problem, stay at the situation stage or end without forcing a reason to continue.
Test the current response
Find out what the prospect does today and whether that response leaves room for change. This shows whether the situation gives you a reason to keep talking.
If they mention an incumbent provider, ask, "is that still the case?"14 Ask whether they have internal resources to solve the problem on their own.15 When the prospect is receptive, ask about their knowledge of the situation.16 You can also ask what they have already tried and what remains unresolved.
Use the answer to separate a problem they live with from one they want to address. You can ask a question that exposes a gap in what they know about the situation.17 Move on when the prospect acknowledges a reason to examine the current approach further.
Set the purpose for the next conversation
End discovery when you know what the next conversation needs to accomplish. The prospect's desired outcome gives you a cleaner handoff than your own agenda.
Ask, "What do you really want out of this call, out of this conversation?"18 After the prospect has spoken, use a soft follow-up such as "I'm curious to know" before asking for more detail.19 Use the answer to decide whether to propose a meeting, keep learning, or close the thread. If the prospect cannot name a reason to continue, do not stretch the call with more questions.
When the answer is thin
Thin answers are a signal to slow down and ask for meaning. When you get stuck, ask, "what do you mean?"20 If the answer remains vague, ask about a specific part of the process. Specific questions are preferred to broad questions for this work.21
What not to do
These mistakes come from asking for more detail than the call needs or letting the script outrun the prospect.