A lead filled out a form, opens your emails, spends time on your site — none of that means they’re ready for sales. Our lead nurturing article explained that the MQL-to-SQL transition is a matter of stage; BANT is the oldest and most widely used framework for deciding exactly which concrete questions drive that transition. IBM developed this four-letter acronym for its sales teams in the 1960s, and half a century later it still forms the backbone of B2B lead qualification.
B — Budget
Does the prospect have, or can they secure, a budget for this purchase? This isn’t about asking “how much can you spend” directly — it’s about understanding whether a budget-approval mechanism is actually moving inside their purchase process. If budget approval in an enterprise software sale is tied to an annual planning cycle, that fact also tells the sales team how patient it needs to be.
A — Authority
Is the person you’re talking to in a position to make the purchase decision, or at least influence it? In B2B sales, the decision usually belongs to a committee, not one person — which is why modern BANT practice expands “authority” from finding a single decision-maker toward mapping every influencer in the decision process. Talking only to the IT department and never accounting for finance sign-off makes the deal look further along than it is, right up until it stalls at the last step.
N — Need
Does the prospect have a concrete problem that needs solving, and does it actually line up with what you’re offering? This criterion separates someone filling out a form out of curiosity from someone with a real problem. How clearly the need is defined also determines where the sales conversation should start — a lead who can describe their problem precisely is ready for a solution comparison, not a product intro.
T — Timeframe
When is the purchase decision expected to happen? “We’re just researching” and “we’ll pick a vendor within three months” call for different prioritization. A lead with an undefined timeframe may not be worth the sales team’s limited time right away even if it meets the other three criteria — it goes back into nurturing instead.
The Limits of BANT
BANT was designed for the direct-sales model of the 1960s — an era when the salesperson called and talked, and the buyer was passive. Today, most B2B buyers finish the bulk of their own research long before talking to a sales team, which means criteria like “budget” and “timeframe” need to be inferred well before that conversation, through content consumption and behavioral signals. That critique gave rise to alternative, needs-first frameworks like GPCT (Goals, Plans, Challenges, Timeline). BANT’s advantage is still its simplicity and how easily it establishes a shared language between sales and marketing.
How BANT Gets Applied in Marketing Automation
It’s more accurate to think of BANT not as four questions asked in a call, but as the logic behind a lead scoring system. In practice, it looks like this:
- Budget signal: Adding a company-size or annual-revenue field to the form, or scoring a pricing-page visit.
- Authority signal: The job-title field — assigning higher points to titles like “Director,” “Founder,” or “Procurement Lead.”
- Need signal: Which content got downloaded or which product page got visited; a “pricing” or “request a demo” page is a much stronger need signal than a generic blog post.
- Timeframe signal: A “when are you planning to get started?” form field, or a high visit frequency in a short window.
Once these four signals combine and cross a threshold, the lead automatically moves from MQL to SQL and gets handed off to sales. As covered in our CRM vs. marketing automation article, an undefined handoff point is the single most common source of friction between the two teams — BANT reduces that friction by tying the definition to concrete criteria.
Summary
BANT tests whether a lead is actually ready for sales with four questions: do they have budget, can they influence the decision (Authority), do they have a concrete problem (Need), and when will they decide (Timeframe). Designed half a century ago for direct sales calls, it now forms the logic behind lead-scoring rules in marketing automation and turns the “is this lead ready?” debate between sales and marketing into a matter of concrete criteria.