Why qualification frameworks exist

A Sales Academy premium module, sold separately from the core curriculum. Module 3 taught the eight letters and what each one stands for; this module assumes you already have that and goes several layers below it — evidence standards, honest scoring, champion engineering, multi-threading a real buying group, and surviving the deal review where a VP takes your qualification apart. Read module 3 first. Nothing here repeats it.

What you'll learn

• Where MEDDIC actually came from — PTC, 1996, and the three names attached to it — how it became MEDDICC and then MEDDPICC, what problem it solves for a rep versus for a VP, and the honest critique of frameworks as CRM box-ticking.
• Each of the eight letters at practitioner depth — what it really means, the questions that uncover it, what evidence looks like versus what reps kid themselves with, the specific way deals die when it's missing, and a life-sciences or health-tech worked example for every letter.
• A full RAG scoring method — defined evidence standards for red, amber and green; the forcing rules that drop a deal to red regardless of the other letters; stage-appropriate expectations; and three worked scorecards on realistic deals of very different health.
• Champion development as a craft — the three tests, how to build a champion who can't yet buy, what to put in their hands, how to run champion succession when yours leaves, and the difference between a champion, a coach and a cheerleader.
• Multi-threading in practice — mapping a buying group of six to sixteen people, the order you meet them in, exact wording for the executive-access ask, and five moves when you're single-threaded and stuck.
• Running MEDDPICC in a deal review — how a VP grills a rep, the questions that expose weak qualification, how to answer "how do you know?" for every letter, and how to disqualify out loud without looking weak.
• The common misuses — MEDDPICC as a stage gate rather than a diagnostic, the letter that is most often faked, the "we have a champion" delusion, and when the whole framework is overkill.

1. Why qualification frameworks exist

Complex deals fail for a small number of repeatable reasons

Enterprise deals do not fail creatively. The same handful of causes recur: nobody could put a number on the problem, the person with the money was never met, the requirements were written around a competitor, the customer's own process took longer than anyone mapped, the paperwork ambushed everyone after the decision, or the internal advocate turned out to have no power.

That repetition is the whole basis of qualification frameworks. Because deals die the same ways, a checklist of the things that must be true is genuinely predictive — a memory device for other people's failures.

The origin: PTC, 1996

MEDDIC was created inside PTC (Parametric Technology Corporation) in 1996, credited to Dick Dunkel, working with Jack Napoli, under the sales leadership of John McMahon — the same John McMahon who later wrote The Qualified Sales Leader.

PTC sold Pro/ENGINEER — computer-aided design software — into large manufacturers with sizeable buying committees, growing from nothing to a billion dollars of revenue in a decade. As it scaled, attrition became severe and it could not hire experienced sellers fast enough to replace those leaving.

MEDDIC was the answer to a scaling problem, not an intellectual one. Dunkel and Napoli reverse-engineered it from PTC's own won and lost deals: look back at what closed and what didn't, ask what was missing each time, turn the recurring gaps into a list. It is a list of scars, not a theory of persuasion — and it was born in a company selling a technical product to committees, which is why it transfers so well to laboratory informatics, clinical software and medical devices, and so badly to a transactional inside-sales motion.

How MEDDIC became MEDDICC and MEDDPICC

Each added letter is another scar. Teams kept losing deals to competitors they had never asked about, so a second C for Competition was appended, giving MEDDICC. Teams kept watching verbally-won deals sit unsigned for a quarter while legal, security and procurement ground through their machinery, so a P for Paper process was inserted, giving MEDDPICC.

This course standardises on MEDDPICC, using module 3's definitions: MEDDIC is the original six; MEDDICC is those six plus Competition; MEDDPICC is those six plus Paper process and Competition. If an advert or interviewer says MEDDIC or MEDDICC they almost always mean the full modern discipline — say "we ran MEDDPICC; some shops call it MEDDICC" rather than correcting them. Variants proliferate and mean little: treat MEDDPPICC and the rest as trivia.

What it does for a rep, and for a VP

