BANT Lead Qualification Template
Budget, Authority, Need, Timeline - the oldest qualification framework in B2B, reworked for how buying actually happens now. This page gives you the modern reading of each letter, a 2-minute question set, a disqualify-fast doctrine, and a copy-paste CRM kit: four fields plus an automation that moves a deal to Qualified the moment all four are filled.
Who this is for
BANT is for anyone with more leads than selling time: founders doing their own sales, the first SDR or AE hire, agencies triaging inbound, and AI SDR agents that need a machine-checkable definition of "qualified." Use it at the top of the funnel - the first call, the inbound reply, the demo request - where the decision is binary: does this deal deserve pipeline time or not? For complex enterprise deals with eight-person buying committees, graduate to the MEDDPICC checklist; for impact-led selling, use SPICED. BANT is the triage layer that decides whether those heavier frameworks ever get invoked.
Credit where due: BANT originated inside IBM's sales organization, decades before SaaS existed. The letters survived because the underlying questions - can they pay, can they sign, do they hurt, is there a date - never stopped mattering.
BANT is a filter, not a script
The framework got its bad reputation from reps who read the four letters aloud: "What's your budget? Are you the decision maker?" Nobody answers those honestly on a first call, and the interrogation costs you the relationship. The modern usage is different: BANT is a private checklist the seller fills in after a natural conversation. You never ask a BANT question by name - you extract the four signals from discovery and record them as structured data.
| Letter | Legacy reading | Modern reading |
|---|---|---|
| Budget | "Do you have $X allocated?" | Is there a path to money? A confirmed line item is rare pre-discovery. What matters is whether the pain is expensive enough that funding can be found. |
| Authority | "Are you the decision maker?" | Access to power. You rarely start with the economic buyer. A champion who can and will get you there counts; an influencer with no access does not. |
| Need | "Do you need this?" | The problem in their words, with a cost attached. If you cannot quote the prospect describing the pain, you do not know the need. |
| Timeline | "When will you buy?" | Is there a forcing event? A contract expiry, an audit, a launch, a hire. "Sometime next year" is not a timeline, it is a polite no. |
The 2-minute question set
Ask in N-T-A-B order, not B-A-N-T. Need first, budget last - once the pain and the forcing event are on the table, the money and authority questions stop feeling invasive. Every question below maps to one of the four fields in the kit.
| Field | Ask this | You are listening for |
|---|---|---|
| Need | "What made you take this call?" then "What happens if you do nothing for six months?" | A concrete cost of inaction, in their words. Vague curiosity = not a need. |
| Timeline | "Is there a date this has to be solved by?" then "What happens if that slips?" | A named forcing event with consequences. No event = nurture, not pipeline. |
| Authority | "Who else feels this problem?" then "When something like this got bought before, who signed?" | Whether your contact is the buyer, can produce the buyer, or is guessing. |
| Budget | "Have you bought something in this category before?" then "Where did that money come from?" | A funding pattern. Past purchases prove a path to money exists even without a current line item. |
Disqualify fast
The point of qualification is disqualification. A clean "no" after two minutes is worth more than a warm "maybe" you chase for six weeks. Three rules, and the kit below enforces all of them mechanically:
- Any hard disqualifier kills the deal now. No path to money, no access to power, no forcing event - pick any one and the deal goes to nurture or Lost today, not after three more follow-ups.
- Gaps become next-call objectives. Three of four filled? The deal stays in Lead and the empty field is literally the agenda for the next touch. Never invent an answer to make the record look complete.
- No deal enters Qualified with an empty field. Deals that skip into Qualified on gut feel are how forecast rot starts. Make the promotion automatic and conditional, and the rule becomes impossible to break.
The kit: 4 fields + auto-qualify automation
This JSON sets up the whole system in any Relm workspace: three enum groups, four custom fields on the deal object, and two automations. The first moves a deal from lead to qualified only when all four fields are filled and none holds a disqualifier. The second sends budget-dead deals straight to lost - the disqualify-fast doctrine as code. Apply it by POSTing each enums row to /v1/enums, each fields row to /v1/fields, and each automations row to /v1/automations - in that order. Stage keys match Relm's default pipeline (lead, qualified, proposal, won, lost); adjust if you renamed stages. The two automations fit the Free plan exactly - its cap is two.
{
"enums": [
{ "group": "bant_budget", "value": "confirmed", "label": "Confirmed - budget line exists" },
{ "group": "bant_budget", "value": "attainable", "label": "Attainable - champion can find the money" },
{ "group": "bant_budget", "value": "none", "label": "None - no path to money" },
{ "group": "bant_authority", "value": "economic_buyer", "label": "Talking to the economic buyer" },
{ "group": "bant_authority", "value": "champion", "label": "Champion with access to power" },
{ "group": "bant_authority", "value": "no_access", "label": "Influencer only - no access" },
{ "group": "bant_timeline", "value": "this_quarter", "label": "Forcing event this quarter" },
{ "group": "bant_timeline", "value": "next_quarter", "label": "Forcing event next quarter" },
{ "group": "bant_timeline", "value": "this_year", "label": "Forcing event this year" },
{ "group": "bant_timeline", "value": "none", "label": "No event, no date" }
],
"fields": [
{ "object": "deal", "key": "bant_budget", "label": "Budget", "data_type": "select", "enum_group": "bant_budget" },
{ "object": "deal", "key": "bant_authority", "label": "Authority", "data_type": "select", "enum_group": "bant_authority" },
{ "object": "deal", "key": "bant_need", "label": "Need (their words)", "data_type": "text" },
{ "object": "deal", "key": "bant_timeline", "label": "Timeline", "data_type": "select", "enum_group": "bant_timeline" }
],
"automations": [
{
"name": "BANT complete - move to Qualified",
"trigger_event": "deal.updated",
"conditions": [
{ "field": "stage", "op": "eq", "value": "lead" },
{ "field": "bant_budget", "op": "exists" },
{ "field": "bant_budget", "op": "neq", "value": "none" },
{ "field": "bant_authority", "op": "exists" },
{ "field": "bant_authority", "op": "neq", "value": "no_access" },
{ "field": "bant_need", "op": "exists" },
{ "field": "bant_timeline", "op": "exists" },
{ "field": "bant_timeline", "op": "neq", "value": "none" }
],
"actions": [
{ "type": "move_deal_stage", "stage": "qualified" },
{ "type": "create_activity", "activity_type": "note", "body": "Auto-qualified: BANT complete. Budget={{bant_budget}}, Authority={{bant_authority}}, Timeline={{bant_timeline}}. Need: {{bant_need}}" }
]
},
{
"name": "BANT disqualifier - no path to money",
"trigger_event": "deal.updated",
"conditions": [
{ "field": "stage", "op": "eq", "value": "lead" },
{ "field": "bant_budget", "op": "eq", "value": "none" }
],
"actions": [
{ "type": "move_deal_stage", "stage": "lost" },
{ "type": "create_activity", "activity_type": "note", "body": "Disqualified: no path to budget. Recycle to nurture - do not keep working this." }
]
}
]
}Two design notes. Conditions are ANDed and read custom fields directly, so exists + neq "none" together mean "filled, and filled with something fundable." And the stage = lead guard means the rule only promotes deals sitting in Lead - it will never yank a Proposal-stage deal backward. If auto-losing budget-dead deals feels harsh, point the second automation at a nurture pipeline instead; the doctrine only requires that they leave your active pipeline today.
The same four fields work in any CRM that supports custom fields - the framework stands on its own. Relm just makes the setup a single agent instruction, because fields, enums, and automations are all plain REST endpoints an LLM can call directly.
Apply it with your agent
If your agent is connected to Relm over MCP, paste this prompt along with the JSON above:
Set up BANT qualification in my CRM:
1. Call relm_describe_schema for the objects and fields, and
relm_list_pipelines for the stage keys.
2. From the kit JSON I pasted: create every enum option
(relm_create_enum_value), then the four deal fields
(relm_create_field), then both automations (relm_create_automation).
3. Backfill: list open deals in the "lead" stage, read each deal's
activities, and fill any bant_ field the notes clearly support.
Leave fields empty when the evidence is thin - never guess.
4. Reply with: fields created, automations created, deals backfilled,
and which deals are one field away from auto-qualifying.Over REST, the qualification rule is one call:
curl https://api.relmcrm.com/v1/automations \
-H "Authorization: Bearer relm_test_..." \
-H "Content-Type: application/json" \
-d '{
"name": "BANT complete - move to Qualified",
"trigger_event": "deal.updated",
"conditions": [
{ "field": "stage", "op": "eq", "value": "lead" },
{ "field": "bant_budget", "op": "exists" },
{ "field": "bant_budget", "op": "neq", "value": "none" },
{ "field": "bant_authority", "op": "exists" },
{ "field": "bant_authority", "op": "neq", "value": "no_access" },
{ "field": "bant_need", "op": "exists" },
{ "field": "bant_timeline", "op": "exists" },
{ "field": "bant_timeline", "op": "neq", "value": "none" }
],
"actions": [{ "type": "move_deal_stage", "stage": "qualified" }]
}'Use a relm_test_ key to rehearse - test mode is free, unlimited, and invisible to live data. Once qualified deals start flowing, put numbers behind the letters with the lead scoring framework, and see how to give your AI agent a CRM for the full agent setup.
FAQ
Is BANT still relevant in 2026?
Yes - as a filter, not a call script. BANT fails when reps read the four letters as interview questions. It works when it is a private checklist the seller fills from a natural conversation, used to decide which deals deserve pipeline time. For transactional and mid-market deals it is still the fastest qualification frame there is.
When should I use BANT instead of MEDDPICC or SPICED?
Use BANT when sales cycles are short, buying committees are small, and you need a fast keep-or-kill decision - inbound triage, SMB, mid-market, founder-led sales. Use MEDDPICC for complex enterprise deals with multi-stakeholder committees, and SPICED when you sell on impact and need a frame that survives post-sale into customer success.
Should missing budget disqualify a lead?
A missing budget line item should not - most real problems have no line item yet. What disqualifies is no path to money: the pain is not expensive enough for anyone to fund fixing it. Record budget as confirmed, attainable, or none, and only treat none as a disqualifier.
What order should I ask BANT questions in?
Not B-A-N-T. Lead with Need, then Timeline, then Authority, and leave Budget for last - N-T-A-B. Opening with budget questions before the prospect has articulated the pain reads as self-serving and gets you guarded answers. Once the need and a forcing event are on the table, budget and authority questions answer themselves.
Can an AI agent fill BANT fields automatically?
Yes. Because the four criteria live as structured CRM fields, an agent can read call notes or transcripts, extract budget, authority, need, and timeline signals, and write them to the deal over REST or MCP. The auto-qualify automation then promotes the deal the moment all four are filled - no human data entry in the loop.