Key takeaways
- SPICED (Situation, Pain, Impact, Critical Event, Decision) is Winning by Design's framework for understanding the customer, built to carry one language across the whole revenue lifecycle.
- MEDDPICC is gap analysis across the whole deal. It names roles and lanes SPICED folds into one letter: Economic Buyer, Champion, Competition and Paper Process.
- They overlap more than people think. Pain and Impact map to Identify Pain and Metrics; Decision maps to Decision Criteria, Decision Process and the Economic Buyer.
- The acronym matters less than how you run it. Grade every element on buyer-validated evidence, and have a play for every gap.
Video · MEDDPICC Tips
Stop Using MEDDPICC to Qualify Deals. Use It for This Instead · David Weiss on YouTube
On this page
What Is SPICED?What Is MEDDPICC?MEDDPICC vs SPICED: Side by SideWhere They OverlapWhat SPICED Doesn't Name (and MEDDPICC Does)Where Each One Is StrongCan You Use SPICED and MEDDPICC Together?The Acronym Matters Less Than How You Run ItThe Bottom LineMEDDPICC vs SPICED FAQ"Should we use MEDDPICC or SPICED?"
I get some version of that question a lot. Usually from a team that already uses one and is wondering if the grass is greener.
Here's my honest answer. They're not really competitors. They were built to do different jobs, and they overlap more than most people realize.
SPICED is a strong, simple language for understanding a customer. MEDDPICC is gap analysis for complex deals. Plenty of teams can use both without confusing anyone.
This post goes letter by letter: what each framework covers, where they line up, what SPICED doesn't name that MEDDPICC does, and how to decide. If you want the full MEDDPICC breakdown first, start with MEDDPICC: The Complete Guide.
What Is SPICED?
SPICED comes from Winning by Design. Here are the five letters, using Winning by Design's own definitions:
- Situation: the customer's current context, "including their business environment, constraints, priorities, and triggers for change."
- Pain: "The specific friction, inefficiency, or risk the customer is experiencing as a result of their current situation, expressed in concrete, observable terms."
- Impact: the consequences of solving or not solving the problem, in terms that matter to the business, covering "both rational outcomes and emotional stakes."
- Critical Event: "The deadline, milestone, or external force that creates urgency and determines when a decision must be made."
- Decision: how the customer will make the choice, "including stakeholders involved, success criteria, tradeoffs, and the process required to move forward."
Notice the orientation. Winning by Design positions SPICED as a framework that aligns sales, marketing, customer success and RevOps around one shared language, applied across the full revenue lifecycle. It sits alongside their Bowtie, which they describe as "a framework for how recurring revenue organizations acquire, retain, and grow customers."
That matters. SPICED was designed so the same words follow the customer from first call through onboarding, renewal and expansion.
And on whether it can live alongside other frameworks, Winning by Design's own FAQ says yes. They describe SPICED as "framework-agnostic", built to layer into existing processes.
What Is MEDDPICC?
MEDDPICC stands for Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion and Competition. It grew out of MEDDIC, which was developed at PTC in the 1990s.
Most people call it a qualification framework. I don't.
MEDDPICC is gap analysis across the whole deal. Qualification asks, "Should I spend time on this?" Gap analysis asks, "Where am I in this deal, what don't I know yet, and what do I do about it?"
Your sales process is the car. MEDDPICC is the blind spot detector. It rides along with you all the way to signature.
MEDDPICC vs SPICED: Side by Side
Here's how the letters line up. This isn't a perfect one-to-one map. SPICED's letters are broader, so one SPICED letter often covers ground that MEDDPICC splits into several.
| SPICED | MEDDPICC | |
|---|---|---|
| Created by | Winning by Design | Developed at PTC in the 1990s (as MEDDIC); Competition and Paper Process added later |
| Built to | Give the whole revenue team one language for understanding the customer | Find the gaps across a complex deal, from first call to signature |
| Current state | Situation, Pain | Identify Pain |
| Value of solving it | Impact (rational and emotional) | Metrics |
| Urgency | Critical Event (its own letter) | No dedicated letter. Lives in Decision Process (the compelling event) and Metrics (the cost of delay) |
| Who decides | Decision (stakeholders involved) | Economic Buyer, Champion |
| How they decide | Decision (success criteria, tradeoffs, process) | Decision Criteria, Decision Process |
| Legal, security, procurement | Not named | Paper Process |
| Alternatives, including doing nothing | Not named | Competition |
| Strongest at | Early discovery, urgency, one language across the lifecycle | Complex, multi-stakeholder enterprise deals with real procurement and legal |
Where They Overlap
Most frameworks are trying to get you to the same place. They just label the parts differently.
Pain and Impact ≈ Identify Pain and Metrics. SPICED's Pain is the problem in concrete terms. Impact is what solving it, or not solving it, means to the business. In MEDDPICC, that's Identify Pain and Metrics. Same destination: a problem the buyer agrees with, tied to a number they agree with.
I like that SPICED's Impact explicitly includes emotional stakes. People make decisions emotionally and justify them logically. MEDDPICC doesn't say that out loud, but if your Metrics are only a spreadsheet, you'll feel it.
Critical Event ≈ the compelling event inside Decision Process. This is where SPICED earns real credit. It makes urgency its own letter. MEDDPICC doesn't. In my world, the compelling event lives in the Decision Process and the cost of delay lives in Metrics.
A compelling event isn't a date you guess. It's a deadline the buyer recognizes, with a clear cost of delay if they miss it. SPICED forces that conversation by name. If your MEDDPICC team keeps forecasting dates the buyer never agreed to, that's a lesson worth stealing. (More on the difference in What Is a Compelling Event?)
Decision ≈ Decision Criteria, Decision Process and Economic Buyer. SPICED's Decision is wide. By Winning by Design's definition, it covers the stakeholders, the success criteria, the tradeoffs and the process. In MEDDPICC, that's at least three letters, sometimes four.
What SPICED Doesn't Name (and MEDDPICC Does)
To be fair to SPICED: a strong seller using it well will ask about competition, champions and legal. Nothing in the framework stops them.
But a framework works by what it names. What it names gets graded. What it doesn't name gets skipped when people are busy.
Four things MEDDPICC names that SPICED doesn't:
1. Champion. SPICED's Decision includes "stakeholders involved." It doesn't ask whether anyone is selling for you. MEDDPICC does. And a Champion is a behavior, not a person. They have access to power, they use it, and they sell for you when you're not there. A friendly contact who answers your emails is not that. (What a real champion is.)
2. Economic Buyer as a distinct role. The person who controls the funds at this deal size is not always in the stakeholder list you built in discovery. And it shifts with deal size. Cross a discretionary limit and the Economic Buyer moves up a level. MEDDPICC makes you find that person by name.
3. Competition. Your biggest competitor usually isn't on the shortlist. It's the status quo. Then named competitors, building it in-house, and other priorities fighting for the same budget. SPICED's Pain and Impact help you beat the status quo. But nothing in SPICED asks you to map what else the customer could do instead of buying from you.
4. Paper Process. Business yes is intent. Paper yes is execution. Security reviews, legal redlines, procurement and signature authority are where forecasted deals go to slip. MEDDPICC gives that lane its own letter. SPICED's Decision covers "the process required to move forward," which can include it, but it's easy to stop at the business decision.
Here's why this matters in practice. One letter means one color. If Decision is green in SPICED, it can hide a red Economic Buyer, a yellow champion and a paper process nobody has mapped. MEDDPICC splits those apart, so each one gets its own red, yellow or green.
Where Each One Is Strong
SPICED is strong when:
- You want one shared language across sales, customer success and the rest of the revenue team.
- Your discovery is weak and you need a simple structure reps will actually use on a first call.
- Urgency is your problem. Deals stall at "let's revisit next quarter" because nobody named the critical event.
- Your motion runs on recurring revenue, and renewal and expansion matter as much as the first close.
MEDDPICC is strong when:
- Deals involve several stakeholders, real budget approval, procurement and legal.
- You lose to "no decision" or to a competitor nobody mapped.
- Your forecast keeps slipping because deals were "commit" before anyone knew the paper process.
- You need managers and sellers to inspect the same gaps in a deal review.
And for the record, MEDDPICC doesn't stop at signature either. The same letters decide whether an account renews and grows. Customer success can prove the Metrics, keep the Economic Buyer close and run the renewal like a new deal. (That's covered in MEDDPICC for Customer Success.)
Can You Use SPICED and MEDDPICC Together?
Yes. And for a lot of teams, I'd argue it's the best answer.
Here's the pattern I'd suggest. Use SPICED language in discovery. Use MEDDPICC as gap analysis once a deal is complex enough to deserve it.
That's consistent with how I already think about qualification. Use something lighter to decide if a deal deserves your time. Once you invest, MEDDPICC runs the deal.
In practice:
- Early discovery: Situation, Pain, Impact and Critical Event give reps a clean, easy structure for the first conversations. It's buyer-friendly. It keeps them on the problem, not the pitch.
- Once you invest: layer MEDDPICC over it as the gap analysis. Your Pain and Impact work becomes Identify Pain and Metrics. Your Critical Event feeds the Decision Process. Then you go find what SPICED didn't name: the Economic Buyer, a tested Champion, the Competition and the Paper Process.
- After the close: SPICED is built to carry into customer success, and so is MEDDPICC. Pick one vocabulary for the account team so nobody has to translate.
One rule if you combine them. Map them once, then teach one set of words per conversation. Don't make reps run two acronyms on the same call. And never ask the letters out loud. Nobody on the buying side wants to be asked, "Who's your economic buyer?"
Video · Sales Plays: Buying Process
The Strategic Trigger Play: Find a Compelling Event and Why Now · David Weiss on YouTube
The Acronym Matters Less Than How You Run It
Here's the part that matters more than the choice.
Whichever framework you use, it fails the same way. It gets bolted onto the sales process as admin. A few required CRM fields. A checklist managers nag about. It's not connected to what the seller should actually do next.
So it becomes theater.
Three things make either one work:
1. Grade on evidence, not feelings. Color-code every element. Red: I don't know. Yellow: I think I know, or there's misalignment. Green: I know and can prove it, with names, dates, numbers and documents the buyer validated. Red isn't bad. Calling yellow green is. (The color-coding cheat sheet shows what that looks like.)
2. Have a play for every gap. Knowing a Critical Event is red is useless without the action that moves it to yellow. Same for a red Champion or a red Paper Process.
3. Run it on a rhythm. Daily deal reviews for sellers. 1:1s, deal reviews and forecast calls for leaders. That's what makes it stick after the training ends.
Deals don't move on hope. They move on evidence. Neither acronym changes that.
The Bottom Line
SPICED and MEDDPICC aren't rivals. SPICED gives your whole revenue team one simple language for understanding the customer, and it makes urgency its own letter. MEDDPICC goes deeper on complex deals: it names the Economic Buyer, the Champion, the Competition and the Paper Process, and gives each one its own color.
If your deals are fast and your biggest gap is discovery, SPICED may be all you need. If your deals involve buying committees, procurement and legal, you need what MEDDPICC names, whatever you call it.
And for many teams, the answer is both: SPICED language up front, MEDDPICC as the gap analysis once you invest.
For how these compare to BANT and SPIN, read MEDDPICC vs BANT (Plus SPIN and SPICED). For Challenger and Miller Heiman, see Top Sales Methodologies Compared.
MEDDPICC vs SPICED FAQ
What does SPICED stand for? Situation, Pain, Impact, Critical Event and Decision. It's a framework from Winning by Design, used to structure how revenue teams understand a customer across the whole lifecycle, from first call through renewal and expansion.
Is SPICED better than MEDDPICC? Neither is better in general. SPICED is simpler and makes urgency its own letter. MEDDPICC is deeper on complex deals: it names the Economic Buyer, Champion, Competition and Paper Process, which SPICED doesn't call out on its own. Pick based on your deals, not the acronym.
What does MEDDPICC cover that SPICED doesn't? Four things SPICED doesn't name explicitly: a Champion (someone selling for you when you're not there), the Economic Buyer as a distinct role, Competition (including the status quo), and the Paper Process (legal, security, procurement and signature). A good SPICED seller can still cover them, but nothing in the framework forces it.
Is Critical Event the same as a compelling event? Close. Both are about timing the buyer recognizes. My test for a compelling event: it's a deadline the buyer recognizes, with a clear cost of delay if they miss it. In MEDDPICC it lives in the Decision Process, with the cost of delay in Metrics.
Can you use SPICED and MEDDPICC together? Yes. Winning by Design describes SPICED as framework-agnostic. A practical pattern: use SPICED's language for discovery, then use MEDDPICC as gap analysis once a deal is complex enough to invest in. Map the two once so your team isn't translating on every call.
Which one should a SaaS startup use? If your deals are fast and single-threaded, start lighter: SPICED, or MEDDIC. Look at your last 10 deals. If they involve several stakeholders, procurement and legal, you'll need what MEDDPICC names. (MEDDIC for SMB and startups goes deeper.)