BANT Framework: Questions, Template and When It Fails

In Gong's analysis of 11,331 B2B opportunities, deals where budget came up on the first call were won 49% of the time, against 7% for deals where budget never came up. That gap is the case for the BANT framework, the four checks of budget, authority, need and timeline that tell a rep whether a deal deserves the next hour. The catch is that a buyer who cannot answer the budget question on day one is not always a bad lead, and a rigid BANT gate throws some good ones away. This guide covers what each BANT criterion means, the questions Spona's sales team asks on discovery calls, a free BANT scorecard template in Google Sheets, where BANT sits in your sales process and the deals where it fails.

Get thousands of leads in 4 minutes.

Stop stitching tools together.
Start with verified sales data, delivered in minutes.

SCALE SALES NOW

No contracts · No setup · No onboarding

What is BANT in sales?

BANT is a sales qualification framework that checks four things before a rep spends more time on a deal: whether the buyer can pay (budget), who can approve the purchase (authority), whether there is a problem worth solving (need) and when the purchase has to happen (timeline). A lead that passes all four is a BANT-qualified lead and becomes a sales opportunity; a lead that passes none goes back to marketing or out of the pipeline. If qualification itself is new to you, our guide to what lead qualification is covers the basics this framework builds on.

Most teams run the BANT sales methodology on the first discovery call and again before a proposal. Its appeal is speed: four questions a new rep can learn in a day, and a shared language for the handoff between sales development reps (SDRs) and account executives.

What does BANT stand for in sales?

BANT stands for budget, authority, need and timeline:

• Budget: can the buyer fund the purchase, now or with a business case?
• Authority: who approves the spend, and how?
• Need: which problem would the purchase solve, and what does that problem cost today?
• Timeline: when does it have to work, and what event sets that date?

IBM's own forms spell the T as "Timeframe", and many teams say "timing".

Where the BANT sales methodology came from

BANT is credited to IBM. Most guides date it to the 1950s or 1960s, but none of the ones we read cites a document for that. What IBM did publish are partner forms. Its BANT Criteria Form v5.0 from November 2009 asked partners to describe "how the budget has been, or will be identified and approved", to name at least one C-level or line-of-business executive, to describe the customer's business issue and to list the key decision milestones. Two details from those forms are worth copying today: a budget that "will be" approved counted, and "Procurement and Purchasing contacts are not valid executive decision makers."

BANT criteria: budget, authority, need and timeline

Each BANT criterion is a question with an answer you can check. The table shows what to confirm for each one and what counts as a pass.

Budget has strong data behind it and is often asked badly. Gong's pricing data shows the same first-call edge as the budget figure above: deals where price came up on the first call were won 42% of the time, on the second call 32%, on the third call or later 15%, and 5% when price never came up. That is a correlation, not proof that talking about money wins deals, but it suggests that buyers who mean it discuss money early. Budget is more forgiving than price: deals where budget first came up on the third call or later still won 40%. A budget that does not exist yet is a low score, not a fail, as the scorecard below shows.

Authority decides whether a qualified deal can close. Across 9,056 opportunities, Gong found that SMB deals without a decision maker, meaning a VP, C-level executive or managing director, were 80% less likely to close. Yet authority is rarely one person: in Forrester's buyer research, 13 people took part in the average purchase decision, and 89% of purchases involved two or more departments. Confirm who approves and how, not only whether your contact is "the decision maker".

Need carries the other three. A buyer with an expensive problem finds budget and an approver; a buyer without one finds neither. Gong's analysis of 519,000 discovery calls found that the most effective calls uncover three to four business problems, so do not stop at the first one.

Timeline is usually shorter than it looks. In the 6sense 2024 Buyer Experience Report, buyers were nearly 70% through their buying process before they engaged sellers (about 60% in the 2025 report), and they made the first contact more than 80% of the time. By your first call, much of the evaluation is done. Ask for the event behind the date; IBM's sample BANT template asked partners for at least two dates in the customer's decision process.

BANT questions to ask on a discovery call

The same Gong study of 519,000 discovery calls found that asking 11 to 14 questions per call goes with the best results, and a later Gong analysis found that too many questions greatly harm a sale to the C-suite. So the lists below are a menu, not a script: pick two or three per letter. Ask them in call order, which is not the order of the acronym: need first, then timeline and authority, and budget about three quarters of the way into the call. That is where Gong's top reps bring up price, between minutes 38 and 46. Each list opens with the question Spona's own sales team uses.

BANT need questions

Spona asks: "Which missing contacts, poor fit or outdated records are costing your team time?" Generic versions for any product:

• "What made you look at this now?"
• "How do you handle it today, and what does that cost in hours or missed revenue?"
• "What happens if nothing changes this quarter?"
• "Who on your team feels this problem most?"

Listen for a number. "Two people lose a day a week to it" is a need; "we want to be more efficient" is not one yet.

BANT timeline questions

