BANT Was Never a Discovery Framework. Stop Grading Reps Like It Is.

BANT is older than most of the reps using it, and it was never built to do what we now ask it to do. IBM's sales organisation put it together in the 1950s and 60s as a triage tool for inside reps working high call volumes — a way to decide, fast, whether a lead was worth a callback. Budget, Authority, Need, Timeline. Four boxes. Tick them, file the lead, move on. It was designed for filing, not finding. Somewhere in the last twenty years, sales enablement decided it was a discovery methodology, and every qualified-pipeline problem I've seen since traces back to that mix-up.

A filing cabinet is not a fishing rod

Here's the category error, stated plainly: BANT tells you where to put a deal once you already understand it. It does not tell you how to build that understanding in the first place. Use it after a real conversation, as a checkpoint, and it does its job perfectly well — four fast questions that confirm what you already suspect. Use it as the conversation itself, and you get reps who walk in with four boxes to fill and treat the call as complete the moment the boxes are ticked, regardless of what's actually behind each tick.

Listen to what this sounds like on a real call. Minute three, rep asks: "So what's the budget looking like for something like this?" Prospect: "I don't know, maybe £50k, something like that." Rep ticks Budget: Yes, moves to Authority. Nothing was tested. Nobody asked where the £50k came from, whether it survives a real business case, or who else would need to agree to spend it. The box is green. The deal is "qualified." None of that is qualification — it's data entry with a script running it.

The pipeline this manufactures

This is where it gets expensive. Sales ops teams build stage-gates off these four fields because they're simple to report on, which means a deal can sit at "Stage 3 — Qualified" fully green across Budget, Authority, Need, and Timeline while having zero evidence of a mapped decision process, zero evidence anyone has tested the actual decision criteria, and zero mention of what happens once the deal reaches legal or procurement. The deal looks healthy in the forecast because BANT has no field for any of that. It was never asked to have one — it's an artefact of an era when the person on the phone usually was the whole buying committee, and there wasn't a paper process worth mapping because nobody's IT security team had a vendor review process yet.

Run the maths on your own forecast slippage and I'd bet a meaningful chunk of it traces to exactly this: deals that were BANT-green and collapsed in month two, not because the rep lied, but because BANT gave them nowhere to write down the thing that actually killed the deal. You cannot fail a field that doesn't exist.

Where BANT is genuinely fine

To be fair to a sixty-year-old acronym: in high-volume, short-cycle, transactional selling — one decision-maker, no procurement gate, a deal that lives or dies inside a single call — BANT's crudeness is a feature. You don't need a mapped decision process for a £2,000 SaaS seat that one manager can approve on their own card. The four boxes are the right amount of qualification for that motion, and adding MEDDIC-style depth to a five-minute call is over-engineering. The mistake isn't using BANT. It's using BANT for a deal shaped like a six-month enterprise procurement cycle and being surprised when it doesn't catch the things that only show up in six-month enterprise procurement cycles.

What enablement teams get wrong

The reflex, when a deal like this blows up, is to blame the rep for "not qualifying properly." That's backwards. The rep qualified exactly as trained — hit the four fields, move to proposal. The actual failure sits with whoever decided BANT was a sufficient discovery script and built the pipeline review, the coaching rubric, and the stage-gate definitions around it. Coaching reps to "hit BANT" harder doesn't fix this. It just makes them faster and more confident at filling in a form that was never designed to catch the failure mode currently killing your deals.

The fix isn't complicated, but it does mean admitting the acronym your CRM stages are built around is doing a job it was never designed for.

1. Move BANT to the back of the call, not the front. Use it as a two-minute checkpoint after real discovery, to confirm what you've already found — not as the script that generates the finding.
2. Give reps a discovery structure that actually has a "why now" and a "who else" built in, rather than bolting those on informally when a manager happens to notice they're missing. A Discovery Call Script & Flow Template built around genuine curiosity questions, not field-filling, does this without inventing a new acronym for reps to memorise.
3. Coach and grade against decision process and paper process explicitly, since neither has a home in BANT and both are exactly where deals you thought were qualified go to die. A Paper Process & Decision Criteria Checklist gives you something concrete to grade a transcript against, instead of "did they mention budget."
4. If you're going to standardise on a qualification framework for anything above transactional, pick one that matches your actual deal complexity, rather than defaulting to the acronym everyone already knows. The Qualification Framework Comparison Guide (BANT vs. MEDDIC vs. CHAMP) is worth ten minutes before your next enablement rebuild, because BANT and MEDDIC aren't competing options for the same job — they were built for different jobs entirely.

BANT isn't wrong. It's misfiled. Put it back in the filing cabinet, where it's genuinely useful, and stop asking it to go out and find things it was never built to look for.