Is this sales lead qualified? A BANT assessment

Is this sales lead qualified? A BANT assessment

Decision tree saleslead qualificationcrmrevenue

Walk through the BANT framework to determine whether a prospect is a qualified opportunity worth pursuing. This tree routes your rep to the right next action — whether that's advancing to discovery, nurturing for future pipeline, disqualifying early, or looping in a Senior AE for a complex deal.

Overview

Type
Decision tree
Tags
sales, lead qualification, crm, revenue
Entry
Q1
Questions
5
Outcomes
4
Author
Andrew
Last updated
2026-05-12

Decision Tree

Start: Has the prospect confirmed they have budget allocated or available for this type of solution?

yes

  • Continues to question: Are you speaking directly with the economic buyer or decision-maker, or do you have a clear path to them?

no

  • Continues to question: Is there a strong, clearly articulated pain or business need driving this conversation?

Machine-Readable JSON (Canonical Model)

View JSON
{
  "_meta": {
    "schema": "https://www.drawdecisiontree.com/decision-dag.schema.json",
    "source": "https://www.drawdecisiontree.com",
    "description": "DrawDecisionTree.com is a free tool for building, sharing, and embedding interactive decision trees. This file is the machine-readable export of a published decision tree. The `dsl` field contains the original source in the Decision DAG DSL; the `dag` schema is documented at the URL in `schema` above.",
    "links": {
      "interactive": "https://www.drawdecisiontree.com/t/drawdecisiontree/sales-lead-qualification.html",
      "embed": "https://www.drawdecisiontree.com/embed/path/drawdecisiontree/sales-lead-qualification",
      "dsl_reference": "https://www.drawdecisiontree.com/decision-tree-dsl-reference.html",
      "guides": "https://www.drawdecisiontree.com/guides",
      "schema_docs": "https://www.drawdecisiontree.com/decision-dag.schema.json",
      "author_trees": "https://www.drawdecisiontree.com/trees/drawdecisiontree"
    },
    "generated_at": "2026-05-29T12:05:39.352Z"
  },
  "author": {
    "handle": "drawdecisiontree",
    "first_name": "Andrew",
    "last_name": null,
    "avatar_url": "1d32d828-b6ca-40ec-bdd7-771fe7b9c36a/avatar-1778531481027.svg",
    "display_name": "Andrew"
  },
  "file": {
    "id": "fde8c11f-db9a-4826-95c5-3c36dadb55f0",
    "name": "Is this sales lead qualified? A BANT assessment",
    "public_slug": "sales-lead-qualification",
    "updated_at": "2026-05-12T16:53:43.587978+00:00",
    "url": "https://www.drawdecisiontree.com/t/drawdecisiontree/sales-lead-qualification.html",
    "json_url": "https://www.drawdecisiontree.com/t/drawdecisiontree/sales-lead-qualification/tree.json",
    "dsl_url": "https://www.drawdecisiontree.com/t/drawdecisiontree/sales-lead-qualification/tree.dag"
  },
  "meta": {
    "description": "Walk through the BANT framework to determine whether a prospect is a qualified opportunity worth pursuing. This tree routes your rep to the right next action — whether that's advancing to discovery, nurturing for future pipeline, disqualifying early, or looping in a Senior AE for a complex deal.",
    "mode": "decision",
    "entry": "Q1",
    "tags": [
      "sales",
      "lead qualification",
      "crm",
      "revenue"
    ],
    "image": "https://images.unsplash.com/photo-1552664730-d307ca884978?w=1200&q=80"
  },
  "questions": [
    {
      "id": "Q1",
      "text": "Has the prospect confirmed they have budget allocated or available for this type of solution?"
    },
    {
      "id": "Q2",
      "text": "Are you speaking directly with the economic buyer or decision-maker, or do you have a clear path to them?"
    },
    {
      "id": "Q3",
      "text": "Is there a strong, clearly articulated pain or business need driving this conversation?"
    },
    {
      "id": "Q4",
      "text": "What is the prospect's expected purchase timeline?"
    },
    {
      "id": "Q5",
      "text": "Is the deal size, complexity, or strategic importance above your normal threshold for independent handling?"
    }
  ],
  "outcomes": [
    {
      "id": "QUALIFIED",
      "label": "Qualified Lead"
    },
    {
      "id": "NURTURE",
      "label": "Nurture Track"
    },
    {
      "id": "DISQUALIFY",
      "label": "Disqualify"
    },
    {
      "id": "ESCALATE",
      "label": "Escalate to Senior AE"
    }
  ],
  "dsl": "dag: Is this sales lead qualified? A BANT assessment\nversion: 1.0.0\nimage: https://images.unsplash.com/photo-1552664730-d307ca884978?w=1200&q=80\ndescription: Walk through the BANT framework to determine whether a prospect is a qualified opportunity worth pursuing. This tree routes your rep to the right next action — whether that's advancing to discovery, nurturing for future pipeline, disqualifying early, or looping in a Senior AE for a complex deal.\ntags: sales, lead qualification, crm, revenue\nentry: Q1\n\nQ1: Has the prospect confirmed they have budget allocated or available for this type of solution?\n  hint: Budget confirmation doesn't require an exact number — look for signals like an approved budget line, a recent purchase of a comparable solution, or a clear statement that funds can be made available. Avoid accepting vague answers like \"we'll figure it out\" as confirmed budget. If they're still in planning cycles, probe the timeline before moving on. A prospect who says \"we'd need to find budget\" is telling you the need is not yet a priority.\n  yes -> Q2\n  no  -> Q3\n\nQ2: Are you speaking directly with the economic buyer or decision-maker, or do you have a clear path to them?\n  hint: The economic buyer is the person who can sign the contract or approve the spend. \"Clear path\" means your champion has explicitly agreed to introduce you or sponsor internal access — not just a hopeful assumption. If you're stuck at a lower level with no introduction promised, that's a risk flag worth noting before advancing. Multi-stakeholder deals require mapping all decision-makers before moving to formal proposal.\n  yes -> Q4\n  no  -> [NURTURE]\n\nQ3: Is there a strong, clearly articulated pain or business need driving this conversation?\n  hint: A strong need is one the prospect has described in their own words with real business impact — lost revenue, compliance risk, operational inefficiency, or customer churn. If the need is vague or the prospect is \"just exploring,\" the opportunity may not be mature enough to advance. Use this question to distinguish genuine urgency from casual interest. Ask the prospect what happens if they do nothing — a compelling answer signals real pain.\n  yes -> Q4\n  no  -> [DISQUALIFY]\n\nQ4: What is the prospect's expected purchase timeline?\n  hint: Timeline shapes how you should prioritize and resource this opportunity. A deal closing within 90 days typically justifies active pursuit and executive involvement. Deals beyond 6 months may still be valuable but require a nurture strategy rather than active selling cycles. Use the prospect's own words — if they say \"no rush,\" probe for what would change that. Look for external forcing functions like contract renewals, board reviews, or compliance deadlines.\n  A: Within 90 days -> [QUALIFIED]\n  B: 3–6 months -> Q5\n  C: Beyond 6 months or undefined -> [NURTURE]\n\nQ5: Is the deal size, complexity, or strategic importance above your normal threshold for independent handling?\n  hint: Consider deal size relative to your average ACV, whether the account is on a named or strategic list, whether multiple stakeholders or procurement layers are involved, or whether the technical requirements exceed standard scope. When in doubt, a quick internal calibration with your manager or Senior AE costs little and can prevent mis-scoping early in the cycle. Enterprise logos, regulated industries, and multi-division accounts almost always warrant escalation.\n  yes -> [ESCALATE]\n  no  -> [NURTURE]\n\n[QUALIFIED]: Qualified Lead\n  color: #16a34a\n  description: This lead meets the core BANT criteria and is ready to advance to an active sales cycle. Schedule a formal discovery call within 48 hours to map stakeholders, confirm technical fit, and establish mutual success criteria. Log the opportunity in your CRM with budget, authority, need, and timeline fields populated. Set a follow-up task and propose a next step with a specific date before leaving the conversation. Create a mutual close plan and share it with the prospect to confirm alignment on the path forward.\n  code: SALES-QL-001\n\n[NURTURE]: Nurture Track\n  color: #2563eb\n  description: This prospect shows interest but lacks one or more BANT elements needed to justify active selling investment right now. Enroll them in a structured nurture sequence — a mix of relevant content, quarterly check-ins, and event invitations — to stay top of mind without over-investing rep time. Set a CRM reminder to re-qualify in 60–90 days or sooner if a trigger event occurs such as a funding round, leadership change, or renewal cycle. Document the specific gap — budget, authority, or timeline — so future outreach can address it directly.\n  code: SALES-QL-002\n\n[DISQUALIFY]: Disqualify\n  color: #dc2626\n  description: This prospect lacks both budget confirmation and a clearly defined need, making active pursuit a poor use of selling resources at this time. Log the disqualification reason in your CRM clearly — this protects forecast accuracy and helps marketing refine targeting criteria. Send a brief, professional closing note that leaves the door open if circumstances change. Move your time to higher-probability opportunities in your pipeline and review your lead source to identify whether ICP criteria need tightening.\n  code: SALES-QL-003\n\n[ESCALATE]: Escalate to Senior AE\n  color: #9333ea\n  description: The size, complexity, or strategic value of this deal warrants involvement from a Senior Account Executive or your sales manager before the next customer touchpoint. Prepare a concise deal brief covering what you know about budget, authority, need, and timeline, along with the key risks and open questions. Request an internal sync within 24 hours so the Senior AE can assess whether to co-own or take the lead on the account. Do not make promises to the prospect about pricing, timelines, or product roadmap until internal alignment is confirmed.\n  code: SALES-QL-004\n"
}

