BANT

What BANT Is

BANT is IBM's 1950s qualification checklist, still alive in onboarding decks everywhere. Budget, Authority, Need, Timeline — four criteria that together signal whether a prospect has the minimum conditions to be worth a salesperson's time. Screen all four and you have a qualified opportunity. Miss two and you have a nurture sequence. The framework predates the CRM, the SDR role, and most of the B2B software companies using it, which tells you something about both its durability and its limitations.

How BANT Qualification Works

There is no formula. BANT is a discovery checklist, not a calculation. Reps validate each criterion through open-ended questions on initial calls, log the findings in CRM fields, and most orgs use the results as a gate for moving a prospect from marketing-qualified to Sales Qualified Lead status. Leads that pass all four criteria advance to an AE. Leads that fail two or more route to nurture with a 90-day return date stamped on them.

Some teams score BANT in partial credit — three of four criteria present still advances a lead with a caveat flagged in the CRM. That is a judgment call, not a standard, and different teams draw the line differently.

BANT Qualification Worked Example

An SDR gets an inbound lead from a VP of Engineering at a 300-person SaaS company. The prospect has $60,000 approved in the current quarter's IT budget (Budget: confirmed). She owns the tooling decision outright and reports directly to the CTO (Authority: confirmed). Her team has a documented security gap the product closes (Need: confirmed). SOC 2 audit is in 10 weeks and the tool needs to be live before it (Timeline: confirmed). Four of four. The lead converts to SQL, an AE takes the first discovery call, and the deal enters Stage 1 at 20% probability.

Replace "SOC 2 audit in 10 weeks" with "we're thinking about this for next fiscal year" and that same lead goes to nurture. Timeline unconfirmed is not a pipeline entry.

When Sales Teams Use BANT

Sales development teams apply BANT at the top of funnel — inbound triage and outbound prospecting — to protect AE capacity from unwinnable conversations. RevOps uses BANT field compliance as a pipeline quality signal: a forecast full of opportunities with "Authority: Unknown" is a deal slippage factory, not a pipeline. VP Sales and Finance review BANT completion rates during pipeline coverage audits to diagnose whether SDRs are passing leads too aggressively.

Enterprise AEs often bypass BANT for complex accounts where a single contact rarely controls all four criteria. Coalition buying, multi-budget approvals, and 18-month timelines break the checklist model. That gap is exactly why MEDDIC and MEDDPICC were developed.

Common BANT Gaming Patterns and Limitations

Every BANT criterion is self-reported and optimism-prone, which makes each one gameable. Budget is the worst offender. A prospect who says "we have budget" may mean "we plan to request budget next quarter," and a rep who wants to hit SQL targets accepts the soft confirmation and checks the box. Analysts who have audited stalled pipelines put the rate of false Budget confirmations at roughly half of all deals that die in procurement. BANT's Budget question cannot distinguish between "approved funds" and "aspiration."

Authority leaks almost as badly. Mid-level champions routinely overstate their influence, and reps advancing toward quota accept "I have a lot of pull with the CFO" as Authority: confirmed. The difference between a champion and an economic buyer is the signature — and BANT does not require you to have met the person who signs.

Timeline manipulation is structural at end of quarter. Closing pressure causes reps to log aggressive close dates for deals with no genuine urgency, which inflates pipeline confidence and depresses win rate accuracy in the following quarter when those deals slip.

BANT does not assess competitive position, political dynamics, or implementation risk. A prospect that passes all four criteria can still lose to the status quo or a better-positioned competitor. That is not a flaw unique to BANT — no checklist survives contact with an indecisive procurement committee — but it is the reason the framework has spawned successors for 30 years.