MEDDIC: the complete guide to qualifying B2B deals

If your company just rolled out MEDDIC and your CRM now holds six fields nobody can fill in honestly, this guide is for you.

MEDDIC is a B2B sales qualification framework built on six criteria: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion. It was created at Parametric Technology Corporation in the 1990s to qualify large, complex deals before a team invests months in them. Each letter is a question about the buyer's organization, not about your product. A deal is qualified when you hold verifiable evidence for all six, not when the six fields are filled in.

That last sentence is where most MEDDIC rollouts come apart. The framework is not hard to understand. It is hard to feed. This guide covers what each letter asks, and then the part almost nobody writes about: where the evidence for each one actually comes from.

Key takeaways

• MEDDIC qualifies a deal that is already in your pipeline, while a go/no-go decision qualifies whether to pursue an incoming opportunity at all.
• Across the ten editorial pages ranking in Google's US top 20 for "meddic" in August 2026, the words transcript, call recording and meeting notes appear zero times, and the word evidence appears twice in total.
• Four of the six MEDDIC criteria are established verbally, in discovery and stakeholder calls, which is why the CRM fields fill up with generic language.
• MEDDPICC adds Paper Process and Competition to the same six criteria, and fits deals that run through procurement or a formal tender.
• BANT is not obsolete. It answers a smaller question: BANT asks whether a lead is worth a call, MEDDIC asks whether a deal is worth a quarter.

What does MEDDIC stand for?

MEDDIC is an acronym for the six things you need to know about a deal before you can call it qualified. Read as a checklist, it takes two minutes to learn. Read as an evidence standard, it takes a full sales cycle to satisfy.

The table below adds a column you will not find in most explanations of the framework: what a rep typically writes in each field when the evidence is missing. If your CRM looks like the fourth column, you do not have a MEDDIC problem, you have a collection problem.

One clarification before going further, because the two get confused in bid teams. MEDDIC qualifies a deal that is already in your pipeline. Deciding whether to pursue an incoming opportunity in the first place is a different exercise with different criteria, covered in our go/no-go bid qualification framework. Run the go/no-go first, then run MEDDIC on what survives.

Who created MEDDIC, and when

Sources disagree on this, and the disagreement is worth resolving because it changes what the framework was designed to do. Some accounts credit Dick Dunkel, others credit Jack Napoli, and several credit both without distinguishing their roles.

The most precise account comes from MEDDICC, the organization that maintains the framework today: MEDDIC was created in 1996 inside PTC by Dick Dunkel, working under SVP John McMahon, alongside Jack Napoli. The useful distinction is between authorship and diffusion. Dunkel wrote it. Napoli and McMahon turned it into something an entire sales organization ran on.

That matters because MEDDIC was not designed as a lead scoring model. It was reverse engineered from won and lost enterprise deals, in a company selling six figure software to buying committees. It assumes a long cycle, several stakeholders, and enough deal value to justify the work of qualifying properly. Apply it to a two call transactional sale and it will feel like bureaucracy, because it is.

A note on the numbers you will see elsewhere: published accounts of PTC's revenue growth over this period contradict each other, so we have left the figure out rather than pick the most flattering version.

What each of the six criteria actually asks

Each letter below follows the same structure: the question, what a defensible answer looks like, and the signal that tells you the answer is not real yet.

Metrics

Metrics is the economic case for change, expressed in the buyer's units rather than yours. Not "we improve productivity," but "your support team handles 400 tickets a week and you want to hold that volume without hiring a fourth agent."

A defensible answer has a baseline, a target, and a source. The signal that it is not real: the number came from your own value calculator rather than from the buyer's mouth. A metric you supplied is a hypothesis. A metric the buyer supplied is a commitment you can quote back to them in month four when the deal stalls.

Economic Buyer

The economic buyer is the person who can release the budget without a second approval. Not the person who runs the evaluation, and not always the most senior person in the room.

A defensible answer includes a name, and an account of how you know. "Their CFO signs anything above 50k, my champion told me on the 12th" is evidence. A job title with a question mark is a guess. The signal that it is not real: you have never spoken to this person and you are planning to meet them at the end of the cycle. If the economic buyer only appears at signature, you are not selling to them, you are hoping about them.

