Best Practice•2026-06-23•9 min read

70+ Sales Discovery Questions to Uncover Real Pain (2026)

Team Laxis

Laxis Team @ Laxis

A rep gets on a call, runs through a tidy list of questions, hears "yeah, that's a challenge for us," and books a demo. Two weeks later the deal goes dark. Nobody was lying. The rep just never found out whether the problem actually hurt enough to change anything.

That gap is what good sales discovery questions exist to close. Discovery is the part of the deal where you find out whether there's a real, quantified problem, who has to sign off on solving it, and how this company actually buys things. Get that right and the demo writes itself. Get it wrong and you're forecasting a deal that was never real. In one survey, roughly 60% of sales leaders blamed poor discovery as the leading cause of lost deals — not pricing, not the competitor, discovery.

So this isn't just a list to copy-paste. It's 70-plus questions grouped by what they actually uncover, plus how to run discovery so the questions do their job. Skip to the categories if you want the questions, but the technique section is where most reps are losing deals.

Why discovery is where deals are won or lost

Here's the uncomfortable part. Gong studied more than 500,000 discovery calls and found that reps who won deals asked around 15 to 16 questions, while reps who lost asked closer to 20. Asking more questions didn't help — past a point it hurt, because the call started feeling like a form. What separated winners was what they did with the answers: they followed the thread, quantified the pain, and let the buyer talk. The optimal talk-to-listen ratio on those calls landed around 43 to 46% talking for the rep. If you're doing most of the talking on a discovery call, you're pitching, and pitching too early is how you talk yourself out of the sale.

The goal of discovery is not to describe your product. It's to leave the call with two things: a quantified problem (in dollars, hours, or risk) and a map of how the buyer makes this decision. If you don't have both, you don't have a qualified deal — you have a nice conversation. Everything below is built to get you those two things.

Questions that map the current situation

Start wide. You need a picture of how things work today before you can find what's broken. These are low-threat, easy to answer, and they set up every harder question later. Don't rush them.

Current situation and state

Walk me through how your team handles this today, start to finish.
What tools or systems are you using for it right now?
How long have you been doing it this way?
Who's involved in that process day to day?
How often does this come up — daily, weekly, once a quarter?
What's working well about the current setup? (Yes, ask this — it tells you what not to threaten.)
What prompted you to take this call now, as opposed to six months ago?
Have you tried to fix this before? What happened?
If nothing changed, would that be a problem, or is this a "nice to have"?
How does this connect to the goals your team is measured on this year?

That last pair matters more than it looks. "What prompted you to take this call now" surfaces the trigger event — the thing that turned a background annoyance into a priority. No trigger usually means no urgency, and no urgency means the deal stalls no matter how good your product is.

Questions that uncover pain and quantify impact

This is the heart of discovery. Anyone can get a buyer to admit something is "a bit of a pain." Your job is to find out how much it actually costs and what happens if it isn't fixed. Pain the buyer can't put a number on rarely gets budget.

Pain and impact

Where does the current process break down most often?
What's the most frustrating part of it for the people doing the work?
When it goes wrong, what's the knock-on effect downstream?
Who else in the company feels this pain, and how does it show up for them?
Is this getting better, worse, or about the same over the last year?
What have you had to give up or work around because of it?

Now quantify. Once they've named a problem, don't move on — dig in with follow-ups that force a number.

Quantifying follow-ups

Roughly how many hours a week does your team lose to this?
If you put a dollar figure on it, what would that be — even a rough one?
Is the cost mostly in time, money, or missed opportunity?
How many deals, tickets, or hires did this affect last quarter?
What's it costing you to not solve this — and what's that number a year from now?
If you could wave a wand and fix it tomorrow, what would that be worth to you?
Who feels that cost most — you, your boss, the finance team?

The phrasing "is the cost mostly in time, money, or missed opportunity" is a favorite because it's almost impossible to dodge. The buyer has to pick, and whichever they pick tells you how to frame everything after. That's the "I" in MEDDPICC — Identify Pain — done properly, with metrics attached.

