A bad discovery call feels like a job interview: the rep runs down a checklist, the prospect gives short answers, and both leave with less enthusiasm than they started. A good one feels like a conversation with someone who understands the problem better than you do. The difference is not the questions themselves, it is the order, the follow-ups and the willingness to shut up after asking. This guide gives you 25 questions organized by what you actually need to learn, with the follow-ups that turn a yes-or-no into a story.
What discovery has to establish
Every qualification framework, from BANT to MEDDIC, is a list of things you need to know before a deal is real. Strip away the acronyms and there are five:
- The problem. What is broken, how badly, and what it costs them.
- The trigger. Why now, and what happens if nothing changes.
- The people. Who decides, who influences, who can block.
- The process. How they buy, what they have tried, what a decision looks like.
- The fit. Whether you can actually solve it, and whether the money exists.
You will not get all five in one call and you should not try. Aim for a clear picture of the problem and the trigger, a sketch of the people, and one honest signal on fit. The process and the money come in the second conversation, once you have earned the right to ask. If you want the framework underneath this, our guide to BANT covers what each letter is really asking.
The opening two minutes
Do not open with questions. Open with a reason for the call and a proposed shape, then ask permission. “Thanks for taking the time. You mentioned in the form that lead routing is slow. I would like to spend most of this call understanding how that works today and what it is costing you, and then if it makes sense I can show you what we do in the last ten minutes. Does that work?” Now they know you are not going to pitch for thirty minutes, and they have agreed to talk about themselves. That agreement is what makes the questions below feel like curiosity rather than interrogation.
Questions about the problem
Start broad, then narrow. The first question should be impossible to answer with one word.
- “Walk me through what happens today when a lead comes in.” Let them describe the process end to end. Take notes on every place they hesitate or sigh.
- “Where does that break down?” Follow-up: “How often?”
- “What does that cost you?” If they say “a lot,” follow up: “Help me put a number on it. Is it hours, deals, people?”
- “Who feels this most?” The answer tells you whether you are talking to the person with the pain or someone adjacent to it.
- “What have you tried already?” Follow-up: “What happened?” Their failed fixes tell you what they believe the cause is, which is not always the real cause.
Questions about the trigger
Problems can exist for years without anyone buying anything. You are looking for the reason this problem is a priority now.
- “What made you look into this now rather than six months ago?” The single most important question on the call.
- “Is there a date this needs to be solved by?” Follow-up: “What happens on that date?”
- “If this is still the same in a year, what does that mean for you?” Personal consequences drive urgency more than company ones.
- “What else is competing for attention on your side right now?” You are asking what could push this deal down the list.
Questions about the people
Ask these conversationally, spread through the call, not as a block. A block of “who decides” questions sounds like you are qualifying them out.
- “Who else is involved in figuring this out?” Softer than “who is the decision maker” and gets a fuller answer.
- “When you brought this up internally, what was the reaction?” Reveals supporters and skeptics at once.
- “Who would need to sign off on a change like this?” Follow-up: “Have they seen anything yet?”
- “Is there anyone who would prefer things stay as they are?” Every deal has a blocker. Better to find them now.
- “How did the last tool in this area get chosen?” Tells you the real process, not the official one.
Questions about the process
Save most of these for the second call, but ask one or two if the first call is going well.
- “What does the evaluation look like from here?” Follow-up: “Who runs it?”
- “Are you looking at other options?” Follow-up: “What do you like about them so far?” Asking about competitors calmly signals confidence.
- “What would you need to see to feel confident this works?” This is the question that writes your proof-of-concept plan.
- “Is there a procurement or security review we should plan for?” Late surprises kill more deals than competitors do.
Questions about fit and money
Budget questions asked too early get a defensive answer. Asked after the cost of the problem is on the table, they get an honest one.
- “Given what this is costing, what would a reasonable investment to fix it look like?” Anchors on their number, not yours.
- “Is there budget set aside, or would this need to be found?” Both answers are fine. “Found” means a longer cycle and an internal champion.
- “What did you spend on the last thing you tried?” A proxy for what they consider normal.
- “If we could solve the routing problem but not the scoring part, would that still be worth doing?” Tests whether the scope you can actually deliver is enough.
Closing the call
- “What have I not asked that I should have?” Consistently surfaces the thing they were waiting to say.
- “Based on what you have heard, does it make sense to keep going?” Ask for the honest no. A polite maybe wastes both calendars.
- “What is the right next step, and who should be in the room?” Never end a call without a scheduled next one or an explicit reason there is none.
The habits that make the questions work
- Silence after the question. Count to four. The best answers come after the first, shallow one.
- Follow up with “tell me more” more than with the next question. Depth beats coverage. Eight questions explored is better than twenty-five skimmed.
- Reflect before moving on. “So if I have it right, leads sit for about two days because routing is manual and Priya is the only one who does it.” Being understood is why people keep talking.
- Write down their words, not your interpretation. “Leads rot” goes in the CRM as “leads rot.” Their language is what you will use in the proposal.
- Do not solve on the call. The moment you start explaining your product, discovery ends. Save it for the last ten minutes you asked for at the start.
After the call
Within an hour, log the five things: problem, trigger, people, process, fit, each in two lines. Assign a disposition, since a discovery call is exactly the point where an MQL becomes an SQL or does not. If your team has not agreed what that transition means, the MQL to SQL handoff checklist has the definitions and the reason codes. Then send a three-line recap to the prospect with their words in it and the agreed next step. Reps who do this consistently close a meaningfully higher share of their discovery calls, not because the recap is persuasive but because it proves they listened.