Decision Criteria

Decision criteria are the standards the buyer will actually judge vendors against, in their order of importance. Technical, commercial, and often political.

The best possible evidence here is written and comes from the buyer: an evaluation grid, a scoring sheet, a procurement requirements list. Second best is the criteria repeated back in a call and confirmed. The signal that it is not real: your notes list the criteria in the order that flatters your product. Buyers rarely rank price first out loud and rarely rank it last in practice.

Decision Process

The decision process is the sequence of steps, owners and dates between today and a signed contract. Legal review, security review, procurement, board approval, budget cycle.

A defensible answer is a dated sequence with a named owner per step. The signal that it is not real: a single quarter written in the close date field. "Q3" is not a process, it is a wish. This is also the criterion that changes most often, which is exactly why it decays fastest in a CRM.

Identify Pain

Identify Pain is the business consequence of doing nothing. It is not a feature gap. A feature gap produces a nice to have. A consequence produces a budget.

A defensible answer connects a specific event to a cost or a risk: a failed audit, a missed renewal, a team that lost two people because of the workload. The signal that it is not real: the pain is described in your product's vocabulary rather than in the buyer's. If you can only articulate the pain by naming your own category, the buyer has not felt it yet.

Champion

A champion is someone with internal influence who sells on your behalf when you are not there. Three conditions, all required: they benefit personally from the change, they have credibility with the economic buyer, and they are willing to spend some of it.

The evidence for a champion is behavioral, never declarative. Did they introduce you to someone senior? Did they forward your document internally? Did they tell you something they were not supposed to? The signal that it is not real: your champion is friendly, responsive and pleasant, and has never once put themselves at risk for your deal. That is a contact, not a champion. It is the single most over reported field in MEDDIC.

Is MEDDIC outdated, or just badly implemented?

MEDDIC is not outdated. It is, in a lot of organizations, quietly resented, and the reason is worth taking seriously rather than dismissing as rep laziness.

The most visible statement of the objection sits on Reddit, in an r/sales thread that ranks on the first pages of Google for the term itself and drew more than eighty comments. Its argument is that MEDDIC and its peers have become CRM exercises disguised as a sales methodology, with reps filling out fields to keep managers off their backs. If you have sat through a deal review where six fields were read aloud and nobody learned anything, you have watched this happen.

Here is the part that makes the objection more than venting. In August 2026 we took the ten editorial pages ranking in Google's US top 20 for "meddic" and counted terms across their main content, with word boundaries applied to avoid false matches. The results:

• transcript: 0 occurrences across all ten pages
• call recording: 0 occurrences
• meeting notes: 0 occurrences
• verbatim: 0 occurrences
• evidence: 2 occurrences in total, on two of the ten pages

Ten guides explain what the six letters mean. None of them explain where the answers come from. That gap is not an editorial oversight, it is the actual failure point, and it lands squarely on the rep. The framework asks for evidence, the training explains the letters, and nobody addresses the twenty minutes of retrieval work that separates the two. So reps write what they remember, managers inspect what reps wrote, and everyone treats the resulting document as if it described the deal.

Badly implemented MEDDIC is a reporting layer. Well implemented MEDDIC is an inspection tool that tells you what you do not know yet. The difference is entirely in the sourcing.

Where the evidence for each criterion actually lives

Run through the six criteria and ask a narrower question than usual: not "what is the answer," but "in what artifact was this answer created?" The pattern that emerges explains most of the empty fields.

Four of the six are established verbally. They exist as audio, in calls that were recorded and never listened to again. The evidence is not missing, it is unretrieved, and the retrieval cost is high enough that a rep with eight live deals will rationally choose to type from memory instead.

This is the case for pulling qualification evidence from the deal record rather than from recall. Cobl connects to call platforms and reads transcripts against the deal, so a metric a buyer stated on a call in week two is still available in week nine, in the buyer's own wording. The Gong integration consolidates several calls on the same deal rather than treating each one separately, which is what MEDDIC requires: the decision process rarely emerges in one conversation.

