Back to Details

lead-qualification-bant

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Lead Qualification: BANT

潜在客户资格认定：BANT

Systematically qualify leads using the BANT framework to identify sales-ready opportunities and prioritize follow-up efforts.
借助BANT框架系统化筛选潜在客户，识别可推进销售的机会并确定跟进优先级。

When to Use This Skill

何时使用该技能

  • Discovery calls with inbound leads
  • Qualifying outbound responses
  • Training SDRs on qualification
  • Building qualification scorecards
  • Improving lead handoff quality
  • 与inbound线索的挖掘式通话
  • 筛选outbound线索的回复
  • 培训SDR（销售开发代表）掌握资格认定方法
  • 构建资格认定评分卡
  • 提升线索交接质量

Methodology Foundation

方法论基础

Based on the IBM BANT Framework (Budget, Authority, Need, Timeline), modernized with:
  • Consultative discovery approach
  • Scoring-based qualification
  • Flexible question sequencing
  • Modern buying committee awareness
基于IBM BANT框架（预算Budget、权限Authority、需求Need、时间线Timeline），并结合以下内容进行了现代化升级：
  • 顾问式挖掘方法
  • 基于评分的资格认定机制
  • 灵活的问题排序逻辑
  • 对现代采购委员会的认知

What Claude Does vs What You Decide

Claude的工作 vs 你的决策

Claude DoesYou Decide
Structures BANT questionsQualification threshold
Scores responsesHandoff criteria
Identifies gapsFollow-up approach
Suggests next stepsException handling
Creates call guidesDisqualification rules
Claude的工作你的决策
构建BANT问题框架资格认定阈值
对回复进行评分线索交接标准
识别资格认定缺口跟进策略
建议后续步骤特殊情况处理规则
创建通话指南淘汰规则

Instructions

操作步骤

Step 1: Understand BANT Components

步骤1：理解BANT的核心要素

ComponentQuestionWhy It Matters
BudgetCan they afford it?No budget = no deal
AuthorityCan they decide?Need decision maker
NeedDo they need it?Problem = urgency
TimelineWhen will they decide?Forecasting
核心要素问题示例重要性
预算Budget他们是否有能力承担？没有预算就没有成交可能
权限Authority他们是否有决策权？需要对接决策人
需求Need他们是否有相关需求？问题=紧迫性
时间线Timeline他们何时会做出决策？便于销售预测

Step 2: Design Discovery Questions

步骤2：设计挖掘式问题

Budget Questions:
  • Direct: "What budget have you allocated for this?"
  • Indirect: "How are initiatives like this typically funded?"
  • Value-based: "If we could solve [problem], what would that be worth?"
Authority Questions:
  • "Who else needs to be involved in this decision?"
  • "Walk me through how decisions like this are typically made."
  • "Who signs off on purchases in this range?"
Need Questions:
  • "What prompted you to look into this now?"
  • "What happens if you don't solve this?"
  • "How is this problem affecting [metrics/team/goals]?"
Timeline Questions:
  • "When are you hoping to have a solution in place?"
  • "What's driving that timeline?"
  • "What needs to happen before a decision can be made?"
预算相关问题：
  • 直接提问："您为此分配了多少预算？"
  • 间接提问："这类项目通常是如何获得资金支持的？"
  • 价值导向："如果我们能解决[具体问题]，这对您来说价值几何？"
权限相关问题：
  • "还有哪些人需要参与这个决策？"
  • "请介绍一下这类决策通常的制定流程。"
  • "这个预算级别的采购需要谁签字批准？"
需求相关问题：
  • "是什么促使您现在开始关注这个领域？"
  • "如果不解决这个问题会有什么后果？"
  • "这个问题对[指标/团队/目标]有哪些影响？"
时间线相关问题：
  • "您希望何时能落实解决方案？"
  • "是什么驱动这个时间节点？"
  • "在做出决策前还需要完成哪些事项？"

Step 3: Score Each Component

步骤3：对各核心要素评分

ScoreCriteria
3Strong - Clear, confirmed
2Moderate - Indicated but not confirmed
1Weak - Vague or unclear
0None - Not present or disqualifying
Qualification Threshold:
  • 10-12: Sales-ready (SQL)
  • 7-9: Needs development (MQL)
  • <7: Not qualified (Nurture/Disqualify)
