Sales Discovery Questions: 25 That Size the Problem, and the Five Spona Reps Ask

Sales discovery questions are the questions a rep asks to understand a buyer's situation, problem, cost, target and decision path before proposing anything. The good ones return a number or a name you can write down. The 25 below sit in five groups, one per answer.

Gong analyzed 519,000 recorded discovery calls and found that the most effective ones uncover three to four business problems. Each question here states what the answer tells you, so you know when to stop asking. After the bank come the five questions Spona's own reps ask, word for word, with the unit they log for each. One recorded deal shows what the answers sized.

Get thousands of leads in 4 minutes.

Stop stitching tools together.
Start with verified sales data, delivered in minutes.

SCALE SALES NOW

No contracts · No setup · No onboarding

Sales discovery questions: the five answers you need

A discovery call has done its job when you leave with five answers. Those five: how the work runs today, what breaks, what it costs, the target state and who decides. Everything else is detail.

Buyers notice when those answers are missing. In Salesforce's State of Sales research, 59% of business buyers say most reps do not take the time to understand their goals. The same research found that 86% are more likely to buy when their goals are understood.

The five groups are not new. Neil Rackham's team studied more than 35,000 sales calls in 23 countries and sorted questions into four types: situation, problem, implication and need-payoff. This bank keeps the first three under plainer names and splits the fourth in two. Outcome questions set the target state, and decision questions map who approves it and when.

Decision questions earn their place because buyers arrive late and committed. According to 6sense's buyer research, buyers are nearly 70% through their purchasing process before they engage a seller. And 81% already have a preferred vendor at first contact. If you do not ask how they will decide, you learn it when you lose.

There is no canonical list of the five types of discovery questions. At Highspot, the five types are open-ended, priority-alignment, process-clarifying, stakeholder-mapping and fit-check. At Articulate, they are contextual, problem, impact, qualification and strategic. The five groups below sort questions by what the answer tells you.

Discovery questions by what they uncover

These 25 sales discovery questions are for B2B calls. Each answer lands in one of the five groups. Pick from them; do not read them out. A call uses 11 to 14, as the section on order and count explains.

Situation questions

Situation questions set the baseline. Keep them to three or four. The buyer has answered them before, and anything you could have read on their website costs you goodwill.

1. How does your team build a target list today, from the first filter to the first email? The answer tells you the workflow and where the hours go. Log the steps and the tools.
2. Who owns that process, and who else touches it each week? You learn the daily user, who is often not the buyer. Log both roles.
3. How many hours a month does it take, across everyone involved? This is the number the rest of the call builds on. Log hours a month, marked as the buyer's estimate.
4. Which tools and data sources sit in that process, and what do they cost you? You learn the incumbents and the budget already spent. Log vendors and annual spend.
5. What changed recently that made this worth a call? You learn the trigger: a new market, a lost rep, a missed quarter. Log it in the buyer's words.

Problem questions

Problem questions find what breaks. Gong's call data says the best calls surface three to four problems, so stop digging once you have them.

1. Where does the process break down most often? Tells you the buyer's own ranking of the pain. Log the top problem first.
2. Out of the last batch of records you worked, how many had the right person and a usable contact? Tells you data quality as a ratio you can test later. Log usable records per 100.
3. How long has this been a problem, and what have you tried? Tells you whether the buyer has given up on fixing it. Allego asks it as "What's stopped you from solving this previously?" Log the failed attempts.
4. Who feels this first when it goes wrong? Tells you who will champion a change. Log the role.
5. What does a bad week look like because of it? Tells you the problem in operational terms: bounced emails, missed sends, rework. Log one concrete example.

Impact questions

Impact questions turn a complaint into a cost. This is the group that reveals business value, and the easiest to skip, because the buyer has to think before answering.

1. If you add up the rework, the bounces and the wasted sends, what does this cost you in a month? Tells you the buyer's own figure, which they will defend later. Log it in hours or in money, never both in one field.
2. How many meetings or replies did you miss last quarter because the data was wrong or late? Tells you the revenue side of the cost. Log meetings a month, separately from hours.
3. What is an hour of the people doing this work worth to you? Tells you the rate that turns hours into money. Log the hourly value as the buyer states it.
4. Which target did this put at risk? Tells you how the problem shows up in the buyer's own scorecard. Log the target and the shortfall.
5. What happens if nothing changes for another two quarters? Tells you urgency. The Humble Sale's version is "What happens to this project if it slips six months?" Log the consequence in the buyer's words.

