What is BANT?

This page expands the BANT entry in the BSTT sales glossary.

What BANT is, and what it is not

BANT is a qualification framework, which puts it in a specific slot in a sales system. A sales methodology governs how conversations run inside each stage of a deal. A sales process is the stage-by-stage path the deal travels in the CRM. The qualification framework polices what enters the pipeline at all. BANT does that policing with four yes-or-no checks, and it does nothing else. There is no BANT discovery script and no BANT negotiation move.

The simplicity is the point. Four questions any seller can memorize, apply on a first call, and answer without a form. The simplicity is also the limitation: four binary checks cannot describe a committee purchase where budget lives in three places and authority is distributed. That tension explains both why BANT survives in SMB selling and why enterprise teams moved past it.

The four letters, spelled out

• B, Budget. Does the buyer have money allocated for this purchase, or a realistic path to allocating it.
• A, Authority. Is the seller talking to the person who can commit, or someone who will have to re-sell it internally.
• N, Need. Is there a clear business problem this purchase solves, stated by the buyer rather than assumed by the seller.
• T, Timeline. Is there a date by which the buyer intends to decide or act.

In practice a BANT check on a live deal reads like a gate. B = funds earmarked in this quarter's ops budget. A = speaking with the owner, who signs. N = invoicing errors are costing rework every month. T = wants a fix running before the new hire class starts. Any box the seller cannot fill after two conversations is the reason the deal stalls later.

The reorders: NABT, CHAMP, ANUM, GPCT

Most of what came after BANT keeps its checklist shape and changes the order, because the order is where BANT breaks. Leading with budget often distorts the conversation before the buyer has finished describing the problem.

• NABT (Need, Authority, Budget, Timeline). The minimal fix: the same four checks, reordered so the conversation starts with the buyer's problem rather than their wallet.
• CHAMP (Challenges, Authority, Money, Prioritization). A fuller reframe that leads with the buyer's challenges. Prioritization adds a pressure check BANT lacks: even with challenges, authority, and money present, does this rank high enough in the buyer's stack to get acted on this quarter.
• ANUM (Authority, Need, Urgency, Money). Promotes authority to first position, on the logic that a deal with a clear need, a budget, and a timeline is still dead if the seller is talking to someone who cannot commit. Common in transactional and mid-market B2B where buying-committee complexity is moderate.
• GPCT (Goals, Plans, Challenges, Timeline). HubSpot's inbound-era framework. It leads with the buyer's goals and what they are doing about them today, which fits conversations with operators who arrive already articulate about their objectives.

The heavier successors went further and changed the shape. MEDDIC, built inside PTC in the 1990s, replaced yes-or-no checks with six written fields per deal, and MEDDPICC extended it with Paper Process and Competition. SPICED, from Winning by Design, is the SaaS-native cousin, described in our glossary as more rigorous than BANT and lighter than MEDDPICC.

Where BANT came from

BANT was developed at IBM in the 1960s, and it set the first qualification standard in B2B selling. Every named framework in this category descends from it or reacts to it: the named-methodology era that followed, Sandler in 1967, SPIN in 1988, MEDDIC in the 1990s, all built on the premise BANT established, that a deal should be interrogated before it is worked. Six decades later the framework it started is still the baseline check on many B2B teams.

Who teaches BANT

None of the 49 providers we profile sells a branded BANT program. The framework is six decades old, public domain, and simple enough to install from a page like this one, so there is no certification to buy and no license to pay for. In our reviews of provider curricula, BANT shows up as background vocabulary rather than product.

What teams buy instead is training on the successors. MEDDIC and MEDDPICC have a canonical teacher in MEDDIC Academy and a dialect inside Force Management's Command Series. SPICED belongs to Winning by Design, and the MEDDIC vs SPICED comparison covers that trade. If the goal is sharper qualifying conversations rather than a new framework, the discovery call cheat sheet is the faster path.

For a founder-led team building its first sales system, our own guidance is blunt: MEDDIC light, SPICED, or BANT works. Pick one and use it consistently. The enforcement matters more than the acronym.

Strengths and criticisms

Strengths

• Four questions any seller can memorize. No form, no fields, no software. A new seller can apply BANT on day one, which is more than can be said for any written-field framework.
• A baseline beats no framework. Many B2B teams, especially in SMB selling, still run BANT as the first-pass check, and a consistently applied BANT beats an inconsistently applied anything.
• Right-sized for short cycles. Six to eight written fields per deal is the wrong overhead for a short SMB cycle. BANT's four checks fit the motion.

Criticisms

• Budget-first distorts the conversation. The documented weakness. Do you have a budget for this? produces a defensive reaction; How are decisions of this size typically funded at your company? produces information. BANT's own ordering pushes sellers toward the first question.
• Binary checks miss committee complexity. A checked Authority box says nothing about a five-person buying committee, a procurement stage, or a champion without power. MEDDIC's written fields exist because these are the deals BANT passes and loses.
• Teams outgrow it. The common switching path in our guides runs from BANT to MEDDIC or SPICED as deal size grows. Staying on BANT past that point turns qualification into theater.

Frequently asked questions

Related terms and guides