Tip: Quantify before you sympathize. When a buyer describes a problem, the instinct is to nod and say "totally, we hear that a lot." Resist it. Instead ask, "Help me understand the scale — what's that costing you?" You can only build a business case around a number, and the buyer will use that same number to sell the deal internally when you're not in the room.

Questions about goals and the desired outcome

Pain tells you what they're running from. Goals tell you what they're running toward — and a good deal needs both. These questions also give you the language for your proposal, because the buyer just handed you their definition of success.

Goals and desired outcome

If we're talking a year from now and this went great, what's different?
What does success look like in a number you'd actually report on?
What would need to be true for this to be a clear win for you personally?
Is there a specific target or metric your team is chasing this quarter?
How would solving this change your day-to-day?
What's the upside if you get this right — and who notices?
Are there adjacent problems you'd hope to knock out at the same time?

"What does success look like in a number you'd actually report on" is doing quiet MEDDPICC work — that's your Metric. If they can't name one, you've learned something important: this may not be a funded priority yet.

Questions that reveal the decision process and stakeholders

Deals die in the buying process far more often than in the product evaluation. Collaborative discovery calls that include multiple stakeholders close at meaningfully higher rates, so finding out who else matters early is not optional. This is where you map the Economic Buyer, the Champion, the Decision Process, and the Paper Process — the guts of MEDDPICC.

Decision process and stakeholders

Walk me through how a decision like this usually gets made here.
Besides you, who else would weigh in before this moves forward?
Who ultimately signs off — and who could quietly kill it?
Has your team bought something like this before? How did that go?
What would the people above you want to see before they said yes?
Is there a formal evaluation, a security review, or procurement involved?
Who'd be against this internally, and why?
What's derailed a project like this for you in the past?
If you and I agreed today, what happens next on your side?

"Who could quietly kill it" is blunt on purpose. Most reps only ask who the decision maker is and miss the person in security, legal, or finance who never joins a call but can veto everything. Naming the blocker early is how single-threaded deals become multi-threaded ones.

Tip: Ask "why does that matter?" three times. Buyers give you surface answers first. When someone says "we need better reporting," don't write it down and move on — ask why. "So my VP stops asking me for updates." Why does that matter? "Because last quarter we missed a number and nobody saw it coming." Now you're at the real stake. The third "why" is usually where the deal actually lives.

Questions on budget, authority, and timeline

This is classic BANT territory, and the mistake is asking it like a customs officer. You don't need to interrogate — you need to know whether money exists, who controls it, and when. Phrase it as help, not a demand.

Budget, authority, and timeline

Have you set money aside for this, or is that still to be worked out?
Is there a budget owner for this, or would it come from a shared pool?
What have you spent on similar problems before — ballpark?
Who has to approve a spend at this level?
Is there a date this needs to be solved by, and what's driving it?
What happens if this slips a quarter — real consequence, or life goes on?
Where does this sit against everything else on your plate right now?
Is there a contract renewal, budget cycle, or event we should be aware of?

"What happens if this slips a quarter" is the honesty test. If the answer is "life goes on," you have a real problem with urgency — better to know now than to forecast a deal that closes six months late. If you want the full framework, our guide to BANT and our breakdown of MEDDPICC go deeper on where each of these questions fits.

Questions about competition and alternatives

Your real competitor is often "do nothing." These questions surface who else the buyer is looking at, what standard you're being measured against, and whether inertia is your biggest threat.

Competition and alternatives

What other options are you weighing, including building it yourselves?
Have you looked at any specific vendors so far? What did you think?
What would make you choose one option over another?
What's your honest fallback if you don't buy anything this year?
What would a competitor have to get wrong for you to rule them out?
Is there an incumbent tool you'd be replacing, and who championed it?

