MEDDPICC vs SPICED: Which Sales Discovery Framework Fits Your Sales Cycle?

Every few months a new LinkedIn post declares that MEDDPICC is the only serious framework for enterprise B2B, or that SPICED is cleaner and more modern, or that GAP Selling renders both obsolete. The advocates are usually smart people. They're also usually wrong in the same way: they're treating an information checklist as if it were a philosophy.

Let me paint you a picture. Imagine a doctor who, instead of diagnosing a patient, simply picks their favourite symptom checklist and works through it line by line — without ever deciding what "a concerning answer" actually looks like for this specific patient. The checklist is not the problem. The absence of clinical judgment behind it is. That's exactly what happens when sales teams adopt MEDDPICC or SPICED without defining what good looks like under each component.

This article is for VP Sales, CROs, and sales leaders at B2B SaaS companies who are evaluating which discovery framework to standardise on — or who have already implemented one and are wondering why it hasn't moved the needle.

The Most Important Distinction Most Sales Leaders Miss

A sales discovery framework is a structured information checklist that defines which intelligence a sales team needs to gather to assess deal quality, buying readiness, and close probability. It tells reps what to find out — not how to find it out.

A sales methodology is the behavioural and conversational approach a rep uses to gather that information. SPIN Selling, Challenger Sale, value-based selling — these are methodologies. They describe how to elicit information, how to position insights, how to handle objections. They apply to the discovery framework but are not the same thing.

MEDDPICC, SPICED, MEDDIC, BANT, and GAP Selling are not sales methodologies. They are information frameworks — checklists that define what your team needs to know. The methodology is how you get there.

This distinction matters because it explains why companies can implement MEDDPICC in their CRM, run a two-day training on it, and see zero improvement in win rates six months later. They changed the labels on the fields. They didn't change the quality of the conversations.

The Evolution: From BANT to Modern Frameworks

BANT — Budget, Authority, Need, Timing — was developed at IBM in the 1960s for a world where enterprise software came with pre-allocated procurement budgets. A salesperson would call in, qualify the budget and the decision-maker, confirm the need, and map the timeline. Clean, transactional, linear.

That world no longer exists for the vast majority of B2B SaaS deals. Research by the Challenger Sale team at Gartner found that the average buying group for a complex B2B solution now involves between 6 and 10 stakeholders. Budgets are rarely pre-allocated — they're justified retroactively once the problem is understood. Nobody woke up on Monday with budget earmarked for your category of software.

Modern frameworks reflect this reality. Three shifts are visible across the evolution:

Pain elicitation has become disproportionately prominent. SPICED's entire P-I-C sequence (Pain, Impact, Critical Event) is dedicated to the problem dimension. GAP Selling builds an entire discovery structure around current state versus future state. Even MEDDPICC's Implicated Pain acknowledges that surface-level pain is insufficient — you need to understand what happens to the business if the problem remains unsolved.

Decision-making process information has become more explicit. MEDDPICC separates Decision Criteria, Decision Process, and Paper Process into three distinct components. SPICED combines them under Decision Process. Each is responding to the same reality: more stakeholders, more complex approval chains, more deal deaths at committee stage rather than at the champion level.

The 60% ideal weighting on Need/Pain is not coincidental. Roughly 60% of deal success comes from how deeply you understood and validated the problem. Getting the decision process and competition right matters — but it's secondary if the pain isn't real and urgent.

Breaking Down the Four Frameworks Worth Focusing On

BANT: Retire It

BANT isn't worth implementing in a modern B2B SaaS motion. Asking for budget upfront is both premature and damaging — it signals that you care more about the size of the deal than the size of the problem. If you're still using BANT as your primary qualification framework, the issue isn't the framework. It's that you haven't updated your commercial philosophy since the 1960s.

SPICED: Best for SMB, Mid-Market, and Teams New to Frameworks

SPICED — Situation, Pain, Impact, Critical Event, Decision — was developed and popularised by Winning by Design, a B2B SaaS go-to-market consultancy. Its primary advantage is simplicity.

