Qualification

Sales Qualification Frameworks Compared: BANT, MEDDIC and More

• No invented stats
• Written for UK readers
• 5 min read
• Published 19 September 2026

Every qualification framework is a memory aid. That's all. None of them close deals, none of them contain secret knowledge, and the differences between them matter far less than whether your team uses one consistently. The reason to pick one is so that two reps describing the same deal use the same words.

Here's what the main frameworks actually cover, where each one is strongest, and the failure mode each one tends to produce.

The frameworks at a glance

BANT: the default, and its problems

BANT came out of an era when a single senior buyer with a budget line could authorise a purchase. In that world it's excellent: four things to confirm, easy to remember, easy to teach a new starter in an afternoon.

Two things have changed. First, buying committees got bigger, so "Authority" is rarely a single person. Second, for a lot of modern purchases there is no pre-existing budget — the money gets found if the case is good enough. A rigid reading of BANT disqualifies perfectly good deals because nobody has allocated a budget line for a problem they haven't named yet. That's a real cost, and it's a big reason experienced reps drift away from BANT.

Used sensibly, "Budget" means "is there a plausible route to money at roughly this size?" rather than "is there an approved figure?" If you want the longer version of that argument, see how to handle "we don't have budget right now".

MEDDIC: powerful, and frequently misapplied

MEDDIC is the most thorough of the common frameworks and was designed for complex enterprise sales with long cycles and many stakeholders. Its real contribution is forcing two questions most reps avoid: who is the economic buyer, and who inside the account will argue for you when you're not in the room?

The problem is that MEDDIC is often adopted by teams whose deals don't warrant it. If your average deal is £4,000 and closes in three weeks, documenting six fields plus decision criteria per opportunity costs more than it returns. We've written a fuller treatment in MEDDIC explained for small sales teams, including how to run a stripped-down version that keeps the useful parts.

CHAMP, GPCTBA and SPICED

CHAMP reorders BANT to start with challenges rather than budget. That ordering is genuinely better as a conversation guide, because nobody enjoys being asked about money in the first ten minutes. As a data model it's near-identical to BANT, so switching from one to the other is mostly a re-badging exercise.

GPCTBA/C&I is thorough and consultative, and the "Consequences and Implications" part is the best bit — it asks what happens if the goal is missed and what happens if it's hit. That's the part most frameworks skip, and it's where urgency actually comes from. The downside is obvious from the acronym: it's too unwieldy to use live. Treat it as a deal review structure rather than a call script.

SPICED suits recurring-revenue businesses because it makes "critical event" explicit — a date-anchored reason the buyer must act. Genuinely useful when a real event exists, such as a contract expiry, a regulatory deadline or a system being switched off. It becomes fiction when reps invent one to satisfy the field, which is a common and quietly destructive habit.

When a framework becomes theatre

You can tell a framework has stopped working when the fields are filled in for the manager rather than for the deal. Symptoms:

• Every opportunity has a champion named, and none of them have ever sent an unprompted email
• "Critical event" is the same quarter-end date across half the pipeline
• Reps complete the fields the night before the pipeline review, from memory
• Deals that score well on the framework lose at the same rate as deals that score badly

That last one is the test that matters. If your qualification scoring doesn't correlate with your win rate after a couple of quarters of data, the scoring is decorative. Either the criteria are wrong for your market or the data is being entered dishonestly, and both are worth finding out.

How to choose

A reasonable rule of thumb, based on deal shape rather than fashion:

• One buyer, under a month, low four figures — BANT or CHAMP, three or four questions, no separate CRM fields
• Two to four stakeholders, one to three months — CHAMP or a reduced MEDDIC: economic buyer, pain, decision process
• Five-plus stakeholders, procurement involved, six months or more — full MEDDIC, and expect to spend time on dealing with procurement as a separate workstream
• Renewals and expansions — SPICED, because the critical event is usually genuine

Whichever you pick, write down what each criterion means in your business, in one sentence, with an example of a passing and a failing answer. A framework without local definitions just moves the inconsistency from the pipeline stage to the qualification field.

The part no framework covers

None of these tell you whether the buyer will actually get it over the line internally against competing priorities. That's a judgement call, and it comes from listening to how the prospect talks about the project relative to everything else on their plate. A deal that scores perfectly on MEDDIC and sits fourth on the buyer's priority list will slip, and slip again.

The practical counterweight is to treat qualification as continuous rather than a gate you pass once at stage two. Re-ask the questions at the proposal stage; answers change. Reps who do this catch stalling deals early — see how to spot a deal that's never going to close for the specific signals.

A minimum viable version

If you're a small team with no framework at all, don't start with MEDDIC. Start with four written questions you must be able to answer before a deal enters your forecast:

1. What specifically goes wrong for them today, described with an example?
2. What happens to them if nothing changes this year?
3. Who signs, and what's the route to that person?
4. What has to be true for this to be decided by a specific date they named?

That's enough for most businesses under about twenty staff. Add structure when the deals get complicated enough to need it, not before.

Spotted a mistake or a number we can't back up? Tell us and we'll fix it.