BANT: Budget, Authority, Need, Timing, and What It Gets Wrong About B2B

BANT: Budget, Authority, Need, Timing, and What It Gets Wrong About B2B

BANT is a sales lead qualification checklist made of four questions: does the prospect have Budget, does this person have Authority to decide, is there a genuine Need, and is the Timing such that a purchase could happen soon. A lead answering all four is treated as qualified and passed to a salesperson. A lead failing any one of them is not.

It is the oldest and simplest of the qualification frameworks in common use, and its simplicity is both why it spread and why it fails on a large share of modern B2B purchases. Worth noting at the outset: the letters also stand for unrelated things outside sales, so a search for the bare acronym returns dictionary entries and a card game alongside the framework described here.

The four questions, and what each was designed to catch

Budget. Is money allocated, or plausibly available, for this kind of purchase. Designed to stop sellers spending months on organisations that were never going to spend anything.

Authority. Can this person decide, or are you talking to someone who will have to sell it internally. Designed to stop deals stalling one layer below where they get approved.

Need. Is there a real problem your product addresses, as opposed to polite interest. Designed to stop a demo being mistaken for demand.

Timing. Is there a reason this happens in a defined window rather than eventually. Designed to stop a pipeline filling with deals that never close.

Each was a sensible response to a real failure. Read as a diagnostic list, all four still are.

Holds up well

• Need: a real problem is still the precondition for everything
• Timing as a QUESTION: what makes this happen in a window
• Both are about the buyer's situation rather than your convenience

Holds up badly

• Budget: frequently created after the decision rather than before it
• Authority: rarely held by one person in a committee purchase
• Timing as a GATE: a genuine buyer six months out fails it today

Where the textbook definition breaks

Budget usually does not exist before the decision. In a large share of B2B purchases the line item is created because someone decided to solve the problem, so asking early whether budget exists gets a truthful no from exactly the buyers most worth having. The productive version of the question is whether they could get budget, from whom, and what that process looks like.

Authority is rarely singular. Committee purchases are the norm above modest deal sizes, and the useful questions are who has to agree, who can veto, and who controls the money. A single yes-or-no authority check reduces that to a binary and then routes on it. This is exactly the gap MEDDIC was built to close, with separate checks for the economic buyer, the decision criteria and the decision process.

Timing as a gate discards good pipeline. A perfect-fit company planning a replacement next year fails the timing check and gets dropped, which converts a real future customer into a rejection. As a question timing is valuable. As a pass or fail it is a filter on your own convenience.

The four are treated as equal. Need is the precondition; the other three are properties of when and how a purchase happens. A lead with strong need and no timing is a real opportunity that is early. A lead with budget, authority and timing but no need is not an opportunity at all, and it will consume months proving it.

It is answered by the seller, not the buyer. In practice the fields get filled in from inference after a call. Once that happens the framework records the seller's optimism in four boxes and reports it as qualification, which is worse than no framework because it looks like evidence.

Why the criteria must never become billing conditions

There is a specific commercial version of this that matters whenever someone is paid per meeting or per qualified lead.

If budget, authority and timing are written into a definition of a qualified meeting, then a genuine conversation with exactly the right person at exactly the right company can be rejected afterwards because that person said the money is not in this year's plan. The meeting happened, the person was right, and the outcome was decided by a fact that changes every quarter.

Our position is that a meeting qualifies on a different basis: the company matches the audience agreed in writing before launch, the person has real responsibility for or influence over the area, they agreed to a relevant business conversation, they attended and took part, and they were not on the suppression list supplied at the start. Budget, timing, authority and immediate intent are deliberately outside that definition. They are useful things for a salesperson to learn on the call and poor things to make anyone's invoice depend on, and the reasoning is set out in pay-per-appointment B2B and in qualified lead generation services.

Using the four questions well

• ~Depends: Need is treated as the precondition, not as one of four equal boxes
• ~Depends: Budget is asked as a process question rather than a yes or no
• ~Depends: Authority is recorded as a map of people, not a single name
• ~Depends: Timing is captured as a date and a reason, and never used to disqualify
• ~Depends: Each answer comes from something the buyer said, not from inference
• ~Depends: None of the four appears in a commercial definition of a qualified meeting

Where it still earns its place

Three situations where the simplicity is a genuine advantage rather than a limitation.

Transactional deals with one decision maker. Where a single person really can decide and pay, the four questions map neatly onto reality and anything heavier is overhead.

Inbound triage at volume. A fast read of an enquiry against four questions is a reasonable first filter when hundreds arrive, provided the output routes rather than discards. The population it is applied to is described under inbound lead.

As a conversation prompt. Used as four things to find out rather than four boxes to tick, BANT is a decent structure for a first call, particularly for a new salesperson who needs a shape to hold. Turning that into a call that disqualifies well is covered in the discovery call.

The common feature of all three is that the framework is being used to organise a person's attention rather than to make a routing decision on their behalf. That is the distinction worth carrying away from it. As a memory aid for what to establish in an unfamiliar conversation, four short words are hard to beat. As an automated gate applied to a database, the same four words discard a substantial share of the buyers you would most like to have.

The framework's real successor for complex deals is the MEDDIC family, which replaces one authority check with several and adds the parts BANT never had, described in MEDDPICC.

The reorderings, and what each one is arguing

Several later frameworks are BANT with the letters reprioritised, and each reordering is an argument about which check should come first. Knowing what the argument is makes them easier to choose between than the acronyms suggest.

Need first. The most common revision, on the grounds that a problem is the precondition for everything else and that starting with money teaches sellers to interrogate strangers about their budget before establishing there is anything to buy. Frameworks in this family lead with the problem, then the person, then the money, then the date.

Authority reframed as the buying group. The observation that no single person has authority in a committee purchase, so the useful output is a map of who agrees, who vetoes and who signs, rather than a name in a field.

Budget reframed as funds. The argument that the question is not whether money is allocated today but whether the organisation could find it, from where, and what that would require. This survives contact with the very common case where the budget line is created after the decision.

Timing reframed as consequence. Instead of asking when they will buy, asking what happens to them if nothing changes. A buyer who can articulate a cost of delay has a date whether or not they have named one, and a buyer who cannot does not have a real timeline however confidently they gave you a quarter.

The common thread is that every revision moves the framework away from a checklist a seller can complete and toward a set of things a seller has to find out. That is the honest read of BANT's limitation: as a list of facts to collect it is easy to fill in and easy to fill in wrongly, and as a list of things to understand it is still a reasonable structure for a first conversation.

One practical note about all of them. A framework only works if the answers come from the buyer's own words, recorded as they said them, rather than from a seller's summary written afterwards. The single highest-value habit in any of these systems is quoting the buyer in the field rather than paraphrasing them, because a quote can be re-read later by someone who was not on the call and a paraphrase cannot be checked at all.

Related terms

Lead qualification is the practice BANT is one instrument for. MEDDIC is the enterprise-grade replacement. Lead scoring is the automated version applied to inbound traffic. And an account executive is the seat whose time all of it exists to protect.

The short version

BANT asks four questions: budget, authority, need, timing. Need is the precondition and the other three describe when and how a purchase happens. Use them as questions, never as gates, keep them out of any definition that money depends on, and reach for MEDDIC when several people have to agree.

Getting the right person into the conversation where these questions become answerable is the part we run: see what a first campaign produces.