Outcome questions

Outcome questions describe the target state. Without them, the impact figure has nothing to compare against, and you cannot size a pilot.

1. If this process took a quarter of the time, what would the team do with the hours? Tells you whether the saved time has a use, and so whether anyone will fight for the change. Log the proposed use.
2. How many usable contacts do you need next month, and in which segment? Tells you the first batch size and the targeting. Log contacts a month, geography, roles and company filters.
3. How would you measure that this worked, three months in? Tells you the metric the buyer will report upward. Log the metric and its current value.
4. What would good enough look like, as opposed to perfect? Tells you the acceptance bar for a pilot. Log the threshold.
5. Which part of the problem would you fix first if you could fix only one? Tells you where a pilot should start. Log the priority.

Decision questions

Decision questions map the path to a yes. According to 6sense, the average buying group has 11 people, so the person on the call is rarely the only vote. Ask about the process, not the budget. Budget belongs to qualification, which the BANT framework covers, and the committee mapping for enterprise deals belongs to MEDDIC.

1. Walk me through how you bought the last tool in this area. Tells you the real approval path, which is often not the org chart. Gong's wording is ["Walk me through how you purchased [incumbent]."](https://www.gong.io/blog/sales-discovery-questions/) Log the steps and who signed.
2. Who else needs to see this before you could run a pilot? Tells you the approver and the audience for a sample. Log the roles. On 23 of 371 recorded Spona discovery and evaluation calls, the buyer said a version of "My manager needs to see the test first."
3. What would the person who signs want to see in the results? Tells you the approver's acceptance criteria. Log them as a checklist.
4. Is there a date this has to be working by, and what set it? Tells you the compelling event, or its absence. Log the date and the reason.
5. What would stop this from going ahead, even if the pilot works? Tells you the risks the buyer already sees: procurement, a running contract, a hiring freeze. Log each one.

The five questions Spona asks

Spona sells verified B2B lead lists, so its reps use discovery to size one thing. That is the gap between the hours a team spends on list research and the hours it wants to spend. The framing comes from gap selling, which has its own post.

Three Spona reps asked the same five questions over about seven weeks. Here they are word for word, with the unit each rep logs. The last column says whether the question works on a small deal, which the team defines as a first purchase under $500.

Three things in that table are easy to miss. Question 2 asks for a ratio, not an opinion, and the rep later checks it against a free sample. Question 4 names four hours inside the question as an assumption, not a promise, and the rep logs it that way. Question 5 keeps the hourly value out of the gap figure, so a buyer's estimate never gets mixed into a measured result.

Where Spona fits: the answer to question 3 is a search brief. You describe that segment in a chat, and Spona mines 40+ sources, verifies each lead and delivers a scored list in about 4 minutes. Every search starts with a free sample, and the price per lead shows at checkout.

Spona does not fit the other half of the job: it does not record, transcribe or score the call itself. If you want the five answers captured automatically, Gong, Allego and Jiminny sell that. Spona also has no outcome data on these questions. Nothing in its records shows that they move win rates, only that three reps log the answers in the same units.

How the answers sized one deal

One recorded deal shows the five answers in use; it is a single case, not a benchmark. The buyer was the founder of a UK company with 11 to 50 people. Every figure below is the buyer's own estimate, logged as stated.

The first question produced the baseline: about 18 hours a month to research 600 target contacts. Question 4 set the target at 4 hours a month for the same volume. That left a gap of 14 hours a month, which the rep logged as projected capacity, not as time saved.

The founder put a loaded value of $50 an hour on that time. At 14 hours, the buyer's figures put the gap at $700 a month. The log calls it capacity, not revenue or realised savings, because nobody had saved anything yet.

Question 3 sized the first batch at 600 qualified contacts. After a free sample, the buyer agreed a 600-contact pilot. Nothing in the record says Spona saved this buyer 14 hours or $700. Those are the buyer's projections, not results.

The baseline is not unusual. In Salesforce's State of Sales survey of 4,050 sales professionals, sellers put nearly one full day of their workweek into prospecting. The average seller spends 40% of their time selling. An 18-hour month on list research fits that picture.

What would that pilot cost on Spona's public prices? This is our calculation from the pricing page, not the deal's invoice. A credit costs $0.008 to $0.01 by plan.

The Free plan's 3,000 one-time credits cover the session and leave 2,000 credits. On Standard Search with email only, that buys 285 to 666 leads before anyone pays. So the free credits cover roughly half to all of a 600-contact email pilot.

