BANT: Budget, Authority, Need, Timeline
BANT is a sales lead-qualification framework built around four criteria: does the prospect have Budget set aside, does the person you are talking to have Authority to approve a purchase, is there a genuine Need your product addresses, and is there a real Timeline driving when they intend to act. It is widely credited to IBM and remains one of the oldest and most recognized sales qualification checklists.
Where BANT came from and what it is for.
BANT dates back to IBM's internal sales practices, developed for a world of large, single-buyer enterprise hardware deals with a clear budget line and one approving executive. It became one of the most widely taught lead-qualification frameworks in B2B sales, largely because it is short, memorable, and easy to apply in a five-minute conversation.
Its purpose is triage, not deal strategy: BANT helps a rep or marketing team quickly decide whether a lead is worth investing further time in, before a full sales process begins. It is typically used at the top of the funnel, during a discovery call, an inbound lead's first qualifying conversation, or a sales development rep's outbound follow-up.
What each letter actually checks for.
| Letter | What it checks | Example question |
|---|---|---|
| Budget | Has money been allocated, or could it be, for solving this problem | "Has funding been set aside for this, or would it be a new request?" |
| Authority | Can this person approve the purchase, or influence who does | "Besides yourself, who else is typically part of a decision like this?" |
| Need | Is there a real, acknowledged problem the product solves | "What happens if this goes unaddressed for another two quarters?" |
| Timeline | Is there a concrete event or deadline driving urgency to act | "Is there anything specific driving when you'd need this in place?" |
Where BANT runs into trouble.
BANT was built for a simpler sale than most modern B2B software deals involve. Two assumptions in particular do not hold as often as they used to: that there is a single person with Authority, and that a Budget line already exists before a conversation starts. Contemporary enterprise purchases frequently involve several stakeholders and a budget that gets created in response to a compelling case, not before one.
Used rigidly, BANT can also cause reps to ask overly blunt questions ("what's your budget?") that put a prospect on the defensive, or to disqualify a deal too early because one box is not checked yet, even when the prospect is genuinely a good fit. Most modern qualification frameworks, including MEDDIC, were built partly as a response to these gaps.
Common questions about BANT.
What does BANT stand for?
BANT stands for Budget, Authority, Need, and Timeline. It is a sales lead-qualification framework used to judge whether a prospect is worth pursuing: do they have money set aside, is the person you are talking to able to approve a purchase, do they have a real problem your product solves, and is there a concrete window in which they intend to buy.
Who created the BANT framework?
BANT is widely credited to IBM, which used it internally to qualify sales leads starting in the mid-20th century. It predates modern SaaS sales and was designed for a world of long enterprise hardware sales cycles with a single clear budget owner.
Is BANT still used today?
Yes, but often in a modified or partial form. Many teams still use Budget and Timeline as quick filters early in a deal, while relying on newer frameworks like MEDDIC for complex, multi-stakeholder B2B sales where a single Authority is rare and Need requires more nuance than a yes/no check.
What is the main criticism of BANT?
BANT assumes a single decision-maker and a pre-existing, self-identified budget, which fits fewer deals than it used to. Modern B2B purchases often involve multiple stakeholders, no fixed budget line until late in the process, and needs the buyer has not yet fully articulated. Rigid, checklist-style use of BANT can cause reps to disqualify a viable deal too early or ask overly blunt questions that put a prospect on the defensive.
What are good BANT qualifying questions?
Budget: "Has funding been allocated for solving this, or would this be a new line item?" Authority: "Besides yourself, who else would be involved in a final decision?" Need: "What happens if this problem goes unsolved for another two quarters?" Timeline: "Is there an event or deadline driving when you need this in place?" Open, indirect phrasing tends to get more honest answers than a direct "what is your budget."
How is BANT different from MEDDIC?
BANT is a four-point lead-qualification checklist, typically used early and quickly. MEDDIC is a deeper, six-part qualification and deal-management framework aimed at complex enterprise sales with multiple stakeholders, adding elements like a named Champion inside the account and an explicit Decision Process, not just a Budget and an Authority.
Running a BANT-style discovery call live.
Qualification frameworks are easy to know and hard to execute mid-conversation, especially the follow-up question that turns a vague answer into a real one. CerebroEcho listens to your Zoom, Google Meet, or Microsoft Teams call in the browser and can surface a next-question suggestion in typically around 1.5 seconds when a prospect's answer needs a sharper follow-up, only you see it.
Nothing to install. Works on Chrome or Edge, desktop only. Starts free; audio coaching from $14.99/month.
More sales & interview glossary terms.
Qualify smarter, live on the call.
CerebroEcho whispers a sharper follow-up question the moment a discovery answer needs one. No install, no card required to start.