BANT: The Lead Qualification Framework That Still Works

BANT was invented at IBM in the 1960s. Sixty years later, it is still the most widely used qualification framework in sales. That longevity is not nostalgia — it is evidence that BANT captures something fundamental about how B2B purchasing decisions work.

Budget, Authority, Need, Timeline. Four questions that determine whether a prospect can buy from you. Not whether they want to — that is a different question. Whether they CAN. A prospect who loves your product but has no budget cannot buy. A prospect with budget but no authority to approve cannot buy. A prospect with budget and authority but no pressing need will not buy this quarter. And a prospect with budget, authority, and need but no timeline will buy "eventually" — which is sales code for "never."

BANT's simplicity is its strength. You can teach it to a new rep in 10 minutes. You can evaluate any deal against it in 30 seconds. And if a deal fails any of the four criteria, you know immediately that it is not qualified — which saves you from investing 20-30 hours of selling time on a prospect who was never going to become a customer.

But BANT's simplicity is also its weakness. When used mechanically — checking boxes instead of genuinely understanding the prospect's situation — BANT produces shallow qualification that misses nuance. This guide will show you how to use BANT effectively: the right questions for each element, the red flags that indicate false qualification, and when BANT i s sufficient versus when you need a deeper framework like MEDDIC.

B — Budget: Can They Afford It?

Budget is the most straightforward BANT element and the most commonly mishandled. Reps either ask about budget too early (before establishing value, which anchors the conversation at a low number) or too late (after investing significant time in a deal that turns out to have no money).

The timing rule: discuss budget AFTER you have established the cost of the prospect's problem but BEFORE you invest in a customized proposal. Typically, this means the end of the first or second discovery call.

Questions that work:

"Have you allocated budget for solving [this specific problem], or is this something we would need to build a business case for?" — This question distinguishes between prospects who have pre-approved budget (fast track) and prospects who need to justify the expense (slower track, requires ROI documentation). Both can be qualified prospects, but they require different approaches.

"Typically, solutions in this space cost $X-$Y per user per month. Does that align with what you were expecting?" — This anchors the prospect at your price range before they have a chance to anchor you at their number. If they say "that is in the ballpark," budget is likely workable. If they say "that is way more than we expected," you either need to reframe value or accept that the deal is not viable.

"What is the cost of NOT solving this problem? You mentioned [quantified pain from earlier in the conversation]. If that continues for another 12 months, what does that cost?" — This is the Hormozi question. When the cost of the problem exceeds the cost of the solution by 5-10x, budget objections dissolve because the prospect cannot afford NOT to buy.

Red flags for budget:

• "We do not really have budget for this" after two conversations — this is not a timing issue. This is a "we cannot buy" issue. Move to nurture.
• "We have budget but it is very limited" — clarify what "limited" means in specific numbers. If their "limited budget" is $20/user/month and your product starts at $79, the gap is structural.
• "Budget approval takes 6 months" — this is a timeline issue disguised as a budget issue. The budget might exist, but the pr ocess to access it extends your sales cycle significantly.

A — Authority: Can They Say Yes?

Authority identifies who has the power to make or approve the purchase decision. In complex B2B sales, this is almost never the person you are initially talking to. Your first contact is typically a Director or Senior Manager — someone with influence but not final authority for investments above $10,000-$20,000.

The mistake most reps make: accepting "I make the final decision" from a contact whose title suggests otherwise. A Director can approve a $5,000 purchase. They probably cannot approve a $50,000 annual platform investment without VP or C-level sign-off. When a Director says "I decide," they might mean "I decide the shortlist and recommend to my boss, who approves." That is influence, not authority. If you treat influence as authority, you will be surprised when the deal stalls in "committee review" after you thought it was a done deal.

Questions that reveal real authority:

"For an investment of this size, walk me through the approval process. Who ultimately signs off?" — This is direct without being confrontational. It asks about the process, not the person's power — which avoids putting them on the defensive.

"Have you purchased software like this before? How did that decision work?" — Historical precedent reveals the actual process better than hypothetical questions. If last time "I had to get VP approval and then procurement reviewed the contract" — you know the real decision path.

"Would it be helpful if I presented directly to [the person they report to] so they can get their questions answered firsthand?" — This accomplishes two things: it multi-threads the deal (engaging the real authority), and it tests whether your contact has the confidence and political capital to introduce you upward. A champion who can arrange this meeting is valuable. A contact who deflects ("let me handle it internally") may not have the influence they claim.

Red flags for authority:

• Title is Manager or below on a deal above $20,000 — they almost certainly need approval from above.
• "I just need to run it by a few people" — how many people? Who are they? What do they care about? If the contact cannot answer these questions, they do not understand their own buying process.
• You have been in the deal for 4+ weeks and still have not spoken to anyone above your initial contac t — you are single-threaded with someone who cannot close.

