BANT. A 1960s framework still disqualifying good 2026 deals.
BANT — Budget, Authority, Need, Timing — is an IBM-developed qualification framework from the 1960s, still widely taught in sales bootcamps, and increasingly out of step with how modern B2B actually works. The framework was designed for a buying environment where a single decision-maker had all four answers — a CIO with a tooling budget, deciding alone, with a clear need and a quarterly timeline. That environment no longer exists in most enterprise sales. Modern B2B is consensus-driven, multi-stakeholder, with budget often allocated after the deal advances rather than before. BANT's hard-qualification logic produces systematic false negatives — disqualifying genuinely qualified champions because they don't have all four answers in week 2. This essay covers the four criteria with then-vs-now analysis, the false-negative problem in detail, where BANT still works (transactional SMB sales with single decision-makers), the modern replacements (GAP sizing, MEDDIC qualification, consensus-aware methods) that fit consensus-buying, and how to use BANT as one input rather than the verdict.
01What BANT is
BANT is a qualification framework that asks four diagnostic questions about a sales opportunity:
- Budget — Does the prospect have allocated budget for this purchase?
- Authority — Does the contact have the authority to make this purchase decision?
- Need — Is there a real, articulated need for the product?
- Timing — Is there a defined timeline for the purchase decision?
In its original form, BANT was a binary qualification gate: all four had to be confirmed before the deal advanced. A prospect missing any of the four was disqualified — either out of the funnel entirely or pushed back to marketing-nurture status. The discipline simplified what was, in the 1960s, a complex qualification process into a clear checklist that a junior salesperson could execute.
BANT has remained in widespread training because of three properties:
It's simple. Four words, easy to remember, fits on an index card. A new SDR can internalize BANT in five minutes; SPIN or MEDDIC takes substantially longer.
It produces clean numbers. "47% of MQLs pass BANT" is a measurable, defensible metric that sales and marketing can argue about. Less rigorous frameworks don't produce clean conversion data.
It feels rigorous. Disqualifying prospects feels like discipline; advancing only "qualified" deals feels efficient. Sales leaders who came up in the 1990s-2000s often associate BANT with the rigor of "real" sales process.
The simplicity, measurability, and feeling-of-rigor make BANT comforting. The problem is that all three properties are also why it produces false negatives in modern B2B.
02The IBM 1960s origin
BANT was developed inside IBM's sales organization in the 1960s, when IBM was selling mainframe computers to large enterprises. The buying environment of that era had three properties that shaped the framework:
Single decision-maker. Mainframe purchases were typically made by a single CIO or VP of Data Processing, with explicit corporate authority to commit budget. The decision-maker had all four answers — they knew the budget (they controlled it), they had the authority (they were the buyer), they understood the need (they ran the function), and they knew the timeline (they set it).
Pre-allocated budget cycles. Enterprise IT budgets in the 1960s were planned annually, with quarterly review cycles. By Q2, most line items were spoken for; new purchases required either replacing planned items or waiting for next year's budget. The Budget question had a deterministic answer.
Multi-million-dollar deals with multi-year cycles. An IBM mainframe sale was a multi-year, multi-million-dollar commitment. The cost of pursuing an unqualified deal was enormous; the rigor of BANT-style hard qualification was justified by the deal economics.
The framework was right for that environment. It's the changes in environment — not changes in the framework — that have made BANT increasingly mis-fit:
- Modern enterprise B2B has 5-7 stakeholders, not one. The Authority question doesn't have a single answer.
- Modern budgets are increasingly allocated reactively, not pre-planned. Budget often gets created when a champion advocates for a project, not before.
- SaaS economics have changed deal cycles. Modern enterprise deals close in 30-180 days, not 12-24 months. The cost of pursuing borderline deals is much lower than in IBM's 1960s context.
- Buyers research extensively before contacting sales. By the time they're in a discovery call, the "Need" question is often partly resolved — they wouldn't be talking if there were no need at all.
BANT's structural mismatch with the modern environment isn't a flaw in the original framework — it's a consequence of being designed for a buying environment that no longer dominates.
03The four criteria (then vs now)
Each criterion examined in operational context — what BANT assumed in 1960, what modern B2B actually looks like, and where the framework breaks:
The pattern across all four criteria: BANT assumes the buyer has fixed answers to the four questions; modern B2B treats those answers as outputs of the sales process, not inputs to it. The framework worked when the answers were stable; it fails when the answers are emergent.
04The false-negative problem
The most damaging consequence of BANT's mis-fit with modern B2B is the false negative — disqualifying genuinely winnable deals because the prospect doesn't yet have all four answers. A worked example:
The example illustrates the systematic problem: BANT's three-of-four-fail outcome on a typical mid-funnel deal is the same outcome it would produce on a completely unqualified deal. The framework can't distinguish "qualified champion at the wrong stage" from "tire-kicker with no real interest" — both look identical in BANT terms.
Sales orgs running strict BANT lose somewhere between 20% and 40% of their winnable pipeline to this false-negative problem. The deals are real; the qualification framework is wrong.
Modern frameworks distinguish these states. GAP Selling asks "is the gap big enough to support a deal?" — which the example deal passes easily. MEDDIC asks about Metrics, Economic Buyer, Decision Process, Identified Pain — which surfaces the champion as the path to the Economic Buyer rather than disqualifying based on authority. Both frameworks would correctly classify the example deal as a qualified mid-funnel opportunity.
05Where BANT still works
BANT isn't universally obsolete — it still fits certain selling environments. The fit map:
The honest synthesis: BANT works for transactional simple-buyer sales; it's wrong for modern enterprise B2B. Sales orgs that run a mix of motions need to be explicit about which qualification framework applies to which deal type. Applying BANT uniformly across motions damages the enterprise side; applying GAP/MEDDIC uniformly is overkill for the transactional side.
06The modern replacements
What modern qualification frameworks do better than BANT, and which to use when:
GAP Selling replaces BANT's binary Need with a sized gap. The relevant question isn't "is there a need?" — it's "is the gap big enough to support this deal size?" GAP answers the qualification question while also creating the value frame for the deal. Best replacement for BANT in mid-market and enterprise sales.
MEDDIC replaces BANT's four criteria with six richer ones (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identified Pain, Champion). Treats Authority as a process to map rather than a binary to check. Surfaces the Economic Buyer (which BANT calls Authority) as a target to access rather than a gate. Best replacement for high-stakes enterprise deals.
SPIN Selling isn't a qualification framework but its discovery architecture surfaces all four BANT criteria as part of natural conversation rather than as direct interrogation. Top reps often run SPIN discovery and arrive at BANT-equivalent qualification without ever asking BANT questions directly. Best for the discovery phase regardless of which qualification framework you use after.
Modern frameworks generally share three improvements over BANT: they treat Authority as a multi-stakeholder reality rather than a single-person check; they treat Budget as something deal-progression creates rather than presupposes; and they replace binary Need with sized gap or quantified outcome. These three improvements alone capture most of what modern qualification needs to do that BANT doesn't.
07How to use BANT correctly
If your org still uses BANT (and many do), the discipline that prevents the false-negative problem:
- Use BANT as a visibility checklist, not a qualification gate. The four criteria are useful as "do I have visibility into these?" questions. Use them to identify gaps in your understanding. Don't use them to decide whether to advance the deal.
- Recognize that BANT's "Authority" usually means Economic Buyer. Reframe the question from "does this person have authority?" to "do I know who the Economic Buyer is and how to access them?" The shift makes the question productive instead of disqualifying.
- Treat Budget as something to be created, not confirmed. Modern B2B budget often gets allocated when the champion makes the case. "We don't have budget yet" is a fact about the current state, not a forecast about whether the deal will close. Coach reps to help champions build the budget case rather than walking away from no-budget conversations.
- Use GAP-style sizing instead of Need binary. "Is there a need?" is the wrong question. "Is the gap between current and future state large enough to support a deal of this size?" is the right one. GAP sizing turns Need from a yes/no question into a quantitative diagnostic.
- Treat Timing as emergent rather than pre-existing. Open-ended "sometime this year" isn't a disqualification — it's an opportunity to help the buyer establish a timeline. Asking "what would make Q3 the right time for this?" advances the deal in ways "do you have a timeline?" doesn't.
- Layer BANT on top of GAP or MEDDIC, never instead of. If your sales-ops process requires BANT scoring (many CRMs default to this), keep the scoring as a reporting artifact but make actual qualification decisions on a richer framework. Don't let the reporting layer drive the deal decisions.
- Train SDRs out of BANT-as-script. Many SDR programs teach BANT as a literal script: "do you have budget? do you have authority? do you have a need? do you have timing?" This is the worst version. Coach SDRs to surface the four areas through natural conversation rather than direct interrogation; the answers are far better.
08Common mistakes
Modern qualification needs signal context, not a 1960s checklist.
BANT can't tell you whether a deal is qualified because it can't see the signals that actually predict closing — funding rounds, tech changes, exec moves, hiring spikes. Mama surfaces those signals so qualification can be based on what's actually happening at the account rather than four questions designed for the 1960s.