DSL Representation

dag: Is this sales lead qualified? A BANT assessment
version: 1.0.0
image: https://images.unsplash.com/photo-1552664730-d307ca884978?w=1200&q=80
description: Walk through the BANT framework to determine whether a prospect is a qualified opportunity worth pursuing. This tree routes your rep to the right next action — whether that's advancing to discovery, nurturing for future pipeline, disqualifying early, or looping in a Senior AE for a complex deal.
tags: sales, lead qualification, crm, revenue
entry: Q1

Q1: Has the prospect confirmed they have budget allocated or available for this type of solution?
  hint: Budget confirmation doesn't require an exact number — look for signals like an approved budget line, a recent purchase of a comparable solution, or a clear statement that funds can be made available. Avoid accepting vague answers like "we'll figure it out" as confirmed budget. If they're still in planning cycles, probe the timeline before moving on. A prospect who says "we'd need to find budget" is telling you the need is not yet a priority.
  yes -> Q2
  no  -> Q3

Q2: Are you speaking directly with the economic buyer or decision-maker, or do you have a clear path to them?
  hint: The economic buyer is the person who can sign the contract or approve the spend. "Clear path" means your champion has explicitly agreed to introduce you or sponsor internal access — not just a hopeful assumption. If you're stuck at a lower level with no introduction promised, that's a risk flag worth noting before advancing. Multi-stakeholder deals require mapping all decision-makers before moving to formal proposal.
  yes -> Q4
  no  -> [NURTURE]

