Back to Blogs

60 Sales Discovery Questions for Every Stage of the Sales Cycle

A practical perspective for connecting this idea to your revenue team’s next move.

Sales discovery questions are the questions a seller asks to understand a buyer’s situation, problem, cost of inaction, decision process and timeline before proposing anything. Good discovery questions are open, specific to the buyer and spread across the call. Below are 60 of them, grouped by what each one helps you learn, with follow-ups and a call structure.

Last updated: 20 October 2026

Use this list as a menu, not a script. Gong’s analysis of more than 519,000 recorded B2B sales calls found the greatest chance of success at 11 to 14 targeted questions per discovery call, with top performers spreading their questions through the conversation while average reps front-loaded them (Gong Labs, first published June 2017, updated March 2026). So pick the dozen that matter most for this buyer, and keep the rest for later calls and other stakeholders.

What is a discovery call?

A discovery call is an early conversation in which the seller learns whether there is a real problem worth solving, whether the buyer can solve it with you, and what it would take. Its output is not a demo booked; it is a shared, written understanding of the problem, its cost, who decides and what happens next.

That understanding matters because buying decisions involve many people. Forrester’s 2026 buying research found that a typical buying decision includes 13 internal stakeholders and nine external influencers (Forrester, 21 January 2026). What you learn from the first contact has to survive being retold to people you may never meet.

How to structure a discovery call

  • Open and set the agenda. Confirm the time, say what you want to learn, and ask what they want to get out of the call. “By the end, I’d like us both to know whether this is worth a second conversation. Does that work?”
  • Confirm your research. Check what you think you know about their role and situation rather than reciting it.
  • Go from broad to specific. Start with goals and the current process, then narrow to where it breaks and what that costs.
  • Quantify impact. Turn the problem into time, money, risk or missed targets, in the buyer’s own numbers.
  • Map the decision. Who else is involved, how they decide, and what has to be true for a yes.
  • Summarise and agree a next step. Play back what you heard in two or three sentences, ask what you missed, and book a specific next step with the right people.

Spread the questions. If you ask ten in a row in the first ten minutes, the call becomes an interview; mixing questions with short, relevant observations keeps it a conversation.

Situation and context questions

Goal: understand the buyer’s world and validate your research. Keep these short; buyers dislike answering questions their website already answers.

  • “How is your team set up today, and where does your role sit in it?”
  • “I saw [recent change, hire, launch or announcement]. How is that affecting your team’s priorities?”
  • “Walk me through a typical week. Where does most of your team’s time go?”
  • “Which tools and systems does your team rely on most for this work?”
  • “What has changed in the last six to twelve months that made this worth looking at now?”
  • “Who are your customers for this process, inside or outside the company?”
  • “How do you measure whether this part of the business is going well?”
  • “What does your leadership ask you about this area most often?”

Goals and success questions

Goal: find out what the buyer is trying to achieve and how they will judge success. These answers become your metrics later.

  • “What are the two or three results you are personally measured on this year?”
  • “If we met in six months and this had gone well, what would be different?”
  • “Which of those goals is most at risk right now?”
  • “How far are you from where you need to be on that number?”
  • “Who set that target, and what happens if it is missed?”
  • “What would your manager need to see to call this project a success?”
  • “Are there goals for next year this needs to support?”
  • “What have you already tried to move that number?”

Pain and current-process questions

Goal: find the gap between where they are and where they want to be, and exactly where the current process breaks.

  • “Can you walk me through how this works today, step by step?”
  • “Where does that process usually break down?”
  • “Can you give me a recent example where it went wrong?”
  • “What do people do to work around it today?”
  • “How much time does your team spend on that workaround in a normal week?”
  • “Which part of this frustrates your team the most?”
  • “Have you tried to fix this before? What happened?”
  • “What do you think is causing it, underneath?”
  • “Is this the same for every team or region, or worse in some?”
  • “If you could change one thing about how this works, what would it be?”

Impact and cost-of-inaction questions

Goal: make the problem concrete and measurable, in the buyer’s terms rather than yours.

  • “What does this problem cost you today, in time, revenue or risk?”
  • “How does it show up in the numbers you report on?”
  • “Who else feels the effect of this, and how?”
  • “What happens if nothing changes for the next twelve months?”
  • “Is this costing revenue, or mainly time and effort?”
  • “How does this affect your customers’ experience?”
  • “How urgent is this compared with the other projects competing for your team’s time?”
  • “What would solving it make possible that you can’t do today?”

Decision process and stakeholder questions

Goal: understand who decides, how, and in what order. This is where many deals that look healthy are lost later. A stakeholder map template helps you record the answers.

  • “Besides you, who would be involved in a decision like this?”
  • “Who has the final say on whether this gets funded?”
  • “How have you made decisions like this in the past? What were the steps?”
  • “Who could slow this down or stop it, even if they are not leading it?”
  • “What criteria will you use to compare options?”
  • “Which of those criteria matter most to each person involved?”
  • “Are IT, security, legal or procurement usually involved? At what point?”
  • “Who would use this every day, and how will their view be gathered?”
  • “Is there anyone who would prefer things stay as they are?”
  • “Would it help if I put together a short summary you could share internally?”

Questions 39 and 40 are worth extra time because buying groups often disagree. In a Gartner survey of 632 B2B buyers, 74% of buyer teams showed unhealthy conflict during the decision, and groups that reached consensus were 2.5 times more likely to report a high-quality deal (Gartner, 7 May 2025). Asking each stakeholder what matters to them surfaces that conflict while you can still help resolve it.

