What is MEDDPICC?

What does MEDDPICC stand for?

MEDDPICC stands for Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Implicate the Pain, Champion, Competition. It is a sales qualification framework: a fixed set of questions a seller answers about a specific opportunity, used to decide whether the deal is real, how likely it is to close, and what is missing before it can.

It is not a sales process (the stages a deal moves through) and it is not a script (what you say on a call). It sits underneath both: at every stage, you should be able to answer more of the eight letters than you could at the last one. A deal that has moved from stage 2 to stage 4 with no new MEDDPICC answers has not actually progressed, whatever the pipeline report shows.

The framework predates the acronym's current form. It started as six letters, MEDDIC, and two more were added later. The next section covers exactly where each version came from, because the origin has been the subject of a real US federal court case decided this year, and the honest answer is more interesting than "nobody knows."

Where MEDDPICC actually came from

MEDDIC was created in 1996 inside PTC (Parametric Technology Corporation), by Dick Dunkel, working under SVP John McMahon alongside teammate Jack Napoli. PTC's sales team had grown to roughly 300 reps and was losing people faster than it could hire and train replacements. McMahon tasked Dunkel and Napoli with finding out, systematically, why PTC won deals, why it lost them, and why deals slipped. The pattern that held across the team's opportunities became six letters: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion. PTC's sales organisation grew from $0 to $1 billion in revenue over the following decade, and MEDDIC is widely credited as part of that discipline.

That history comes from MEDDICC Ltd's own account, published on its site and corroborated by Dick Dunkel's own recorded interview with the company. It is also, as of April 2026, on the public record in federal court. A US District Court found that the term "coined in 2005 by former Parametric Technology Corporation (PTC) employees" was "built on the earlier MEDDIC acronym developed at PTC in the early 1990s," a slightly earlier dating than MEDDICC Ltd's own "1996," though both point to the same company and the same original team.

Two letters were added later: a second C for Competition, and a P for Paper Process, forming MEDDPICC. MEDDICC Ltd, the company founded in 2020 by Andy Whyte (an 18-year enterprise sales veteran who learned the framework directly from Dick Dunkel while at Sprinklr, and author of the book MEDDICC), calls this eight-letter version "our preferred variation." It is the version most enterprise sales teams mean today when they say MEDDPICC, and it is the version this article walks through letter by letter.

Lahoutifard's own account, published on MEDDIC Academy's site, does not dispute that he did not coin the acronym. His argument is narrower: that a trademark protects a training product's name, not the underlying idea, the way Six Sigma or PRINCE2 can be trademarked as certification brands while the methodology itself stays open. He points to codifying the framework into the first public MEDDIC slide deck in 2013 and the first paid MEDDIC/MEDDPICC certification course in 2017 as his real contribution, and quotes McMahon's own 2023 description of the framework's origin as "an iterative, organic process," not a single invention. The court sided with MEDDICC Ltd on the trademark question. Neither side disputes that the framework itself grew out of PTC's sales floor in the 1990s and 2000s and has no single living owner.

Why this matters for a reader deciding whether to use MEDDPICC: it means no vendor can restrict who teaches it, writes about it, or builds software around it. The version described in this article is free to use in any CRM, with any team, with no licence required.

The eight letters, the question each one tests, and where the answer lives

Each letter below follows the same shape: what it means, the question a rep should be able to answer out loud on a deal review, and the CRM field that should hold the answer so it survives past the call. The field-naming convention is MEDDICC's own, taken from its CRM integration documentation (its enterprise product syncs MEDDPICC data into HubSpot and Salesforce using exactly this pattern): one status field, one notes field, per letter.

Metrics: the quantified value of your solution

Metrics are the specific, quantified business outcomes your solution is expected to deliver for this customer, not a generic ROI slide. MEDDICC's own materials split them into three kinds: M1s (outcomes you have already delivered for other customers, used to open a conversation), M2s (the outcome personalised to this prospect's numbers), and M3s (the M2 validated after go-live, which then becomes a new M1 for the next deal). A metric with no number attached, "improves efficiency," is not a Metric in this framework; it is a claim waiting for one.

Question to ask: What number does this customer expect to move, and did they tell you that number or did you assume it?

CRM field: metric_status (a strong / medium / low picklist) and metric_notes (long text, where the actual figure and its source live). A metric that only exists in a slide deck and never makes it into the notes field does not survive the deal being handed to another rep, or to Customer Success at renewal.

Economic Buyer: the person with the overall buying authority