Q3: Is there a strong, clearly articulated pain or business need driving this conversation?
  hint: A strong need is one the prospect has described in their own words with real business impact — lost revenue, compliance risk, operational inefficiency, or customer churn. If the need is vague or the prospect is "just exploring," the opportunity may not be mature enough to advance. Use this question to distinguish genuine urgency from casual interest. Ask the prospect what happens if they do nothing — a compelling answer signals real pain.
  yes -> Q4
  no  -> [DISQUALIFY]

Q4: What is the prospect's expected purchase timeline?
  hint: Timeline shapes how you should prioritize and resource this opportunity. A deal closing within 90 days typically justifies active pursuit and executive involvement. Deals beyond 6 months may still be valuable but require a nurture strategy rather than active selling cycles. Use the prospect's own words — if they say "no rush," probe for what would change that. Look for external forcing functions like contract renewals, board reviews, or compliance deadlines.
  A: Within 90 days -> [QUALIFIED]
  B: 3–6 months -> Q5
  C: Beyond 6 months or undefined -> [NURTURE]

Q5: Is the deal size, complexity, or strategic importance above your normal threshold for independent handling?
  hint: Consider deal size relative to your average ACV, whether the account is on a named or strategic list, whether multiple stakeholders or procurement layers are involved, or whether the technical requirements exceed standard scope. When in doubt, a quick internal calibration with your manager or Senior AE costs little and can prevent mis-scoping early in the cycle. Enterprise logos, regulated industries, and multi-division accounts almost always warrant escalation.
  yes -> [ESCALATE]
  no  -> [NURTURE]

