BANT: The Original Qualification Framework

BANT is, by most accounts, the oldest formal sales qualification framework still in everyday use. It's commonly attributed to IBM, developed decades ago in an era when enterprise technology sales looked nothing like it does now — a single mainframe or system purchase, negotiated with a single IT director who controlled a fixed annual budget and could say yes without a committee. Sources aren't perfectly consistent on the exact year or the precise internal history, so it's fairer to treat "IBM, mid-20th century" as the well-corroborated shape of the story rather than a precisely dated fact. What's not in dispute is that the framework spread far beyond IBM and became, for a long stretch of B2B sales history, close to the default way reps decided whether a lead was worth pursuing.

The four questions

Budget asks whether the prospect has money allocated, or realistically obtainable, for a purchase in this category — not necessarily an exact number, but confirmation that funding isn't a fantasy. Authority asks whether the person on the call can actually decide, or carries enough influence that their support meaningfully moves a decision. Need asks whether there's a real, acknowledged problem the product addresses — not a nice-to-have, but something painful enough to justify spending on it. Timeline asks whether there's a concrete reason to act in a defined window, rather than "maybe next year." Historically, reps worked through these more or less in order, and a prospect who cleared all four was considered qualified to move forward in the pipeline.

Where it fits, and where it breaks down

BANT still earns its place in fast, high-volume qualification work — SDR calls, inbound lead scoring, any context where a rep needs a quick, teachable checklist to decide whether a lead deserves more time. Its weakness shows up as deals get more complex. Modern B2B purchases, especially in software, are frequently made by committee: five to ten stakeholders, no single person who can unilaterally say yes, and a budget that often doesn't exist as a line item until the need has already been proven internally. Qualifying strictly by BANT's order — checking for budget and a single decision-maker before fully exploring need — risks disqualifying a real opportunity simply because the money and the org chart haven't caught up yet to a problem that's genuinely worth solving. That gap is exactly why newer frameworks emerged as an explicit response: NEAT replaces "Budget" and "Authority" with "Economic impact" and "Access to authority," reflecting that impact often has to be proven before budget appears, and that reps rarely get direct access to the final decision-maker early on.

Reading about it isn't the same as doing it

BANT's four letters are easy to memorize and surprisingly hard to execute well on a live call — asking "what's your budget?" too bluntly can shut a prospect down, and confirming real authority often takes several careful, indirect questions rather than one direct one. The skill isn't knowing the acronym; it's asking each of the four questions in a way that doesn't feel like an interrogation, adapting the sequence when a prospect answers out of order, and knowing when a "soft no" on budget or timeline is actually a "not yet" worth pursuing differently. That's a live conversational skill, and it's built through repetition, not by reading the definition one more time. See The Practice Gap for why this holds for every methodology on this list.

Practicing BANT with Frontline Coach

Frontline Coach ships BANT as one of 12+ built-in sales methodologies, alongside its modern successor NEAT and deeper qualification frameworks like MEDDIC, plus 6 CX methodologies and 8 coaching frameworks. SDRs and account executives can rehearse a full BANT qualification call against a simulated prospect — including the ones who push back on budget or dodge the authority question — and get scored on the conversation before it happens for real. See pricing — plans start at $9.99/mo.