Explained / Other / 26 September 2026
BANT in 2026: still useful, or obsolete?
BANT (Budget, Authority, Need, Timeline) is the original qualification framework, developed at IBM in the 1960s. In 2026 it is widely derided as obsolete and widely used in practice. The right reading: BANT is a useful starting framework that needs adaptation for modern UK B2B buying processes; the underlying concerns are still the right concerns.
BANT is too thin for enterprise B2B and is genuinely obsolete for that segment. For SMB and mid-market with shorter cycles and simpler buying structures, BANT-with-adaptation is still functional. The honest answer is contextual: BANT for SMB short-cycle, MEDDPICC or equivalent for enterprise.
Where BANT comes from
BANT (Budget, Authority, Need, Timeline) is the original B2B sales qualification framework, attributed to IBM in the 1960s. The framework's premise: a real opportunity has identified budget, an identified decision authority, an articulated need, and a defined timeline to act. Absent any of the four, the opportunity is not yet real.
For decades BANT was the canonical qualification framework taught to B2B sellers globally. From the 2010s it has been progressively displaced in enterprise B2B by MEDDIC, MEDDPICC, and other more granular frameworks. By 2026, BANT is widely derided in enterprise B2B circles as obsolete. It is also widely used in practice, particularly in inbound and SMB sales contexts. The honest reading is contextual.
The case against BANT in modern B2B
Three substantive critiques of BANT in modern enterprise B2B:
First, Budget is rarely identified at the start of a buyer's evaluation. Modern enterprise buyers often initiate evaluation before a specific budget is allocated; the budget is created or reallocated as the business case develops. Sellers who insist on identifying Budget early disqualify legitimate opportunities.
Second, Authority is rarely a single person in modern B2B. Group decision-making is the norm at enterprise scale; identifying "the decision-maker" is a 1970s frame that does not match how decisions are actually made in 2026.
Third, BANT is too thin for enterprise. The four letters do not surface enough about the deal to support meaningful forecasting or selling. Specifically: BANT does not surface internal politics, competing alternatives, or implementation risk, all of which are first-order in enterprise B2B.
The case for BANT in some segments
Despite the critique, BANT remains functional in specific segments:
SMB sales with shorter cycles: a 30-60 day cycle to a small business buyer with a single decision-maker maps reasonably well to BANT. The buyer does have a budget (or does not), is the authority, has a need, and has a timeline. The framework's simplicity is a feature.
Inbound sales qualification: BANT works as a fast triage framework for inbound leads at the SDR layer. Does this lead have any of the four. If yes, pass to AE. If no, nurture or disqualify.
Transactional and high-velocity sales: where the cycle is short enough that elaborate qualification frameworks add overhead without value, BANT provides enough structure.
How modern UK B2B teams handle BANT
The honest pattern visible in UK B2B sales teams in 2026: run BANT at the inbound SDR layer for fast triage, run MEDDPICC or equivalent at the enterprise AE layer for substantive qualification, do not pretend BANT is sufficient for enterprise deals while also not pretending MEDDPICC is necessary for SMB.
Some teams blend the two: BANT-plus, where the four BANT letters are extended with a "deal context" layer that adds Champion, Competition, and Decision Process from MEDDPICC. The blended frame addresses BANT's thinness without imposing full MEDDPICC overhead.
The honest answer
For UK B2B sales leaders thinking about whether to teach BANT: the question is which segment your team is selling into.
Enterprise B2B with multi-stakeholder decisions and 6+ month cycles: BANT is too thin. Use MEDDPICC, Sandler, Challenger, or another methodology designed for that complexity.
Mid-market with 3-6 month cycles: BANT-plus or equivalent works; pure BANT is borderline.
SMB with sub-90-day cycles: BANT works. The simplicity is a feature.
Inbound triage: BANT works as fast triage; it is not a substitute for substantive AE-level qualification later in the cycle.
The mistake is treating BANT as universally good or universally obsolete. The honest answer is contextual.
Source: Original BANT framework developed at IBM in the 1960s. Editorial synthesis from UK practitioner observation.