Most enterprise deals don't lose on product.
MEDDPICC is a sales qualification framework used in complex enterprise B2B deals. It structures a deal review around eight elements — Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, Competition — to surface what the seller knows, what they assume, and what they have not yet tested.
The framework descends from MEDDIC, created at PTC in 1996. MEDDIC had six letters; MEDDICC added Competition; MEDDPICC added Paper Process — the procurement, legal, and security gauntlet that follows commercial agreement. Each addition came from the same observation: deals were slipping for reasons the original framework did not surface.
What MEDDPICC is not: a discovery script, a closing technique, or a substitute for a full sales methodology like solution selling. It is the qualification layer — the structured test of whether a deal in pipeline is real. Run alongside discovery and value selling, it tells the team what is missing. Run as a stand-alone checklist, it becomes paperwork.
Three patterns make MEDDPICC more useful in 2026 than it was in 1996, when the underlying ideas first emerged.
The typical enterprise B2B deal involves more than a dozen stakeholders, often spread across geographies and functions. A deal review based on the AE's gut feel — once viable when three people made a decision — collapses against a committee where the seller has never met half the participants. MEDDPICC forces the team to name who matters and what they care about, before the deal is forecast.
Enterprise CROs are held to forecast accuracy in ways that did not exist a decade ago. A pipeline padded with deals that lack a named economic buyer or a documented decision process is not a forecast — it is a guess. MEDDPICC scoring gives the team a defensible answer to the question, "why is this deal in the forecast?"
Procurement, security review, legal redlines, and AI governance committees now extend the close cycle in regulated industries. Paper Process — the second P that distinguishes MEDDPICC from MEDDICC — exists because that gauntlet kills deals that looked closed. Deals do not slip because the buyer changed their mind; they slip because nobody mapped the steps from verbal yes to signature.
The teams that close their forecast are not the ones with the best sellers. They are the ones where the discipline of qualification survives the next reorganization, the next rep transition, and the quarter when the pipeline is light and the temptation to inflate is high.
Each element tests something different. The order matters less than the discipline of testing each against current evidence — not against what the seller hopes is true.
The quantified business outcome the buyer expects. Not "improve productivity" — closer to "reduce close-cycle time by 20% on a $400M pipeline." Without a number in the buyer's own language, value is asserted, not proven. The test: can you write the metric down in the buyer's own words, with their own number?
The single person who can release the budget. Not the project sponsor, not the user, not the IT director running the proof of concept. The economic buyer can say no when everyone else says yes. The test: have you met them, do you know what they care about, and would they take your call?
The written and unwritten standards the buyer will use to compare options. Written: RFP responses, security requirements, integration depth. Unwritten: the procurement leader's preference for a vendor she has used before, the CIO's caution about another platform commitment. Both matter. The test: could you draft the buyer's evaluation matrix from memory?
The sequence of approvals between today and a signature. Who reviews, who recommends, who approves. What happens if someone says no — does the process route around them, or does the deal stop? The test: can you draw the decision flow on a whiteboard, with names on every box?
The procurement, legal, security, and IT-governance steps that follow commercial agreement. Vendor onboarding, MSA redlines, security review, data processing agreements, AI governance committees. The test: have you walked the paper process with someone who has run it before in this account, and do you know how long each step takes?
The cost of inaction — what happens if the buyer does nothing. Pain has to be specific, owned, and quantified. "We're not happy with our current vendor" is not pain; "we lost two competitive deals last quarter because our deal-review process took eleven days" is pain. The test: can the buyer articulate the cost of doing nothing in their own words, in front of their boss?
An internal advocate who actively sells your solution when you are not in the room. A champion has personal credibility with the economic buyer, has something to gain from the deal closing, and will spend political capital to move it forward. A coach who shares information but will not advocate is not a champion. The test: would they defend your deal in a meeting you are not invited to?
What the buyer is also evaluating, where you are positioned, and what would make them choose another option. Includes the do-nothing option, which is the most common winner in enterprise deals. The test: can you name the alternatives — including in-house build and "wait six months" — and the conditions under which each would beat you?
Eight elements is a lot to hold during a deal call, which is why MEDDPICC works as a structured deal review, not as a discovery script. The conversation is set by the buyer; the qualification structure is set by the framework.
The three variants in circulation are the same framework with different scope. The version a team uses tells you what failure modes their deals tend to hit.
The original — Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion. Created at PTC in 1996, adopted broadly through the 2000s as the baseline qualification layer in enterprise software. Still useful for deals where competition is light and procurement is straightforward.
Adds a second C for Competition. Reflects what happened to enterprise software through the 2010s — categories crowded, every deal became a multi-vendor evaluation, and "what else are they looking at" became a discipline that could not be skipped.
Adds a P for Paper Process. Reflects what happens after verbal agreement in modern enterprise deals — procurement, legal review, security audit, data processing agreements, AI governance committees. Teams selling to regulated industries, public sector, or large enterprises rarely operate without it.
A small minority of practitioners write it as MEDDPICCC, treating Champion and Coach as separate letters. The eight-letter form is the dominant convention.
BANT (Budget, Authority, Need, Timeline) and MEDDPICC are often compared as if they were alternatives. They are not. They sit at different points in the funnel and answer different questions.
BANT is an inbound triage framework. Built by IBM in the 1950s, refined since, designed to be run in a few minutes during a discovery call. It answers: is this lead worth a follow-up? Useful when an SDR is sorting hundreds of inbound leads a week.
MEDDPICC is a deal-execution framework. It runs alongside a deal for months, scored at every stage, surfacing risk as evidence accumulates. It answers: is this deal real, qualified, and forecastable? Useful when an AE is running 8 to 15 strategic opportunities and needs to know which ones are at risk.
Most enterprise teams running complex deals use both — BANT-style qualification for inbound triage, and MEDDPICC for the deals that pass triage and enter the pipeline. The mistake is using BANT alone for enterprise deals; budget and timeline give a junior view of qualification that misses the buying committee, the decision process, and the paper process entirely.
The framework is the easy part. The discipline of running it consistently — through pipeline reviews, rep transitions, quiet quarters, and noisy ones — is the work.
Most teams adopt MEDDPICC as a slide deck or a spreadsheet first. The first scorecard is built in a deal review. It gets emailed around. Two weeks later, half the team uses it and half does not; six weeks later, the rep who built it has moved on and the rest of the team is back to gut-feel forecasting.
The shift to running MEDDPICC inside Salesforce — as fields on the opportunity record, scores in a heat map, and a structured input to forecast review — is what makes the discipline durable.
Each letter is a structured field per opportunity, with the score and a free-text note describing the evidence. The opportunity record holds the qualification state in the same place as stage, amount, and close date.
Pipeline review opens a heat map: opportunities ranked by score, color-coded by the lowest-scored element. The forecast meeting starts with the cold deals, not the hot ones. The reps who know their deals best are the ones who can defend their scores against challenge.
When a rep leaves, the next rep inherits the scoring history alongside the deal. The new rep does not have to rebuild qualification from scratch — they have a record of what was tested, what was assumed, and what was missing.
ARPEDIO's opportunity management module runs MEDDPICC scoring as a native Salesforce object — eight scored fields per opportunity, a deal heat map across the pipeline, and integration with the rest of the account plan. The AI Agent layer is built lean — designed to read Salesforce data in a single pass without firing chargeable action events — to flag deals where evidence has gone stale or where a score and the underlying activity disagree.
A score taken at deal qualification and never updated is just a milestone. The framework's value is tracking how evidence changes — a champion who was a 3 last month and a 1 this month is a leading indicator. Static scoring misses the leading indicators entirely.
Pain is not a question you ask in the first meeting and then check off. Pain is the cost of inaction, owned by a specific buyer, quantified in their language, and re-tested as the deal evolves. A deal where pain was scored 3 in March and never revisited is a deal where the team has stopped listening.
A coach gives you information. A champion sells your deal in your absence. Most sellers have coaches; many fewer have champions. The cost of the confusion is forecast deals that lose at the buying committee because nobody was advocating when the alternative was being defended.
The paper process is where deals slip in the last 30 days of the quarter. Mapping it after verbal agreement is too late — by then, the seller has already forecast the deal, the procurement timeline is what it is, and the slip is structural. Map paper process while the deal is still being qualified, not while it is being closed.
The framework's job is to tell the team what is missing, not to tell management how confident the team is. Teams that report MEDDPICC scores to leadership without using the scoring to drive next-best actions turn the framework into theater. The scorecard is the output; the deal-review meeting is the work.
A North American technology services company running an inside-sales motion across mid-market and a strategic-account motion across the top 50 customers. The strategic team had adopted MEDDPICC two years earlier as a slide deck. Adoption was uneven; scoring drifted; forecast accuracy was around 60%.
The team moved MEDDPICC scoring into Salesforce as structured fields on every strategic opportunity, with a 0–4 scale and a defined evidence test per score. Pipeline review became a heat map. The first three reviews were uncomfortable — half the deals in forecast had economic buyers scored 0 or 1, and a third had no documented paper process.
Over the next two quarters, the discipline shifted. Reps stopped forecasting deals where the economic buyer was unknown. Pipeline shrank by 18%. Win rate on forecast deals climbed materially. The pattern is visible in the published WBM Technologies case, where opportunities scoring above a defined MEDDPICC threshold close at 98% — the heat map became the operating tool of the strategic-accounts team.
The Strategic Accounts Director's read at that point: the framework did not make any individual deal easier. It made the team honest about which deals were real. The lesson the team took away wasn't about the win rate. It was about the discipline of downgrading deals that were not qualified — the practice that, over two years, turned the forecast into something the CFO could plan against.
MEDDPICC is a sales qualification framework used in complex enterprise B2B deals. It structures a deal review around eight elements — Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, and Competition — to surface what the seller knows, what they assume, and what they have not yet tested. The output is a clearer view of whether a deal is real, what is missing, and what to do next.
MEDDPICC stands for Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, and Competition. Each letter names a discipline a seller has to demonstrate before forecasting a deal — quantified business outcomes, named approver, written criteria, mapped buying steps, mapped procurement steps, owned pain, internal advocate, and a competitive read.
MEDDIC is the original six-letter framework (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion), created at PTC in 1996. MEDDICC adds a second C for Competition. MEDDPICC adds a P for Paper Process — the procurement, legal, and security steps that follow commercial agreement. Most enterprise teams running long, regulated, or multi-stakeholder deals use the eight-letter version because the paper process is where deals slip late.
BANT (Budget, Authority, Need, Timeline) is a lightweight inbound qualification framework — designed to triage early-stage leads in a few minutes. MEDDPICC is a deal-execution framework — designed to run alongside a complex deal for months, surfacing risk as it changes. BANT asks whether a lead is worth pursuing; MEDDPICC asks whether the deal you are working is real, qualified, and forecastable. The two operate at different points in the funnel; teams running enterprise deals typically use BANT-style qualification to triage inbound and MEDDPICC to run the deals that pass.
MEDDPICC runs as a recurring deal review, not a one-off scorecard. The seller maps each of the eight elements against current evidence, scores each on a defined scale (commonly 0 to 4), and identifies the gaps. The deal-review meeting walks the lowest-scored elements and assigns next actions. The score moves as evidence is gathered and tested with the buyer — not when the seller feels more confident.
The second C is Competition — what the buyer is also evaluating, where you are positioned, and what would make them choose another option. The first C is Champion. Some teams write the framework as MEDDPICCC when they treat Champion and Coach as separate roles, but the eight-letter form (one Champion, one Competition) is the most common.
Strictly, MEDDPICC is a qualification framework — a checklist of disciplines that have to be present for a deal to be forecastable. A full sales methodology covers prospecting, discovery, value selling, negotiation, and close. MEDDPICC sits inside a broader methodology as the qualification layer. Most enterprise teams pair MEDDPICC with a discovery framework and a value-selling motion rather than treating it as the entire process.
There is no universal threshold — scoring scales and weightings vary by team. A common pattern is a 0 to 4 scale per element, with deals only forecastable above a defined cumulative score and with no element scored zero. The threshold matters less than the discipline of moving deals out of the forecast when key elements are missing, rather than carrying weak deals on optimism.
A champion is an internal advocate who actively sells your solution inside the buying organization when you are not in the room. A champion has personal credibility with the economic buyer, has something to gain from the deal closing, and will spend political capital to move it forward. A coach who shares information but will not advocate is not a champion — sellers commonly mistake coaches for champions and discover the difference late.
Yes. MEDDPICC works in any system that can hold structured data per opportunity, but Salesforce-native tooling makes it durable. The eight elements become fields on the opportunity record, scoring drives a deal heat map, and forecast review surfaces the lowest-scored deals. The discipline is the same; the platform changes whether the discipline survives the next reorganization or rep transition.
A 5-minute walkthrough of ARPEDIO's MEDDPICC heat map running natively on Salesforce — no form, no setup.