"What would make you choose one option over another" hands you the Decision Criteria directly. Write down their exact words — those are the boxes your proposal has to check, in the order the buyer ranks them.

Questions that close the discovery

End the call deliberately. These questions confirm you heard right, catch anything you missed, and set a real next step instead of a vague "we'll be in touch."

Closing the discovery

What haven't I asked about that I should have?
Of everything we covered, what matters most to you?
On a scale where this is a genuine priority vs. a maybe, where does it sit?
Who else should be in the room for the next conversation?
If the next step made sense to you, what would it be?
Is there any reason this wouldn't move forward that we haven't talked about?

"What haven't I asked about" is the most underrated question in sales. Buyers routinely raise the thing that actually matters when you give them the floor at the end.

The technique that makes the questions work

Questions are only as good as how you ask them. Four habits separate reps who run discovery from reps who read questions off a script.

Ask open, not closed

"Is that frustrating?" gets you a yes. "Walk me through what that's like" gets you a story with details you can dig into. Open questions start with what, how, or "walk me through." Save yes/no questions for confirming, not exploring.

Chain your follow-ups

The gold is never in the first answer. It's in the second and third. Treat every answer as a door: "Tell me more about that." "Why does that matter to you?" "What's the impact of that?" The best reps ask fewer distinct questions but go three layers deep on each one.

Actually listen

Aim to talk less than half the time. That means leaving silence after a question instead of filling it, and reflecting back what you heard — "so if I've got this right, the real issue is X, not Y." Buyers correct you when you're wrong and trust you more when you're right. Both are wins.

Avoid the three classic mistakes

Interrogating. Firing questions in sequence with no reaction turns discovery into a deposition. React, connect, then ask the next thing.
Happy ears. Hearing "that sounds great" and logging it as buying intent. Enthusiasm isn't a metric. Push for the number.
Pitching too early. The moment you hear a problem you can solve, the urge to launch into features is enormous. Don't. You haven't quantified it yet, and a demo before discovery is a guess.

The bottom line

The best reps aren't collecting answers to fill in a scorecard. They're building a case the buyer will make for them when the room is full of people who never took your call. That's the real test of a discovery question: not "did I get an answer," but "did I get something my champion can repeat to their CFO." If the number, the stakeholder map, and the timeline can survive being retold without you there, you ran good discovery. If they can't, you ran an interview.

Frequently asked questions

How many questions should I ask on a sales discovery call?

Gong's analysis of more than 500,000 discovery calls found that reps who won deals asked roughly 15 to 16 questions, while reps who lost asked closer to 20. More isn't better past a point. Aim for depth over volume: a dozen or so strong questions with real follow-ups beats a rapid-fire checklist that makes the call feel like an interrogation.

What is the best sales discovery question to uncover pain?

There's no single magic question, but the highest-impact move is quantifying pain the buyer already named. After they describe a problem, ask what it's costing in time, money, or missed opportunity, and what happens if nothing changes for another year. That turns a vague complaint into a business case with a number attached.

How is a discovery call different from a qualification call?

Discovery is about understanding the buyer's situation, pain, goals, and buying process. Qualification is deciding whether the deal is worth pursuing. Frameworks like BANT and MEDDPICC are qualification structures, but you gather the evidence to fill them in during discovery. In practice, good discovery questions do both at once.

What is the ideal talk-to-listen ratio on a discovery call?

Gong Labs data points to roughly 43 to 46 percent talking for the rep and 54 to 57 percent for the buyer on strong discovery calls. Lost deals skew toward the seller dominating the conversation. If you're talking more than half the time on a discovery call, you're probably pitching instead of learning.

How do I remember everything a buyer says in discovery?

You mostly can't from memory, which is why the buyer's exact words get lost between the call and your CRM. Structured note-taking during the call helps, and an AI meeting assistant like Laxis records, transcribes, and summarizes the conversation, then pulls out pain, next steps, and action items so your qualification is based on what was actually said.