We brought Kris to SaaStr AI 2026. Here's a glimpse.Read more →Exclusive Founder Offer is Live Now!Read more →Kris@Work raises $3M seed funding led by InfoEdge Ventures.Read more →Exclusive Founder Offer is Live Now!Read more →InfoEdge Ventures-Backed Kris@Work Strengthens Founding Team.Read more →We brought Kris to SaaStr AI 2026. Here's a glimpse.Read more →Exclusive Founder Offer is Live Now!Read more →Kris@Work raises $3M seed funding led by InfoEdge Ventures.Read more →Exclusive Founder Offer is Live Now!Read more →InfoEdge Ventures-Backed Kris@Work Strengthens Founding Team.Read more →

How to Qualify Leads With BANT: The 4-Step Framework (2026)

15 August 2026

Blog_cover_image

BANT qualifies a lead against 4 questions: does the prospect have Budget, Authority, Need, and Timing. BANT works by trading depth for speed: one quick pass across 4 questions. That speed is why it has lasted for decades, and also why it strains on bigger, multi-stakeholder deals. Knowing how to qualify leads with BANT well is less about the 4 letters than about reading which one is missing and deciding what to do next.

Qualification is how a sales team decides which deals get its hours, and getting that call wrong is expensive. Landbase found in 2024 that 67% of lost B2B deals trace back to poor lead qualification rather than product or price. BANT is the oldest answer to that problem, and for a large share of deals it is still the fastest.

TL;DR: How to qualify a lead with BANT

  1. On the first call, work 4 questions: Budget, Authority, Need, Timing. Let the conversation set the order, not the acronym.
  2. Grade each answer as met, soft, or missing, based on evidence, not agreement.
  3. Score the lead: 3 of 4 clears the bar, 2 holds for nurture, 1 or none drops down the list.
  4. Act on the missing letter. No Timing means nurture until a trigger appears. No Budget means build the business case before you push.
  5. As deals grow more complex, step up from BANT to MEDDIC, and to MEDDPICC for enterprise deals ($100K and up).

What BANT Stands For

BANT stands for Budget, Authority, Need, and Timing. Each is a question you answer about a lead before you invest selling time in it.

Budget Can the prospect fund a solution?
Authority Can your contact approve the purchase, or influence who does?
Need Is there a problem worth solving, and does your product solve it?
Timing Is there a reason to act now rather than in a year?

IBM created BANT in the 1950s to qualify mainframe buyers quickly, when a deal often came down to 1 decision-maker and 1 budget line. That simplicity is still the framework's strength. It is also the root of its limits, which we come to later.

__wf_reserved_inherit

How to Qualify Leads With BANT: Run the 4 Questions

Knowing what the letters stand for is not the same as running them on a live call. Each question has a good version and a lazy version, and the lazy version is why BANT gets a bad name. Here is how to work each one.

Budget

Budget is not only whether the money exists. It is whether money has been set aside for this kind of problem, and whether your contact has any say over it. Asking "what is your budget" in the first 5 minutes rarely works, because most buyers have not set a number yet. They are still defining the problem. You learn more by asking what they already spend on adjacent tools, and how budget decisions get made inside the company.

A useful set of questions:

  • Has a budget been set aside for this, or would it need to be requested?
  • What do you spend on tools or approaches that address this today?
  • Who signs off once a solution is chosen?

If there is no allocated budget, that is not always a reason to disqualify. Early-stage deals often have no line item yet, so a missing budget usually means you move to Need first and let a strong enough problem create it.

Authority

Authority asks whether your contact can approve the deal or shape who does. Asking someone directly if they are the decision-maker almost never works, because most people say yes even when the answer is more complicated. A better approach is to ask who else tends to get involved, and how the company bought something similar last time.

Questions that surface the fuller picture:

  • Who else would need to weigh in before this moves forward?
  • When your team last bought something like this, who was involved?
  • If we reach a proposal, who signs it?

