Here is a stat that should make every VP of Sales uncomfortable: 70% of B2B purchases, including those made at S&P 500 companies, begin without a predefined project plan or allocated budget. The decision to buy was not waiting to happen. It was created. By someone who made a buyer feel the cost of inaction more clearly than the cost of change.
That creation happens inside the discovery call framework. Not in the demo. Not in the proposal. In the conversation that most teams treat as a pre-demo formality.
It is not a formality. It is the engine of the deal. And most teams are running it at about 40% capacity.
Why SPIN Selling Is Still the Right Starting Point
Neil Rackham published SPIN Selling in 1988. Most sales teams today still use some version of it, even if they don't know the name.
That's not a coincidence. It's what Nassim Taleb would call the Lindy Effect at work: ideas that survive long enough tend to keep surviving, because time itself is evidence of robustness. A framework taught, tested, and refined across 40 years of sales cycles in hundreds of industries has earned the right to be called durable. The fact that discovery frameworks invented in 2011 (Challenger), 2015 (SPICED), and 2018 (MEDDPICC) all still orbit around the same core concepts Rackham described suggests those concepts are structural, not fashionable.
SPIN stands for Situation, Problem, Implication, and Need-Payoff. I'll use a version of the first three: Situation, Pain, and Impact. The logic is the same. The emphasis is different. And there is a layer Rackham didn't name that I'll add at the end.
Layer 1: Situation
Situation questions establish context. They answer: what is happening here, and is this the right conversation to be having?
Good situational questioning covers what their current process looks like, what triggered the demo request, what the team structure looks like, and whether there are any red flags that disqualify this deal before going further.
That last point is chronically under-used. Most reps treat situational questions as warm-up. They're also the fastest path to disqualification. A company that switched CRM six months ago, or is in the middle of a restructure, or has just signed a three-year contract with a competitor: not leads to nurture. Leads to park. Situational questions let you find that out in the first ten minutes instead of the last ten weeks.
A useful structure here is the CCO opening: Closed, Closed, Open. Start with two closed questions the buyer can answer easily, then open up to a broader question that gives them room to share context. The psychological logic, drawn from Kahneman's substitution heuristic, is that an easy specific question sets the emotional tone before the harder open question lands. It creates momentum without the interrogation feeling that a sequence of open questions can produce. Keep situational questions to two or four in sequence. Beyond that, even genuinely curious questions start to feel like form-filling.
One more principle from practice: earn the right to ask. Walking in cold and firing situational questions feels extractive. Earning the right looks like this: a short educational observation about a problem you commonly see in their space, or a user story from a similar company, before opening the first question. "Most teams I speak to in your position tell me X is a growing problem. Is that something you're seeing as well?" frames you as a peer with context, not a rep filling out a qualification sheet.
Pre-research sharpens this further. Knowing their industry, funding stage, or recent hiring pattern means your situational questions can be directional rather than exploratory. "I noticed you've added three SDRs in the last quarter. What's driving the push?" is a different opener than "So, tell me about your team."
The benchmark reality: across 1,400+ reviewed calls, situational questions are the most consistently executed element of discovery. Most reps get here. The problem is they treat getting here as success.
Layer 2: Pain
Pain questions move from what is happening to what is wrong because of it. They surface negative consequences of the situation the buyer just described.
Good pain questions are simple. "Is that a problem for you?" is a pain question. "How does that affect your team?" is a pain question. "I can imagine that's not a situation you'd want to keep indefinitely" is a softened version. The goal is to draw out the emotional and operational friction the buyer is experiencing, ideally in their own words.
Two principles matter here. First, keep the sequence short. Two consecutive pain questions is fine. Three is the limit before the call tips into something that feels like an interrogation. Mix in acknowledgements, observations, and situational follow-ups to keep the rhythm conversational.
Second, distinguish between a pain and a problem. This distinction is not semantic. A pain is a negative experience. A problem is a pain that the buyer has decided is worth solving. Not all pains become problems. Most don't. The buyer with a headache doesn't necessarily want surgery. Your job is not to list everything that hurts: it is to find the pain that has already crossed the threshold into "this needs to change."
The outbound/inbound asymmetry matters here too. Inbound leads often arrive with pain already formed into a problem, which is why inbound close rates run around 35%. Outbound leads haven't crossed that threshold (outbound close rates around 6%). Outbound discovery is therefore harder by design: you're not qualifying an existing problem, you're helping create the category of problem that your solution addresses. That requires more patience, more curiosity, and more deliberate framing.
Think of it like a sonar operator on a submarine. They can hear something in the water. That's the situation. They can tell it's getting closer. That's the pain. But until they know the size, the speed, and the heading — that's impact — they have no idea whether to surface or to dive. Most discovery calls stop at "something's there." The decisions that matter require the full picture.
Pain is the motor of a deal. But a motor without fuel doesn't move anything. Impact is the fuel.
Layer 3: Impact
This is where most discovery calls stop being mediocre.
Knowing a pain without knowing its impact is like knowing someone has a headache without knowing whether it's been going on for three hours or three years, whether it's affecting their work, and whether it's a symptom of something more serious. You have a description, not a diagnosis.
Impact questions quantify and elevate pain. The simplest ones literally contain the word: "What's the impact of that on your team?" "What impact is this having on your numbers?" Other useful variants: "Why is this a priority now versus six months ago?" That question does not ask for impact directly. It asks for urgency. And urgency and impact are closely related. If the answer is vague, that's diagnostic: the pain hasn't yet crystallised into a problem that will generate internal momentum for a purchase.
When the answer feels thin, name it. "It feels like this is more of a nice-to-have for you right now." This is counter-intuitive but consistently useful. A buyer who confirms the nice-to-have framing has told you something important: this deal won't close without more work on urgency. A buyer who pushes back ("No, actually it's costing us...") has just given you the impact language you needed.
The gap between Discovery (4.2) and Demo (6.5) in the benchmark data tells the story. Teams are better at showing their product than at understanding the buyer's world. That's backwards. A strong demo built on weak discovery informs but doesn't persuade. And the reason most demos fail to produce a committed next step is not the demo itself. It's a discovery failure that ran into a buyer who never fully felt the cost of their current situation.
If you want to work on the full arc from discovery to a demo that closes, the Discovery & Demo training covers exactly this: scored call review as the baseline, then building the demo around the specific pains and impacts surfaced in discovery.
The Problem with Stopping Here: Commodity Information
Here is the uncomfortable truth about SPI discovery done well but not done deeply: it produces commodity information.
Any well-trained rep from any of your competitors can get to the same place. Ask situational questions. Surface pain. Ask about impact. If they're good, they'll arrive at the same set of facts: this team has X problem, it's costing approximately Y, and it's been going on for Z months.
Now both of you walk into a demo knowing the same things. Both of you position your product against those known pains. The buyer chooses based on brand familiarity, pricing, or whoever followed up faster. You have not created any advantage by being a better discoverer.
The Challenger Sale research makes this precise. In their analysis of buyer behaviour, they found buyers were most likely to shift their purchasing vision when a vendor provided new information about the buyer's own situation that the buyer hadn't previously considered. Not better information. Novel information. A framing of the problem the buyer hadn't named for themselves.
This creates two additional dimensions that separate excellent discovery from merely good discovery.
The Novelty Dimension: Getting Out of the Red Zone
The Novelty Dimension is the degree to which a discovery call surfaces information or problem framing that is new to the buyer: insights about their own situation they had not previously identified, quantified, or named. A rep operating in the Novelty Dimension does not simply extract what the buyer already knows — they introduce a frame that shifts how the buyer understands the cost or scope of their problem.
Basic discovery (red zone) extracts what the buyer already knows: high-volume, low differentiation. Advanced discovery surfaces what they didn't know they knew, sharply increasing urgency and close rate. Most reps stop at the zone boundary.
The distinction maps directly to problem awareness. A buyer who has already named their problem and is evaluating solutions is in the toughest environment for an outsider: you must be a demonstrably better solution to win. A buyer who knows there's a problem but doesn't know how to solve it is looking for a consultant. A buyer who hasn't yet recognised the full scope of the problem is the opportunity, particularly in outbound. That third environment is where Advanced Discovery lives.
The best way to get there is to be suggestive and directive in your questioning without being pushy. Customer stories are the cleanest mechanism: "A team very similar to yours told us they were losing X hours per week to Y, which was creating Z downstream. Is that something you recognise?" The story provides the frame. The question invites the buyer to map their reality onto it. If they say yes and start elaborating, you've just opened a territory of the problem they hadn't fully articulated before the call. That's the beginning of a buying vision shaped by your conversation, not just your product.
Challenger Sale research puts a number on this: create the buying vision and you win 74% of the time (Forrester). That's not a coincidence. The rep who shapes how the buyer sees their own problem earns an asymmetric advantage. Competing vendors who only explore what the buyer already knows will arrive at the same destination with less purchase momentum behind them.
The value you add as a seller is by identifying the things the buyer didn't know before.
The Altitude Dimension: From User Pain to Business Problem
The Altitude Dimension describes at which organisational level a pain is understood and felt. User-level altitude means the problem registers only with the person doing the work. Business-level altitude means it registers as a cost or risk on a P&L or revenue forecast. Executive altitude means it is connected to a priority the CRO, CFO, or board is already tracking. A well-qualified deal requires the pain to be understood at the altitude where the budget decision actually lives.
Even if you've reached impact, and even if the information you've surfaced is genuinely novel, there is one more failure mode: you've discovered a user-level pain that can't generate budget.
The person on the call feels the problem. It costs them time, frustration, and workarounds. But it cannot be translated, as currently framed, into a business priority that a CFO or CRO would fight for in a budget conversation. And budget lives higher up.
A well-qualified deal requires movement on all three dimensions simultaneously. Deep pain that stays at user level never gets budget. Novel pain framing without altitude stays interesting but not urgent. Altitude without depth is a vague executive worry with no internal champion.
This is what I call the altitude of a problem. A problem only becomes actionable when it registers at the right altitude in the organisation: ideally at the level of whoever controls the budget for solving it. Think in three layers:
impact
impact
impact
Most reps discover at the persona layer and stop there. That's why they lose deals in procurement: not because the product wasn't right, but because the internal champion couldn't make a business case that resonated with whoever approved the spend.
The fix is to help the user translate their pain upward. Sometimes they'll know how. Often they won't: they're not paid to think strategically about company-wide impact. When they can't make the translation themselves, that's the cue to involve the next level up. "This is genuinely costing you a lot of time, and I think we both know it'll be difficult to get budget approved if we frame it only at that level. How does your manager see this problem? Do you think it would be worth getting them into a follow-up call to explore the business-level impact together?"
That question does two things: it moves the deal forward, and it gets the next-level stakeholder into the conversation before the proposal stage, which is the single most common place multi-stakeholder SaaS deals go to die.
One technique that works well here: give the buyer homework. "Before we reconnect, could you pull the pipeline value for deals that haven't had a customer conversation in the last 30 days and are due to close this quarter?" That exercise forces the buyer to quantify the cost of their own inaction in their own CRM. When they come back with a number, urgency tends to arrive with them.
A user-level pain gets you a fan. A business-level pain gets you a champion.
Putting It Together: What a Complete Discovery Call Looks Like
A complete discovery call across all five dimensions does not need to be a marathon. The sequence can move efficiently if you know what you're building toward.
| Dimension | Goal | Signal you're done |
|---|---|---|
| Situation | Context and disqualification | You understand the scope and have no red flags |
| Pain | Negative consequences surfaced | The buyer has named what's wrong in their own words |
| Impact | Cost of the problem | You have numbers or language that makes the problem feel expensive |
| Novelty | Problem they hadn't named | The buyer elaborates on a frame you introduced, not one they brought |
| Altitude | Business-level translation | You understand how this registers above the user level |
The benchmark: most reps reach Situation consistently. Around half reach Pain meaningfully. Fewer than 25% close out Impact. Almost none deliberately pursue Novelty or Altitude. That gap is not a talent gap. It's a coaching gap. Reps stop early because they haven't been shown what good looks like at layers four and five, and they haven't been scored on those dimensions in call reviews.
The Qualification Test at the End of a Discovery Call
You are only truly well-qualified when you can say yes to all of the following:
Pain: Does the buyer experience a genuine negative consequence, described in their own words?
Impact: Is that consequence quantifiable? Does the buyer feel the cost of inaction clearly?
Novelty: Did you surface at least one element of the problem the buyer hadn't fully articulated before this call?
Altitude: Is the problem framed at a level that justifies budget? Does someone with spending authority recognise it as their problem?
If you can say yes to all four, you have a deal worth investing time in. If you're missing one or more, you have a conversation worth continuing — in a follow-up call designed to close the gap, not a proposal designed to manufacture urgency that the discovery hasn't yet created.
Frequently Asked Questions
SPI stands for Situation, Pain, Impact. Derived from Neil Rackham's SPIN Selling (1988), it describes the three core layers of an effective B2B sales discovery call. Situation questions establish context and scope. Pain questions identify negative consequences of the current situation. Impact questions quantify those consequences to establish whether the pain constitutes a genuine business problem worth solving.
Two to four situational questions in sequence before opening up, a maximum of two consecutive pain questions, and at least one impact question for every pain that surfaces. Impact questions are chronically under-asked: 75% of reviewed B2B SaaS discovery calls score zero on impact questioning according to Nils Brosch's seven-year benchmark dataset of 1,400+ calls.
Pain is a negative experience the buyer describes. Impact is the cost or consequence of that pain, quantified in time, money, risk, or strategic priority. A buyer who says "our onboarding process is slow" has named a pain. A buyer who says "our onboarding is slow, new hires take 90 days to full productivity, and we're losing two deals per quarter while we wait" has named an impact. Without impact, you cannot determine whether the pain constitutes a problem worth budgeting for.
Novelty means surfacing a problem framing that is new to the buyer — something they hadn't identified or articulated before the conversation. Challenger Sale research found buyers are most likely to shift their purchasing vision when a vendor provides new information about their own situation. Customer stories are the cleanest mechanism: framing a problem you've seen elsewhere, then inviting the buyer to recognise it in their own context.
Usually because discovery stopped at pain without reaching impact, novelty, or altitude. The buyer experienced an interesting conversation but didn't leave with a sharper sense of the cost of their current situation. Without that sharpness, there is no internal urgency to drive the deal forward. 70% of B2B buying processes begin without a pre-existing budget or project plan. The discovery call has to create the commercial rationale that unlocks both. A call that only confirms what the buyer already knew doesn't accomplish that.
One Thing to Do Differently on Your Next Discovery Call
After the next pain a buyer describes, don't move on. Ask: "Why is that a priority now versus six months ago?" Then listen carefully. If the answer is vague, say so: "It feels like this is more of a nice-to-have for you right now." The response to that will tell you everything you need to know about whether you have a deal or a conversation.
See how your team scores on discovery
My Discovery & Demo training begins with a scored call review, mapping which framework components are consistently missing, which are present but thin, and where the 60% pain weighting is being lost. Built around your real calls, not generic exercises.
