What's a BANT score, and why is yours climbing in real time?

At some point in the 1950s, a sales trainer named Buck Rodgers at IBM decided there had to be a better way to tell a real prospect from someone who was just lonely and wanted to talk about enterprise software. He came up with BANT: Budget, Authority, Need, Timeline. Whether or not they can buy, whether or not they're the one who decides, whether or not they actually have a problem you solve, and whether or not it's happening soon.

BANT has been the working model for B2B qualification ever since, largely because it's correct. It's not a perfect oracle. It's a framework, a useful set of questions to ask, and like most useful frameworks it works much better when you actually use it than when you forget about it until the deal is already lost.

The traditional problem: getting BANT data required asking for it, which meant a human rep, a form, or an awkward email sequence. Quincer scores it live, in the conversation, as signals emerge, without making anyone fill out a qualification questionnaire at gunpoint.

What the four letters actually mean

Budget is not "do you have money." It's "do you have money earmarked for something like this." Someone who says "we have budget approved for a new tool this fiscal year" is a different prospect from someone who says "we'd love to find a way to do this eventually." Both are honest. Only one is close to a purchase.

Authority is whether the person you're talking to can say yes, or whether their answer starts with "I'd need to check with." That's not a disqualifier on its own, many great champions can't sign checks, but knowing it shapes the next step. Are you booking a meeting for them, or for them plus their manager?

Need is the clearest signal, and the one visitors give away most freely. "We're currently doing this manually," "we switched from X and it broke," "we have a team of forty and the spreadsheet is a nightmare," are all Need signals. The visitor is explaining their problem. The agent is listening.

Timeline is urgency. "We want to be live by Q3" is a different conversation from "exploring options for eventually." Both are worth having. Only one warrants dropping everything else to move fast.

BANT is not a gating ritual. It's a map. The score tells you where to focus, not whether someone is allowed to talk to you.

How Quincer scores it live

The agent doesn't ask "are you the decision maker?" like a nervous SDR with a checklist. It has a conversation. It asks about the current setup, the team size, the timeline, the pain point. Each answer moves a dial. By message four or five, the score is usually meaningful. By message seven or eight, the routing decision is obvious.

Watch the score build in real time as four buying signals surface:

The score reaches 82 and Quincer's routing kicks in. Hot leads get booked immediately, with the right rep or calendar, and the agent offers times right there in the chat. It doesn't wait for a human to triage the transcript on Monday morning. The human gets a notification: "new Hot lead, 82, already booked Thursday 2pm, here's the summary."

The four lights turning on

Think of BANT as four light switches. At the start of a conversation, all four are off. As the visitor answers questions or volunteers information, the switches flip. "Team of 40" lights N (Need). "Budget approved" lights B. "I make the call" lights A. "Switching this quarter" lights T. When all four are on, you're looking at about as hot a lead as you'll find in a web chat.

What the score actually drives

Cold to Warm to Hot is not just a label. It's a routing decision. A Cold lead gets a helpful answer and a low-friction follow-up, usually an email or a piece of content that moves them along without burning a rep's calendar. A Warm lead might get offered a time, but gently. A Hot lead at 82 gets: "Want a 20-minute walkthrough? I have Thursday 2pm or Friday 10am open." The booking offer comes fast, because the signal is strong and the window is narrow.

If the visitor can't book right now, Quincer captures the contact, logs the score and the reasoning to the CRM, and triggers a follow-up email. The rep doesn't inherit a mystery form-fill. They inherit a context-rich lead: here's what they said, here's why they're a 78, here's what I offered, here's what happened.

A note on BANT as a heuristic

BANT is a guide, not a verdict. An 82 is a strong signal. It is not a guarantee. A person who says all the right things might be a researcher, or a student, or a competitor doing reconnaissance. A 55 who "has to check with someone" might become your biggest account six months from now once the internal politics sort out. The score is a prioritization tool. It tells you who to call back first, not who deserves to be talked to.

Quincer treats it that way. It surfaces the score as context for the human who takes the handoff, with the reasoning shown, not just the number. "Budget confirmed verbally, authority explicit, need is active, timeline is Q3" is more useful than "82" alone.

The best part of live BANT scoring is that it's not doing anything clever. It's doing what a good rep would do in the first five minutes of a call: ask a few smart questions, listen for the signals, and form a view. The difference is that Quincer does it for every single visitor, at 2pm and at 2am, in 50 languages, without forgetting to ask about timeline.