Treat the answer as a map, not a name. Most B2B purchases now involve several people, so the goal is to learn the shape of the group rather than to confirm a single title.

Need

Need is the question the other 3 depend on, so it earns the most care. A prospect who says a problem sounds interesting has not shown need. A prospect who can tell you, without prompting, what the problem costs them has shown it. Push for that detail.

  • What does this problem cost you today, in time, money, or missed revenue?
  • What have you tried already, and why did it not hold?
  • Who else in the business feels it?

A clearly defined, costed Need does more than qualify the lead. It pulls budget forward, raises urgency, and gives your champion a reason to bring other people in. Weak Need is usually why the other letters stay weak too.

Timing

Timing asks whether there is a reason to act now. It is the easiest letter to fumble, because "when are you looking to buy" invites a vague answer. Anchor it to an event instead.

  • What is driving the timeline: a renewal, a new hire, a deadline?
  • What happens if nothing changes by the end of the quarter?

A prospect with a genuine trigger, a renewal date, a new leader, a compliance deadline, will name it without much prompting. A prospect who says "sometime this year" is telling you the timing question is still open, which is a reason to nurture rather than to push.

How to Score BANT and Decide

Running the 4 questions gives you answers. Scoring turns those answers into a decision. Most teams grade each of the 4 criteria and count how many the lead meets. 3 of 4 usually clears the bar, 2 holds for nurture, and 1 or none drops down the list.

The count is less useful than the letter that is missing. A lead with Budget, Authority, and Need but no Timing is not unqualified; it is a deal waiting for a trigger, so you nurture it until one appears. A lead with Need, Timing, and Authority but no Budget is a business case you have not built yet. Score to find the gap, then work the gap. The moment scoring becomes a tidy number for a dashboard, reps start gaming the boxes instead of reading the deal.

In practice, weight Need and Timing highest early on. A deal with a sharp, costed Need and a dated trigger tends to find budget and pull in the right people on its own; a deal with budget but no urgency tends to sit. The missing letter tells you what to fix. The strong letters tell you whether it is worth fixing.

Where BANT Falls Short

BANT was built for a simpler sale, and it shows its age in 2 places.

The first is Authority. BANT assumes 1 buyer, and modern B2B does not have 1 buyer. Gartner's 2024 B2B buying research puts the typical buying group for a complex purchase at 6 to 10 people, each able to slow or block the deal. Treating Authority as a single yes-or-no question misses most of that room.

The second is its point of view. BANT is rightly criticised as seller-centric: its 4 questions measure whether a lead is worth your time, not whether you are the right answer to the buyer's problem. For a fast, transactional deal that trade-off is fine. For a long, considered one, it leaves too much unasked. That gap is what heavier frameworks were built to close.

BANT vs MEDDIC vs MEDDPICC: When to Use Which

BANT is a triage tool. It sorts a serious buyer from a curious one quickly, which is what you want on a first call and across a high volume of leads. Once a deal grows in size and complexity, you need a framework that maps the buying group and the buying process, not only the 4 basics.

MEDDIC is the common step up. Developed at PTC in the 1990s, it adds Metrics, Economic Buyer, Decision Criteria, Decision Process, and Champion on top of the pain BANT already probes. MEDDPICC extends MEDDIC with 2 more: Paper Process, the administrative, legal, security, and procurement steps needed to get a contract signed, and Competition, the rival vendors and status-quo bias you are positioned against. MEDDPICC is the framework Kris uses internally, because it fits the enterprise deals where paperwork and a wide buying group decide the outcome. CHAMP, a lighter reorder of BANT that leads with the buyer's challenges, is a fourth option for discovery-led selling.

The practical question is not which framework is best, but which fits the deal in front of you.

Framework Best for Deal size Sales cycle Stakeholders
BANT Fast triage, transactional deals Small, simple Short 1-3
MEDDIC Moderate complexity Under $100K Shorter Several
MEDDPICC Enterprise, legal and procurement heavy $100K+ Long Many (6-10+)