The Economic Buyer is the person who can say yes when everyone else says no, and no when everyone else says yes. They rarely announce themselves. MEDDICC's guidance is to look for veto power over the budget line, priorities that track the organisation's strategic goals rather than one department's, and access to funds that were not already earmarked for this purchase. A VP who loves your product but has to ask someone else for the money is not the Economic Buyer; they are, at best, a strong Champion.

Question to ask: If this person said no tomorrow, could anyone else in the account overrule them?

CRM field: economic_buyer_status and economic_buyer_notes. The notes field is where you record not just a name, but how you confirmed the authority, since "I assume it's the CFO" is a guess, not a qualified field.

Decision Criteria: how your solution is evaluated

Decision Criteria are the standards the buying committee will actually judge proposals against, and MEDDICC groups them into three kinds: Technical (does it functionally do the job), Economic (cost, risk, return), and Relationship (do the two organisations' values and working style fit). Different stakeholders weight these differently. A CTO leans technical; a CFO leans economic. The framework's real warning is that most prospects have not written their criteria down before you arrive, which means an unshaped set of criteria is an opening to help shape them in your favour, not a gap to wait out.

Question to ask: Has the buying committee agreed on criteria in writing, or is everyone privately scoring you against something different?

CRM field: decision_criteria_status and decision_criteria_notes, ideally with the technical, economic and relationship components broken out as separate lines inside the notes so a reviewer can see which one is weak.

Decision Process: how the buyer decides on your solution

The Decision Process is the sequence of steps and approvals the buyer will follow to reach a purchase decision, typically split into technical validation and business/financial approval. MEDDICC's own material makes a sharp distinction worth repeating exactly: engagement is not progress. Extra demos, reference calls and reports do not move a deal forward unless they correspond to a confirmed step in the buyer's actual process. Without knowing the steps, a rep cannot tell the difference between a deal that is advancing and one that is simply generating activity.

Question to ask: Name the next three approvals this deal needs, in order, and who signs each one.

CRM field: decision_process_status and decision_process_notes, cross-referenced against your own pipeline stages so a stalled Decision Process (unlike a stalled pipeline stage) is visible on its own.

Paper Process: how you go from decision to signature

The Paper Process is everything that happens after the buyer has decided to buy and before a signature exists: legal review, security questionnaires, procurement sign-off, Master Service Agreement negotiation. MEDDICC treats this as a distinct letter, separate from Decision Process, because deals that have cleared every technical and business hurdle routinely stall here for weeks, and a forecast that does not track the Paper Process separately cannot see that risk coming.

Question to ask: Has legal or procurement seen this deal yet, and do you know their standard turnaround time?

CRM field: paper_process_status and paper_process_notes, updated whenever the deal touches a new internal reviewer on the customer's side. This is also the field most often left blank on deals that later slip a quarter, because "we're basically done, just paperwork" is exactly the moment sellers stop tracking it.

Implicate the Pain: the problem your customer is facing

Implicating the Pain means making the customer feel the specific, personal consequences of the problem you solve, not merely getting them to admit the problem exists. MEDDICC's own phrasing distinguishes "identifying" a pain (the customer agrees it is a problem, in the abstract) from "implicating" it (the customer understands what happens to them specifically if it stays unsolved). Without that second step, there is no urgency, and a deal with no urgency loses every tie-break against a competing priority.

Question to ask: What happens to this person, specifically, in the next two quarters if nothing changes?

CRM field: implicate_pain_status and implicate_pain_notes. Note the naming discrepancy worth flagging directly: MEDDICC's own site labels this letter "Implicate the Pain," while a large share of the wider industry, including many MEDDIC-trained sellers, still says "Identify Pain," the term from the original six-letter version. Both describe the same letter; only the emphasis changed as the framework matured.

Champion: who can help drive your deal forward

A Champion is a person inside the account with power, influence and a genuinely vested interest in your win, who will act as an internal seller on your behalf when you are not in the room. MEDDICC's test has three parts, and a contact needs all three to count: power and influence, a willingness to sell internally for you, and a personal stake in the outcome. A helpful contact missing one of those three is a Coach, useful for information, but not able to carry the deal alone. The framework's own summary is blunt: no Champion, no deal.

Question to ask: Has this person ever introduced you to someone above them, unprompted?

CRM field: champion_status and champion_notes. Distinguishing a real Champion from a friendly Coach in this field, rather than defaulting every warm contact to "Champion," is one of the more common places MEDDPICC gets applied loosely.

Competition: any alternative person, vendor, or initiative

Competition is anything competing for the same budget or attention as your deal, and MEDDICC's own breakdown names four kinds worth tracking separately: direct rivals, a self-build alternative, a different initiative competing for the same funds, and inertia (the customer doing nothing at all). MEDDICC titles one of its own training videos "The #1 Competitor You're Ignoring in Every Sales Deal," and on its Decision Process page states that 60% of deals are lost to it, a figure published on MEDDICC's site without an external citation, so treat it as MEDDICC's own claim about its own client base rather than an independently audited industry statistic.

Question to ask: If this deal dies, what does the customer do instead, including doing nothing?

CRM field: competition_status and competition_notes, with inertia tracked as its own line rather than folded into "no named competitor," since "no competitor" and "the customer might just do nothing" are different risks that need different plays.

A worked example: qualifying one deal against all eight letters

Take a mid-market manufacturer evaluating a new field-service scheduling platform, a €60,000 annual deal with a six-month sales cycle so far.

Read across that table and the deal's real risk is obvious in a way "we're in stage 4 of 6" never shows: the Metrics, Champion and Pain are genuinely strong, but the Economic Buyer has never been met and the Paper Process has not started. A forecast built on stage alone would call this deal on track. A forecast built on MEDDPICC would flag it as one confirmed introduction to the COO away from being genuinely qualified, and one procurement conversation away from a Paper Process surprise in month seven.

Where MEDDPICC gets applied badly

The framework is precise. The way teams roll it out often is not. Four mistakes show up repeatedly across how MEDDPICC actually gets used, not in the framework itself:

• Filling in the status field without the notes field. A picklist marked "Strong" with no supporting text is an opinion, not qualification. The value of MEDDPICC comes from what is written in the notes, which is exactly the field most sales teams skip under time pressure.
• Treating a Coach as a Champion. MEDDICC's own three-part test exists because this substitution is the single most common way deals look qualified and are not. A friendly contact with no power to introduce you upward is not carrying your deal.
• Confirming Decision Criteria once and never revisiting it. Criteria shift as new stakeholders join a buying committee, and a criteria field last updated two months ago on a six-month deal is stale by definition.
• Scoring every letter the same way regardless of deal size. An eight-field framework applied with equal rigour to a €4,000 self-serve deal and a €400,000 enterprise deal wastes time on the small one and still under-serves the large one; see the next section.

When MEDDPICC is the wrong tool

MEDDPICC was built inside PTC for exactly one kind of deal: enterprise, multi-stakeholder, with a real procurement process and a genuine chance the deal never closes at all. It carries real cost to run: eight fields, a notes discipline, and a rep trained to ask about the Paper Process before it becomes urgent.

That cost does not pay for itself on every deal. A short sales cycle, a single decision-maker, and a low enough price that the buyer does not need internal sign-off is the profile where a lighter framework fits better. BANT (Budget, Authority, Need, Timeline), the older and simpler alternative, asks four questions instead of eight and skips Paper Process and Competition almost entirely, which is exactly the trade a transactional deal can afford to make. The two frameworks solve different problems: BANT asks "is this worth our time," MEDDPICC asks "will this specific deal actually close, and what is standing in the way." For a full side-by-side, including where each one breaks, see BANT vs. MEDDIC vs. MEDDPICC.

The practical rule most enterprise teams land on: run MEDDPICC in full on deals above a threshold size or with more than one buying stakeholder, and let smaller, single-stakeholder deals use a lighter check. Applying all eight letters to a deal that will never touch procurement is qualification theatre, not qualification.

Why MEDDPICC lives in the CRM, not the deal review

A rep can recite all eight letters from memory in a deal review and still lose the deal, if none of it is written down anywhere another person can see. MEDDPICC's actual value shows up at three moments a spoken answer cannot reach: when a manager reviews forty deals in an hour and needs the notes field, not a meeting, to spot the weak one; when a deal is handed to a new rep mid-cycle and the incoming rep has to reconstruct six months of context from what is written, not what was said; and at renewal, when the M2 metric promised at the start becomes the M3 result Customer Success is expected to defend.

None of that works if MEDDPICC lives only in a spreadsheet a manager keeps privately, or in a rep's head. It has to be structured fields on the deal record itself, which is a CRM and reporting problem before it is a sales-skill problem. For the mechanics of building that structure so it survives contact with a real pipeline, see Revenue operations KPIs your CRM cannot calculate and Sales infrastructure: the rules layer.

If your team already runs MEDDPICC in deal reviews but the fields it produces do not make it into the CRM, or make it in but nobody trusts what is there, that is a system problem, not a training problem.

If you want a second pair of eyes on your own setup, Salestruct runs a free diagnostic.