Question 36 matters more than its length suggests. The economic buyer is not always the most senior person on the call, and our guide to economic buyer mistakes covers how to find and engage them.

Budget, paper process and timing questions

Goal: understand how money is approved and what has to happen before a contract can be signed.

  • “Is there budget set aside for this, or would we need to build a business case together?”
  • “How are purchases of this size usually approved?”
  • “What does your procurement or contract process look like, and how long does it usually take?”
  • “Are there security, privacy or compliance reviews we should plan for?”
  • “Is there a date or event that this needs to be in place by?”
  • “What else is competing for the same budget?”

Competition and alternatives questions

  • “What other options are you considering, including doing nothing or building it in-house?”
  • “What do you like about the approach you use today?”
  • “What would a solution have to do for you to choose it over the alternatives?”
  • “Have you used a tool like this before? What worked and what didn’t?”
  • “What would make you decide to keep things as they are?”

Next-step and confirmation questions

  • “Based on what we discussed, what would be a useful next step for you?”
  • “Who else should be in that next conversation?”
  • “What would you need to see or hear to move forward?”
  • “What could get in the way between now and a decision?”
  • “Can I summarise what I heard, and you tell me what I missed?”

Follow-up questions that get past the first answer

The first answer to a discovery question is usually the safe one. Short follow-ups get to the real one:

  • “Can you tell me more about that?”
  • “What makes you say that?”
  • “Can you give me an example?”
  • “How did that affect you personally?”
  • “What happened next?”
  • “Is that the main issue, or is there something underneath it?”

Discovery questions mapped to MEDDPICC

If your team qualifies with MEDDPICC, discovery is where most of the fields get filled. This table shows which questions above feed each letter; our MEDDIC and MEDDPICC guide explains each one.

MEDDPICC element

What you need to learn

Questions from this list

Metrics

The measurable result the buyer wants

9, 10, 12, 27, 28

Economic buyer

Who funds and approves the decision

36, 13, 46

Decision criteria

How options will be compared

39, 40, 53

Decision process

The steps and people between now and a decision

35, 37, 41

Paper process

Approvals, procurement, security and legal steps

47, 48

Identify (implicate) pain

The problem and its cost

17-24, 30

Champion

Who will sell internally when you’re not there

43, 44, 57

Competition

Alternatives, including doing nothing

51-55

Recording the answers matters as much as asking. Ebsta reports that only 36% of deals that pass discovery carry full qualification data (Ebsta, page last updated 26 July 2025; it does not publish its sample or method).

Discovery questions by stakeholder

Stakeholder

What they care about

A question to ask them

Economic buyer (CFO, VP, CRO)

Business outcome, risk, return

“What would make this one of the projects you fund this year?”

Day-to-day user

Ease of use, time saved, fewer workarounds

“What part of your week would you most like to get back?”

IT or security

Integration, data handling, access control

“What does a new tool need to pass before you’re comfortable with it?”

Procurement

Terms, process, comparison

“What does a clean evaluation look like from your side?”

Champion

Their own credibility and goals

“What would make this a win for you personally?”

Common discovery mistakes

  • Pitching too early. If you start presenting before you can restate the buyer’s problem in their words, you are guessing.
  • Interrogating. Firing questions back to back, in the same order on every call, makes buyers guarded. Spread them and react to the answers.
  • Leading questions. “Wouldn’t it be great if…” gets agreement, not information.
  • Single-threading. Learning everything from one contact leaves you blind to everyone else in the decision.
  • Not writing it down. Answers that live in a rep’s notebook can’t be coached, forecast or shared with the buyer.

Practising these conversations before live calls helps: see how to close a sale with AI practice, which covers moving from diagnosis to a bounded next-step ask.

What to do with the answers

Discovery answers are only useful if the buyer and your own team can see them. Three habits help:

  • Update the CRM the same day. Put metrics, the economic buyer, decision criteria and next steps in fields, not free-text notes.
  • Send a written recap. Summarise the problem, its cost, the people involved and the agreed next step, and ask the buyer to correct it.
  • Turn the timeline into a shared plan. A mutual action plan template lists every step, owner and date to a decision. A digital deal room can hold the recap, the plan and the documents a buyer asked for (security answers, a business case) in one link they can forward to colleagues.

Frequently asked questions

How many questions should you ask on a discovery call?

Gong’s analysis of more than 519,000 recorded B2B calls found the best results at 11 to 14 targeted questions, spread through the call rather than front-loaded. Treat that as a guide: a well-chosen dozen beats a script of 30.

What are the best discovery questions to ask?

The best questions are open and specific to the buyer: “Can you walk me through how this works today?”, “Where does it break down?”, “What does that cost you?” and “Who else would be involved in a decision like this?” cover the process, the pain, the impact and the decision.

What is the difference between discovery and qualification?

Discovery is the conversation where you learn about the buyer’s situation, problem and decision. Qualification is the judgement you make from what you learned: whether this is a real, winnable opportunity worth investing in. Frameworks such as BANT and MEDDPICC structure that judgement.

How long should a discovery call be?

Long enough to understand the problem, its cost and the decision process; for most B2B sales that means a scheduled call rather than a quick chat. If the buyer’s situation is complex, plan for more than one discovery conversation, with different stakeholders.

Should you ask about budget on the first call?

Yes, but frame it as how decisions get funded rather than how much they have: “Is there budget set aside, or would we need to build a business case together?” The answer tells you whether you’re in a planned purchase or need to help create one.

Want discovery answers to turn into a plan your buyer can see? See Revspire’s deal rooms.

Sources

Read more Revspire articles