What are the best discovery call questions?

The best ones move from situation (how things work today) to problem (what's broken) to impact (what it costs) to decision process (who decides and when). A strong example from each: "Walk me through how your team handles this today," "Where does that break down," "What does that cost you when it does," and "How does a purchase like this get approved here." Pick the four or five that fit the deal rather than asking all of them.

How many questions should I ask on a discovery call?

Fewer than you think, four to six strong ones, asked deliberately, with real listening between them. A discovery call is not a survey. If you're rattling through fifteen questions, the prospect feels processed and you're not going deep on anything. One good impact question, fully explored, beats five surface ones.

What's the difference between situation and problem questions?

Situation questions map the current state, what tools, what process, who's involved. They're low-threat and warm the prospect up. Problem questions go after the friction, where it breaks, what's frustrating, what triggered the call. Situation is the setup; problem is where discovery actually starts. Don't spend the whole call in situation.

How do I ask about budget without killing the deal?

Frame it as part of mapping the decision, not a demand. "When a purchase like this gets approved here, is there usually a budget set aside, or is that part of the conversation?" That phrasing makes it easy to answer honestly either way. The mistake is avoiding the question, a deal with no budget path is one you want to find out about early, not at the end.

Resources · Discovery

Discovery call questions.

A working list of strong discovery questions, grouped by what each one is for: situation, problem, impact, and decision process. Steal the ones that fit your deal.

In short

Strong discovery questions fall into four groups: situation, problem, impact, and decision process. Move through them in that order.
Situation and problem questions surface what's broken. Impact questions attach money and urgency to it. Decision-process questions tell you whether the deal is real.
Ask open questions, then stop talking. The best discovery is mostly listening, the question is the small part, the silence after it is the work.

How discovery questions actually work

Discovery is not an interrogation and it is not a survey. It is a guided conversation that moves from "what's going on" to "what's it costing you" to "who decides and when." The questions below are grouped by that arc. You won't ask all of them on one call, pick the four or five that fit the deal in front of you and let the prospect's answers pull the next one.

Across every group, the rule is the same: ask an open question, then go quiet. The question is the small part. The silence after it, and what the prospect fills it with, is where discovery actually happens. For the why behind the method, see what a discovery call is and how MEDDIC maps onto these questions.

Group 1

Situation, map the current state

Use these early to understand how things work today, before you go looking for pain. "Walk me through how your team handles [process] right now, start to finish."

"What tools or systems are involved in that today?" "How long has it been set up this way?" "Who touches this process besides you?" "How often does this come up, daily, weekly, every quarter?" Situation questions are low-threat, so they warm the prospect up. Don't linger here, though. They are the setup, not the point.

Group 2

Problem, find what's actually broken

Now go after the friction. "Where does that process tend to break down?" "What's the most frustrating part of doing it that way?"

"If you could change one thing about how this works today, what would it be?" "What have you already tried to fix it, and what happened?" "What made you take the call today, what changed?" That last one is gold: it surfaces the trigger event, which is the difference between a nice-to-have and a deal with a clock on it.

Group 3

Impact, attach money and urgency

A problem with no cost attached does not get funded. Impact questions make the cost concrete. "When that breaks, what does it cost you, in time, money, or headcount?"

"How many people does it affect, and how often?" "What does that mean for the goals you're measured on this quarter?" "If nothing changes in the next six months, what happens?" "Has anyone above you noticed this, or felt it?" Impact is where a vague annoyance becomes a number a buyer can take to their boss. Get the number in their words, not yours.

Group 4

Decision process, is this deal real

Plenty of good discovery dies because nobody asked how a decision actually gets made. "Walk me through how a purchase like this gets approved at [company]."

"Besides you, who else would weigh in on a decision like this?" "What's worked, or not worked, the last time you brought in a tool like this?" "What would need to be true for you to move forward?" "Is there a budget set aside for this, or is that part of the conversation?" "What's your timeline, is this a this-quarter thing or a someday thing?" These are the questions reps skip because they feel pushy. They are not pushy. They are how you find out whether to spend the next month on this deal.

Discovery is mostly listening. The question is one sentence. Everything that matters is in the answer, so ask, then get out of the way.

The Lateral team

Mistakes that kill good discovery

The first is happy ears, hearing one yes and racing to a demo before you've found real pain or a real timeline. The second is stacking questions: asking three at once so the prospect picks the easy one and you lose the hard one. Ask one, wait, then go deeper on what they said.

The third is treating it like a checklist. If you're reading questions off in order without reacting to the answers, the prospect feels processed, not heard. The list is your map, not your script. Follow the tension in their answers, not the order on the page.

Frequently asked

What are the best discovery call questions?: The best ones move from situation (how things work today) to problem (what's broken) to impact (what it costs) to decision process (who decides and when). A strong example from each: "Walk me through how your team handles this today," "Where does that break down," "What does that cost you when it does," and "How does a purchase like this get approved here." Pick the four or five that fit the deal rather than asking all of them.
How many questions should I ask on a discovery call?: Fewer than you think, four to six strong ones, asked deliberately, with real listening between them. A discovery call is not a survey. If you're rattling through fifteen questions, the prospect feels processed and you're not going deep on anything. One good impact question, fully explored, beats five surface ones.
What's the difference between situation and problem questions?: Situation questions map the current state, what tools, what process, who's involved. They're low-threat and warm the prospect up. Problem questions go after the friction, where it breaks, what's frustrating, what triggered the call. Situation is the setup; problem is where discovery actually starts. Don't spend the whole call in situation.
How do I ask about budget without killing the deal?: Frame it as part of mapping the decision, not a demand. "When a purchase like this gets approved here, is there usually a budget set aside, or is that part of the conversation?" That phrasing makes it easy to answer honestly either way. The mistake is avoiding the question, a deal with no budget path is one you want to find out about early, not at the end.