评分标准
3优秀 - 清晰且已确认
2良好 - 有提及但未确认
1一般 - 模糊或不明确
0不合格 - 无相关信息或直接淘汰
资格认定阈值：
  • 10-12分：可推进销售（SQL，销售合格线索）
  • 7-9分：需进一步培育（MQL，营销合格线索）
  • 低于7分：不合格（培育/淘汰）

Examples

示例

Example 1: Discovery Call Guide

示例1：挖掘式通话指南

Output:
undefined
输出：
undefined

BANT Discovery Call Guide

BANT挖掘式通话指南

Call Structure (30 minutes)

通话结构（30分钟）

PhaseTimeFocus
Opener3 minRapport, agenda
Context5 minSituation questions
Need8 minProblem discovery
Authority5 minDecision process
Budget4 minInvestment capacity
Timeline3 minDecision timing
Wrap-up2 minNext steps
阶段时长重点
开场3分钟建立rapport、介绍议程
背景了解5分钟现状问题提问
需求挖掘8分钟问题发现
权限确认5分钟决策流程
预算探讨4分钟投入能力
时间线确认3分钟决策时机
收尾2分钟后续步骤

Opening Script

开场脚本

"Thanks for taking the time, [Name]. Before we dive in, I'd love to understand what's happening on your end so I can make this as useful as possible for you.
I'll ask some questions to understand your situation, and you can ask me anything about [Company/Product]. Sound good?
What prompted you to take this call today?"
"感谢您抽出时间，[姓名]。在深入交流前，我想先了解您这边的情况，以便让本次沟通更有价值。
我会问一些问题来了解您的现状，您也可以随时询问关于[公司/产品]的任何问题。没问题吧？
是什么促使您今天参与这次通话的？"

Need Discovery

需求挖掘

Situation Questions:
  • "Tell me about your current [process/tool/approach]."
  • "How long have you been doing it this way?"
  • "How many people/deals/projects does this affect?"
Problem Questions:
  • "What's the biggest challenge you're facing with [area]?"
  • "How is that impacting [team/revenue/efficiency]?"
  • "What have you tried to solve this?"
Implication Questions:
  • "What happens if this doesn't get solved this year?"
  • "How does this affect your ability to [hit goals]?"
  • "What's the cost of the status quo?"
Scoring Need:
SignalScore
Clear, urgent problem with measurable impact3
Problem acknowledged, some urgency2
Problem exists but low priority1
No clear problem or "just looking"0
现状问题：
  • "请介绍一下您当前的[流程/工具/方法]。"
  • "您采用这种方式多久了？"
  • "这会影响到多少人/交易/项目？"
问题类问题：
  • "您在[该领域]面临的最大挑战是什么？"
  • "这对[团队/收入/效率]有哪些影响？"
  • "您尝试过哪些解决方法？"
影响类问题：
  • "如果今年不解决这个问题会有什么后果？"
  • "这会如何影响您达成[目标]的能力？"
  • "维持现状的成本是多少？"
需求评分标准：
信号评分
明确、紧急且有可衡量影响的问题3
已确认问题，有一定紧迫性2
存在问题但优先级低1
无明确问题或仅“了解一下”0

Authority Discovery

权限挖掘

Questions:
  • "Who else would need to be involved in evaluating a solution like this?"
  • "Walk me through how you've made similar decisions in the past."
  • "If you decided to move forward, what would the approval process look like?"
  • "Is there anyone who could block or slow down this decision?"
Follow-up mapping:
  • "Besides yourself, who would use this day-to-day?"
  • "Who would need to sign off on the budget?"
  • "Is there a procurement or legal review process?"
Scoring Authority:
SignalScore
Economic buyer, can sign contract3
Key influencer, direct access to buyer2
User/evaluator, no budget control1
No influence, wrong contact0
问题：
  • "还有哪些人需要参与这类解决方案的评估？"
  • "请介绍一下您过去制定类似决策的流程。"
  • "如果您决定推进，审批流程是怎样的？"
  • "是否有人可能会阻碍或延缓这个决策？"
跟进问题：
  • "除您之外，还有哪些人会日常使用这个产品？"
  • "预算审批需要谁签字？"
  • "是否需要经过采购或法务审核？"
权限评分标准：
信号评分
经济采购决策人，可签署合同3
关键影响者，可直接对接决策人2
用户/评估者，无预算控制权1
无影响力，对接对象错误0

Budget Discovery

预算挖掘

