Sales discovery questions: 50 examples, a call framework and practice

Discovery exists to understand before proposing. A prospect who has put their own problem, its cost and their deadline into words is already half convinced; a prospect who gets a recited presentation will simply compare prices. Yet discovery is often rushed, for three recurring reasons.

• Product pressure. You know the answer and cannot wait to show it.
• Fear of silence. After a short answer, you fill the gap instead of following up.
• The questionnaire. You run through a list without listening, and the prospect feels interrogated rather than helped.

A good discovery call aims for four outcomes: a problem stated by the customer, a measurable stake, a clear picture of who decides and how, and a dated next step. Everything else is comfort.

These three acronyms appear in every sales team, and they are often confused. They do not serve the same moment.

SPIN tells you how to ask: it gets the customer to state the cost of their problem. BANT and MEDDIC tell you what you need to know to decide whether to pursue an opportunity. The MEDDICC variant adds a second C for Competition.

A classic trap is to use BANT as a form. Analyses of the method point out that it can turn into a one-way, seller-centered interrogation that discards prospects too quickly. The remedy is simple: use SPIN to run the conversation, and BANT or MEDDIC as a mental checklist filled in as you go, not in a burst of questions.

A framework keeps you from wandering without turning the call into a questionnaire. Five steps are enough for a thirty to forty-five minute meeting.

1. Frame (3 minutes). Purpose of the call, duration, agenda, and the prospect's agreement on that plan.
2. Understand the context (7 minutes). Situation, organization, current tools.
3. Explore the problem (10 minutes). Difficulties, causes, past attempts, then quantified implications.
4. Decision (7 minutes). Stakes, decision makers, criteria, budget, timeline.
5. Close (5 minutes). Restate what you understood, get the customer's confirmation, set a dated next step.

Timings are indicative. The order is what matters: raise budget only once value has been expressed, and propose nothing before you have restated the problem in the customer's own words.

These sixteen questions open the meeting. The first eight set the scene; the next eight bring out what is not working.

Situation and context (8 questions)

1. Could you tell me about your role and your team?
2. How does this process work today, end to end?
3. Which tools or suppliers do you currently use for it?
4. How long have you worked this way?
5. How many people are involved, and on which sites?
6. What has changed in your business over the last twelve months?
7. How do you measure success on this topic today?
8. What made you get in touch now?