The champion criterion is a special case, because it cannot be interviewed into existence. What you can do is give your champion something usable and then watch what they do with it. Cobl reports how many times a shared document was opened and viewed, which converts an unanswerable question into an observable one: a champion who circulated your internal business case is behaving like a champion, and one who never opened it is a contact.

How to run MEDDIC without adding admin work to your reps

The failure mode of every qualification rollout is the same: the framework arrives as an obligation, the CRM grows six fields, and nothing is removed to make room. Four things separate the rollouts that hold.

1. Define the evidence standard before the field. Decide, as a team, what an acceptable answer looks like for each letter, using the third column of the first table above. A field without a standard becomes a text box.
2. Source from the record, not from memory. If filling six fields means re listening to three calls, it will not happen twice. Pull from transcripts, emails and shared files, and let the rep confirm or correct rather than reconstruct.
3. Inspect gaps, not completeness. In deal reviews, ask which criterion is weakest and what would close it. A review that checks whether fields are populated teaches reps to populate fields.
4. Calibrate against your own outcomes. After a quarter, compare the criteria present in won deals against those in lost deals. In most B2B organizations two letters carry most of the predictive weight, and they are not the same two everywhere. Your win rate analysis tells you which ones.

The objection to all of this is time, and it is a fair one. It is also measurable. At Randstad, moving recurring document work from manual drafting to generated first drafts cut the time per item from roughly 25 minutes to 3, a saving of more than 88% on that task. Qualification notes are not job postings, but the mechanism is identical: the expensive part is assembly, not judgment, and assembly is the part that can be handed off.

MEDDIC vs BANT: which one fits your deal?

BANT stands for Budget, Authority, Need, and Timeline. It predates MEDDIC by decades and gets dismissed more often than it deserves. The two frameworks are not competitors, they answer questions of different sizes.

The honest position: BANT is not dead, it is misapplied. Using it to qualify a nine month enterprise deal is the actual error, because "Authority" quietly asks you to name one decision maker in a committee of twelve. Using MEDDIC to qualify an inbound demo request is the opposite error, and it is the one that generates the resentment described earlier. Many teams run both, BANT at the top of the funnel and MEDDIC from the first qualified opportunity onward.

MEDDIC vs MEDDPICC: what the two extra letters add

MEDDPICC keeps the six MEDDIC criteria and adds two that matter once a deal reaches a buying organization with formal procedures.

You will also see MEDDICC with two Cs, where the second C stands for Competition alone. The distinctions are real but minor. Choose the version that matches how your buyers actually purchase, and do not run two variants in the same organization.

Paper Process is where qualification stops being a note taking exercise and turns into production work. At CERAP Prevention, tender responses and compliance dossiers regularly run past 200 pages, and Eric Henon, its Director of Subsidiaries and Development, described the old routine plainly: rereading everything each time, checking that nothing had changed, and copy pasting carefully, which was repetitive, slow and error prone. Preparing tender responses moved from about three days to one. If your deals include a paper process, budget for it during qualification rather than discovering it two weeks before the deadline.

What MEDDIC will not tell you

Qualification frameworks describe a deal. They do not create demand, and they are not a substitute for judgment.

• It will not tell you how to sell. MEDDIC assesses. It contains no guidance on discovery technique, negotiation or objection handling.
• It will not tell you whether you should have taken the deal at all. That is a go/no-go decision, made earlier and on different criteria.
• It is poorly suited to short, low value cycles. The overhead exceeds the deal.
• It can be gamed. Any framework tied to forecast expectations will be filled in optimistically. This is a management problem, not a framework problem.
• Automated evidence still needs a human check. Pulling a metric from a transcript can misattribute who said it or strip the qualifier that changed its meaning. Whatever tooling you use, the rep confirms before the answer counts. AI is useful for retrieval, not for judgment.

Qualify on evidence, not on fields

MEDDIC has held up for close to thirty years because the six questions are the right ones. What has changed is that the answers now sit in recorded calls, shared files and message threads that no rep has time to mine by hand. Teams that treat qualification as a retrieval problem get a real picture of their pipeline. Teams that treat it as a form get a tidy CRM and the same forecast surprises as before.

If you want the evidence assembled for you from the deal itself, rather than typed from memory at the end of the week, you can try Cobl for free for 30 days.