Soft Questions (Start Here):
  • "How are initiatives like this typically funded—is it department budget, or does it come from elsewhere?"
  • "Have you set aside budget for solving [problem] this year?"
  • "When you've purchased [similar solutions] before, how did the funding work?"
Direct Questions (If Appropriate):
  • "What budget range are you working with?"
  • "Our solutions typically range from $X to $Y—does that align with your expectations?"
  • "Is budget already approved, or is that part of the process?"
Value-Based (If Hesitant):
  • "If we could save you [X hours/dollars/etc], what would that be worth to the business?"
  • "What's the cost of not solving this problem?"
Scoring Budget:
SignalScore
Budget allocated, confirmed range3
Budget not set but path to funding clear2
"We'd need to find budget"1
No budget, no path to funding0
温和提问（优先使用）：
  • "这类项目通常如何获得资金支持——是部门预算还是其他渠道？"
  • "您今年是否为解决[该问题]预留了预算？"
  • "您过去采购[类似解决方案]时，资金是如何落实的？"
直接提问（视情况使用）：
  • "您的预算范围是多少？"
  • "我们的解决方案价格通常在$X到$Y之间——这与您的预期是否相符？"
  • "预算是否已经获批，还是需要走审批流程？"
价值导向提问（对方犹豫时）：
  • "如果我们能为您节省[X小时/美元等]，这对企业来说价值几何？"
  • "不解决这个问题的成本是多少？"
预算评分标准：
信号评分
已分配预算，且确认了具体范围3
未设定预算但有明确的资金获取路径2
"我们需要寻找预算"1
无预算，也没有资金获取路径0

Timeline Discovery

时间线挖掘

Questions:
  • "When are you hoping to have a solution in place?"
  • "What's driving that timeline?"
  • "Is there an event or deadline that's creating urgency?"
  • "What needs to happen between now and a decision?"
Red Flags:
  • "No rush" / "Just exploring"
  • "Maybe next year"
  • "We'll see how this goes"
Green Flags:
  • Specific date or quarter
  • External event driving urgency
  • Already evaluated competitors
Scoring Timeline:
SignalScore
Decision within 30 days, specific date3
Decision within 90 days, general timeline2
"This quarter" or "this year"1
"No timeline" or "just exploring"0
问题：
  • "您希望何时能落实解决方案？"
  • "是什么驱动这个时间节点？"
  • "是否有某个事件或截止日期带来了紧迫性？"
  • "从现在到做出决策前还需要完成哪些事项？"
红色预警信号：
  • "不着急" / "只是了解一下"
  • "可能明年"
  • "看看情况再说"
绿色积极信号：
  • 具体日期或季度
  • 外部事件带来紧迫性
  • 已在评估竞争对手
时间线评分标准：
信号评分
30天内做出决策，有具体日期3
90天内做出决策，有大致时间线2
"本季度"或"今年内"1
"无时间计划"或"只是了解一下"0

Wrap-Up & Next Steps

收尾与后续步骤

If Qualified (Score 10+): "Based on what you've shared, I think there's a strong fit here. Here's what I'd suggest as next steps:
  1. [Schedule demo with AE]
  2. [Send relevant case study]
  3. [Intro to additional stakeholders]
Does that work for you?"
If Needs Development (Score 7-9): "I appreciate your time today. It sounds like [summarize situation].
Before we move forward, it might make sense to [address gap]. Would it help if I [offer value]?
Let's reconnect in [timeframe] to see where things stand."
If Not Qualified (Score <7): "Thanks for the conversation. Based on what you've shared, it sounds like [timing/budget/need] might not be right for a deeper evaluation right now.
I'm going to add you to our newsletter so you stay in the loop, and I'll check back in [timeframe].
Sound good?"
undefined
若合格（评分10+）： "根据您分享的信息，我认为我们的匹配度很高。我建议后续按以下步骤推进：
  1. [安排与销售AE的演示]
  2. [发送相关案例研究]
  3. [介绍给其他相关利益相关者]
这样安排可以吗？"
若需培育（评分7-9）： "感谢您今天的时间。听起来[总结现状]。
在推进之前，可能需要先[解决缺口]。如果我[提供价值支持]会有帮助吗？
我们在[具体时间]再联系，看看进展如何。"
若不合格（评分<7）： "感谢您的交流。根据您分享的信息，目前[时间/预算/需求]可能还不适合深入评估。
我会把您加入我们的通讯列表，以便您及时了解动态，我会在[具体时间]再联系您。
可以吗？"
undefined