For a rep, it converts optimism into a to-do list. Someone who "feels good" about a deal has nothing to work on; someone whose Economic buyer is amber and Paper process is red has two schedulable actions this week. It also protects both your time and your credibility — every hour on a deal with no quantified pain and no route to power is stolen from one that could close, and a rep who says "this is amber on the economic buyer, so I'm not committing it" and is right buys enormous latitude for the deals they do commit.

For a VP, it is one inspection language across a whole team. Without it a pipeline review is thirty different narratives; with it, the same eight questions can be asked of any deal in any territory and the answers compared. It also makes coaching diagnosable — a rep consistently red on Decision process has a different skill gap from one consistently red on Metrics — and it underwrites the forecast, because a leader who must tell a board what will close needs an evidence standard, not a mood.

Voice from the field

"This misunderstanding represents why many qualification methodologies, including BANT and MEDDICC, get a bad name because junior salespeople feel they need to check off answers to every element during every engagement with a customer."
— Andy Whyte, MEDDICC (2020)

The honest critique

The most common failure is that MEDDPICC becomes eight CRM fields, filled the night before a forecast call in the vocabulary the manager rewards, until "fully qualified" means "all boxes populated" rather than "I understand why this customer will buy". A dropdown reading "Budget: approved" looks rigorous and says nothing about how money moves.

The second failure is turning it into an interrogation. Reps who have just learned the letters march through them in discovery like a form, which customers experience as being processed. The letters are a checklist for you, not a script for them. The third is treating it as a stage gate — section 7 covers this, but in short, forcing every letter to green before a deal can advance produces reps who manufacture evidence rather than gather it.

None of this argues against the framework. It argues for using it as a diagnostic — questions you ask the customer and yourself — rather than as paperwork you produce for a manager. Interviewers who came up in genuine MEDDPICC organisations can tell within a minute which version you learned.

Field note

Ask, in an interview, who reads the MEDDPICC fields. In a real MEDDPICC shop the answer is immediate and specific: the manager reads them before every one-to-one, deal reviews start from the weakest letter, and there is a named forcing rule about what cannot be committed. Where it's theatre, the answer is vague — "it's in Salesforce", "we review it quarterly". That one question tells you more about how you will be coached than anything on the careers page.

2. Each letter in depth

Each letter below follows the same structure: what it really means, the questions that uncover it, what good evidence looks like against what reps kid themselves with, the failure mode when it's missing, and a worked life-sciences or health-tech example. All companies and people named in examples are fictional.

M — Metrics

What it really means. Not "the value we deliver", but the customer's own quantified statement of the outcome they expect, in units their finance function recognises, tied to a baseline they measured. The distinction between your number and their number is the entire letter.

The questions that uncover it. What is that costing you today, and how do you know? Whose numbers would your board believe, and who owns that data? What happens to the case if we're half as good as we claim?

Evidence versus self-deception. Green is a number the customer produced or validated, written down somewhere you didn't write — a slide in their business case, an email from their finance analyst — with a stated method and a named owner. Reps kid themselves with vendor ROI calculators and percentages with no baseline: arithmetic dressed as evidence.

The failure mode. Without customer-owned metrics your business case is a marketing document. It dies the first time it reaches someone whose job is scepticism about spending.

Worked example — Northbrook Therapeutics. A clinical-stage biotech scaling into GMP manufacturing evaluates a laboratory information management system. The rep's deck says "40% faster batch release". The metric that carries the deal is different: their QA lead calculates batch record review at 11 days against a 5-day target, each delayed batch costing roughly £18,000 in held inventory and idle suite time, across 60 batches next year — a model in their spreadsheet that the CFO has seen.

E — Economic buyer

What it really means. The individual who can release the funds without anyone else's permission and who bears the consequences. Not the most senior person you've met, and not the org-chart budget-holder if that budget is subject to a committee: the person whose "yes" is dispositive.

The questions that uncover it. Who signs at this value? Has that person funded something similar before, and what happened? When did you last take a proposal like this to them, and what did they push back on?

Evidence versus self-deception. Green is a meeting you were in, after which something changed — they set a condition, asked for something, named a date — plus independent confirmation that this is who signs at this value. Reps kid themselves with a name in a CRM field, a twenty-minute courtesy meeting six months ago, or a champion's assurance that "she'll approve whatever I recommend": possibly true, and not evidence.