SPICED is a five-component B2B sales discovery framework that maps the deal context (Situation), problem (Pain), business consequence (Impact), timing driver (Critical Event), and buying process (Decision) into a memorable, linear structure designed specifically for SaaS selling cycles.

The framework's strength is accessibility — a new AE can internalise the five letters in 20 minutes. More importantly, the I for Impact pushes reps beyond surface pain: not just "our reporting is slow" but "slow reporting costs our finance team 3 extra hours per week, roughly €80K annually in labour." That quantification is where SPICED adds genuine value.

SPICED is ideal for SaaS deals under €100K ACV with buying committees of 3 or fewer decision-makers. Above that threshold, the Decision component becomes structurally too thin.

One addition I'd argue SPICED needs regardless of deal size: Competition. Understanding who else is in the evaluation is vital in almost every B2B SaaS sale, yet SPICED doesn't include it as a named component. If you're using SPICED, add a C.

GAP Selling: The Framework That's Also a Methodology

Keenan's GAP Selling is unique because it attempts to be both an information framework and a sales methodology simultaneously. The core model maps Current State (where the prospect is now — physical reality, business problems, impact, emotions, root cause) against Future State (where they want to be) and defines the value of the solution as the size of the gap between the two.

The framework's strength is that it's explicitly value-adding rather than value-extracting. Most discovery frameworks ask reps to gather information for the seller's benefit. GAP Selling flips this: by helping a prospect articulate precisely where they are now and where they want to be, the discovery itself becomes a value-adding interaction.

The bigger the gap between current state and future state, the more value you can charge for closing it. GAP Selling makes this explicit — not as a negotiation tactic, but as a diagnostic truth.

The weakness is complexity. The current state map across five dimensions is comprehensive but cognitively demanding for reps to apply consistently in real-time. In practice, I see teams implement GAP Selling conceptually but revert to simpler shortcuts under pressure. Use it as an intellectual layer on top of MEDDIC or SPICED rather than as a replacement.

MEDDIC vs MEDDPICC: The Enterprise Question

MEDDIC — Metrics, Economic Buyer, Decision Criteria, Decision Process, Implicated Pain, Champion — is the standard for complex B2B enterprise sales. MEDDPICC adds Paper Process and Competition.

MEDDPICC is an eight-component enterprise B2B sales qualification framework developed in the early 1990s at PTC. It extends MEDDIC with explicit attention to the legal and procurement paper process and competitive landscape, and is most effective in deals with multiple stakeholders, procurement involvement, and ACVs above €100K.

The Economic Buyer / Champion distinction is the most valuable structural feature of both. In European enterprise deals — where decision-making is consensus-oriented and the buying committee is broader — having a champion who supports you is not the same as having an economic buyer who has signed off. Teams that conflate these two roles consistently overestimate deal probability.

The Paper Process component is genuinely enterprise-specific. Above €200K ACV, the paper process can be the single longest phase of the entire deal cycle. A champion who tells you "procurement is just a formality" has usually never run a large contract through their own legal team.

On Competition: I'd argue this should be standard across all frameworks, not just MEDDPICC. MEDDIC's omission of Competition is the one place where I'd deviate from the standard regardless of deal size.

There is, however, a structural blind spot in MEDDPICC that its advocates rarely acknowledge — and Keenan, with an obvious interest in making the point, nonetheless makes it correctly. In his LinkedIn writing and A Sales Growth Company material, he argues that every B2B deal is won or lost across three decisions: why should I change, why now, and why you. MEDDPICC is heavily optimised for the third decision — economic buyer access, paper process, competitive positioning. It is relatively weak on the first two.

"80% of the sale happens in the first 2 decisions — why should I change, and why now? MEDDPICC leans heavily on Decision 3: the economic buyer and paper process." — Keenan, A Sales Growth Company

This is a genuine limitation, not a sales pitch for any alternative framework. The Implicated Pain component in MEDDPICC is supposed to address "why should I change" — but in practice it's often filled with surface-level pain descriptions that don't establish urgency. A rep who has ticked the Implicated Pain box but hasn't made the prospect feel the cost of inaction has a CRM field, not a qualification signal. The 60% weighting on Pain below reflects this: establishing why change and why now is the majority of the sale, and it happens in discovery conversations long before procurement enters the picture. MEDDPICC gives you excellent tools for the back half of the deal. It does not give you the tools to create the conditions that make the back half reachable.