Example 2: Lead Scoring

示例2：线索评分

Input:
Score this discovery call:

Lead: Sarah, VP of Sales at TechCorp (200 employees, B2B SaaS)

Call notes:
- They're struggling with sales forecasting accuracy
- Current process: spreadsheets, very manual
- Problem: missed quarters twice last year
- Sarah said "This is one of my top 3 priorities"
- Budget: "We have money set aside, around $30-40K"
- Decision: Sarah + CEO would need to approve
- Timeline: Want something in place by end of Q1
- Also evaluating one competitor
Output:
undefined
输入：
为这次挖掘式通话评分：

潜在客户：Sarah，TechCorp公司销售副总裁（200名员工，B2B SaaS企业）

通话记录：
- 他们在销售预测准确性方面存在困难
- 当前流程：手动使用电子表格
- 问题：去年有两个季度未达成目标
- Sarah表示"这是我的三大优先事项之一"
- 预算："我们预留了资金，大约3-4万美元"
- 决策：Sarah + CEO需要批准
- 时间线：希望在Q1末落实解决方案
- 同时在评估一家竞争对手
输出：
undefined

BANT Qualification Score: Sarah @ TechCorp

BANT资格认定评分：TechCorp公司的Sarah

Overall Score: 11/12 ⭐ SALES QUALIFIED

总评分：11/12 ⭐ 销售合格

Component Breakdown

各核心要素评分明细

Need: 3/3 ✅

需求：3/3 ✅

Evidence:
  • Specific problem: forecasting accuracy
  • Measurable impact: missed quarters twice
  • Priority confirmed: "top 3 priorities"
  • Current solution: manual spreadsheets (pain point)
Assessment: Clear, urgent, quantifiable need.
依据：
  • 具体问题：预测准确性不足
  • 可衡量影响：两个季度未达成目标
  • 已确认优先级："三大优先事项之一"
  • 当前方案：手动电子表格（痛点）
评估： 明确、紧急且可量化的需求。

Authority: 3/3 ✅

权限：3/3 ✅

Evidence:
  • VP of Sales = key decision maker
  • Identified CEO as co-decider
  • No mention of procurement blockers
Assessment: Strong authority. Champion and economic buyer access.
依据：
  • 销售副总裁=关键决策人
  • 已确认CEO为共同决策人
  • 未提及采购障碍
评估： 权限充足，对接了发起人和经济决策人。

Budget: 3/3 ✅

预算：3/3 ✅

Evidence:
  • Budget explicitly set aside
  • Range provided: $30-40K
  • Indicates planning and approval
Assessment: Confirmed budget, specific range, ready to purchase.
依据：
  • 明确预留了预算
  • 提供了具体范围：3-4万美元
  • 表明已完成规划和审批
评估： 预算已确认，有具体范围，可推进采购。

Timeline: 2/3 ⚠️

时间线：2/3 ⚠️

Evidence:
  • "End of Q1" = specific deadline
  • Evaluating competitor = active process
  • But: Q1 could be 3-4 months out
Assessment: Good timeline but not immediate. Slight risk of delay.
依据：
  • "Q1末"=明确截止日期
  • 正在评估竞争对手=活跃决策流程
  • 但：Q1可能还有3-4个月时间
评估： 时间线良好但非紧急，存在轻微延迟风险。

Qualification Summary

资格认定总结

ComponentScoreStatus
Need3/3✅ Strong
Authority3/3✅ Strong
Budget3/3✅ Strong
Timeline2/3⚠️ Good
Total11/12SQL
核心要素评分状态
需求3/3✅ 优秀
权限3/3✅ 优秀
预算3/3✅ 优秀
时间线2/3⚠️ 良好
总计11/12SQL

Recommendation

建议

Status: Sales Qualified Lead (SQL)
Handoff Notes for AE:
  • Strong pain point: forecasting failures costing them quarters
  • Budget confirmed at $30-40K
  • Key stakeholders: Sarah (VP Sales) + CEO
  • Timeline: EOQ1 (track for potential slip)
  • Competition: 1 competitor being evaluated
Suggested Next Steps:
  1. Immediately warm handoff to AE
  2. Schedule demo within 48 hours
  3. Send forecasting case study
  4. Identify CEO meeting opportunity