Most teams that grow past simple SMB deals end up running a hybrid: BANT to triage the first call, then MEDDIC or MEDDPICC once a deal is worth deeper qualification. Running a single framework for every deal, whatever its size, is the more common mistake.

Worked Example: Running BANT on a Borderline Deal

The easy calls do not need a framework. A prospect who answers every question well is an obvious yes, and one who dodges all 4 is an obvious no. BANT earns its keep on the deals in between, where the answers are mixed and the rep has to decide. Here is one of those.

Take a hypothetical 90-person software company that books a demo for a $9,000-a-year customer-onboarding tool. On the discovery call, the answers come back uneven.

Need is strong. The VP of Customer Success explains that onboarding runs on a shared spreadsheet, 2 enterprise customers churned last quarter citing a slow start, and she can put a rough revenue figure on it. That is a costed problem, not a vague one. Clear pass.

Timing is there but soft. She wants something in place "this quarter if it is smooth," driven by a board review on retention, but there is no hard deadline. Call it half a pass: there is a trigger, but not urgency yet.

Authority is the wrinkle. She owns the problem and controls a tools budget, but a $9,000 tool that touches customer data will go through a security review, and she admits IT "will have opinions." So she is the economic buyer, but not the only gate. Half a pass, with a named risk.

Budget is plausible but unconfirmed. She has bought in this range before and has not ringfenced money for this yet. Lean pass.

Add it up and this is a 3-of-4 deal with 2 soft edges, Timing and Authority. The lazy read marks it qualified and forecasts it for the quarter. The honest read is that it is qualified to advance, not to commit. The next moves follow straight from the 2 soft letters: pull the security reviewer into the next call before it becomes a late-stage surprise, and turn the board review into a firm deadline by asking what she needs to show, and when. Do that, and a soft 3-of-4 hardens into a committed deal. Skip it, and the same deal stalls in security review in week 6 and slips the quarter.

That is the point of scoring the letters rather than the deal as a whole. The score did not tell the rep to walk away or to celebrate. It told them which 2 things to fix next.

A BANT Qualification Script and Checklist

If you skipped straight here, this is BANT you can use on your next call. 2 things make a script work, and most templates give you only the first: the question to ask, and the answer to listen for. The second is where qualification is decided. The script is general-purpose, so adapt it to your product and voice, and the contractions are left in because it is meant to be spoken.

Open (set context, not only rapport):

"Before we get into the product, I want to understand where you're at, so I don't waste your time on things that don't apply."

Then work the 4 questions, and grade the answer, not the fact that they gave one.

Need. Ask: "Walk me through what's not working today. What made you take this call?" A strong answer is a costed, named problem ("we lost 2 renewals last quarter to slow onboarding"). A weak answer is a feeling ("things are a bit messy"). If you cannot write down what the problem costs, Need is not confirmed.

Budget. Ask: "Have you actively been trying to solve this, or is it more exploratory right now?" A strong answer names prior spend on the problem or an owner of the money. A weak answer is "we would have to see." No number this early is fine; no owner is the risk.

Authority. Ask: "If this makes sense, who else would need to be involved?" A strong answer gives names and roles, including anyone who can block ("IT will need to sign off"). A weak answer is "just me" on a deal that clearly touches other teams, which usually means a gate you have not found yet.

Timing. Ask: "Is something driving the timing now, rather than 6 months ago or 6 months from now?" A strong answer is a dated event: a renewal, a board review, a compliance deadline. A weak answer is "this year sometime," which is a nurture signal, not a close signal.

Run the checklist after the call, not during it:

☐ Can I write the problem down with a cost attached? (Need)

☐ Do I know who owns the money, even if the amount is unset? (Budget)

☐ Have I named everyone who can say no, not only who says yes? (Authority)

☐ Is there a dated event driving this, not a vague quarter? (Timing)

☐ Would I stake my own forecast on this closing this quarter?

The last line is the honest test. 3 clear yeses and a soft edge is a deal to advance and de-risk. 1 clear yes is a deal to nurture, whatever the call felt like.

