Most discovery calls fail for the same reason. The rep asks two or three surface-level questions, hits a silence, and fills it with a feature walkthrough. Twenty minutes later, the prospect says they need to think about it. There was no discovery. There was a monologue with a question-shaped opening.
A structured discovery call framework solves this by removing improvisation from the equation. The rep follows a repeatable sequence: situation, pain, impact, critical event, decision. The questions are pre-built. The timing is planned. The ratio of talking to listening is measured. And the call ends with a committed next step, not a vague follow-up.
BANT vs. MEDDIC vs. SPICED: which framework to use
Three frameworks dominate B2B discovery in 2026. Each is built for a different deal profile. Using the wrong one for your sales motion creates friction: either you over-qualify early and lose deals you should have won, or you under-qualify and fill your pipeline with opportunities that never close.
| Framework | Best for | Weakness |
|---|---|---|
| BANT | Transactional SMB deals under $10k ARR, 1 to 2 touch sales, SDR qualification before AE handoff | Leading with budget before establishing value puts reps in a vendor position. Prospects lie about budget when ROI is unclear. |
| MEDDIC | Enterprise deals over $100k ARR with four or more stakeholders, 90-day-plus cycles, competitive displacement | Too heavyweight for SMB or mid-market. Hard to complete all six components on a single discovery call. |
| SPICED | B2B SaaS, mid-market, 30 to 90 day cycles where urgency needs to be surfaced, not manufactured | Requires reps to resist the urge to move to decision before impact is fully quantified. |
For most B2B SaaS discovery calls, SPICED (Situation, Pain, Impact, Critical Event, Decision) is the right starting point. It centers the conversation on impact and urgency rather than budget, it fits a 25 to 30 minute call structure, and it produces the information needed to write a business case, not just a proposal. If your deal size or stakeholder count grows, layer MEDDIC components on top.
The 8 to 12 question structure
Eight to twelve questions is the right range for a 25-minute discovery call. Fewer than eight leaves gaps in your understanding of the buyer's situation and buying process. More than twelve and the call feels like an interrogation rather than a conversation.
The sequence maps directly to SPICED. Each question serves a specific purpose: establishing context, surfacing pain, quantifying impact, identifying urgency, or mapping the decision. Reps who understand why each question is asked can adapt the wording without losing the structure.
Situation questions (2 questions)
- Q1. Opening. "What prompted you to take this call today?" or "What is driving the conversation now, rather than six months ago?"
- Q2. Current state. "Walk me through how [the relevant process] works today."
These two questions do two things: they surface the buyer's motivation for showing up, and they establish the baseline you will measure pain against. Do not skip them to get to pain faster. Without context, pain questions land as leading rather than curious.
Pain questions (3 to 4 questions)
- Q3. Breakdown. "Where does that process break down?"
- Q4. Impact. "What happens when it does?"
- Q5. Frequency. "How often does that come up?"
- Q6. Spread. "Who else on the team feels that, and how?"
Pain questions are not about confirming a problem you already assumed exists. They are about letting the buyer articulate it in their own language. The words they use here are the words that belong in your follow-up email, your proposal, and your champion's internal business case.
Impact quantification questions (2 to 3 questions)
- Q7. Dollar or hour value. "If you put a number on it, how much is that costing you in time, revenue, or deals each month?"
- Q8. Future value. "What would it mean for the business if you solved this in the next 90 days?"
- Q9. Past attempts. "What have you tried before, and why did it not stick?"
Question 7 is where most reps flinch. Asking a prospect to put a number on their problem feels presumptuous. It is not. It is the most useful question on the call. The number does not need to be precise. It needs to be shared. A rough figure that the buyer generates is worth more to the sale than a precise figure your marketing team calculated.
Critical event and decision questions (2 questions)
- Q10. Urgency anchor. "Is there a deadline, event, or initiative that makes solving this more urgent now than six months ago?"
- Q11. Stakeholder map. "Who else needs to weigh in before you move forward, and what matters most to them?"
- Q12. Decision path. "If everything we discuss today checks out, what does the path to a decision look like on your end?"
Not every call will use all twelve questions. Pick the eight to ten most relevant given what the buyer says in the first few minutes. The structure is a framework for sequencing, not a script to read aloud.
The 25-minute timing breakdown
A discovery call that runs long is almost always a call where the rep talked too much in the wrong phase. Structure the time explicitly before you dial.
The rapport phase is three minutes, not ten. You are not building a friendship. You are creating enough comfort that the buyer will answer candidly when you ask harder questions in minute five.
The question phase is the core of the call and should run 15 to 18 minutes. If you find yourself past minute 21 and still asking discovery questions, you ran over. Either you asked too many questions or you gave long answers between questions. Both are recoverable on the next call if you review the recording.
Positioning is not a demo. It is three to four sentences connecting what the buyer just told you to a specific capability. "Given what you said about losing three days of engineering time to manual reconciliation every month, the part of what we do that is most directly relevant is..." That is positioning. The full demo belongs in the next meeting.
Next steps get their own four minutes because they are the most important part of the call. A discovery call with no committed next step is a call that is effectively over.
The 43/57 talk-listen rule
Analysis of top-performing B2B discovery calls consistently shows a 43/57 ratio: the rep talks 43% of the time, the prospect talks 57%. Calls where reps talk more than 60% convert to a next step at roughly half the rate of calls that hit the 43/57 target.
The fastest lever for improving your ratio is not asking better questions. It is asking shorter questions. A question that runs four sentences is not a question. It is a hypothesis with a question mark at the end. The buyer answers the hypothesis, not the underlying question you actually wanted to ask.
The second lever is silence. When a prospect finishes answering, most reps start talking within one second. Top performers wait two to three seconds. That pause creates space for the buyer to add something they did not initially think to say. The additions are almost always the most diagnostic information on the call.
Measure your ratio on every recorded discovery call. Tools that score talk time are standard across most call recording platforms. If you are consistently above 50%, address it specifically: write shorter questions, practice the pause, and review recordings where you hit 43/57 to identify what you did differently.
How to quantify pain in dollars or hours
A discovery call that ends with "the prospect has a problem" is not done. The call is done when you have turned that problem into a number the buyer generated themselves. Quantification is what separates a deal from a conversation.
There are three reliable methods for quantifying pain in B2B discovery.
Time calculation
Ask how many hours per week the team spends on the problem. Get the loaded hourly cost if you can, or use a reasonable estimate for the role. Multiply by 52. That is the annual time cost. Do the math out loud with the prospect so the number becomes shared rather than something you invented later in a proposal.
Example: "If your ops team spends eight hours a week on manual reconciliation and you have four people on that, that is 32 hours at roughly $80 per hour fully loaded. About $133,000 per year in labor sitting on a process that should not require human intervention. Does that feel roughly right?"
Revenue calculation
Ask how many deals stall or are lost because of the problem each month. Multiply by average contract value. That is the monthly revenue leaking through the gap.
Example: "You said you lose about two deals a month where pricing complexity is the stated objection. At $40,000 ACV, that is $80,000 in monthly pipeline that does not close. Over a year, that is close to $1 million in revenue attributable to one friction point. How does that land with you?"
Capacity calculation
Ask what the team could produce if the problem were solved. Translate additional output into revenue or headcount equivalents. This works especially well for problems that limit throughput rather than causing direct loss.
Example: "If your reps were not spending 40% of their time on manual data entry, how many more calls could they make? At your current connect rate and ACV, what does that translate to in incremental pipeline per quarter?"
The method matters less than the habit. Every discovery call should end with a shared number. If the buyer pushes back on the math, that pushback is diagnostic. It tells you where their real constraints are.
What happens after discovery
The discovery call produces three outputs that drive the rest of the deal: a pain statement in the buyer's own words, a quantified impact figure they helped generate, and a committed next step with a date.
The follow-up email sent within two hours of the call should contain all three. Not a summary of features you mentioned. Not a generic "great to connect." A mirror of what the buyer said, in their language, with the number attached, and the next meeting invite already in motion.
If you are running GTM simulations to model where discovery call quality fits in your pipeline conversion rates, Numi's simulation layer lets you test the revenue impact of improving discovery depth before you invest in training or tooling.
Discovery is not the sexiest part of the sales process. It is the most leveraged. Get the questions right, protect the ratio, put a number on the pain, and commit to a next step before hanging up. Every other part of the deal follows from those four habits.