Risk to Monitor:
  • Timeline could slip if Q1 pressure eases
  • Competitor evaluation ongoing—need to differentiate
状态：销售合格线索（SQL）
给销售AE的交接说明：
  • 强烈痛点：预测失误导致季度目标未达成
  • 预算已确认：3-4万美元
  • 关键利益相关者：Sarah（销售副总裁）+ CEO
  • 时间线：Q1末（需跟踪是否延迟）
  • 竞争情况：正在评估1家竞争对手
建议后续步骤：
  1. 立即将线索交接给销售AE
  2. 在48小时内安排演示
  3. 发送销售预测相关案例研究
  4. 争取与CEO会面的机会
需监控的风险：
  • 若Q1压力缓解，时间线可能延迟
  • 竞争对手正在被评估——需突出差异化

Handoff Email Template

交接邮件模板

Subject: SQL Handoff: TechCorp - Sarah (VP Sales)

Hi [AE],

Qualified lead ready for you:

**Account:** TechCorp (200 employees, B2B SaaS)
**Contact:** Sarah, VP of Sales
**BANT Score:** 11/12

**Key Points:**
- Problem: Missed 2 quarters due to bad forecasting
- Current: Manual spreadsheets
- Budget: $30-40K set aside
- Timeline: End of Q1
- Decision: Sarah + CEO
- Competition: Evaluating 1 competitor

**Why They'll Buy:**
This is a "top 3 priority" per Sarah. They have budget, authority, and urgency. Main risk is timeline slip.

**Suggested Approach:**
Lead with forecasting accuracy story. Ask to meet CEO early.

[Your calendar link for warm intro call]

— [SDR Name]
undefined
主题：SQL线索交接：TechCorp - Sarah（销售副总裁）

您好[AE]，

以下是已合格的线索：

**客户：** TechCorp（200名员工，B2B SaaS企业）
**联系人：** Sarah，销售副总裁
**BANT评分：11/12**

**关键信息：**
- 核心痛点：预测失误导致两个季度未达成目标
- 当前方案：手动电子表格
- 预算：已预留3-4万美元
- 时间线：Q1末
- 决策人：Sarah + CEO
- 竞争情况：正在评估1家竞争对手

**他们的采购动机：**
这是Sarah的"三大优先事项"之一，他们有预算、权限和紧迫性。主要风险是时间线可能延迟。

**建议沟通策略：**
以预测准确性为切入点，尽早安排与CEO的会面。

[我的日历链接，用于安排暖场介绍通话]

—— [SDR姓名]
undefined

Skill Boundaries

技能边界

What This Skill Does Well

该技能的优势

  • Structuring qualification calls
  • Scoring leads objectively
  • Identifying qualification gaps
  • Creating handoff documentation
  • 构建资格认定通话框架
  • 客观评分潜在客户
  • 识别资格认定缺口
  • 创建交接文档

What This Skill Cannot Do

该技能的局限性

  • Replace conversation skills
  • Know your specific thresholds
  • Handle objections in real-time
  • Guarantee lead quality
  • 无法替代沟通技巧
  • 不了解您的具体阈值
  • 无法实时处理异议
  • 无法保证线索质量

References

参考资料

  • IBM BANT Original Framework
  • TOPO SDR Qualification Guide
  • Gartner B2B Buying Research
  • SalesHacker Discovery Call Guide
  • IBM BANT原始框架
  • TOPO SDR资格认定指南
  • Gartner B2B采购研究
  • SalesHacker挖掘式通话指南

Related Skills

相关技能

  • lead-qualification-meddic
    - Enterprise qualification
  • icp-matching
    - Pre-call fit assessment
  • outbound-sequencer
    - Pre-qualification outreach
  • lead-qualification-meddic
    - 企业级资格认定
  • icp-matching
    - 通话前匹配度评估
  • outbound-sequencer
    - 预资格认定触达

Skill Metadata

技能元数据

  • Domain: SDR Automation
  • Complexity: Beginner-Intermediate
  • Mode: cyborg
  • Time to Value: 30 min per call
  • Prerequisites: Basic discovery skills
  • 领域Domain: SDR自动化
  • 复杂度Complexity: 初级-中级
  • 模式Mode: 人机协作cyborg
  • 价值实现时间Time to Value: 每次通话30分钟
  • 前置要求Prerequisites: 基础挖掘沟通技能