- Discovery questions produce the evidence; BANT or MEDDPICC is the scorecard that evidence fills in.
- 18 questions in five groups: situation and change, impact and cost of inaction, buying group and decision process, timeline and urgency, budget and alternatives.
- Every question comes with what a complete answer contains, so a manager can tell a real answer from a placeholder.
- Five checks confirm discovery actually happened: read the record, count buyer-side people, score one call per rep per week, compare close dates, check what the economic buyer has done.
- Red Hat reports a 50%+ increase in win rates on deals with 70%+ MEDDPICC completion (case study linked in the post).
A deal sits at 60% in your commit. Ask who signs it, what breaks for the buyer in Q1, or why now, and you get a shrug and a note from six weeks ago. That gap opened in discovery, and nobody sees it until the forecast call.
Sales discovery questions are the questions a rep asks early in a deal to establish the buyer's situation, the cost of leaving it alone, who decides, on what timeline, and against which alternatives. Below, 18 of them are grouped by what each one proves, with what a complete answer contains. Last comes the part most question lists skip: how you confirm those answers exist anywhere outside the rep's head.
What Are Sales Discovery Questions?
Sales discovery questions are open questions a seller asks in the first conversations of a deal to learn what the buyer is trying to change, what it costs them today, who has to agree, when it has to happen, and what they'd do instead. What they produce is evidence. Frameworks such as BANT or MEDDPICC are the scorecard; discovery is the conversation that fills it in.
That distinction matters for the person who owns the number. Stages record what the rep believes. Discovery answers record what the buyer said, and only one of those predicts whether the deal closes.
Why Discovery Decides Your Forecast
Deals advance on stage changes, and those don't cost anything. Your commit column fills with opportunities that cleared “Discovery complete” without anyone recording a buyer-side date, a named economic buyer, or a cost the buyer can quote. By the time that shows up in a manual pipeline review, the quarter's half gone.
Two findings frame the stakes. Gartner's B2B buying research finds that 99% of B2B purchases are driven by organizational changes, which makes “what changed?” the single question that separates a real project from a browsing exercise. And Red Hat, a Backstory customer, reports a 50%+ increase in win rates on deals with 70%+ MEDDPICC completion: the deals with complete qualification evidence won, and discovery is where that evidence comes from.
There's a prerequisite, too. Buyers answer hard questions for sellers they trust, so rapport-building questions come first and earn the right to ask the ones below.
18 Sales Discovery Questions, Grouped by What They Prove
Each group maps to one thing a qualified deal has to show. Under every question is what a complete answer contains, so a manager reviewing the deal can tell a real answer from a placeholder.
Situation and Change
- What changed in the business that put this on the agenda now? You're listening for a dated event: a reorganization, a missed quarter, a new executive, a system contract that ends in March.
- How does your team handle this today, step by step? You want the current process, the tools involved, and the roles that touch it, in order.
- Where does today's approach break, and how often? Listen for a frequency and a recent example. “Sometimes” is not an answer; “twice last month, including the Q3 close” is.
- Who else in the company feels this problem? Expect names or roles beyond your contact. Every one of them is a future thread in the deal.
Impact and Cost of Inaction
- What does this cost you in a quarter, in a number you report on? Qualified buyers attach the problem to a metric they own and give it a size. No number yet means the buyer hasn't done the math, and neither have you.
- What happens to your plan when nothing changes by that date? Tie the consequence to the event from the first question: a missed target, a renewal at risk, a headcount request denied.
- Which metric would your CFO look at to call this a success? You're after the metric and the target, in the buyer's words. That's the success criterion that goes in the proposal.
- Has anyone tried to fix this before, and what happened? Prior attempts show what the organization will tolerate and which objections you'll meet already formed.
Buying Group and Decision Process
- Who signs the contract, and who has to say yes before it reaches them? Complete means the economic buyer is named along with the approval chain, in sequence. “My boss” is a placeholder.
- Who could stop this without a vote? Security, legal, procurement, a skeptical VP in a neighboring team. Each one named is a risk you can plan for.
- How did your company buy the last tool like this, from first call to signature? You want the steps, who ran each one, and how long the whole thing took. That timeline is your close date, not the rep's.
- Who inside the company wants this to happen, and what does a win look like for them personally? This identifies your champion and the stake that keeps them engaged after the demo.
Timeline and Urgency
- What date matters, and what's driving it? Real deadlines have a reason behind them: a contract renewal, a fiscal-year boundary, a product launch. No driver means it's a wish.
- What has to be true for you to start in that month? Preconditions come back: budget approval, a security review, a hire. Each one is a milestone to track.
- What else competes for this money and this team's attention this quarter? Your project gets ranked against the buyer's other priorities. Third place rarely closes on time.
Budget and Alternatives
- Is budget allocated for this, or does it need to be created? Allocated means an owner and a line item. To-be-created means a process, and that process has its own timeline.
- What other options are you weighing, including building it yourselves or doing nothing? Expect a list of alternatives. Doing nothing is a competitor in every deal, so it belongs on that list.
- What would make you decide to do nothing? This surfaces the real objection while there's still time to answer it. Ask it now, or hear it in month three as a price objection.
How Many Discovery Questions Should a Rep Ask on One Call?
Enough to cover the five groups across the first two or three conversations, never all 18 in one sitting. One or two questions from each group on the first call produce a qualified-or-not verdict. Everything else fills in during the technical call and the proposal review.
Completeness is measured in answers, not in questions asked. Nine recorded ones covering all five groups qualify a deal; 15 about the current process and none about who signs don't.
How Do You Know Discovery Actually Happened?
“Discovery complete” is a checkbox, and it holds no evidence. Those answers live in a call recording, an email thread, a meeting invite, or a rep's notebook. Five checks tell you which.
- Read the record, not the stage. For each committed deal, find where the answer to the cost question and the answer to the “who signs” question actually live. Only one copy, in the rep's memory, and the deal isn't qualified, whatever the stage says.
- Count the buyer-side people on the calendar. List the distinct people from the account who've joined a meeting or an email thread in the last 30 days. One name means a single-threaded deal, however complete the notes look. Our library page on buying committee coverage covers what a healthy count looks like.
- Score one discovery call per rep per week against the 18. Mark which groups got covered and which got skipped. Patterns show fast: the rep who never asks about budget, the team that never asks what changed. Our call coaching rubric gives you a 20-minute cadence for this.
- Compare the rep's close date to the buyer's date. Your timeline question produced a day and a driver. Close dates with no buyer-side event behind them are guesses dressed as forecasts.
- Check what the economic buyer has done, not what the rep says about them. Has the person who signs replied to anything, accepted a meeting, opened the proposal? Silence from the signer is the earliest slip signal you'll get.
Done by hand, these five checks mean reading call notes and inbox threads for 40 deals every week, and that's why the checkbox wins. Underneath sits a storage problem: where the answers live. Discovery happens in calls, emails, and meetings; the CRM field holds a summary typed afterward, or nothing.
Backstory removes the typing step. It captures every email, meeting, and call across the team, matches each one to the right opportunity and contact, and scores the deal against MEDDPICC, SPICED, or your own framework from that evidence, with AI reading the conversations for the answers and flagging the gaps: a missing economic buyer, a champion who went quiet, a stage with no discovery behind it.
Red Hat used that to standardize and enforce MEDDPICC qualification globally inside CRM, with 2,000 sellers now submitting forecasts in one unified view. Reps don't change how they work. What changes is the record, which stops depending on what anyone remembered to type.
Sales Discovery Questions FAQ
What Is the Difference Between Discovery and Qualification?
Discovery is the conversation that gathers evidence about the buyer's situation, impact, decision process, timeline, and budget. Qualification is the verdict you reach from that evidence using a framework such as BANT or MEDDPICC. Skipping discovery and filling in the framework from assumptions produces a qualified-looking deal with nothing underneath it.
Should Discovery Questions Follow a Script?
Follow a map, not a script. Those five groups are the territory every discovery has to cover; the order and wording adapt to the buyer. Rigid scripts read as interrogations and shut buyers down. Call mapping covers how to plan the route without reading from a page.
When Should a Rep Ask Discovery Questions?
After rapport, and then continuously. Call one covers change, cost, and who signs; the technical evaluation adds process and preconditions; the proposal review revisits budget and alternatives, because both move during a deal. Discovery that stops after call one produces the 60% deal nobody can explain.
What Are the Best Discovery Questions for a First Call?
Five, one per group: what changed, what it costs in a number you report on, who signs and who has to agree first, what date matters and why, and what would make you do nothing. Those five answers are all you need to decide whether the deal's worth a second call.
Run the five verification checks on your top 10 committed deals this week and count how many have a recorded answer for cost and signer. Then see how Backstory scores every deal against your qualification framework from the actual emails, meetings, and calls: explore Opportunity Qualification.
Related Insights
Explore more expert insights on AI adoption, sales execution, and revenue intelligence to help your team close more deals with confidence.
See Backstory in action,
no meeting required
See the platform for yourself, or get the guide to help you evaluate it.