N — Need: Do They Have a Problem You Solve?

Need seems obvious — if they took the meeting, they must have a need, right? Not necessarily. Many prospects take meetings because they are "researching," "curious," "doing due diligence for next year," or "their boss told them to look into this." None of these are genuine needs. A genuine need has three components: a specific problem, a quantifiable impact, and a reason it matters NOW.

A vague interest is not a need: "We are looking at CRM options" — this is browsing, not buying.

A problem statement is closer: "Our reps spend too much time on admin work" — this is a problem, but it is not yet quantified or urgent.

A qualified need is specific, quantified, and urgent: "Our reps spend 4 hours per day on admin, which costs us $480,000 per year in lost selling time, and we need to fix it before Q3 planning because the board is asking why quota attainment dropped 22% year-over-year." — This is a qualified need. It has a specific problem (4 hours/day on admin), a quantified impact ($480,000/year), and urgency (board pressure before Q3).

Your job during qualification is to help the prospect progress from vague interest to qualified need by asking the SPIN Implication questions that connect the surface problem to deeper consequences (see our SPIN Selling guide).

Questions that qualify need:

"What is the biggest challenge you face with [problem area] today?" — Surface the problem.

"How is that affecting your team's performance? What does it cost you per month?" — Quantify the impact.

"What happens if this does not get solved in the next 90 days?" — Establish urgency.

If the prospect can answer all three with specific, concrete responses — you have a qualified need. If they give vague answers like "it would be nice to improve" or "we are just exploring" — the need is not strong enough to drive a purchase decision in the ne ar term. Move to nurture and re-engage when circumstances change.

T — Timeline: When Will They Buy?

Timeline is the qualifier that separates "we will buy" from "we will buy someday." And "someday" is not a timeline — it is a polite way of saying "we have no urgency and this will keep getting pushed to next quarter indefinitely."

A real timeline has a specific deadline, a consequence for missing it, and a defined process to get from today to decision.

Real timeline: "We need to have a new platform in place by July 1 because our current contract expires and we already decided not to renew. The evaluation needs to be complete by May 15 so procurement can review the contract in June."

Fake timeline: "We are hoping to make a decision by end of quarter." — This sounds specific but it is not. What happens if the decision does not happen by end of quarter? Nothing. There is no deadline, no consequence, and no defined process. It will get pushed to "hopefully next quarter" and then to the quarter after that.

Questions that reveal real vs fake timelines:

"What is driving the timeline? Is there a contract expiration, a budget cycle, a strategic deadline?" — If there is a forcing function — a contract expiring, a budget that disappears at fiscal year-end, a board mandate — the timeline is real. If there is no forcing function, the timeline is aspirational.

"What happens if you do not make a decision by [their stated date]?" — If the answer is "nothing, we just keep going as we are" — there is no urgency. If the answer is "we miss our Q3 targets" or "we have to renew the contract we are trying to escape" — the urgency is real and the timeline is hard.

"Walk me through the steps between now and a signed contract. Who is involved at each step, and how long does each step take?" — This maps the actual buying process. If there are 6 steps and each takes 2 weeks, the real timeline is 12 weeks — regardless of what the prospect hopes. Understanding the process prevents the common trap where the prospec t says "we can decide in 2 weeks" but the actual process takes 8.

BANT vs MEDDIC: When to Use Each

BANT and MEDDIC are not competitors — they are tools for different situations. Using MEDDIC on a $3,000 SMB deal is over-engineering. Using BANT on a $200,000 enterprise deal is under-qualifying.

Use BANT when:

• Deal size is under $25,000
• Sales cycle is under 60 days
• 1-3 decision makers are involved
• The buying process is straightforward
• You need to qualify high volume quickly (SDR qualification for inbound leads)

Use MEDDIC when:

• Deal size is over $50,000
• Sales cycle is 3-12 months
• 6-10+ stakeholders are involved
• The buying process involves procurement, legal, security review
• The cost of losing a single deal (in wasted selling time) exceeds $10,000

For the $25,000-$50,000 middle ground, use BANT for initial qualification and then layer in MEDDIC elements (Champion identification, Decision Process mapping) as the deal progresses. This hybrid approach gives you the speed of BANT at the top of the pipeline and the depth of MEDDIC as deals get larger and more complex.

Both frameworks are enhanced by AI. Clozo's AI analyzes call transcripts to identify BANT signals automatically — budget mentions, authority references, need articulations, and timeline statements. On the Closer plan ($999/user/month), built-in MEDDIC/SPIN/BANT scoring frameworks evaluate each deal against your chosen methodology and flag which elements have been confirmed versus which are still missing. This systematic approach prevents deals from progressing through the pipeline without proper qualification — the most expensive mistake in sales.

Qualify smarter with AI-powered BANT scoring →

Frequently Asked Questions

Stop Reading. Start Closing.

30-day risk-free start. free trial.