BANT

What is BANT?

BANT is a sales qualification framework developed by IBM in the 1960s. Four letters: Budget, Authority, Need, Timeline. A rep qualifies a prospect by confirming budget is available, the prospect has decision authority, a genuine need exists, and there's a defined buying timeline. If any of the four are missing, the deal gets disqualified or pushed to a later stage.

BANT was designed for a simpler buying era. In 1960s mainframe sales, the buyer was usually a single executive with authority, budget, and a clear timeline to implement. Modern B2B SaaS buying almost never matches that profile. Buying committees of 6–10 people make decisions. Budget comes from multiple cost centers. Authority is distributed. Timelines are fluid. BANT's four checkboxes don't capture any of that complexity.

Despite its age, BANT is still the most-used qualification framework in B2B — not because it's the best, but because it's the shortest. For inbound SDR qualification on transactional deals under $10K ACV, BANT's four fields are enough. For anything more complex, BANT misses the fields that actually predict close: the decision process, the procurement path, the competition, the economic buyer (who is not the same as 'authority' in the modern sense).

What each letter means

The original IBM definition has been interpreted loosely over the decades. The most common modern reading:

• Budget — is money allocated for this category? Some teams require a confirmed line item; others accept 'funds would be found if the solution is right.' Looser interpretation weakens the signal.
• Authority — does this contact have decision authority, or can they escalate to someone who does? The 1960s version assumed the contact was the decision-maker. The modern version has to include escalation paths because most early contacts are champions, not approvers.
• Need — is there a concrete problem the prospect is trying to solve? 'We want better reporting' is not need; 'we missed board targets by 15% last quarter because our forecast was wrong' is need.
• Timeline — when does the prospect plan to make a decision and implement? A specific quarter or date is qualifying; 'sometime soon' is not.

Why BANT still shows up (and where it fails)

BANT persists because SDR teams need a fast framework. On a 15-minute inbound qualification call, asking about budget, authority, need, and timeline is short enough to get through without annoying the prospect. The four fields populate CRM cleanly. The AE gets a basic signal of whether to take the meeting. For inbound qualification on deals under $10K ACV, BANT is good enough.

BANT fails on everything above that. Three structural problems: (1) Authority is a single-decision-maker concept that doesn't fit committee buying. The early contact with 'authority' often turns out to need five other approvers. (2) Timeline without a Compelling Event is fiction. Prospects who say 'Q3' rarely mean it; without a dated business reason forcing the decision, timelines slip. (3) BANT captures no information about procurement, security review, paper process, or competition — all of which determine whether the deal actually closes.

Gartner Sales Research 2024 found that deals qualified on BANT alone had 15–22% lower win rates than deals qualified with MEDDPICC or NEAT frameworks on equivalent enterprise opportunities. The gap widened as deal size grew. Above $100K ACV, BANT-only qualification produced win rates so low that Gartner labeled the practice 'actively harmful' to forecast accuracy.

When to use BANT vs when to use something heavier

Use BANT for inbound SDR qualification on transactional B2B deals under $10K ACV with single decision-makers and sub-30-day sales cycles. BANT is the right weight for that motion — anything heavier slows the SDR's throughput and drops inbound conversion.

For mid-market deals in the $10–100K range with 2–4 stakeholders and 30–90 day cycles, upgrade to SPICED or NEAT. These frameworks are closer to BANT in weight but replace 'Authority' with more useful concepts (Access to power, Decision Process) and require a Critical Event or quantified Impact instead of a vague Timeline.

For enterprise deals above $100K ACV with committees of 5+ and cycles of 3–9 months, upgrade to MEDDPICC. The eight-letter framework captures Paper Process, Competition, and Champion — the fields that determine whether complex deals actually close. Running BANT on enterprise is malpractice.

Common mistakes reps make with BANT

1. Accepting soft budget answers. 'We don't have a specific budget but we'd find money for the right solution' is not a qualifying answer. Push for a range. If no range, the deal isn't real.

2. Confusing 'Authority' with Economic Buyer. The early-stage contact usually has influence, not authority. Pushing for BANT authority in discovery creates false positives.

3. Taking 'Q3' at face value. Without a Compelling Event tied to that quarter, 'Q3' means 'someday.' Most Q3 timelines slip to Q4, then Q1 next year.

4. Forecasting BANT-qualified enterprise deals as commit. BANT isn't enough data to commit a six-figure deal. Use BANT for early pipeline qualification on those deals, then layer MEDDPICC before commit.

How Gangly handles BANT-style qualification

Gangly's Call Prep Engine generates BANT prompts for SDR discovery calls when the deal is flagged as transactional or PLG motion. Live Call Coach watches the call and flags when a BANT answer is soft ('we'd find budget') vs firm ('we have $40K allocated'). Post-Call Notes captures the exact BANT responses verbatim so the AE inheriting the deal sees what the prospect actually said, not a rep's interpretation.

For enterprise deals, Gangly automatically switches to MEDDPICC prompts — because BANT is the wrong weight at that deal size. The rep doesn't have to remember which framework to run; the system adapts to the deal's characteristics.

See how Call Prep Engine works →

Frequently asked questions