Intent. Gather facts without wearing the prospect out. A few questions are enough if you prepared the meeting (website, news, the contact's profile).

Common mistakes. asking things that are on the website, asking too many (the prospect switches off), or talking about context forever without reaching the problem.

Problem (8 questions)

1. What is not working as well as you would like?
2. Where do you lose the most time or energy?
3. How often does this problem occur?
4. What is the main cause, in your view?
5. What have you already tried to fix it?
6. Why was that not enough?
7. Who in the organization feels this problem most strongly?
8. On a scale of 1 to 10, how high a priority is it this year?

Intent. Get the customer to name the problem in their own words. A problem the prospect recognizes and ranks is worth more than a need the seller assumes.

Common mistakes. offering a solution at the first difficulty, suggesting the problem ("you must be struggling with..."), or stopping at the symptom without looking for the cause.

These fourteen questions are what separates a seller from an order taker: they give the problem a cost, then have the customer describe the value of a solution.

Implication and stakes (8 questions)

1. What consequences does this have on your business?
2. How much time do you and your teams spend on it each week?
3. What does it cost you, in euros or in missed opportunities?
4. What effect does it have on your customers or your employees?
5. What happens if nothing changes over the next twelve months?
6. Who else is affected, and how?
7. Which of your leadership's objectives does this put at risk?
8. How does this affect the way you are evaluated?

Intent. Have the customer measure the cost of the status quo themselves. This step creates urgency without pressure and prepares the discussion on price.

Common mistakes. inventing figures in place of the customer, chaining questions without restating, or dramatizing until the prospect feels manipulated.

Need-payoff (6 questions)

1. If this problem were solved, what would change for you in practice?
2. Which benefit would matter most to you?
3. How will you know the project has succeeded?
4. Which indicator should move, and by how much?
5. What would the ideal solution look like?
6. What could prevent you from putting it in place?

Intent. Have the customer describe the value of a solution before any presentation. Their answers become the criteria you build your proposal around.

Common mistakes. asking too early, before the problem has been measured, or noting the answer without using it afterwards in your argument.

These twenty questions cover what BANT and MEDDIC try to establish: who decides, on which criteria, with what resources and by when. They come after value, not before.

Decision makers and approval process (6 questions)

1. Who else will be involved in this decision?
2. How is a decision like this made at your company?
3. Who has the final say, and who can block it?
4. Who will use it day to day?
5. Is there someone internally who is championing this project?
6. Would you be comfortable with us also speaking to finance or procurement?

Intent. Map the buying committee and find an internal supporter. The economic buyer (the person who signs off the budget) is not always the person you are meeting.

Common mistakes. assuming your contact decides alone, asking "who decides?" too bluntly, or ignoring users and procurement.

Decision criteria (5 questions)

1. Which criteria matter most in your choice?
2. Among them, which are essential and which are nice to have?
3. Have you seen other solutions, and what did you think of them?
4. What would make you rule out an offer?
5. Which technical, legal or security constraints must we meet?

Intent. Learn the customer's reading grid so you do not argue past it. A question about competitors can be asked without putting the prospect on the defensive.

Common mistakes. disparaging competitors, discovering a security constraint at signing time, or not separating essential from nice to have.

Budget (5 questions)

1. Is a budget already set aside for this topic?
2. How is an investment of this kind funded at your company?
3. What range do you have in mind, or at least what order of magnitude would be acceptable?
4. Who approves the spend, and above what amount?
5. How did you fund a comparable project in the past?

Intent. Check that the project can be funded and understand the process, rather than extracting a number. Tie the question to the cost of the status quo already expressed.

Common mistakes. opening with budget, announcing your price before knowing the stakes, or accepting a "we'll see" without asking how budget gets released.

Timeline (4 questions)

1. Is there a deadline that shapes this project?
2. What happens if the decision slips by three months?
3. What steps come before signature, and in what order?
4. When do you want the solution to be operational?

Intent. Separate real urgency (a deadline, an event) from mere interest. A timeline rebuilt backwards gives you the steps to validate.

Common mistakes. setting an arbitrary closing date yourself, or treating "by the end of the year" as a commitment.

Four kinds of questions damage a discovery call. Here is how to fix them.

• The closed-question burst. "Do you have a budget? Are you the decision maker?" Prefer "How is a decision like this made at your company?"
• The leading question. "You're not happy with your current supplier, are you?" Prefer "What works well and less well with your current supplier?"
• The double question. "Who decides and what is the budget?" The prospect answers the easier half. One question, one topic.
• The "why" question. It can sound like a reproach. "What led you to...?" or "How did you come to...?" yield the same information.

In every case, a question is only worth what follows it: listening, restating and following up. The worst use of a question bank is to read it in order. Objections that come up along the way are handled with the method in our guide to sales objection handling.

Knowing what to ask is not enough: discovery is won or lost in how you react to the answers. An AI roleplay lets you rehearse without exposing a real prospect. In AI-Coaching, the counterpart is a configurable persona, and your own documents (offer, role sheets, cases) can enrich the scenario. The platform offers text and voice simulations; the free demo lets you try it in text or voice.

The quiet buyer

They answer with a word or half a sentence. Goal: open them up without pushing. Skills to work on: an open question rather than a closed one, a restatement to show you heard ("If I understand correctly, the issue is mostly..."), two seconds of silence after the answer, then a clarifying question ("Could you give me a recent example?").

The rushed buyer

They check the time, interrupt and ask the price in the second minute. Goal: get enough to move forward in ten minutes. Skills to work on: announce the agenda and the time needed, prioritize two or three implication questions, negotiate a second conversation instead of rushing this one.

The talkative buyer

They tell the company's history, digress and answer sideways. Goal: keep the thread without offending them. Skills to work on: pick up the useful sentence, redirect with a bridge ("That's very helpful. To move forward, I'd like to go back to..."), ask questions that bound the answer.

A typical session

1. Pick a persona and a goal (for example "get the cost of the problem in euros").
2. Play the meeting, then read the detailed report and the AI observer's feedback; the observer can also coach in real time.
3. Replay with the same persona, then with a harder profile.
4. Group several scenarios into a pathway or playlist, and track progress in the skills map.

To see the principle, launch the AI roleplay demo, free and with no account. The overall framework is described on the AI simulator for sales teams page.

Score each criterion from 1 to 4 (1: needs work, 4: mastered) after a real meeting or a practice session, based on observable signals. Track the scores over time: progress per criterion says more than an overall mark. The same skills-tracking logic applies at team level with the sales skills map.

A total out of 32 only means something when compared with your own earlier sessions. Once discovery is solid, the next step is turning it into a proposal and then an agreement: see our guide to sales negotiation training with a virtual buyer.