BANT in sales: what it means and how to run it on a live deal

• Budget. Whether the buyer can pay for this, and how that money gets approved.
• Authority. Who can say yes, and whether they’re involved in the deal.
• Need. The business problem your product solves for this buyer.
• Timeline. When they need it solved, and the decision dates on the way there.

IBM’s forms spell the fourth letter Timeframe. It’s the same letter. This page says Timeline.

BANT is widely credited to IBM. Vendors date it to the 1950s or the 1960s, but we found no IBM document from either decade. The oldest IBM BANT document we found is a reseller template dated November 2008. It is the same kind of partner form that resellers filled in to register a deal with IBM, as are the two we quote here: a June 2012 form for IBM’s Value Advantage Plus program for government sales, and a 2013 BANT criteria template (version 3.3) for its Software Value Incentive program.

Neither form treats BANT as a first-call script. The 2012 form says: “Register only validated opportunities, Sales Stage 4 or higher. A validated opportunity is one where you have made at least one sales call and know the customer’s Budget, Authority, Need and Timeframe.” The 2013 form is stricter. “All fields are required,” it says, and deal records missing a description of any of the four “will be rejected as incomplete.”

No partial credit, either. Gong’s BANT guide says a prospect “is considered viable if they meet at least three of the four criteria.” That rule is Gong’s, not IBM’s, and we wouldn’t use it. If a letter is missing, your rep’s next job is to find that answer out. Until they do, the deal isn’t qualified.

Budget

The 2013 form asks you to “describe how / if / when budget has been, or will be, identified and approved for this project.” It allows for budget that doesn’t exist yet.

• “How does a purchase like this get approved here, and when?”
• “Is this in a budget already, or would the money need to be found?”

Authority

The 2013 form says to “include at least one Customer C-level or Line-of-Business Executive on the Contacts tab,” and adds: “Procurement and Purchasing contacts are not valid executive decision makers.” The 2012 form also counts line-of-business contacts who “have authority to make strategy/technology recommendations for their firms.” So IBM counted people who recommend, and not only people who sign.

Today, Authority means a named executive on the deal record. Your champion saying the boss is on board doesn’t count. Procurement runs the buying process, and IBM was right to leave it off the list.

• “Who besides you has to say yes before this goes ahead?”
• “Which executive owns the problem this fixes, and have they seen it yet?”

Need

The 2013 form wants the proposed product and a description of “the customer’s business problem and the key benefits of the proposed solution.” On a deal today, Need is the problem in the buyer’s words and what changes for them once it’s fixed, written down well enough that someone else on your team could repeat it. Interest in a feature is a start. It isn’t a need yet.

• “What happens if this isn’t fixed this year?”
• “How are you handling it today, and what does that cost you?”

Timeline

The 2013 form gets most specific here. It asks, “What is the timeline of key decision milestones, and what decision criteria will be used?” It wants at least two dates, plus a forecast close date at least 15 days after the deal is submitted.

A close date on its own is a guess. Two dated milestones before it, say a security review on the 12th and a budget sign-off on the 28th, give your rep something to check every week.

• “What has to happen on your side between now and a signed contract, and by when?”
• “Is there a date this has to be live by? What’s driving it?”

Yes, as long as it’s the right budget question.

The case against is nine years old and still fair. Forrester wrote in a 2017 post on BANT, about offerings that solve a known problem more effectively, that “It’s unreasonable to expect detailed budget criteria to be identified early in the process or by marketing or lead development.” A buyer who hasn’t scoped the project has no number to give.

The case for comes from Gong. In Gong’s data on 11,331 opportunities with three or more calls, win rates were 7% when budget never came up and 49% when it came up on the first call. That’s one vendor’s data, and a correlation. Deals that died after a single call aren’t in it, and a buyer who’ll talk money on call one may already be further along.

Both are right, and IBM’s wording settles it. Raise it early, but ask how, if, and when it gets approved, instead of “What’s your budget?” A buyer with no number can still tell you who approves spend, whether this is in this year’s plan, and when the next budget cycle starts. That’s enough to keep working the deal. The number can wait until there’s a proposal to price.

BANT fits when one or two people make the decision: an SDR qualifying a meeting before handing it to an AE, a short sales cycle, or a buyer who owns the budget and signs the contract. In those deals, four answers cover everyone who matters.

It breaks on Authority first. In Gartner’s survey of 632 B2B buyers, fielded in 2024, buying groups ranged from five to 16 people across as many as four functions. One letter can’t hold that. A security reviewer, a finance approver, and an executive who never joins a call each have a say, and BANT has nowhere to track them.

For a B2B SaaS team selling to buying groups, our take is to run BANT to decide whether a deal is worth working, then switch to MEDDPICC once the answer is yes. MEDDPICC splits Authority into the economic buyer, the champion, the decision process, and the paper process.

ANUM and CHAMP reorder the same four ideas. ANUM, from a 2013 InsideSales.com post, puts Authority first. CHAMP (Challenges, Authority, Money, Prioritization) leads with the buyer’s problem. Whichever order your team uses, qualifying sits right after prospecting, as stage two of the nine in our B2B sales process guide.

The part of IBM’s form most teams drop is the dates, and the dates are what keep BANT current. A slipped milestone is often the first sign the other letters have moved: a new VP joins, the budget slides into next quarter, or procurement shows up with its own process.

Your best rep watches those dates in their head on about 5 deals. The other 15 get improvised. Arrows runs it on every deal, from a playbook it builds with your team at kickoff. The playbook is written in plain language as a path to close: the milestones and their targets, when each agent action runs, and the rules. If your team qualifies on BANT, that bar can be built into it. Each deal’s Overview says where it is on the path to close, what happens next, and who decides. The Post-call follow-up drafts the recap your rep sends that day, with the next milestone and a date for it. And when that new VP turns up, the Multi-thread action maps who’s on the deal, so your rep can reach them early.

Changes to the CRM your team already uses arrive as proposed updates, and today your rep approves every output before it sends.