MEDDPICC vs MEDDIC: what each letter asks, and a deal scored both ways
MEDDPICC is MEDDIC plus the paper process and the competition. What each letter asks, questions that get real answers, a scored deal, and when it's overkill.
MEDDPICC is a sales qualification framework for complex B2B deals. The letters stand for Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion and Competition. It grew out of MEDDIC, which was created at PTC in 1996, and the two extra letters cover the places where big deals tend to stall late: the contract, and the alternative the buyer is still weighing.
Teams use it as a list of eight things they need to know about a deal before they can forecast it honestly. Most sellers can recite the letters. Where it goes wrong is in deciding when a letter actually counts as known.
What does MEDDPICC stand for?
| Letter | Stands for | What you need to know | A question that gets a real answer |
|---|---|---|---|
| M | Metrics | The measurable result the buyer expects, in their numbers | "If this works, what number moves, and by how much?" |
| E | Economic buyer | The person who can say yes when everyone else says no | "Who signs off on a purchase this size, and have they seen this yet?" |
| D | Decision criteria | What they'll judge the options on | "When you compare options, what has to be true for one to win?" |
| D | Decision process | The steps and people between today and a decision | "Walk me through what happens after this call, up to a yes." |
| P | Paper process | Legal, security review, procurement and signature | "What does procurement need from a new vendor, and how long does that usually take?" |
| I | Identify pain | The problem, what it costs, and who feels it | "What happens if nothing changes for another six months?" |
| C | Champion | Someone inside with influence who wants you to win | "If I'm not in the room, who argues for this?" |
| C | Competition | Every alternative, including doing nothing and building it | "What else are you looking at, including fixing this yourselves?" |
The I is "Identify pain" in the original MEDDIC and "Implicate the pain" in some later versions. Implicate is the better word for the job: you're connecting the problem to something the economic buyer already cares about, not just noting that a problem exists.
MEDDIC vs MEDDICC vs MEDDPICC: what's the difference?
They're the same framework at three sizes.
| Version | Letters | What it adds | Built for |
|---|---|---|---|
| MEDDIC | 6 | The original: metrics, buyer, criteria, process, pain, champion | Enterprise deals with several people deciding |
| MEDDICC | 7 | Competition | Markets where you're rarely the only option |
| MEDDPICC | 8 | Paper process and competition | Deals that slip in legal, security review or procurement |
The paper process letter exists because of a pattern most enterprise sellers will recognise. The buyer says yes in October and the contract signs in February. Nothing went wrong in the sales sense. The deal simply met a security questionnaire, a vendor onboarding form and a legal review that nobody had mapped, and each of those has its own queue. MEDDPICC asks you to map that queue before you put a close date in the forecast.
Competition got its own letter for a similar reason. The alternative that kills most deals usually isn't a rival vendor. It's "we'll leave it until next year", or "our engineers say they can build it". A competition field that only lists other companies misses both.
The three questions underneath the eight letters
Eight letters is a lot to hold in your head during a call. It helps to notice that they answer three questions.
Is it worth it to them? That's pain and metrics. If you can't state the cost of the problem in the buyer's own numbers, the rest of the framework is decoration.
Who decides, and how? Economic buyer, decision criteria, decision process and paper process. Four of the eight letters, which tells you where the framework thinks deals really get lost.
Can you win it? Champion and competition. A deal can be worth it and well understood and still go to someone else, or to nobody.
On a first call you'll mostly be working on the first question. By the third call, if the second question is still mostly blank, the deal is less advanced than it feels.
Heard is not the same as verified
The most common way MEDDPICC fails is quiet. A rep has a good call, fills in all eight fields in the CRM, and the deal looks fully qualified. Then it slips, and nobody can say why, because on paper everything was known.
What was missing is the difference between something the buyer said and something you've confirmed. "The CFO signs off on this" is a claim your contact made. "The CFO joined the second call and asked about payment terms" is a fact. Both fill in the E box. Only one of them should.
So score each letter in three states instead of yes or no:
| State | Means | Example for the economic buyer |
|---|---|---|
| Unknown | You haven't asked, or got no answer | "Not sure who signs" |
| Heard | Your contact told you | "Maria says the CFO approves anything over $50k" |
| Verified | You've seen it yourself, in a meeting, in writing or in a document | "The CFO was on Tuesday's call and asked about terms" |
A forecast built only from verified letters will look worse than one built from heard ones. It'll also be closer to what actually happens.
A deal scored with MEDDPICC
An illustration, with a made-up company and made-up numbers, though the shape is a common one.
You sell contract management software. You've had two calls with the legal operations manager at a manufacturer with about 600 staff. Here's what the CRM says, and what's really behind each field.
| Letter | In the CRM | State | What's really known |
|---|---|---|---|
| Metrics | Cut contract turnaround from 3 weeks to 5 days | Heard | Her estimate. Nobody has measured the current 3 weeks |
| Economic buyer | General counsel | Heard | She says the GC signs. You haven't met the GC |
| Decision criteria | Ease of use, integrations | Verified | She sent over the requirements document |
| Decision process | Demo, then pilot, then decision | Heard | Who runs the pilot, and who decides after it, is unclear |
| Paper process | Standard | Unknown | Nobody has asked procurement anything |
| Identify pain | Contracts stuck in email | Verified | She showed you the shared inbox with 140 open threads |
| Champion | Legal ops manager | Heard | She likes the product. Whether she'll push for it is untested |
| Competition | One other vendor | Heard | "We're also talking to one other company" |
Every field is filled in, so the deal looks qualified. In practice two letters are verified, five are hearsay and one is blank. The honest forecast is "early, with real pain and an untested champion".
The next steps come straight out of the gaps. Ask her to bring the general counsel to the demo, and ask procurement what they need from a new vendor now, while it's still early enough to matter. If she won't do the first, she isn't a champion yet. She's a friendly contact, which is useful, but it's a different thing.
How do you test a champion?
A champion has two things: influence, and a reason of their own to want you to win. A friendly contact has the reason, or neither.
Three tests, roughly in order of how much they ask of the person:
- They give you information you couldn't get otherwise. The real decision process, who's sceptical, what the budget actually is. That shows trust.
- They get you access. A meeting with the economic buyer, or with the security team. That shows influence.
- They sell when you're not there. You hear later that they argued for you in a meeting you weren't in. This is the one that counts, and you usually only find out after the fact.
Someone who passes the first test and not the second is a coach. Coaches are valuable, but deals forecast on a coach tend to slip.
MEDDPICC vs BANT vs SPICED
These three get compared a lot, though they're aimed at different parts of a sale.
| Framework | Stands for | Best at | Weak at |
|---|---|---|---|
| BANT | Budget, Authority, Need, Timing | A quick check on a first call | How the decision actually gets made |
| SPICED | Situation, Pain, Impact, Critical event, Decision | Understanding the customer's situation, especially in recurring-revenue sales | Mapping the paperwork and the politics |
| MEDDPICC | The eight letters above | Forecasting large deals with several people deciding | Small deals, where most of it is admin |
SPICED comes from Winning by Design, and its critical event (a deadline or outside force that sets when a decision has to happen) is a sharper version of BANT's timing. BANT has trade-offs of its own, mainly that it turns away good buyers who haven't set a budget yet.
Plenty of teams end up using two of them: BANT or SPICED to decide whether a first conversation deserves a second, which is roughly the line between an MQL and an SQL, and MEDDPICC once a deal is big enough to forecast.
When is MEDDPICC overkill?
When the deal closes in two calls. If one person can say yes and the contract is a credit card, five of the eight letters collapse into the same answer, and filling in the fields is paperwork for its own sake.
When you're selling to a founder. The economic buyer, the champion and the decision process are all the same person, and they're sitting in front of you.
Before the first conversation. MEDDPICC needs answers from the buyer, so it can't tell you who to contact in the first place. For that you need fit and a reason to get in touch now, both of which you can see from outside: the four checks for outbound are covered here, along with the sales signals worth watching for.
And when it turns into a reporting exercise. If reps fill in letters to get through a pipeline review, the fields stop meaning anything. A manager who asks "how do you know?" about one letter per deal, every week, gets more out of MEDDPICC than one who insists all eight are filled in.