The failure mode. Deals with no economic-buyer access rarely lose; they stall. Nobody says no — the project fails to survive the next round of priority-setting, because no one senior owned it. This is how a "sure thing" evaporates in the last month of a quarter.

Worked example — Calder Vale NHS Foundation Trust. A digital pathology deal at £240,000 over three years. The consultant pathologist driving it insists the Chief Clinical Information Officer "is fully behind us". Testing reveals the CCIO cannot approve above £100,000; the real economic buyer is the CFO, who has never heard of the project. The rep's view of the timing was wrong by two quarters.

D — Decision criteria

What it really means. The standards against which options are actually judged — three lists, not one. Technical criteria (integrations, standards, security, regulatory status), business criteria (payback, total cost, risk, references), and the personal criteria nobody writes down (whose career this protects, who gets credit, who does not want to run another migration).

The questions that uncover it. How will you compare the options? Who wrote that list, and what happened to draft one? If two vendors both clear the technical bar, what decides it?

Evidence versus self-deception. Green is the criteria in the customer's own document, weighted, with a named owner each — better still, one criterion that maps to something only you do well, put there because you taught them why it mattered. Reps kid themselves with a verbal list of generic things ("integration, security, price, support"), a tender specification taken at face value without asking who briefed it, and the assumption that the loudest technical requirement decides it.

The failure mode. If someone else wrote the criteria you are competing on their terms, and will lose on a technicality inserted deliberately. The tell is a requirement so specific it can only describe one product.

Worked example — Calder Vale, continued. The trust's matrix requires "native integration with the existing laboratory information system" and "UK-based deployment references in NHS pathology". The first is a genuine technical need; the second was suggested by the incumbent's account manager, who has four such references and knows the rep has one. Spotting that early converts a lost deal into an argument about the better proxy for safety.

D — Decision process

What it really means. The customer's own machinery for reaching a decision: the steps, who owns each, the dates those bodies meet, the criteria for passing each gate. A project plan that belongs to them, which you should be able to recite.

The questions that uncover it. Walk me through how the last system like this was approved here. Who has to be consulted before it reaches the committee, and what are the committee dates for the year? Who could stop this, even if they can't start it?

Evidence versus self-deception. Green is a written sequence with dates and named owners agreed with the customer — a mutual action plan — plus confirmed meeting dates and knowledge of a previous decision that followed the same path. Reps kid themselves with "they said end of Q3", a timeline built backwards from their own quarter-end, and a process described by someone who has never taken anything through it.

The failure mode. Unmapped decision process is the largest single source of forecast slip. The deal doesn't get worse — it keeps moving right, one committee cycle at a time.

Worked example — Calder Vale, continued. The real path: departmental business case → Digital Programme Board (monthly, papers due ten days prior) → clinical safety assessment under DCB0160, the standard the deploying organisation must satisfy → IG review and DPIA → Capital Investment Group (quarterly) → Trust Board. Miss a papers deadline by a day and the deal moves a month; miss the capital group and it moves a quarter.

P — Paper process

What it really means. Everything between "we've chosen you" and money moving: contract negotiation, the data-processing agreement, information-security assurance, clinical or regulatory documentation, insurance checks, supplier onboarding, purchase-order raising. A separate discipline from the decision process, and where verbally-won deals go to sit.

The questions that uncover it. Once you've selected a supplier, what happens next? Who owns the contract, and how long is their queue? How does a purchase order actually get raised, and who raises it?

Evidence versus self-deception. Green is named contacts in legal, procurement and information security, your paperwork already in their systems — supplier registration complete, security questionnaire returned, DPA agreed in principle — and a realistic elapsed-time estimate from someone who has done it. Reps kid themselves with "procurement is a formality here", with assuming a framework agreement removes all friction (it removes tendering, not contracting), and with the champion's estimate of legal turnaround.

The failure mode. The distinctive one: you win and still miss. The decision is made, everyone is pleased, and the deal lands a quarter late because information governance had a six-week queue.

