45 Sales Discovery Questions That Actually Qualify a Deal

Good sales discovery questions do one of two things: uncover the cost of a problem, or reveal how the buying decision will actually get made. Questions that do neither are filler, and buyers can tell.

Below are 45 questions organized by the six MEDDIC criteria, so each one maps to a specific qualification gap rather than sitting in an undifferentiated list. After that, the part most discovery guides skip: which of these you should no longer be asking at all, because your buyer answered them before the call started.

---

What Separates a Good Discovery Question from a Bad One

Three tests, applied to any question before it earns a place in your call:

1. Does the answer change what you do next? If a yes and a no lead to the same next step, the question is decoration.
2. Does it ask about their world, not your product? "What happens today when a rep needs that data?" beats "how important is real-time data to you?" The first gets a story; the second gets a polite score out of ten.
3. Could they answer it honestly without commitment? Buyers deflect questions that feel like they are being sold to. Process questions asked too early read as presumptuous.

The most common failure is asking questions whose answers you could have looked up. Asking a VP of Sales how many reps they have, when it is on their LinkedIn, spends your credibility in the first two minutes.

---

Metrics: Quantify the Value

You are looking for the buyer's own numbers, not yours.

1. How are you measuring success for this area today?
2. What does that number look like right now?
3. Where would it need to get to for this to be worth doing?
4. What is the gap costing you per month or per quarter?
5. Who reports on that number, and to whom?
6. If nothing changes this year, what happens to that metric?
7. Have you tried to fix this before? What did that cost you?
8. What would a good outcome look like twelve months after buying something?

The follow-up that does the real work: "How did you arrive at that number?" It separates a considered figure from one invented for your benefit.

---

Economic Buyer: Find Who Releases the Money

9. Who else needs to be comfortable with this before it moves forward?
10. Whose budget would this come out of?
11. Has that person been part of a purchase like this before?
12. What does the approval look like at this size of spend?
13. Is this money already allocated, or would it need to be found?
14. What would they need to see from us to be confident?
15. When were you planning to introduce us to them?

Question 15 is deliberately phrased as when, not whether. It assumes access is normal, which it is, and surfaces resistance early if it is not.

---

Decision Criteria: Learn the Standard You Are Judged Against

16. What are the must-haves versus the nice-to-haves for you?
17. How will you compare the options you are looking at?
18. Is there a formal evaluation, or is this a judgment call?
19. What would rule a vendor out immediately?
20. Which of those requirements is genuinely non-negotiable?
21. Are there security, compliance, or procurement requirements we should know about now?
22. Who set those criteria?
23. What did the last vendor you evaluated get wrong?

Question 23 earns its place: buyers describe their real criteria more honestly when talking about someone else's failure than when listing requirements.

---

Decision Process: Map the Path to Signature

24. Walk me through what happens between now and a decision.
25. Who is involved at each of those steps?
26. What typically slows a purchase like this down here?
27. Does this need legal, security, or procurement review?
28. Have you bought something similar recently? How did that go?
29. What is driving the timeline you have in mind?
30. What happens if this slips past that date?
31. Is there a budget cycle or renewal we should be working around?

Question 30 is the honesty test. If nothing happens when the date slips, the date is a preference, not a deadline, and your forecast should reflect that.

---

Identify Pain: Find the Cost of Inaction

32. What made you start looking at this now?
33. How are you handling it today?
34. What breaks when that workaround fails?
35. Who feels that most day to day?
36. How long has this been a problem?
37. What have you already tried?
38. What happens if you do nothing for another six months?
39. On a list of everything your team is dealing with, where does this sit?

Question 39 is the most useful question in this guide. A real problem that ranks seventh on the priority list will not get funded, and knowing that in week one is worth more than a polite yes.

---

Champion: Find Someone Who Will Sell for You

40. What would success with this mean for you personally?
41. Who else internally shares this problem?
42. Has anyone here pushed for something like this before?
43. What would you need from me to make the case internally?
44. Who is likely to object, and what would their objection be?
45. If this stalls, what would most likely be the reason?