The Weighting That Actually Matters

Sixty percent on Pain. Not on the economic buyer, not on budget, not on competition. This is consistent with seven years of call review data from my own benchmark work across B2B SaaS teams in Benelux and DACH: the single most consistent differentiator between deals that close and deals that stall is the depth of pain elicitation in the discovery call.

It's the same conclusion GAP Selling arrives at from a different direction. The gap is the value. The size of the gap determines the price. And the size of the gap is only knowable if your discovery is deep enough to establish both where the prospect is now and what it's costing them to stay there.

So Which Framework Should You Use?

The Step Most Teams Skip — and Why It's Still Not Enough

Implementing MEDDPICC without this step is like installing a CRM without defining your pipeline stages. You've named the containers. You haven't defined what goes in them.

Mark Roberge — former CRO of HubSpot and senior lecturer at Harvard Business School — would push this further, and he'd be right to. In The Sales Acceleration Formula, Roberge argues that the mistake most sales leaders make is adopting industry-standard frameworks as if they were universal laws, when the data inside their own CRM would tell them something more specific and more accurate. At HubSpot, he built regression models against closed-won deals to identify which qualification signals actually predicted close probability. The results looked different from what conventional wisdom suggested.

His point cuts to the core of every framework debate: the framework you choose is a hypothesis. It represents someone else's best guess — from a different company, a different market, a different deal motion — about which information predicts deal success. That guess might be correct for your context. It might not be. You don't know until you test it.

Frameworks are hypotheses about what predicts deal success. Treat them as such. Validate them against your own closed-won and closed-lost data before standardising across your team.

For every component of your chosen framework, your team needs to agree on:

What specific information counts as "captured" for this component? Not "we discussed pain" but "we have a quantified business impact, confirmed by the economic buyer, that maps to at least €X in annual cost or revenue impact."

What are the red flags that disqualify a deal at this component? For Champion, an acceptable answer might be "VP of Sales, has direct budget authority, has purchased solutions in this category before." An unacceptable answer is "the person we've been talking to seems enthusiastic."

What pain points can we realistically solve, and which are we bad at solving? In my work with B2B SaaS teams, I use a PINC diagram — Pain, Impact, Need, Cause — to map this explicitly before training the framework. If your product doesn't solve the pain, winning the logo will produce churn six months later, which is worse than losing the deal.

And then — and this is where Roberge's argument becomes essential — you need to close the loop. Defining what good looks like is only half the job. The other half is measuring whether those definitions actually correlate with outcomes over time.

Tag every component field as filled or empty in your CRM at each deal stage. Run a quarterly analysis of closed-won versus closed-lost deals against those fields. Ask which components were most consistently present in won deals and absent in lost ones. Ask whether your "acceptable champion" definition predicted renewal rates, not just initial close rates. Ask whether your pain quantification threshold correlates with deal size, discount rate, or sales cycle length.

If your MEDDPICC implementation generates data that you never analyse, you've built a reporting system, not a learning system. Roberge's fundamental argument — validated by his work building HubSpot's revenue engine from $0 to IPO — is that the companies that compound their win rates over time are the ones treating their sales process as a continuous experiment, not a fixed methodology to implement and move on from.

Be honest: when did you last run an analysis of your closed-won data against your qualification framework fields?

Defining what good looks like is only half the job. The other half is measuring whether those definitions predict your outcomes — and updating them when they don't.

Where to Start

Pick the framework that matches your deal complexity from the decision tree above. Before training a single rep, run a PINC workshop to map which pain points you actually solve well and what "good" looks like for your champion, economic buyer, and decision criteria. That two-hour exercise will do more for your win rate than any framework implementation.

Then treat the framework as a hypothesis. Set a 90-day checkpoint to run your closed-won and closed-lost data against the qualification fields you've defined. Which components were present in every deal you won? Which were consistently absent in deals you lost? Let the data update the hypothesis.