MEDDICC or SPICED: Let Your Loss Pattern Choose the Framework

Two teams run the same acronym. One closes bigger deals with it and the other produces beautifully complete CRM records and misses the quarter anyway. The letters are identical. What differs is whether anybody asked the questions out loud while a buyer was listening.

This is a short comparison for sales leaders choosing between the qualification checklist everyone inherited and the discovery framework built to replace it. The argument: your loss pattern already tells you which one you need, and the choice matters far less than the discipline underneath it.

Eight Letters, and Where They Came From

The framework was built at Parametric Technology Corporation in the 1990s by Dick Dunkel and Jack Napoli, as Sean Linehan sets out in Exec's guide, updated in February 2026. It has grown letters since. The organisation that now owns the name is unambiguous about which version it backs: "At MEDDICC, we use and recommend the most complete version: MEDDPICC", covering Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Implicate the Pain, Champion and Competition.

Three of those letters carry most of the weight, and HubSpot's guide to the method defines them usefully. Metrics is the economic value the buyer can put a figure against. Economic Buyer is whoever holds final authority to release the money, as distinct from whoever likes you. Paper Process is everything legal, security and procurement will require before a signature is possible. Read those three together and the shape of the method is obvious: it is a checklist testing whether this purchase can physically occur.

The authors of the alternative treat that as precisely the limitation. Their critique traces the method back to one-off software licensing and says it concentrates "heavily on the decision stage" rather than on what the customer is trying to achieve. The firm sells training in its own approach, so weigh the argument accordingly. It still lands for subscription businesses, where whether a deal was worth winning is settled months after the signature.

The Failure Mode Is Always the Same

Before choosing, understand how both get wasted, because it is identical. Linehan names the symptom precisely: "Reps fill in CRM fields after calls to satisfy their manager but don't actually use the framework during conversations." The diagnostic he gives is one any manager can run this week. If every deal has complete fields and your forecast accuracy has not moved, the framework is decoration.

He names two more that cost real money. Teams build a strategy around a champion and discover late that the person cannot approve anything, because "A champion sells for you internally. An economic buyer signs the check." And teams treat procurement as tidying-up rather than qualification, which is why "The paper process is a qualification step, not an afterthought." Weeks disappear into a security review nobody asked about in month one.

Start From Your Losses, Not From the Acronym

Pull your last fifteen deals that died or stalled and label each with the thing that actually stopped it. Wrong person in the room. No problem urgent enough to fund. No date that forced a decision. A procurement path nobody mapped. A competitor, including the competitor called doing nothing. The tallest column is your answer, and getting honest labels is its own exercise, which our guide to asking the buyer rather than the rep sets out.

• Wrong person, or a contract that stalled in legal. Take the checklist. Three of its letters, the one about authority and the two about process, exist for exactly this failure.
• Nothing urgent, no deadline. Take the discovery framework, whose middle letters make a buyer put the problem, its cost and a date into their own words.
• Beaten by an alternative. Take the checklist again, and use the Competition field properly, which per HubSpot's guide includes the status quo as a competitor.

Both Frameworks, Written as Things You Can Say

Letters do not qualify anything. Questions do. Here is the whole of both methods as sentences a rep could use on a call tomorrow.

• Talk me through the way this runs today, start to finish.
• Where does it break, and whose week does that ruin?
• If nothing changes for two quarters, what does that cost in money or headcount?
• After what date does fixing this become harder, or more expensive, or somebody else's problem?
• Who else has to agree, and what will each of them be looking at?
• Who releases money at this size, and have they funded anything similar?
• Once we agree commercially, what do legal, security and procurement need, and how long did that take last time?

Seven sentences, and the two frameworks overlap across most of them. Ask six of them on every opportunity and you will beat somebody who can recite all eight letters while asking nothing. The method's own documentation stresses that a decision is made by a group and has to be mapped deliberately, which is the same conclusion we reached from the buyer's side in why one champion cannot carry a committee.

Trim to Five Fields and Mean It

Whichever you adopt, put five fields in the CRM rather than eight. Every extra box lowers the probability that the rest are answered honestly, because a rep facing a wall of required fields optimises for completion rather than truth. Tell reps explicitly that a blank is an acceptable answer and a guess is not. A blank is information: it says nobody has asked yet.

Then enforce one gate instead of many. Requiring a named money-holder before any proposal leaves the building is the rule with the best return, and the framework will only ever tell you that the name is absent. Somebody still has to go and find the person, which is the work described in mapping the buying committee before you need it.

A Completed Field Is Not Evidence

Here is the position, and it cuts against how most organisations roll these out. The useful question is never which framework a team uses. It is whether a manager can look at any deal and see the evidence behind each answer rather than the answer itself. A metrics field holding a round efficiency figure and nothing else is worth nothing. The same field reading "their operations lead produced that number on 4 March and finance has now seen it" is a qualification. The first is a rep's opinion wearing a framework's uniform, and the uniform is what stops anybody questioning it.

This is why we would resist the standard rollout, which is training followed by required fields followed by a dashboard showing completion. That sequence produces exactly the outcome Linehan describes, and it produces it reliably, because the thing being measured is typing. The alternative costs more management attention and no software: review the blanks rather than the entries, and ask for the source of any answer that is not blank. Linehan's own suggestion is a rubric that defines what each letter looks like for your specific motion, which "becomes the scoring criteria for deal reviews, coaching conversations, and practice scenarios". That works because it moves the standard from whether a box is full to what counts as proof, and our piece on the proof each letter needs works through what that looks like letter by letter.

Teams with a short, transactional cycle and one decision maker should run something lighter. There the overhead genuinely exceeds the return, the lighter version without the procurement step is the right call, and asking for documented proof of a champion's influence is theatre. Exec's guide makes the same distinction, noting the full framework was built for complex multi-stakeholder deals and feels heavy on shorter ones. Our breakdown of why mid-market is its own motion covers where that boundary tends to sit.

The Pushback

"We need one framework across the company." You need shared vocabulary in the deal review. Discovery can run on something else entirely, and plenty of teams qualify with one method and discover with the other.

"Frameworks make people sound robotic." Reading letters aloud sounds robotic. Preparing seven questions does not. The framework belongs in the preparation, never in the call.

"This is too heavy for deals our size." Then run three fields. A problem, its cost and a date make a complete qualification on a short cycle.

What to Change on Monday

Put a single new box on every open opportunity: what goes wrong for the buyer if nobody decides by a stated date. That line is a critical event in plain language, and it will be the emptiest column you own. Then run a ten-minute review in which reps read out nothing except their blanks, and spend the whole slot there. Any box more than half the team has ignored for a month should be deleted and turned back into something a rep says out loud. Neither framework improves a forecast on its own, both are promoted by people who sell training in them, and the evidence behind the answers is the only part that was ever doing the work.