Spona asks: "Which campaign or market launch creates the deadline?"

A quarter with no event behind it ("we'd like it in the first quarter") scores 2 on the scorecard, not 3.

BANT authority questions

Spona asks: "Who approves a data purchase and who will actually use the records?" Then:

• "How did you buy the last tool of this size?"
• "Who else will want a say before this goes ahead?"
• "Would it help if I joined the meeting where you present this internally?"

Skip "Are you the decision maker?" Many contacts say yes to protect their standing, and the answer tells you nothing about how approval actually works.

BANT budget questions

Spona asks: "What do you currently spend on data, tools and manual research each month?" It asks about spend, which most buyers can answer, instead of a budget line, which many cannot. Follow with:

• "Where would the money come from: an existing tool budget or a new line?"
• "What would this need to return for the budget owner to approve it?"
• "Is there a price above which this becomes a hard no?"

When a buyer asks for the price before you know what they need, Spona's reps answer with a question: "The price depends on the targeting and the work needed to qualify each lead. You can see a sample and the cost before committing. What volume and level of verification would be useful?" The reply turns a price question back into a need question.

BANT qualification scorecard (free template)

A scorecard turns four answers into one decision and makes every rep qualify the same way. After the call, score each criterion from 0 to 3; the total is out of 12.

The total sets the status:

• 10 to 12: qualified. Create the opportunity.
• 7 to 9: keep working. Book the next step that fills the weakest letter.
• 0 to 6: nurture or disqualify.

Need works as a gate. A lead that scores 0 or 1 on need is not qualified, whatever its total, because without a costed problem the budget and timeline answers have nothing to stand on.

Copy the free BANT scorecard template in Google Sheets. It scores each lead, sets the status with a formula, holds this scoring guide and the questions from this article, and comes with three worked examples. Open the link, choose "Make a copy" and the copy is yours to edit.

What a BANT-qualified lead looks like

Take an illustrative example. The head of sales at a 40-person marketing agency pays for a contact data tool today (budget 2), approves tools below a set amount herself and this purchase is below it (authority 3), has two SDRs who each lose about 10 hours a week building lead lists (need 3), and starts a new outbound campaign next quarter (timeline 2). The total is 10 and need clears the gate, so this is a BANT-qualified lead, and the next step is a proposal.

Change one answer and the status changes. If the campaign is only planned for "this year" (timeline 1), the total drops to 9, and the right next step is to find the event that sets the date before you write the proposal.

BANT sales process: where it sits in your pipeline

BANT belongs at the handoff from marketing qualified lead (MQL) to sales qualified lead (SQL), and again before the proposal. Spona's own definitions show why. An MQL is an ICP-fit company with an identified relevant role that has asked for a sample, pricing or a demo. An SQL is one where sales confirms a concrete use case, sufficient data fit, a plausible purchasing path and an agreed evaluation or purchase step. Read the SQL definition again and most of it is BANT in other words. In Spona's records, 120 of the 400 MQLs from a two-month cohort (30%) became SQLs within 30 days.

1. Before the call, check fit from data: industry, company size and the contact's role. A call spent confirming that the company fits is a call not spent on budget and timing.
2. On the first call, ask about need and timeline first, authority next and budget late in the call.
3. Within a day, score the four letters in your CRM: four fields from 0 to 3, a total, a status and the date scored.
4. Route by status: an opportunity at 10 to 12 with need at 2 or more, a booked next step at 7 to 9, nurture at 0 to 6.
5. Score again before the proposal and at every stage change, because budgets and dates move.

To see where these steps fall in the stages of a deal, read our guide to the B2B sales pipeline. BANT scores a conversation; lead scoring scores behavior before the conversation, and our lead scoring guide covers that half.

When BANT fails, and when to avoid it

BANT fails when teams use it as a gate instead of a guide. Four cases come up most often.

1. A costly problem with no budget line. A founder told Spona's team there was no data budget, and a rigid screen would have rejected the account. In Spona data, a small sample showed the team would save 10 hours of research a month, which gave the founder a business case to fund. Score that budget 1, not 0, and make the business case the next step.
2. Authority spread across a group. 6sense counts 11 people in the average buying group; Forrester counts 13. "Who is the decision maker?" has no single answer in a group that size. Map who approves, who uses and who can block the deal, which is where MEDDIC's economic buyer and champion help.
3. A buyer who already has a favorite. In the 6sense 2025 Buyer Experience Report, based on more than 4,000 buyers, 94% of buying groups had ranked preferred vendors before first contact, and they bought from that early favorite 77% of the time. A lead can pass all four BANT checks and still be choosing someone else, so ask what they have compared so far and where you stand.
4. An interrogation. Sixteen questions in a row feel like a form, and Gong found that too many questions greatly harm a sale to the C-suite. Ask fewer and listen longer.

Avoid BANT as your main framework in three situations: complex enterprise deals with procurement, security and legal steps, where MEDDIC fits better; self-serve sales, where the buyer never talks to a rep; and inbound leads that arrive with a stated need, where a brief budget and authority check is enough.

