MEDDIC and MEDDPICC: Qualifying the Deals Worth Chasing

Every sales leader has sat in a pipeline review where a rep swears a deal is "90 percent" and can't answer basic questions. Who signs? What are they measuring? Who else is in the running? What happens if they do nothing? That deal isn't 90 percent. It's a hope with a close date attached.

MEDDIC exists to end that conversation. It's a qualification framework rather than a selling technique: a checklist of what you have to know about a deal to forecast it honestly, and a set of questions that tell you what to go find out next. Its extended form, MEDDPICC, adds two letters that reflect how enterprise buying has changed since the original.

Where it came from

MEDDIC came out of Parametric Technology Corporation (PTC) in the mid-1990s. PTC was a Boston-area engineering software company that grew from roughly $300 million to over $1 billion in revenue in a few years. Jack Napoli and Dick Dunkel are credited with codifying the framework as PTC's sales org scaled, and John McMahon, PTC's sales leader at the time, drove its adoption. Dunkel later joined Force Management, which still teaches it.

PTC's sales culture became famous for its rigor, and its alumni carried MEDDIC to BladeLogic, Snowflake, MongoDB, and dozens of other companies. McMahon's 2021 book The Qualified Sales Leader describes that lineage. Along the way the framework grew. MEDDICC added a second C for Competition; MEDDPICC added P for Paper Process. Andy Whyte's book MEDDICC (2020) and the MEDDICC company popularized the expanded versions. These days "MEDDIC" gets used loosely to mean any of them.

Where it fits best

MEDDIC was born in large enterprise deals and that's still its home. It fits when:

• Deals are big enough that a wasted quarter on an unqualified opportunity really hurts.
• Buying involves many stakeholders, formal decision processes, and procurement.
• Forecast accuracy matters to the business and the board.
• Sales cycles are long enough that deals can quietly rot without anyone noticing.

It's overkill for small, transactional deals, where the qualification overhead costs more than the deal is worth. And it doesn't replace a conversation methodology. MEDDIC tells you what you need to know; methods like SPIN or Command of the Message tell you how to have the conversations that uncover it.

How the methodology works

Each letter is a question about the deal. A deal where any letter is blank is not qualified, whatever the rep feels about it.

M: Metrics

The quantifiable business outcomes the customer expects. Not "improve efficiency" but "reduce order-to-cash from 45 days to 30," "cut infrastructure spend by $2M annually," or "add 10 points of gross margin." Metrics give the deal an economic justification and give the champion something to defend the purchase with internally. If the customer can't name a metric, the seller's job is to help them find one. If none exists, the deal is in trouble.

E: Economic Buyer

The person with the authority to spend the money and the discretion to spend it on this. Often not the champion, and often not the person the seller has been talking to for three months. The economic buyer's priorities can differ from the champion's, so the seller has to understand them directly. By MEDDIC's rules, a deal where the seller hasn't met the economic buyer is not forecastable. Full stop.

D: Decision Criteria

The formal and informal standards the customer will use to choose: technical requirements, integration needs, security reviews, vendor viability, price, and usually a few unstated preferences nobody writes down. The seller wants to understand the criteria and, where possible, nudge them toward their strengths before they get locked.

D: Decision Process

The sequence of steps, approvals, and events between today and a signed contract. Who evaluates, who reviews, who signs, in what order, on what timeline. Knowing the process is what lets a seller set a realistic close date instead of picking the last day of the quarter.

P: Paper Process (MEDDPICC)

The legal and procurement track that runs alongside the decision process: contract review, security questionnaires, vendor onboarding, purchase orders. In many enterprises it takes longer than the decision itself. Sellers who ignore it forecast a deal for this quarter that closes next quarter, and then do the same thing the quarter after.

I: Identify Pain

The business problem driving the purchase, and what it costs. MEDDIC insists that pain be specific and quantified, and that the economic buyer feel it, rather than only the end user. Pain ties back to Metrics: the metric is the measure of pain relieved.

C: Champion

Someone inside the customer who has power and influence, who personally benefits from the purchase, and who will sell on the seller's behalf when the seller isn't in the room. MEDDIC is strict about this. A friendly contact is not a champion. A champion has to be tested. Will they arrange access to the economic buyer? Will they share internal information? Will they advocate when it costs them something?

C: Competition (MEDDICC / MEDDPICC)

Every alternative the customer is weighing, including doing nothing, building it internally, or sticking with an incumbent tool. The seller needs to know the whole field and how each option scores against the decision criteria.

Running it

MEDDIC usually runs as a scorecard. Each letter gets a rating (unknown, partial, confirmed, or similar) and gets reviewed in pipeline meetings. Gaps become next steps: "We don't know the paper process, so the action is to ask the champion for the procurement timeline." Over time the scorecard is what makes forecast calls honest, because a deal's stage is tied to what's actually known rather than to how confident the rep sounds.

A worked example

A rep forecasts a $400,000 data platform deal for the quarter. The MEDDPICC review:

• Metrics: Confirmed. Customer expects to retire two legacy systems saving $600K a year.
• Economic Buyer: The CIO. Rep has not met them. Gap.
• Decision Criteria: Partial. Technical criteria known; security review requirements unknown.
• Decision Process: Partial. Technical evaluation done; steering committee date unknown.
• Paper Process: Unknown. Gap.
• Pain: Confirmed. Legacy systems fail monthly; the outage cost is documented.
• Champion: The data platform lead. Has shared internal docs and offered to arrange the CIO meeting. Confirmed.
• Competition: One rival vendor plus "extend the legacy contract." Known.

Three gaps, two of them serious. The manager moves the deal out of commit, and the next steps write themselves.

Strengths and limitations

MEDDIC's great virtue is that it forces honesty and gives reps and managers a shared language. Its weakness is that it turns into box-ticking, with reps filling in fields to satisfy the CRM rather than to understand the deal. We've seen scorecards where every letter says "confirmed" and nobody has met the CIO. It also says nothing about how to create pain or metrics where none exist, which is why it pairs so naturally with a conversation methodology. And it's only as good as the data behind it. That is a systems problem as much as a training one.

Key takeaways

• MEDDIC is a qualification framework, not a conversation method. It tells you what to know and leaves how to sell to other methods.
• It came out of PTC in the 1990s and spread through that company's alumni to much of enterprise software.
• Each letter is a question, and a blank letter means the deal isn't qualified, whatever the rep's gut says.
• MEDDPICC adds Paper Process and Competition to keep up with modern enterprise procurement.
• A champion has to be tested, never assumed. A friendly contact who won't get you to the economic buyer isn't one.

MEDDIC scorecards live or die on data quality. When champion changes, procurement milestones, and competitor mentions get captured as revenue signals instead of typed into a CRM field weeks after the fact, the scorecard stops being a ritual and turns into a forecast you can trust.