Every enterprise sales org above about $50M ARR eventually adopts MEDDIC. Or MEDDPICC. Or some in-house variant of it with an extra letter tacked on for the CRO's favorite risk category. The framework has become so ubiquitous that most sellers can recite the letters without being able to tell you where the deal actually stands.
That's the tension worth writing about. MEDDIC and MEDDPICC are inspection tools. They tell you where a deal is soft. They don't move the deal. Reps who confuse the two — who think filling in every letter is the same as progressing the deal — end up with perfectly qualified pipelines that don't close.
This guide covers what each letter actually means, the difference between MEDDIC and MEDDPICC, when to use each, and the qualifying question that surfaces each letter in a real conversation.
The short version
MEDDIC = Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion. MEDDPICC = the above, plus Paper Process and Competition.
MEDDIC works for medium-complexity B2B deals — six-figure ACV, three-to-six-month cycles, two-to-five stakeholders.
MEDDPICC works for enterprise and regulated deals — seven-figure ACV, six-plus-month cycles, procurement gates, security reviews, competitive bake-offs.
Both are qualification frameworks, not discovery frameworks. Neither one tells you what to ask on a call. They tell you what data you need to have logged before you forecast the deal.
Where MEDDIC came from
MEDDIC was developed at Parametric Technology Corporation (PTC) in the mid-1990s by Dick Dunkel, Jack Napoli, and John McMahon. PTC was selling seven-figure CAD software into industrial manufacturers. The problem they were solving wasn't discovery. It was forecast accuracy.
PTC was growing fast, but their forecast miss rate was destroying board credibility. Reps kept commit-ing deals that slipped. The pattern Dunkel and Napoli identified: reps were qualifying on need and interest but not on the machinery of how the buyer's organization actually made the purchase decision. MEDDIC codified the six data points that predicted whether a PTC deal would actually close.
The framework spread through the ex-PTC diaspora. McMahon went on to help build the sales orgs at BladeLogic, Ariba, Netsuite, and Glassdoor. Dozens of enterprise SaaS companies adopted MEDDIC in the 2000s and 2010s. It became the default enterprise qualification frame.
MEDDPICC was the evolution. As enterprise deals got more complex — more procurement gates, more security reviews, more competitive bake-offs — the original six letters weren't catching all the risk. Paper Process and Competition were added to surface the two most common causes of late-stage slippage.
The letters, decoded
M — Metrics
The quantifiable business impact of solving the buyer's problem. Not the technical output ("faster deployments") but the business number ("$3M in avoided cost, 15% reduction in cycle time").
Qualifying question: "If we solved this problem exactly as we're describing, what number in your business would move — and how much?"
Failure mode: Reps log "improved efficiency" as metrics. That's not a metric. That's a category. If you can't put a dollar or percentage on it that the buyer will defend in front of their CFO, you don't have metrics.
E — Economic Buyer
The person who can say yes without asking anyone. Not the champion, not the decision-maker on the RFP, not the head of the department. The person who owns the P&L that this budget comes from.
Qualifying question: "If your team decided today this was the right solution, whose signature moves the funds — and have they been in a conversation like this before?"
Failure mode: Confusing the champion with the economic buyer. Champions want the deal to close. Economic buyers approve the check. Sometimes they're the same person, usually they're not.
D — Decision Criteria
The explicit and implicit standards the buyer will use to decide between options. Explicit: RFP requirements, feature matrix, security certifications. Implicit: the CIO's private concerns about integration risk, the CFO's private concerns about ROI framing.
Qualifying question: "When you and your team compare options, what are the three things that will actually determine the choice — and which one carries the most weight?"
Failure mode: Only capturing the explicit criteria. The RFP tells you the surface. The implicit criteria are what actually decide the deal.
D — Decision Process
The sequence of steps between now and signed contract. Who reviews. Who approves. What gates exist. How long each gate takes historically. Whether the buyer has done this kind of purchase before.
Qualifying question: "Walk me through the last time your team bought something in this category — who was involved, how long did it take, where did it get stuck?"
Failure mode: Trusting the buyer's initial timeline. First-pass timelines from buyers are always optimistic. Ask them to walk you through the last comparable purchase and add 30% to whatever they said.
I — Identify Pain
The specific problem the buyer wants solved, articulated in their words. Not "efficiency" — "the last two product launches missed deadlines because our teams were duplicating work across three systems."
Qualifying question: "What's the specific event or moment that made this a priority now, rather than six months ago or six months from now?"
Failure mode: Logging generic pain. If the pain description could apply to any company in the industry, you don't have identified pain. You have a talking point.
C — Champion
A person inside the account who wants your deal to close, has credibility with the economic buyer, and will spend political capital to move the deal forward when you're not in the room.
Qualifying question: "Who inside your team is willing to defend this decision to leadership when it gets challenged — and what's their stake in it working?"
Failure mode: Mistaking a supportive contact for a champion. Champions do work when you're not there. Supportive contacts respond to your emails. Test the difference by asking the contact to book a meeting between you and their VP without your intervention. Champions do. Contacts don't.
The MEDDPICC additions
P — Paper Process
The procurement, legal, and finance path between verbal agreement and signed contract. In enterprise deals this can add 60-120 days entirely disconnected from selling.
Qualifying question: "Once your team decides to move forward, walk me through what happens with procurement, legal, and finance — where do most vendors get stuck?"
Failure mode: Discovering procurement exists in the last week of the quarter. Paper Process should be surfaced in the second call, not the last one.
C — Competition
Every other option the buyer is evaluating. Not just direct competitors — also DIY builds, incumbent tools they might expand, and the option of doing nothing.
Qualifying question: "If you don't buy anything at all, what happens? What would your team do instead?"
Failure mode: Only tracking named competitors. "Do nothing" wins more enterprise deals than any named competitor. If you don't have a plan to beat status quo, you don't have a strategy.
MEDDIC vs MEDDPICC: which one to use
The choice isn't ideological. It's a function of deal complexity.
Use MEDDIC when:
- ACV under ~$500K
- Cycle length 3-6 months
- 2-5 stakeholders
- Buyer has bought comparable software before
- Standard MSA, standard security review
Use MEDDPICC when:
- ACV above ~$500K, especially $1M+
- Cycle length 6+ months
- 6+ stakeholders including procurement, legal, security
- Buyer is in a regulated industry (financial services, healthcare, government)
- Explicit competitive evaluation with named alternatives
- First-of-kind purchase for the buyer's organization
The extra two letters aren't ceremonial. Paper Process catches ~40% of the late-stage slippage in enterprise deals. Competition catches the deals lost to status quo that would otherwise show up as "no decision" in the CRM without diagnosis.
Where MEDDIC gets misapplied
Treating it as discovery. MEDDIC is inspection. The data comes from discovery calls (see SPIN), not from asking the buyer "who's your economic buyer?" straight up. Buyers who get asked that question directly get defensive or lie.
Filling every field with something. Half the value of MEDDIC is knowing what you don't know. A deal with no confirmed economic buyer and a fabricated one entered in the CRM is worse than a deal with an empty field, because it hides the risk from the manager reviewing forecast.
Turning it into a checklist meeting. MEDDIC becomes low-value when reps recite the letters in a forecast call. The value is when the manager can inspect each letter against evidence — an email from the champion, a specific quote from the economic buyer, a documented paper process. No evidence, no qualification.
Confusing "identified" with "confirmed." You can identify a champion in the first call. You confirm they're a champion by watching them do something without you in the room. Same for economic buyer.
MEDDIC and multithreading
The framework assumes the seller has access to multiple stakeholders. Champion. Economic buyer. The people running the decision process. In practice, most enterprise deals get stuck because the seller has one contact and can't get to the rest.
This is where multithreading becomes the load-bearing motion. Boomerang data shows 40-55% more deals become multithreaded in stages 2-3 when reps have a systematic way to identify who inside the account has warm paths to the additional stakeholders MEDDIC requires. Without that, MEDDIC turns into a wish list — the rep knows what data they need and has no way to actually gather it.
The move: treat each MEDDIC letter as a research target, not a checkbox. Every unknown letter is a signal that a specific stakeholder needs to enter the deal. Then use whatever warm-intro path exists — customer, employee, partner, investor — to get to that stakeholder before the competition does.
MEDDIC in the AI era
The AI wave has made MEDDIC more useful, not less, but for a non-obvious reason.
Buyers now arrive at first calls with LLM-generated evaluation frameworks. They know what decision criteria to look for. They've generated the RFP with AI. They've had ChatGPT summarize the competitive landscape. Discovery calls that used to be exploratory are now more like structured interviews.
That shifts the seller's edge. The information asymmetry that used to favor the seller — knowing the category better than the buyer — has narrowed. What still favors the seller is knowing the buyer's specific organizational dynamics better than the buyer articulates them.
That's exactly what MEDDIC catches. Metrics only work if you know how this specific CFO thinks about ROI. Economic Buyer only works if you know how this specific org actually approves budget. Paper Process only works if you know how this specific procurement team behaves. All of that is context an LLM can't provide.
The MEDDIC discipline in 2026 is less about qualifying and more about surfacing organizational context the AI can't reach. Reps who use MEDDIC as an inventory of context questions — not a checklist — get the buyer to volunteer information that no one else selling into that account will have.
Example: MEDDIC scoring a live deal
A rep is working a deal at a $2B logistics company. The state after two calls:
- M: Buyer said the problem "costs a lot of money" but couldn't put a number on it. Weak. Not scored.
- E: Rep believes the SVP of Ops is the economic buyer. Never met them. Not confirmed.
- DC: Buyer shared a feature checklist. Explicit criteria clear. Implicit criteria unknown. Partial.
- DP: Buyer described the process as "we'll get you a decision in a few weeks." Not credible. No mention of legal, procurement, security.
- IP: Buyer named a specific event that made this a priority. Strong.
- C: Contact answers emails within a day. Has not booked any additional meetings without prompting. Not a champion. Supportive contact only.
The manager reviewing this deal has to make one call: not "is this qualified" but "what's the next research move." Weak M, unconfirmed E, and no champion means the deal is stuck in first-stage discovery no matter what the CRM stage field says. The next move is a champion-development motion, not a proposal.
That's the actual output of MEDDIC done well. It doesn't tell you the deal is dead. It tells you which specific piece of research to run next.
Frequently asked questions
Is MEDDPICC just MEDDIC with two extra letters? Structurally yes, functionally no. Paper Process and Competition catch specific risk categories that MEDDIC alone misses in seven-figure enterprise deals. If you're selling under $500K ACV, MEDDIC is enough. Above that, the extra two letters catch late-stage slippage that would otherwise show up as forecast miss.
Who invented MEDDIC? Dick Dunkel and Jack Napoli at Parametric Technology Corporation (PTC) in the mid-1990s, with John McMahon on the leadership team. The framework was built to fix PTC's forecast accuracy problem, not their discovery problem.
Can MEDDIC work for SMB deals? Not efficiently. MEDDIC assumes multiple stakeholders, formal decision processes, and identifiable economic buyers who aren't the same person as the end user. SMB deals often have all three roles in one person. For high-velocity SMB motions, BANT or a light qualification frame is better.
What's the difference between MEDDIC and MEDDPICC? MEDDPICC adds Paper Process (procurement, legal, finance path) and Competition (all alternatives including status quo). Same core, two additional risk categories.
How is MEDDIC different from SPIN? SPIN is a discovery method — how to structure the conversation. MEDDIC is a qualification frame — what data to log after the conversation. They layer. Run SPIN in calls, score with MEDDIC afterward.
Is MEDDIC still relevant with AI-assisted buying? More relevant, not less. The organizational context MEDDIC surfaces — how this specific buyer's org actually decides, who signs, how procurement behaves — is exactly the context LLMs can't generate. Reps who use MEDDIC as a research inventory get information no AI-generated evaluation framework contains.
