← All essays

MEDDPICC Is an Evidence Standard, Not a Checklist

Most teams fail MEDDPICC by ticking boxes with their own optimism. Score every letter 0-3 by evidence quality — and the lowest letter is the deal's real score.

Rudy M. Celekli··7 min
MEDDPICCqualificationdeal-inspectionsales-leadershipforecasting

Sit in on almost any pipeline review at a company that "runs MEDDPICC" and you will hear an exchange like this. The manager asks, "Do we have a champion?" The seller says, "Yes — Marcus loves us." The manager nods, moves to the next letter, and eight yeses later the deal stays in Commit.

Nothing in that exchange was qualification. It was a seller grading their own homework, out loud, with the answer key hidden in their own optimism. The letters got covered. No evidence changed hands. And ninety days later that deal will slip, and the autopsy will show that "Marcus loves us" meant Marcus returned emails — while the Economic Buyer had never heard the vendor's name.

Here is the uncomfortable truth about MEDDPICC adoption: most teams that fail with it are not failing to use the framework. They are using it as the wrong kind of instrument. MEDDPICC is not a checklist of things to have. It is an evidence standard — a definition of how well you have to know each thing before you are allowed to count it.

The checklist failure mode

A checklist asks a binary question: do we have Metrics? A champion? Decision criteria? Binary questions invite binary answers, and sellers — who are optimists by trade and by selection — answer them optimistically. "Do we have decision criteria?" Sure, they care about accuracy and ease of use. "Do we know the paper process?" Standard procurement, probably 30 days.

Every one of those answers might be true. None of them is known. The checklist cannot tell the difference, because the checklist has no concept of source quality. It treats "the CFO told the whole steering committee, and I have the email" and "I assume so, based on vibes" as the same checkmark.

This is why MEDDPICC so often becomes what its critics accuse it of being: administrative theater. Eight CRM fields, dutifully filled, describing the deal the seller hopes exists rather than the deal the evidence supports. The framework did not fail. It was never actually applied — because the framework's whole point is the standard of proof, and the checklist implementation deleted the standard and kept the acronym.

The 0–3 scale: grading how you know, not what you claim

The fix is to stop scoring letters on presence and start scoring them on evidence quality. Every MEDDPICC letter, scored at every stage gate, on one scale:

  • 0 — Unknown. Nobody on the account team can speak to it. Honest zeros are the healthiest number in the system; they tell you exactly where to work.
  • 1 — Assumed. The team has a belief, but it originated inside your building. "They usually buy annually." "Procurement is probably standard." Anything sourced from your own pattern-matching is a 1, no matter how experienced the pattern-matcher.
  • 2 — Confirmed by one source. A customer stakeholder said it, and you have it in writing or in a documented call. One source is real progress — and one source is still a single point of failure who can be wrong, overruled, or reorganized.
  • 3 — Confirmed by multiple stakeholders, with evidence. Two or more people inside the account, independently, with artifacts on file: the email, the org chart the champion annotated, the procurement policy document, the verbatim quote with a date on it.

Notice what the scale is actually measuring. It never asks whether the news is good. A deal can score a 3 on Competition because three stakeholders confirmed you are the trailing vendor — that is a perfectly scored letter carrying terrible news, and it is worth infinitely more than a cheerful 1. The scale measures epistemics, not sentiment: not "is this deal winnable?" but "how do we know what we claim to know?"

That single shift changes the texture of deal reviews. "Do we have a champion?" becomes "What has the champion done, at what internal cost, and when?" A champion who has been asked for nothing is a 1 — an assumption wearing a friendly face. A champion who scheduled the Economic Buyer meeting and rehearsed the business case with you last Tuesday is on their way to a 3, and the deal file can prove it.

The lowest letter is the deal's real score

Now the rule that does the most damage to happy-ears forecasting, and therefore the most good:

The lowest letter is the deal's real score. A deal with seven 3s and one 1 is a 1.

Averages are how weak deals hide. A deal that averages 2.5 sounds like a Commit deal — right up until you notice the average is carried by beautiful Metrics and a tested Champion while Paper Process sits at 1 because "procurement is probably standard." Then the signed legal redlines arrive in week eleven of a twelve-week quarter, the security review nobody mapped takes six weeks, and the deal slips — not because anything went wrong, but because something was never known and the average let everyone stop looking at it.

Deals do not close on their average. They close through their weakest link, because the weakest link is where the surprise lives. The lowest-letter rule forces the conversation to that link, every review, until it is raised. It converts MEDDPICC from a status report into a work-finding instrument: the score is not a grade you receive, it is an assignment you are given.

In practice, the rule also changes seller behavior in a way no exhortation ever does. When the deal's forecast category is capped by its weakest letter, sellers stop polishing the letters that are already strong — the comfortable work — and start attacking the letter they have been avoiding, which is almost always the one that requires an uncomfortable conversation: meeting the Economic Buyer, asking the champion to do something with internal cost, mapping the paper process before it is urgent.

Evidence on file: what, from whom, dated

The scale only holds if the evidence is inspectable. So the scorecard I run — Template 4 in the Field Toolkit — has one column that carries the entire system: Evidence on File (what, from whom, dated).

Three fields, all mandatory:

  • What. The artifact itself. A verbatim quote. An email. A document. A number. Not a characterization ("they're feeling urgency") — the thing you would show a skeptic.
  • From whom. A named human being with a title inside the customer's organization. "The team" is not a source. "Priya Sharma, Head of Model Risk, in the March 12 working session" is a source.
  • Dated. Evidence decays. A conditional commitment from two quarters ago, before the reorg, before the new CFO, is not current evidence — it is archaeology. The date tells you whether you know something or whether you knew it.

The test for every entry is simple: could a colleague who has never touched this account read the evidence column and reach the same score you did? If the score requires your faith to hold up, it is a 1, whatever the field says.

And when a field is empty, resist the instinct to treat it as paperwork left undone. An empty field is a finding, not a formality. The deal has just told you, precisely and for free, where to work this week. That is the scorecard doing its job.

What this looks like on Monday

You do not need a rollout, a workshop, or a CRM project. You need three changes to your very next pipeline review:

  1. Ask for the lowest letter first — with its evidence. Not the deal narrative. "What's your lowest MEDDPICC letter, what's the evidence on file, and what's the dated plan to raise it?" The first few reviews will be quiet. That silence is the sound of assumptions being noticed.
  2. Downgrade every letter that cannot cite a source to a 1, publicly and without blame. The point is not to punish sellers; it is to establish that "I'm confident" and "I have evidence" are different claims with different scores. Do this once, calmly, and the whole team recalibrates.
  3. Cap forecast category by lowest letter. No deal enters Commit with any letter below 2. Write the rule down, apply it to one inflated deal this week, and state the reason in evidence language. One visible enforcement teaches the standard better than any enablement session you will ever run.

The teams that get compounding value from MEDDPICC are not the ones with the best-decorated CRM fields. They are the ones who decided that in their pipeline, a claim without a source is not knowledge — and that the deal's weakest-known fact, not its best story, is what goes in the forecast.

Checklists record optimism. Evidence standards produce it — the earned kind, the kind that closes.


Go deeper. The 0–3 evidence scale and the lowest-letter rule come from The Value Engine: How Elite Enterprise Sales Teams Turn Buyer Pain into Forecastable Revenue by Rudy M. Celekli — see the full qualification system demonstrated end-to-end on one $8.9M enterprise deal. Get the book, and download the free Field Toolkit, which includes the MEDDPICC Opportunity Analysis Sheet with the evidence-on-file column ready to run in your next pipeline review.