BUYER READINESS
BANT asks four questions and records four answers. The buyer readiness diagnostic measures whether those answers survive the buyer's own organization.
This page is written for sales-led B2B companies between $1M and $15M in revenue, running multi-stakeholder deals over cycles long enough that a qualified yes and a signature are months apart. If that's your shape and your BANT-qualified pipeline still ends in no decision, this is about the gap between a stated yes and a completed decision. It isn't an argument that BANT is broken. It's an argument about what a screening filter accepts as evidence, and where the buyer readiness diagnostic picks up. The other tools aimed at the same problem are mapped at buyer indecision solutions.
The Deal That Passed BANT on All Four Letters
Picture a deal you qualified cleanly. Budget confirmed, in writing. Your contact had authority and said so. The need was real, documented, and the buyer described it before you did. Timing was this quarter.
Then a company-wide priority shift moved the money to an unrelated initiative. The buyer still wanted the product. Nobody chose a competitor, and nobody raised an objection.
That's the prediction violation. BANT predicts that a buyer holding budget, authority, need and timing is qualified to advance. This one held all four, said so plainly, and did not buy. You didn't lose to a competitor. You lost to a bigger line item.
That scene is a composite from anonymized sales-community accounts, not a client engagement: a multi-stakeholder evaluation, a cycle long enough to cross a planning boundary, a budget decision made a level above the buyer. It carries no deal size or headcount because the accounts it came from didn't, and a page about evidence standards shouldn't invent the numbers that would make it sound sharper.
What a BANT-Clean No-Decision Costs You Across a Year
The four recorded yeses sit in the CRM, so the deal forecasts as healthy right up to the quarter it doesn't close. It gets recommitted. It gets recommitted again. It gets recommitted a third time, on the same four answers nobody has retested.
Then reps spend hours re-confirming those answers, which isn't evidence-gathering. It's re-asking the question that produced the reading. Marketing gets blamed for lead quality when the leads were fine. And the deal that could have closed sat behind it in the queue.
Forrester puts the scale at 86% of B2B purchases stalling during the buying process, which isn't a lead-quality number.
You can price this on your own numbers. Count last quarter's deals that passed BANT cleanly and closed lost with no competitor named, then multiply by your average closed-won deal value over the trailing 120 days. That figure is one quarter of qualified pipeline your qualification step couldn't see into. The arithmetic is at the cost of inaction in B2B sales.
The Four Things Teams Try First, and Why Each One Misses
- Tighten the BANT criteria. Raises the bar on the same stated answers. A stricter yes is still a yes the buyer produced on request.
- Add letters. MEDDIC, then MEDDPICC. More coverage fields, more questions asked, the same instrument. Covered at DecisionScope vs MEDDIC and DecisionScope vs MEDDPICC.
- Get the budget confirmed in writing. Makes the yes more formal, not more durable. A signed budget line doesn't survive a reprioritization it never anticipated.
- Re-qualify at every stage gate. The purest version of the error. Re-asking the four questions re-runs whatever inflated the first reading, and repeating a contaminated measurement isn't triangulation.
All four act on the questionnaire. None of them changes what the questionnaire accepts as evidence. The pattern of qualified deals dying quietly is covered at why qualified deals die.
What BANT Measures, and What It Does Not
IBM built BANT in the 1960s to answer one question: where should a rep spend the next hour. Sixty years later it's still the most widely used qualification framework in B2B, and that longevity is worth respecting rather than sneering at. It lasted because it solves a real problem cheaply.
The Four Letters
- Budget. Does the buyer have funds available for this.
- Authority. Does this contact hold purchase authority, or reliable access to whoever does.
- Need. Is there a real, identified business need.
- Timing. When does the buyer plan to act.
What BANT Was Actually Built to Do
Allocate rep hours at the top of the funnel. Most criticism aimed at BANT is really criticism of teams asking it to do a different job than the one it was built for. What has changed is how little of the decision now happens in front of a seller at all, which Gartner's B2B buying research has tracked for years.
The Hidden Assumption
BANT rests on one assumption: that a stated yes is a clean reading of the buyer's state. Ask, record, treat the answer as data.
In the 1960s that was defensible. The buyer had less information, the group was smaller, and nobody had published the research on what happens to an answer when you ask for it. None of the three holds now: 6sense finds buyers arriving at first contact with a preferred vendor already in mind, so much of the decision forms before the first question gets asked. That assumption is what the rest of this page tests.
What DecisionScope Measures
DecisionScope doesn't screen leads. It scores the buyer across four dimensions, then prescribes the protocol that resolves the weakest.
The Four Readiness Dimensions
- Problem Conviction. Belief that the problem justifies action. Recognition cue: they confirmed the need and can live with it another two quarters.
- Evaluation Clarity. A framework for comparing options. Recognition cue: the requirements list grows every session and no vendor ever looks complete.
- Outcome Confidence. Trust that the chosen solution will work in their environment. Recognition cue: they like the product and keep asking who else like them has done this.
- Organizational Readiness. Internal alignment across all stakeholders. Recognition cue: your contact has authority and still can't get it through.
The Four Resolution Protocols
- Urgency Protocol. Makes the cost of inaction visible before sales conversations begin. Closes Problem Conviction.
- Framework Protocol. Gives buyers a decision structure they trust. Closes Evaluation Clarity.
- Proof Protocol. Provides implementation evidence tailored to their context. Closes Outcome Confidence.
- Alignment Protocol. Maps the buying group and equips your champion for internal selling. Closes Organizational Readiness.
The Weakest Link Principle, and Its Status
The four dimensions aren't independent checkboxes. They form a chain, and the deal moves at the speed of the weakest link. Three maxed dimensions plus one incomplete equals a dead deal.
I hold that as a working model, not a proven law. Each dimension rests on cited research, listed at sources. The chain model hasn't been through a controlled trial, and I'd rather say so than have someone else say it for me.
What Counts as Evidence
Here's the load-bearing difference, and it isn't scope or stage. It's the evidence standard.
BANT accepts what the buyer says. The buyer readiness diagnostic accepts what survives the buyer's organization: a budget that holds through a reprioritization, an authority that produces a decision rather than a meeting, a need urgent enough to outrank what else wants the same money. Harder to observe, and the only ones that predict completion. The same problem inside the richer qualification frameworks is at MEDDIC limitations.
Where They Overlap, and Where They Diverge
| Axis | BANT | DecisionScope |
|---|---|---|
| Question it answers | Should a rep spend time here | Can this buyer finish the decision |
| When it runs | Once, at the top of the funnel | Across the cycle, re-scored as it moves |
| Evidence it accepts | The buyer's stated answer | What survives the buyer's own organization |
| Unit of analysis | One contact, one conversation | The buying group, including who never appeared |
| Output | A yes or no on advancing | A score per dimension, plus the weakest link |
| Origin | IBM, 1960s, built for lead routing | Cited decision research, chain model untested |
| Failure it catches | Hours spent on leads that were never worth it | A qualified buyer who cannot complete the decision |
| Failure it misses | Four confirmed yeses that don't survive review | A lead that was never worth an hour in the first place |
| Known boundary | Asking inflates the answer it records | Scores are only as honest as the CRM behind them |
BANT screens the lead in. DecisionScope tells you whether it can close.
BANT asks four questions and records four answers, and for sixty years that's been enough to decide where a rep spends their time. It's still enough for that. What it can't do is tell you whether those answers survive contact with the buyer's own organization, because they were produced by asking, and asking inflates what it measures. A buyer can hold budget, authority, need and timing, say so plainly, and still be unable to finish the decision.
That gap isn't a flaw in BANT's design. It's the space BANT was never built to look at. Run BANT to allocate the hour, and run the buyer readiness diagnostic to know whether the hour lands. The seller-side and buyer-side mental models are compared directly at the buyer readiness gap.
Sequential, Not Competing
These aren't rival answers to one question. BANT is a gate at the top; readiness is a measurement through the middle. The gate decides who gets in, the measurement tells you which of them can finish, and the workflow below puts them in that order.
When BANT Alone Is Enough
- Transactional deals with a single decision-maker. The stated yes and the deciding are the same act, so there's no gap for a diagnostic to measure.
- Short SMB cycles. Readiness can't drift much between the yes and the signature when the cycle is three weeks.
- Repeat-buyer expansions. The existing relationship already establishes readiness. Re-scoring asks a question you have the answer to.
- Top-of-funnel triage at volume. When the job is allocating rep hours across hundreds of leads, BANT is faster and cheaper than anything I'd sell you.
- Teams with no CRM discipline. Scoring readiness needs data. A stated yes needs a phone call.
In each of these, adding a readiness layer adds process without adding signal. Note how much of the market that covers: everything short, everything single-threaded, everything transactional, everything already sold once to the same buyer. This page's argument is narrower than it sounds, and holds only where the decision outlives the conversation that qualified it.
When You Need the Diagnostic Underneath
- Deals die with no competitor named. Dixon and McKenna found 56% of B2B inaction losses come from buyer indecision rather than a preference for the status quo. The two look identical in a CRM and call for opposite responses.
- The decision is made by a group. Durable group decisions come from a shared structured understanding across the group, which is not what BANT's Authority letter asks about.
- Your champion has to sell internally and you can't see any of it. Building support inside the buyer's organization while absorbing the objections nobody raises in front of you is the work that decides the deal, and none of it happens where a rep can watch. The Alignment Protocol exists because that work is invisible, not because it is optional.
- A confirmed budget moved. Budget is the letter most likely to be true when recorded and false when needed, because it's the most exposed to decisions made above your buyer.
- You re-qualify and the answers never change but the outcomes do. That's the clearest sign the instrument has stopped measuring anything.
Three Things a Stated Yes Cannot Tell You
Asking Inflates the Answer
BANT works by asking. Chandon, Morwitz and Reinartz, in the Journal of Marketing, found that the act of measuring purchase intentions inflates the intention-behavior correlation by 58%. The effect is called self-generated validity: asking someone to state an intention partly creates the commitment it then records.
Read that against BANT's output, which is four stated intentions. Asking "do you have budget for this?" doesn't only measure budget. It invites the buyer to compose a position they may not have held before you asked.
This isn't a criticism of IBM. Self-generated validity was documented four decades after BANT was written, in a journal nobody in 1960s sales enablement was reading. But once you know it, you can't treat a recorded yes as a clean reading, and every forecast built on those yeses inherits the inflation.
Authority Is a Routing Question, Not an Alignment One
BANT's Authority letter asks whether your contact holds purchase authority or access to it. That tells a rep who to talk to next. It says nothing about whether the group behind that contact can converge.
DeChurch and Mesmer-Magnus, in a meta-analysis of shared mental models, find that groups make durable decisions when members share a structured understanding of the problem and of each other's roles. Persuading members one at a time doesn't produce that. Stevenson, Pearce and Porter established the mechanism decades earlier: organizational coalitions form through shared interest, communication and mutual commitment, and those processes predict whether a group coheres or fragments.
A second anonymized composite shows the shape: a renewal-cycle evaluation against an incumbent, with a committee scoring it and one person owning the switch. The buyer ran a real evaluation, preferred the alternative on merit, then let the incumbent auto-renew, because switching meant migration and retraining and all of it landed on that one overloaded owner. Every BANT letter held. Authority was real. The person holding it just couldn't carry the internal cost alone.
Timing Is What a Buyer Says When They Haven't Decided
Of the four answers, Timing is the most freely given and least costly to revise. A date commits nobody. It's the letter that most often reads green while the deal is least ready, because "this quarter" is what a cooperative buyer says to a question they don't want to meet with silence.
What This Argument Owes You
The easy move is to say the average buying group is now thirteen people, so a 1960s framework can't cope. I've made a version of that argument, and it's wrong.
Bronten and Cabrera, in the Journal of Systems Thinking, find that B2B win rates actually peak at four to five stakeholders and decline only past six. That isn't the linear relationship the headcount argument assumes. More people in the room is not automatically worse, and any argument built on the raw number is built on sand.
What survives is structural rather than numerical: what predicts completion is whether the group holds a shared frame, not how many people are in it. That's a narrower claim than "BANT doesn't scale," and it's the only one the evidence supports. It also disciplines my own work, because Organizational Readiness has to be scored on structure rather than headcount or it inherits the identical error. The version of this critique aimed at activity-data tools is at revenue intelligence limitations.
How to Use Both Together
The Combined Workflow
- Run BANT to decide where the hour goes. Fast, cheap, good at exactly this. Nothing below replaces it.
- Score readiness once the deal has earned the hour. Four dimensions, one score each, weakest link named.
- Map each letter onto the dimension that tests whether the yes holds. The mapping is below.
- Re-score before you forecast. A BANT yes recorded in week one isn't evidence in week nine. Dixon and McKenna found reps who diagnosed indecision closed 14% of the time, while those who diagnosed and offered a specific recommendation closed 36%. That lift is their finding, and it's why the prescription matters more than the diagnosis.
Which Dimension Tests Each BANT Letter
- Budget tests as Problem Conviction. Money follows conviction, not the reverse. A budget that survives a reprioritization belonged to a problem someone believed in, and the Urgency Protocol builds that belief before the money is at risk.
- Authority tests as Organizational Readiness. Access to the authority isn't alignment across the group, and the Alignment Protocol closes the difference.
- Need tests as Problem Conviction, read for urgency rather than agreement. A confirmed need and a bleeding one produce identical BANT answers and opposite outcomes.
- Timing tests against all four. A date is what a buyer offers when the decision is still open, so it needs corroboration from somewhere other than the buyer's mouth.
A Short Example
Run the opening deal again with a score in front of it.
- Without the score. Budget confirmed in week one, recorded, never revisited. The deal forecasts at high confidence until the quarter it's defunded.
- With the score. Problem Conviction reads yellow, because the need was confirmed but never priced against what else the buyer is funding. The Urgency Protocol runs, the cost of inaction gets made concrete in the buyer's own numbers, and either the budget hardens or the deal leaves the forecast in week three rather than month five.
Same lead, same four answers, different decision about what the forecast is worth.
Take the Free Buyer Readiness Check
Go back to the deal that passed on all four letters. Budget was true. Authority was true. Need was true. Timing was true. Then the money moved to something that outranked it, and none of the four answers you had recorded could have told you that was coming.
Between 40% and 60% of qualified B2B deals end in no decision. Qualifying harder doesn't move that number, because qualification was never looking at the thing that decides it. Knowing which of the four readiness dimensions is weak tells you which qualified deals are worth the forecast.
Start with the free 4-minute Buyer Readiness Check. No commitment, diagnostic snapshot in minutes.
FAQ
Does DecisionScope replace BANT?
No, and it isn't built to. BANT decides where a rep spends the hour, while DecisionScope tells you whether that hour can land. A team that drops BANT for a readiness diagnostic will just spend expensive scoring effort on leads that were never worth an hour. Run them in sequence. The wider set of tools aimed at this problem is at wiltonblake.com/buyer-readiness/buyer-indecision-solutions.
Can I use DecisionScope alongside BANT?
Yes, and that's the intended use. Qualify with BANT, then score the four readiness dimensions once the deal earns the attention. Each letter maps onto the dimension that tests whether the stated answer holds, so the second pass stress-tests the first rather than repeating it.
Why do BANT-qualified deals still end in no decision?
Because BANT records what the buyer says, and what the buyer says is produced partly by the asking. The 58% inflation in the intention-behavior correlation Chandon, Morwitz and Reinartz documented in the Journal of Marketing applies to every intention-based measurement, BANT included. Four honest yeses can all be true when given and none survive a reprioritization, a committee, or a champion who can't carry the internal cost.
How long does a DecisionScope assessment take?
The free readiness check takes 4 minutes and returns a diagnostic snapshot scored against the four dimensions. It's ungated and perception-based, so it tells you where to look rather than settling the answer. Scoring a real pipeline slice against CRM data is a separate step, and it's the one that produces a number you can forecast on.
How is buyer readiness different from BANT's Need?
Need asks whether a business problem exists. Problem Conviction asks whether the buyer believes it justifies action now, against everything else competing for the same money. A buyer can confirm a real need and still rank it fourth. Need is a yes-or-no field; conviction is a comparison, and only the comparison predicts whether the budget holds. The Urgency Protocol closes that gap.
Will BANT alone work for transactional sales?
Often yes. When one person decides, the cycle is short, and the stated yes and the deciding are the same act, there's no gap for a readiness diagnostic to measure. BANT alone gets weaker as the decision moves from one person to a group and as the time between the yes and the signature grows, which is when 86% of B2B purchases stall.
Does a bigger buying group make BANT less reliable?
Not in the way the common argument claims. Bronten and Cabrera find win rates peak at four to five stakeholders and decline only past six, so raw headcount isn't the variable. What degrades BANT is structural: it asks one contact about a decision the group makes together, and a group without a shared frame produces confident individual answers and no collective one.