Question 45 does two jobs: it gives you the real risk, and a genuine champion answers it candidly while a friendly contact deflects.

---

The Questions You Should Stop Asking

Here is the problem with every discovery question list, including this one: it assumes the first time you learn anything about the buyer is on the call.

That has not been true for years. By the time a B2B buyer books a meeting, they have read your site, compared you to two competitors, and formed most of their decision criteria. Asking them to recite that from scratch is asking them to repeat work they already did, and it is why "so, tell me about your situation" gets a flat answer.

The questions that survive this shift are the ones the buyer could not have answered on their own: the cost of inaction, internal politics, the real priority ranking, who objects. The ones that do not survive are the factual and criteria questions - integrations, compliance, pricing bands, timeline - which buyers reveal freely when they are researching, and grudgingly when interrogated.

This is the gap Parsley is built for. Reps put a Parsley link on their LinkedIn profile and in outbound emails; the presales agent answers prospects' questions from the team's own sales docs, and the questions the prospect asks are themselves qualification data. Someone asking "does this work with HubSpot, and are you SOC 2 compliant" has answered questions 16 through 21 without being asked. Someone asking "I would need to get this past our head of RevOps" has answered question 9.

Those signals land in the CRM as detected MEDDIC criteria, each stored with the quote that triggered it, before the first call. Discovery then starts where it should: on the four or five things the conversation did not cover, which are almost always the pain and champion questions - the ones that need a human anyway.

For the mechanics of capturing qualification this way, see MEDDIC lead qualification without interrogation and how it produces first-party buyer intent.

---

Four Discovery Mistakes

• Asking questions you could have researched. Headcount, funding, tech stack, and org structure are all findable. Spending call time on them signals you did not prepare.
• Running the list. These 45 are a bank, not a script. Picking eight that match the gaps in this specific deal beats working through all of them.
• Accepting the first answer. "We want to improve efficiency" is where discovery starts, not where it ends. The second and third follow-up is where the real answer lives.
• Skipping the priority question. Reps qualify pain but not rank. A genuine problem sitting seventh on a VP's list loses to the six above it, and no amount of value selling changes that arithmetic.

---

Frequently Asked Questions

How many discovery questions should you ask on a first call?

Usually eight to twelve substantive questions with follow-ups, not a list of forty. The constraint is the buyer's patience: a first call should feel like a conversation with someone who prepared, not an intake form. Pick the questions that close your specific qualification gaps.

What are the best open-ended sales discovery questions?

The strongest are the ones that ask for a story rather than a rating: "walk me through what happens today when that breaks," "what made you start looking now," and "what happens if you do nothing for six months." Each produces detail a rating scale cannot.

What is the difference between discovery questions and qualifying questions?

Discovery explores the buyer's situation and problem. Qualification tests that situation against criteria to decide whether the deal is worth pursuing. In practice good discovery questions do both, which is why organizing them by a qualification framework like MEDDIC makes each one accountable to a decision.

Should you ask about budget on the first call?

Ask about value and authority first, budget second. "Whose budget would this come out of" is answerable early and tells you about the decision. "What is your budget" invites either a defensive non-answer or a number anchored below what they would actually pay.

How do you do discovery when the buyer has already researched you?

Skip what they have already worked out and go to what they could not. Buyers arriving with formed criteria find it patronizing to be walked through basics. If you can see the questions they asked before the call, discovery becomes gap-filling rather than starting from zero - which is faster for both sides and makes the call worth their time.

---

The Bottom Line

Discovery questions are only as good as the decisions they inform. Organized by MEDDIC, each question above closes a specific qualification gap, and a deal where you can answer all six criteria with the buyer's own words is a deal you can forecast honestly.

The shift worth making is on timing rather than technique. Buyers now do most of their evaluating before the call, so the reps who win are not the ones with the longest question list - they are the ones who already know which questions have been answered, and spend the call on the ones that have not.

Want the first half of discovery done before the call starts?

Try Parsley free ->