Automating BANT Qualification

__wf_reserved_inherit

Everything above is straightforward to understand and slow to do. The signals behind Budget, Authority, Need, and Timing usually exist before a rep ever dials, scattered across a company's website, news, hiring pages, and past conversations. The work is not the judgement. It is the hour of assembly per account, repeated down a list of hundreds.

That is the part worth automating. Kris Capture reads each account's own signals and messages and fills the BANT breakdown in advance, with the evidence and a short reason attached to each letter. Prospects carry a grade from A+ to F; once a lead becomes an active deal, it carries a score and the fuller MEDDPICC view. The rep opens the account already knowing where it is strong and where it is thin, works a prioritised list instead of a flat one, and sees those scores alongside any lead scoring software already in place.

None of that replaces the call. A funding round hints at Budget and a new VP hints at Timing, but neither confirms anything, so the rep still asks the questions and reads the answers. Automation removes the research, not the judgement.

Common Mistakes When Running BANT

Even a simple sales qualification framework gets misused in predictable ways.

Running the questions in a fixed order is the first. BANT looks like a checklist, so reps march through it top to bottom, and the call starts to feel like an interrogation. Live conversations move differently, and a prospect might reveal Need in the first minute and Budget 20 minutes later.

Treating a "yes" as qualification is the second. A prospect agreeing that a problem exists is not the same as one who has decided to fix it. Agreement is not evidence.

Disqualifying too early on Budget is the third. No confirmed budget at the start of a call is normal, not fatal. It usually means Need has not been built yet.

Skipping Authority because the contact seems senior is the fourth. A senior title is not the same as signing power, and in larger companies procurement, security, or finance can still block a deal a VP has waved through.

To Sum It Up

BANT endures because it is fast, and it works when the deal is simple. 4 questions, honestly answered, tell you quickly whether a lead deserves your time. Its weakness is the flip side of its strength: the simplicity that makes it quick also makes it thin once a deal involves serious money and a room full of stakeholders. The teams that get the most from it treat BANT as the first filter, not the whole system, and move up to MEDDIC or MEDDPICC when the deal earns it. Qualification is not about running an acronym. It is about knowing, before you spend a quarter chasing a deal, whether the reason to chase it is there.

If you would rather not assemble BANT by hand for every account, Kris Capture fills the breakdown from each account's own signals before you dial. You can start free, no credit card, up and running in 15 minutes.

FAQ

What does BANT stand for in sales?

BANT stands for Budget, Authority, Need, and Timing. It is a 4-question sales qualification framework used to decide whether a lead is worth a rep's time. IBM introduced BANT qualification in the 1950s for early technology sales.

How do you qualify a lead with BANT?

Ask whether the prospect has a budget, whether your contact holds or influences authority, whether there is a costed need your product solves, and whether there is a reason to act now. Grade each of the 4, and treat a lead that meets at least 3 as qualified.

Is BANT still relevant in 2026?

For fast, transactional, few-stakeholder deals, yes. For complex enterprise deals it tends to under-qualify, because it assumes a single buyer. Most teams selling into committees use BANT to triage and then layer MEDDIC or MEDDPICC on top.

What is the difference between BANT and MEDDIC?

BANT has 4 criteria and is built for speed. MEDDIC has 6, Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion, and is built for complexity. MEDDPICC extends MEDDIC with Paper Process and Competition for enterprise deals.

How do you score a BANT lead?

Grade each of the 4 criteria and count how many the lead meets. Most teams treat 3 of 4 as qualified, hold a 2 for nurture, and drop a 1. The letter that is missing usually matters more than the total, since it tells you what to work on next.

Can AI qualify leads automatically?

AI can assemble the inputs to BANT, budget signals, the buying group, recent triggers, before a rep starts a conversation, and can grade a lead with the evidence attached. It cannot replace the conversation itself. Confirming a costed problem or genuine authority still depends on a person asking and listening.

Or Share via