Is BANT outdated?

As a gate, yes. As a checklist, no. A HubSpot sales article argued that "BANT isn't good enough anymore" because buyers now arrive better informed, and proposed GPCTBA/C&I instead, a longer framework built around goals, plans and the consequences of doing nothing. The criticism lands on the way BANT is often used: budget first, pass or fail, on the first call. Budget and authority still track win rates in Gong's data, and Spona's own sales team still asks all four BANT questions. Ask them in a different order, score them instead of gating on them, and BANT still works for small and mid-size deals.

BANT vs MEDDIC: which framework fits your deal

BANT asks whether a deal exists; MEDDIC asks how it will be won. MEDDIC (metrics, economic buyer, decision criteria, decision process, identify pain, champion) was created in 1996 at PTC by Dick Dunkel, working with Jack Napoli, according to the MEDDICC training company.

Spona's sales team uses both, split by deal size: "For a small purchase, prioritize need, timing and measurable value, with a brief budget and authority check. Use full MEDDIC for larger annual or complex accounts." For the larger accounts, these are the six questions it adds:

• Metrics: What are your baseline usable contact, bounce, connect and meeting rates?
• Economic buyer: Who owns the financial outcome and can approve a larger rollout?
• Decision criteria: What must a 100-account sample prove to justify buying?
• Decision process: What are the evaluation, security, legal and purchasing steps?
• Identify pain: What does another month of the current workflow cost in hours or missed opportunities?
• Champion: Who will run the test, share results and advocate for adoption internally?

The difference shows in what buyers say. A founder at a company of 5 to 20 people told Spona: "We wanted to test a sample and pay for the data we needed before making a larger commitment." A short BANT check is enough for a purchase like that. A RevOps director at a company of 200 to 1,000 people explained why the team stayed with its existing supplier: "We need documented integrations, security evidence and predictable service levels before changing suppliers." Those are decision criteria and a decision process, which a short BANT check does not reach. Even IBM's sample BANT template asked partners "what decision criteria will be used", so the line between the two frameworks was never sharp.

BANT lead generation: pre-qualify budget, authority and need with Spona

No database can confirm a budget or a deadline. What lead data can do is make sure every first call is with an account that fits, so the call can focus on what only a conversation can answer. Spona's search data shows how teams do that: of 1,000 searches classified by their primary use, seven in ten used a filter combination that stands in for a BANT letter.

The other 25% of searches build local and vertical lists: local businesses by category and city, Shopify stores and IT service providers.

These filters are proxies. They raise the odds that a call is worth having; they do not qualify anyone. Some proxies also cover fewer companies than others: across 10,000 Spona company records, industry is filled for 94% and employee band for 90%, but revenue band for 62% and latest funding round for 8%, because most companies never raise venture money. For timing, intent data platforms that track research activity can spot in-market accounts that hiring and funding signals miss; our guide to buyer intent data explains when that is worth paying for.

Where Spona helps is the step before BANT: a list of accounts that fit and contacts in the right role with verified emails, at a price that suits a test. Qualified leads cost $0.32 to $4 each, there is a free plan with sample leads, and you can check a sample against your scorecard before you buy more. For budget and timing signals, see how to find recently funded startups and which B2B buying signals point to a purchase.

Get thousands of leads in 4 minutes.

Stop stitching tools together.
Start with verified sales data, delivered in minutes.

SCALE SALES NOW

No contracts · No setup · No onboarding

BANT FAQ

Who created the BANT framework?

IBM is credited with it. The oldest dated IBM document we found is a partner form from November 2009 that spells it out as "Budget Authority Need Timeframe"; the 1950s date in many guides comes without a source.

What are the alternatives to BANT?

CHAMP (challenges, authority, money, prioritization) puts the problem first; GPCTBA/C&I adds goals, plans and consequences; MEDDIC and MEDDPICC fit complex enterprise deals; ANUM renames and reorders the same checks, and FAINT adds interest. Our lead qualification checklist compares BANT, CHAMP, MEDDIC and GPCTBA/C&I side by side.

How do you track BANT in a CRM?

Add four fields scored 0 to 3, a total, a status and the date scored, and make them required before a lead becomes an opportunity. Each quarter, compare win rates by BANT score to see which letters predict wins for your team.

Are BANT and MEDDIC forecasting methodologies?

No, both are qualification frameworks. Their answers feed the forecast, though: a deal with an approved budget, a confirmed approver, a costed need and a dated event is one you can commit, while a deal missing two of those is pipeline, not forecast.

Can a lead be BANT qualified without a budget?

Yes, but only if the buyer will build a business case and need, authority and timeline each score 3, for a total of 10. Score budget 1, make the business case the next step and score again afterward. In Spona's founder example, a small sample that showed 10 hours of research saved each month gave the founder a business case to fund.