Worked example — Kestrel Pharma. A global pharmaceutical company selects a specialist analytics platform in March. Then: a master services agreement negotiated by a legal team in another country, a supplier risk assessment, a GxP validation package, a penetration-test report, cyber-insurance evidence above the vendor's cover, and onboarding that cannot begin until the vendor is approved globally. Nine weeks minimum, thirteen realistically. The rep who forecast March signed nothing until June.

I — Identify pain

What it really means. The specific, consequential problem that makes doing nothing worse than doing something. Pain has three levels, and the level determines the deal: found pain creates an opportunity, quantified pain supports a price, implicated pain — where the customer has articulated what happens if it continues — creates urgency.

The questions that uncover it. What made you start looking at this now, and what have you already tried? What does this cost you in a month where nothing goes wrong, and in a month where something does? What happens if nothing changes for another year?

Evidence versus self-deception. Green is pain the customer states in their own words with consequences attached, documented officially — a risk register entry, audit finding, board paper, regulatory observation — and described independently by more than one person. Reps kid themselves with pain they suggested and the customer politely agreed with, generic problems ("data silos", "inefficiency"), and pain owned by users but by nobody with budget: real, felt daily, unfundable.

The failure mode. Without implicated pain the deal loses to the status quo, which is free, installed and blameless. It rarely loses loudly; it loses to "let's revisit in the next planning round".

Worked example — Northbrook Therapeutics, continued. Found: "batch record review is slow." Quantified: "11 days against a 5-day target, roughly £18,000 per delayed batch." Implicated, which is what moved the money: their contract manufacturing customer has written to say continued delays put next year's supply agreement at risk, and the auditor flagged manual transcription as a data-integrity observation. Inaction now has a named cost and consequence.

C — Champion

What it really means. A person with power and influence inside the account who sells on your behalf when you are not in the room, because your success serves their interests. Every element is load-bearing: power, action, self-interest. Section 4 covers development; this is the qualification standard.

The questions that uncover it. What does a win here do for you personally? Who else needs convincing, and what will they object to? What's the most likely reason this doesn't happen?

Evidence versus self-deception. Green is things they have done: secured a meeting with someone more senior, sent your material internally under their own name, told you bad news before you found it. Actions with a cost to them are the only real evidence. Reps kid themselves with enthusiasm — someone who says "I love this" and has never done a thing that would embarrass them if the project failed — and with champions powerful in the wrong domain: beloved by clinicians, irrelevant to capital allocation.

The failure mode. With no champion, nothing happens between your meetings. Someone must carry the case through internal conversations you will never attend; if nobody does, momentum decays to zero regardless of product fit.

Worked example — Calder Vale, continued. The consultant pathologist is enthusiastic and cites your data, but has no budget influence and no history of pushing anything through the Digital Programme Board. A valuable ally, not a champion. The real candidate is the pathology service manager, who owns turnaround times, has taken two business cases through the board, and has a personal stake in the department's reputation.

C — Competition

What it really means. Everything that could win the money instead of you: named rival vendors, an internal build, an incumbent extending scope, doing nothing — and the one reps most often miss, another project competing for the same budget. A hospital choosing between a pathology system and a new endoscopy suite is a competitive deal with no rival vendor in it.

The questions that uncover it. Who else are you looking at, and what do you like about them? What would make you stay as you are? If this doesn't get funded, what does instead?

Evidence versus self-deception. Green is named competitors with a specific read on their position — who introduced them, which criteria they are strong on — plus knowledge of the budget competition and a differentiation position mapped onto the criteria. Reps kid themselves with "they said we're the front-runner", with assuming there is no competition because nobody named one (silence usually means an incumbent), and with believing technical superiority settles it. It settles a technical evaluation, which is one input.

The failure mode. You become column fodder — the third quote that makes someone else's preferred choice procurable. The tells: arriving late, rationed access, criteria that read like a competitor's datasheet.

Worked example — Kestrel Pharma, continued. Two named vendors, the informatics team's proposal to extend an existing platform in-house, and — decisively — a competing bid from clinical operations for the same capital envelope. The rep who mapped only the vendors was fighting the wrong battle: the deal turned on whose business case the CIO chose to sponsor.