Discovery call questions: order and count

Pick 11 to 14 questions from the bank, spread them through the call, and leave the last five minutes alone. Each part has data behind it.

The same Gong analysis found that asking 11 to 14 questions correlates with the greatest success. Beyond that range, success drops to average. It is a correlation, not a cause: good reps may simply ask about that many.

Gong also warns that too many questions harm the sale when selling to the C-suite. With an executive buyer, ask fewer and go deeper. Highspot's own guidance is 8 to 12 questions. The ranges overlap, and the bank is a menu either way.

Top sellers spread their questions evenly through the call instead of front-loading them. A practical order follows the five groups: situation first, problem and impact in the middle, outcome and decision near the end. Menemsha's sequence runs current state, future state, compelling event, commitment, then means and fit, with budget only after fit. Both orders put the decision questions after the buyer has named the cost, not before.

In Gong's analysis of 326,000 sales calls of ten minutes or more, reps talked 57% of the time on won deals. On lost deals they talked 62%. The gap is small, but it favors the rep who talks less. Gong's data also shows that the longer the customer story, the higher the success rate.

Set the length by the deal. Salesforce puts a discovery call at 20 to 30 minutes for a simple transactional sale. A complex enterprise sale takes up to an hour, across several calls. Whatever the length, leave a full five minutes at the end to set up the next step.

For a small deal, that next step is the pilot itself. You already have its segment, its acceptance bar and its approver from the outcome and decision groups.

Discovery is not the cold call. The openers that book the meeting are in the cold call scripts post.

Sales discovery mistakes to avoid

Each discovery call is scarce. Databox surveyed 51 companies and agencies about their funnels. For most, only 10% to 30% of leads turned into a discovery call. Six habits waste the ones you get.

1. Interrogating. Gong's line is that 15 or more questions turn the call into an interrogation. The fix is a shorter list, not faster delivery.
2. Front-loading. Ten questions in the first ten minutes, then a pitch. Decision questions land better once the impact figure exists.
3. Pitching before fit. Menemsha's rule is no pitching in discovery and no budget question before fit. A buyer who has not named a cost has no reason to name a budget.
4. Closed and leading questions. "You're probably losing hours to bad data, right?" gets a yes and no number. Ask for the number.
5. Asking what research could answer. Headcount, the tools in the stack, recent funding: these are on the website or in your data tool. Qualify on paper first and spend the call on what only the buyer knows.
6. Mixing estimates with measured results. A buyer's "about 18 hours" is an estimate. A pilot result is a measurement. Spona's reps keep them in separate fields, and the deal above is written that way: $700 is projected capacity, not a saving. Put the two in one column and the forecast becomes fiction.

Get thousands of leads in 4 minutes.

Stop stitching tools together.
Start with verified sales data, delivered in minutes.

SCALE SALES NOW

No contracts · No setup · No onboarding

Sales discovery questions FAQ

What are good sales discovery questions?

Good sales discovery questions return something you can write down: a number, a name, a date or a consequence. "How many hours a month does list research take?" is good because the answer is a figure the buyer will defend later. "Tell me about your challenges" is weak because the answer is a story you cannot measure. Test each question against the five groups, and cut any whose answer lands in none of them.

What is the difference between discovery and qualification questions?

Discovery questions build understanding: what the buyer does, what breaks and what it costs. Qualification questions decide fit: budget, authority, need and timing, in frameworks such as BANT. The two overlap on the decision group. For a qualification list, use the lead qualification checklist; for the concept, read what lead qualification is.

What are the 5 W questions in sales?

Who, what, when, where and why, applied to the buyer's problem. They map onto the five groups. Who decides, what breaks, where in the workflow, when it must be fixed, and why it matters in hours or money. The 5 W's are a memory aid; the bank above gives you the full sentences.

How long should a discovery call be?

Salesforce's guidance is 20 to 30 minutes for a simple transactional sale and up to an hour, over several calls, for an enterprise deal. For a first purchase under $500, 20 minutes is enough. Plan 11 to 14 questions and a five-minute close, and keep those last five minutes for the next step in every case.

Does discovery work on small deals?

Yes, if the questions are short and each one earns a number. Spona's team marks its five questions as working on first purchases under $500. Each takes one answer: hours, a ratio, a batch size, a target and a gap. Skip the committee mapping, accept a labelled estimate, and validate it on a free sample instead of a long qualification call.