[QUALIFIED]: Qualified Lead
  color: #16a34a
  description: This lead meets the core BANT criteria and is ready to advance to an active sales cycle. Schedule a formal discovery call within 48 hours to map stakeholders, confirm technical fit, and establish mutual success criteria. Log the opportunity in your CRM with budget, authority, need, and timeline fields populated. Set a follow-up task and propose a next step with a specific date before leaving the conversation. Create a mutual close plan and share it with the prospect to confirm alignment on the path forward.
  code: SALES-QL-001

[NURTURE]: Nurture Track
  color: #2563eb
  description: This prospect shows interest but lacks one or more BANT elements needed to justify active selling investment right now. Enroll them in a structured nurture sequence — a mix of relevant content, quarterly check-ins, and event invitations — to stay top of mind without over-investing rep time. Set a CRM reminder to re-qualify in 60–90 days or sooner if a trigger event occurs such as a funding round, leadership change, or renewal cycle. Document the specific gap — budget, authority, or timeline — so future outreach can address it directly.
  code: SALES-QL-002

[DISQUALIFY]: Disqualify
  color: #dc2626
  description: This prospect lacks both budget confirmation and a clearly defined need, making active pursuit a poor use of selling resources at this time. Log the disqualification reason in your CRM clearly — this protects forecast accuracy and helps marketing refine targeting criteria. Send a brief, professional closing note that leaves the door open if circumstances change. Move your time to higher-probability opportunities in your pipeline and review your lead source to identify whether ICP criteria need tightening.
  code: SALES-QL-003

[ESCALATE]: Escalate to Senior AE
  color: #9333ea
  description: The size, complexity, or strategic value of this deal warrants involvement from a Senior Account Executive or your sales manager before the next customer touchpoint. Prepare a concise deal brief covering what you know about budget, authority, need, and timeline, along with the key risks and open questions. Request an internal sync within 24 hours so the Senior AE can assess whether to co-own or take the lead on the account. Do not make promises to the prospect about pricing, timelines, or product roadmap until internal alignment is confirmed.
  code: SALES-QL-004

Machine Access

Questions in this decision tree

Possible outcomes

How to use this decision tree

Click "Open interactive version" to step through the questions. Your answers narrow the tree until a recommended outcome is reached. You can also embed this tree on your own site.

More decision trees by Andrew

Which API design pattern is right for my project?
Which API design pattern is right for my project?
Determine the right API design style for your integration scenario.
Authentication Method Selection
Authentication Method Selection
Authentication is a security-critical, high-friction decision to reverse — migrating users from one auth method to another requires coordinated password resets or credential migration campaigns. This tree eliminates methods that don't match your user type, enterprise requirements, and security posture, giving you a clear shortlist before you write a line of code.
Caching Strategy Selection
Caching Strategy Selection
Premature or misapplied caching adds complexity — stale data bugs, invalidation logic, and distributed consistency problems — without solving the actual bottleneck. This tree routes you to the caching pattern that matches your data access profile, so you apply the right tool to the right problem rather than defaulting to Redis for everything.
CI/CD Pipeline Tool Selection
CI/CD Pipeline Tool Selection
Choosing a CI/CD platform is a long-term infrastructure commitment — pipelines accumulate config, custom scripts, and team muscle memory that make switching painful. This tree eliminates tools that don't fit your source control host, infrastructure model, or team scale, leaving only the options genuinely viable for your situation.
Which cloud provider should I use — AWS, Azure, or Google Cloud?
Which cloud provider should I use — AWS, Azure, or Google Cloud?
Answer a few questions to identify the most suitable cloud platform for your workload.
Container Orchestration Platform Selection
Container Orchestration Platform Selection
Container orchestration is foundational infrastructure — the platform you choose shapes how you deploy, scale, network, and operate every service you run. This tree eliminates options that don't match your operational maturity, cloud provider commitment, and workload complexity, so you land on the platform that fits your team today without over-engineering for a scale you haven't reached.