BANT Qualification

BANT qualifies prospects on four dimensions: Budget, Authority, Need, and Timeline. It's the simplest and most widely used qualification framework in B2B sales. A prospect must demonstrate enough signal across all four dimensions to be considered qualified. BANT works best for transactional and mid-market sales where the buying process is relatively straightforward.

The principle: BANT is a framework for structured thinking, not a checklist to interrogate the prospect with. Never ask "Do you have budget?" "Are you the decision-maker?" "What's your timeline?" in sequence. That's an interrogation, not a discovery call. Uncover BANT through natural conversation.

The 4 Dimensions

B - Budget

Does the prospect have (or can they get) the money to buy?

How to uncover budget naturally:

Budget rules:

• Budget is the least important BANT dimension for initial qualification. Need and authority matter more. If the need is real and the authority is there, budget can often be found or created
• "No budget" doesn't always mean "no money." It often means "I haven't justified this expense yet." Help them build the business case
• Give a price range early. Don't wait until the proposal to share pricing. "Most teams at your stage invest $30-50K/year in this area." This surfaces budget objections early when you can still address them
• Budget objections at the end of the process are discovery failures. If you discover in the proposal stage that they can't afford you, you failed to explore budget during discovery

A - Authority

Is the prospect the decision-maker, or can they influence the decision?

How to uncover authority naturally:

Authority rules:

• The person on the call is rarely the sole decision-maker for deals > $20K. Assume a buying committee exists. Map it
• A champion with no authority is still valuable. They sell internally. But you need to identify and eventually engage the economic buyer
• Authority is about the decision process, not the person's title. A Director at a 50-person company may have full authority. A VP at a 5,000-person company may need 3 approvals. Don't assume from title alone
• Ask "who else would be involved" on every discovery call. This is the authority question that doesn't feel like an authority question. It maps the buying committee naturally

N - Need

Does the prospect have a real, acknowledged problem that your product solves?

How to uncover need:

Need rules:

• Need is the most important BANT dimension. Without a real, acknowledged need, nothing else matters. Budget, authority, and timeline are irrelevant if there's no problem to solve
• Latent need vs active need. A prospect with a latent need ("we could probably do this better") requires more selling effort than one with an active need ("this is broken and it's costing us"). Qualify the urgency, not just the existence of the need
• Quantify the pain. "Our outbound isn't working" is a need. "We're spending $50K/month on SDR salaries and generating $30K in pipeline" is a quantified need that builds its own business case
• If the prospect can't articulate the problem, they won't buy. Not because the problem doesn't exist, but because they can't sell the purchase internally. Help them articulate it

T - Timeline

When does the prospect need to solve this problem?

How to uncover timeline:

Timeline rules:

• A timeline tied to an external event is strong. "Our Outreach contract renews in April" or "We're doubling the SDR team in Q3" are real timelines. "Sometime soon" is not
• No timeline = no deal velocity. Without urgency, deals stall indefinitely. If there's no natural timeline, create one: "Most teams that wait past [event] end up paying 3x more to fix it because [reason]"
• Implied timeline from other signals. A company that just raised funding has an implied 90-day timeline (board expects action). A company hiring SDRs has a 60-day timeline (SDRs start without tools if you miss it). Infer the timeline even if they don't state it
• Early-stage timeline ("next year") = nurture, not pursue. A prospect evaluating for next year's budget is not an opportunity. They're a nurture contact. Don't waste sales time on "next year" unless the deal is > $100K and the evaluation starts now

BANT Scoring

The qualification matrix

Score each dimension 0-3. Total ≥ 8 to qualify as an SQL.

Scoring rules:

• Need ≥ 2 is required. A prospect scoring 0 or 1 on Need should not advance regardless of other scores. Need is the gate
• Total ≥ 8 for SQL. Balanced scores across all four dimensions
• Authority 0 = find the right person, don't disqualify the account. The account may be a great fit. The person you're talking to just isn't the buyer. Find the buyer before disqualifying
• A 3-3-3-0 (no timeline) is a nurture, not an SQL. Perfect fit, real need, budget confirmed, but no urgency. This deal will stall in pipeline. Nurture until a timeline emerges

BANT on Discovery Calls

How to cover BANT in a 30-minute discovery call

Discovery call rules

• Start with Need, not Budget. Leading with budget feels transactional. Leading with their problem feels consultative. Need → Authority → Timeline → Budget is the natural conversation order
• BANT should feel like a conversation, not a form. The prospect should not feel like they're being interrogated on 4 dimensions. The BANT questions are woven into a natural dialogue
• Listen more than you talk. The prospect should speak 60-70% of the time on a discovery call. If you're talking 70%, you're pitching, not discovering
• Take notes on BANT during the call. After the call, score each dimension 0-3 and log in CRM. This score determines whether the prospect becomes an SQL

BANT Limitations

When BANT breaks down

When to upgrade from BANT

BANT is the right framework for:

• Teams with < 10 reps and < $50K ACV
• SDR-to-AE handoff qualification (SDR qualifies on BANT, AE goes deeper)
• Initial qualification before switching to a more detailed framework for deal progression

CRM Implementation

BANT fields in CRM

CRM automation

When bant_qualified = TRUE:
  → Set lifecycle stage to SQL
  → Notify AE for handoff
  → Create task: "Review BANT-qualified lead [Name]"
  → Set SQL Date to today

When bant_need = 0 AND all other dimensions scored:
  → Set lead status to "Disqualified - No Need"
  → Move to nurture sequence

Measurement

Calibration

• If BANT-qualified-to-opp is below 50%: The threshold is too low. Raise the minimum score or add a minimum per dimension
• If most disqualifications are on Budget: Your pricing may be misaligned with your ICP, or you're targeting companies that are too small
• If most disqualifications are on Need: Your ICP definition is too broad, or the SDR isn't digging deep enough on discovery. Coach discovery technique
• If most disqualifications are on Authority: You're talking to the wrong persona. Adjust targeting to reach higher-seniority contacts
• If most disqualifications are on Timeline: Your outbound isn't signal-based. Without a trigger, there's no urgency. Add signal requirements to your list building

Anti-Pattern Check

• Asking "Do you have budget?" in the first 5 minutes. Budget is the last dimension to explore, not the first. Lead with Need. Build the case before discussing money
• Treating BANT as a checklist. "Do you have budget? Yes. Are you the decision-maker? Yes. Do you need this? Yes. When do you want it? Q3. Great, you're qualified!" This is an interrogation, not discovery. Weave BANT questions into natural conversation
• Disqualifying on Budget alone. "No budget" often means "I haven't justified this yet." If Need and Authority are strong, help them build the business case. Budget can be created
• Using BANT for $200K enterprise deals. BANT is too simple for complex, multi-stakeholder deals. Upgrade to MEDDPICC when deals regularly exceed $50K or involve 4+ stakeholders
• Scoring BANT after the call from memory. Score during or immediately after the call while context is fresh. Scoring the next day introduces recency bias and memory gaps
• Need scored 1 but the deal advances. A prospect who can't articulate a specific problem will not buy. Need ≥ 2 is a hard gate. Don't advance deals with weak or no need
• No BANT fields in CRM. BANT scores live in the rep's head, not in the system. Without CRM fields, there's no data to calibrate the model, no way to report on qualification quality, and no accountability for handoff standards
• Same BANT threshold for all deal sizes. A $5K deal with BANT 6/12 might be worth pursuing. A $100K deal with BANT 6/12 is a pipe dream. Consider adjusting thresholds by deal size or using MEDDPICC for larger deals