# Your Qualification Framework Is Not a Sales Process. Treating It as One Is Why Reps Game It.

> MEDDIC, BANT, SPICED: frameworks that describe deal health, not how to sell. The confusion produces compliant CRMs and lost deals.

By Greg McCallum, founder of PeerLab. Published 2026-11-19 in Methodology. Source: https://www.peerlab.ai/blog/qualification-framework-is-not-your-process/

Six months after a MEDDIC rollout, the CRM looks great. Fields are populated, scores are tidy, managers can point at green dashboards in the QBR. And yet forecast accuracy has not moved. Deals that looked qualified are dying in legal. Champions who were marked as "identified" were never actually tested. The team learned to fill in the framework, not to sell better. This is not a training failure. It is a category error that was baked in from the start.

## A Qualification Framework Tells You What You Know. Nothing Else.

MEDDIC, BANT, SPICED, CHAMP: every one of these is a diagnostic instrument. Each asks a version of the same question: given everything currently visible about this deal, do you have enough of the right information to believe it is real?

That is a genuinely useful question. It is not a process.

A qualification framework cannot tell a rep what to do on Tuesday. It cannot specify what a good discovery call looks like, what sequence of conversations produces a champion, how to build a business case, or when to introduce pricing. It is a snapshot, not a map. It tells you where you are, not how to get somewhere.

When organisations bolt MEDDIC fields onto CRM stage gates and call that a sales process, they have confused the instrument with the method. The instrument measures. The method moves.

## What a Sales Process Is Actually Supposed to Specify

A proper sales process defines the sequence of activities, conversations, and exits that move a deal from initial contact to close. It has verifiable exit criteria at each stage, not "MEDDIC fields populated" but "economic buyer met face-to-face and confirmed budget cycle". It answers operational questions:

- What must a rep do before moving a deal to stage three?
- What does a good qualification call produce, in terms of commitments and artefacts?
- Who owns multi-threading, and by which stage?
- What triggers an internal deal review?

A qualification framework answers none of those questions. It audits the output of a process. If your process is good, your MEDDIC fields fill themselves from genuine discovery. If your process is weak, the fields get filled retrospectively from whatever the rep already knows or can plausibly infer.

The two tools solve different problems. Using one to substitute for the other does not give you half a solution. It gives you a theatre production.

## The Two Behaviours This Confusion Produces

**Reverse-engineered fields.** A rep who has been in a deal for three weeks knows a lot. They know roughly who the decision-maker is, they have heard a pain statement or two, they have a sense of budget. When asked to populate MEDDIC before a deal review, they write backwards from what they already know. The fields are accurate as a record of conversations that happened; they are useless as a guide to what should happen next. The CRM now reflects the past, not the future. No one has been asked to do anything they were not already going to do.

**Compliance mistaken for control.** A manager who sees populated MEDDIC fields has visibility into what their rep knows. That is not the same as knowing whether the deal is progressing. "Economic buyer: Sarah Chen, VP of Operations" tells you a name exists in the field. It does not tell you whether Sarah has been met, whether she has articulated a compelling reason to change before the end of the quarter, or whether the rep is hiding behind the champion because cold-calling the VP is uncomfortable. Compliance produces reports. Control requires conversations that the process should be prompting.

The combined result: a pipeline that scores well by the framework's own metrics and still misses number.

## Where Methodology Rollouts Silently Fail

Most rollouts follow a recognisable arc. The framework is introduced in a two-day enablement session. It is mapped to CRM stages. Managers are told to inspect deals using the framework's vocabulary. Reps learn to speak the language of MEDDIC in deal reviews.

The gap is never discussed: the fact that knowing the MEDDIC elements does not tell a rep how to find, build, or test them. That is methodology's job, and most orgs have not separated the two clearly enough to notice it is missing.

Consider what "identify the champion" actually requires a rep to do. They need to know how to run a discovery conversation that reveals internal politics, how to test whether someone has influence rather than just enthusiasm, how to build a relationship that survives a champion going cold. None of that is in MEDDIC. MEDDIC is the destination; the rep needs a vehicle. [Sales Methodology Comparison Guide](https://www.peerlab.ai/library/sales-methodology-comparison-guide/) is a reasonable starting point for thinking through which vehicle fits your motion.

If you want to know whether you have a methodology gap or a framework gap, it helps to be clear on which layer is broken before you try to fix it. A Sales Methodology and a Skills Framework Are Not the Same Thing draws that distinction more precisely than this post can in the space available.

## A Practical Separation

The cleanest way to untangle this is to treat qualification and process as two separate governance conversations.

| Question | Owned by | Tool |
|---|---|---|
| Do we know enough about this deal to forecast it? | Framework | MEDDIC / BANT / SPICED fields |
| Is the rep taking the right actions at each stage? | Process | Stage-exit criteria, activity requirements |
| Where is this specific deal likely to break? | Diagnosis | Deal review conversation, risk scoring |
| Are our reps competent to execute the process? | Skills | Competency assessment, coaching |

A deal review that only uses MEDDIC to audit information completeness is running column one. It is ignoring three other columns that actually explain why deals are won or lost.

If your forecast accuracy has not improved after a framework rollout, the question is almost never "which fields are missing?" It is "do our reps know what to do in order to populate those fields legitimately, and does our process require them to do it?" [MEDDIC Deal Qualification Checklist](https://www.peerlab.ai/library/meddic-deal-qualification-checklist/) can help you audit what you actually have in a deal, but it will not replace a process that generates those answers in the first place.

## The Fix Is Not a Better Framework

There is a whole industry prepared to sell you MEDDPICC as the solution to your MEDDIC problems, then MEDDPICC-R after that. Each iteration adds a letter and an enablement cycle and produces the same result: more fields, same behaviours.

The fix is to hold two distinct tools in your hand and use each for what it was built for. Run MEDDIC, or whichever variant fits your deals, as the diagnostic it is. Use it in deal reviews to surface information gaps. Then ask what process behaviour would have produced that information by now, and whether your process actually requires it.

[Sales Process Maturity Self-Assessment](https://www.peerlab.ai/library/sales-process-maturity-self-assessment/) will tell you honestly whether you have a process or just a stage map with framework fields attached. For many organisations the answer is uncomfortable. That discomfort is the starting point.

The goal is reps who close deals, not reps who close CRM fields. The difference is in what you treat as the work.

**The tool for this:** [Qualification vs. Process Separation Worksheet: Two-Tool Audit](https://www.peerlab.ai/library/qualification-vs-process-separation-worksheet-two-tool-audit/), free and no signup.
