BANT (Budget, Authority, Need, Timeline) was developed by IBM in the 1960s. It was designed for relatively straightforward technology sales, where the decision-maker was usually one person, the buying process was linear, and the main question was whether the prospect could afford the product.
Most complex B2B sales in 2025 don’t look like this. Buying committees are larger. Procurement processes are more involved. The person you’re talking to often isn’t the person who signs. Budget isn’t always defined in advance; it gets created when the business case is compelling enough. And “need” is rarely as simple as whether the prospect said they had one.
BANT is still better than nothing. But it leaves too much uncovered to be a reliable qualification framework for deals with cycle lengths over sixty days, multiple stakeholders, or deal values above £30k. This post is about what to use instead.
It’s worth reading alongside Pipeline Stage Definitions with Exit Criteria, which covers how qualification fits into the broader pipeline architecture.
What BANT gets wrong
Let’s be specific about the gaps.
Budget. BANT asks whether the prospect has a budget. But in a lot of enterprise and mid-market B2B sales, budget isn’t pre-allocated to the category you’re selling into. It gets created when there’s sufficient business case. Disqualifying deals because no explicit budget exists misses a significant portion of deals that could close, and asking “do you have budget for this?” in a first discovery call is both premature and slightly crass.
The better question isn’t “is there a budget?” but “is there a business problem with a financial cost attached to it?” If the answer is yes, budget can almost always be found.
Authority. BANT asks whether you’re talking to the decision-maker. But decision-making in B2B is rarely that simple. The economic buyer who signs the contract is often different from the technical evaluator who assesses fit, who is different again from the champion who’s advocating for you internally. Talking to the “decision-maker” without understanding the full buying committee is a recipe for late-stage surprises.
Need. “Need” is the weakest element of BANT. It’s too binary. The question isn’t whether there’s a need; it’s whether the need is significant enough to justify the disruption and cost of solving it, whether there’s internal urgency around it, and whether your solution is a believable way to address it.
Timeline. BANT asks whether there’s a timeline. But a timeline given in an early discovery call is usually aspirational rather than real, particularly if the prospect isn’t yet far enough into the buying process to have mapped out their internal approval journey. Relying on a stated timeline from week one is a reliable way to have your forecast consistently overstated.
MEDDIC: A better starting point
MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) addresses most of what BANT misses. It was developed at PTC in the 1990s for enterprise software sales and has aged considerably better.
Metrics. What does success look like in quantifiable terms? If you can’t define the measurable outcome the prospect is trying to achieve, you can’t build a business case. If you can define it (reduce close time by 20%, increase pipeline coverage to 4x, recover 15 hours per week of founder time), you have the foundation of a value-based conversation.
Economic Buyer. Not just who the decision-maker is, but whether you have direct access to them. A deal where you’ve only ever spoken to a champion who promises to “take it upstairs” is a much weaker position than a deal where you’ve had a direct conversation with the economic buyer. This is one of the most reliable leading indicators of whether a deal will close.
Decision Criteria. What criteria will the prospect use to make the decision? If you don’t know, or worse, if you’re guessing, you’re flying blind on how to position. The goal isn’t just to know the criteria but to have influenced them: the best commercial operators help prospects define criteria that naturally favour their solution.
Decision Process. How does the buying decision actually get made? Who’s involved, what does the approval chain look like, what internal gates are there (procurement review, legal, security assessment, board sign-off)? Understanding this early prevents late-stage surprises. A deal that was days from closing can stall for three months if procurement needs to get involved and nobody asked about it upfront.
Identify Pain. Similar to Need in BANT, but the emphasis in MEDDIC is on understanding the pain specifically: how significant it is, how widely it’s felt in the organisation, and what the cost of inaction is. Pain that’s felt by one person and isn’t commercially significant isn’t enough to drive a purchase decision.
Champion. Who in the prospect organisation is advocating for you internally? The champion is the person who benefits personally from the deal happening; they’ll fight for budget, navigate internal resistance, and brief you on what you need to know. A deal without a champion is a deal without an internal sponsor, and those deals typically stall or die quietly.
A practical extension: MEDDPICC
MEDDIC has two common extensions worth knowing about.
Paper Process (the extra P). This captures the legal, procurement, and contract review steps that come after verbal agreement. For any deal involving enterprise procurement or legal review, understanding this process early (who’s involved, how long it typically takes, what they’ll scrutinise) can save weeks of timeline slippage at the close. Add this as a discovery question: “Once we have agreement in principle, can you walk me through what the contract and approval process typically looks like?”
Competition (the extra C). Not just “are they speaking to competitors?” but: which ones, where do you stand in the evaluation, and what criteria are they prioritising in the comparison? If you don’t know the competitive situation, you can’t manage it.
What qualification actually looks like in practice
The goal isn’t to make discovery feel like an interrogation. It’s to structure your conversations so that by the time you’ve had two or three substantive calls, you have clear answers to:
- Is there a business problem with a measurable cost?
- Is there a champion who wants this solved and will advocate for it?
- Do we have access to (or a clear path to) the economic buyer?
- Do we understand their decision process and timeline, and does it reflect reality?
- Can we articulate the criteria they’ll use to decide, and do we fit them?
If you can answer all of these with confidence, you have a qualified deal. If you can answer most of them, you have a deal worth continued investment. If you can answer fewer than half, you have an interesting conversation that hasn’t qualified yet.
Build these questions into your discovery framework. Make sure they’re captured in the CRM against each deal record. And use them in pipeline reviews to pressure-test whether deals that look close actually are.
The qualification layer connects directly to how your pipeline stages are structured; each stage should have exit criteria that reflect the qualification elements you’ve confirmed. Pipeline Stage Definitions with Exit Criteria has the template. And if you’re building the full process from scratch, How to Build a Sales Process From Scratch covers the sequence.