BANT. MEDDIC. MEDDPICC. SCOTSMAN. ANUM. The sales profession has no shortage of qualification acronyms. It has a severe shortage of qualification that works.
The problem isn't that these frameworks ask bad questions. Some of the questions are excellent. The problem is structural: every one of these frameworks measures what the rep has asked, not what the buyer has done. And what the rep has asked is not a reliable predictor of whether a deal will close.
A rep can confirm Budget, Authority, Need, and Timeline in a single discovery call and still lose the deal. Why? Because confirming information is not the same as confirming buying behaviour. The buyer said they had budget. They didn't say they'd allocated it. The buyer said the VP was the decision maker. They didn't say the VP had agreed to evaluate. The buyer confirmed a need. They didn't confirm they'd prioritised solving it.
Qualification frameworks fail when they confuse conversation with commitment.
Why BANT Doesn't Predict Deal Closure
BANT was designed by IBM in the 1960s for a world where the salesperson controlled the information flow. The buyer needed the rep to learn about the product, and the rep used that leverage to extract qualification data. That world is gone.
Today's buyer has done 70% of their research before talking to a rep. They know the budget range. They know who the decision maker is. They've already assessed need. BANT confirms things the buyer already knows — it doesn't tell you whether the buyer is actually buying.
Budget confirmed means someone told you a number exists. It doesn't mean money has been allocated, approved, or ring-fenced for your solution. "We have budget" is a conversational response. "We've allocated £200K in the Q3 IT budget, and procurement needs a signed SOW by August 15" is a buying signal.
Authority identified means you know who the decision maker is. It doesn't mean the decision maker is engaged, aware of your deal, or supportive. In complex B2B, authority is distributed — and the person with budget authority may not be the person with political authority to push the purchase through.
Need confirmed means the buyer acknowledged a problem. Every buyer has problems. Not every buyer is solving them. The question isn't whether the need exists but whether it's prioritised above the fifty other things competing for the buyer's attention and budget.
Timeline stated means the buyer gave you a date. Buyers give dates to be polite, to end conversations, and to get reps to stop asking. A timeline is meaningful only when it's anchored to a business event the buyer can't move: a contract expiration, a board mandate, a regulatory deadline.
MEDDIC: Better Questions, Same Structural Problem
MEDDIC improves on BANT by adding Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion. These are genuinely better questions. But the framework still measures whether the rep has gathered information, not whether the buyer has taken action.
A rep can fill in every MEDDIC field in the CRM and have a deal that dies silently. The champion goes quiet. The economic buyer never takes the meeting. The decision process turns out to be longer and more political than anyone admitted. The metrics that justified the purchase get deprioritised when something more urgent appears.
Information gathered is not the same as qualification confirmed. The distinction matters because it determines how you manage your pipeline. If you treat information-gathering as qualification, you'll have a pipeline full of deals that look qualified on paper and stall in practice.
What Actually Predicts Deal Closure
Buyer actions predict deal closure. Not buyer words — buyer actions. Here are the signals that actually matter:
Access Granted
The buyer introduces you to additional stakeholders, the technical team, the procurement team, or the economic buyer. This is an action that costs the buyer political capital. They wouldn't do it unless they were serious. When a champion says "let me set up a meeting with the CFO" and actually does it, that's qualification. When they say it and don't, that's politeness.
Information Shared
The buyer shares internal documents, technical requirements, budget details, competitive information, or organisational context that they wouldn't share with a vendor they weren't seriously considering. The depth of information shared correlates with buying intent. Surface-level responses suggest surface-level interest.
Internal Process Started
The buyer initiates their own internal processes: security review, legal review, procurement paperwork, budget approval, reference checks. These processes are bureaucratic and time-consuming. Nobody starts them for fun. If the buyer has started their internal machinery, they are buying — not browsing.
Time Invested
The buyer's senior people spend time on your deal. Multiple meetings, workshops, technical deep-dives, executive briefings. Senior buyer time is scarce and expensive. Its investment is a signal of priority that no qualification questionnaire can replicate.
How to Build Qualification Criteria That Work
Replace your qualification acronym with a buyer-action checklist. For each stage of your pipeline, define the buyer actions — not rep actions — that justify advancement.
Stage 1 (Discovery): Buyer has described their problem in their own words and agreed to a second meeting. Buyer action: agreed to invest more time.
Stage 2 (Qualification): Buyer has introduced you to at least one additional stakeholder. Economic buyer is aware and has not blocked the evaluation. Buyer action: granted access.
Stage 3 (Evaluation): Buyer has shared decision criteria and process. Technical or security evaluation underway. Buyer action: shared internal information and started internal processes.
Stage 4 (Proposal): Buyer has reviewed commercial terms and provided feedback. Legal or procurement process initiated. Buyer action: engaged on terms and started buying process.
Stage 5 (Commit): Buyer has verbally committed, confirmed timeline, and all internal approvals are in progress or complete. Buyer action: confirmed the decision.
This approach doesn't replace the useful questions in BANT or MEDDIC. It adds the layer they're missing: evidence that the buyer is acting like a buyer, not just talking like one.
The Qualification Audit
Take your current pipeline and apply buyer-action criteria to every deal. For each deal, ask: what has the buyer actually done? Not what have they said — what have they done?
If the answer is "they took a demo and said they'd get back to us," the deal is early-stage regardless of what the CRM says. If the answer is "they introduced us to their CFO, shared their budget timeline, and started a security review," the deal is real regardless of how recently it entered the pipeline.
This audit will shrink your qualified pipeline. That's the point. A smaller pipeline of real deals produces a more accurate forecast than a large pipeline of hopes. And a more accurate forecast produces better decisions across the entire revenue organisation — from targeting to hiring to capacity planning.
If you want the complete qualification diagnostic — the 38 questions that expose which deals in your pipeline are real and which are theatre — the SDR Qualification Framework gives you the systematic audit. Because the pipeline was never as big as the CRM suggests.