lead-qualification-bant

潜在客户资格评估：BANT

使用 BANT 框架系统地评估潜在客户资格，识别具备销售跟进条件的机会，并优先安排后续跟进。

何时使用此技能

• 与入站潜在客户进行需求探索通话
• 评估出站回复的资格
• 为 SDR 培训资格评估
• 制定资格评估评分卡
• 提高潜在客户交接质量

方法论基础

基于 IBM BANT 框架（预算、决策权、需求、时间线），并进行了现代化改进：

• 采用顾问式需求探索方法
• 基于评分进行资格评估
• 灵活安排问题顺序
• 关注现代采购委员会

Claude 的工作与由你决定的事项

Claude 的工作	由你决定
梳理 BANT 问题	资格评估门槛
为回答打分	交接标准
识别信息缺口	后续跟进方式
建议后续步骤	例外情况处理
创建通话指南	淘汰规则

说明

第 1 步：了解 BANT 的组成部分

组成部分	问题	重要性
预算	他们负担得起吗？	没有预算＝没有交易
决策权	他们能做决定吗？	需要找到决策者
需求	他们有这方面的需求吗？	问题带来紧迫性
时间线	他们何时会做决定？	用于预测

第 2 步：设计需求探索问题

预算问题：

• 直接询问：“您为此分配了多少预算？”
• 间接询问：“类似的项目通常如何获得资金？”
• 基于价值询问：“如果我们能解决 [问题]，这对您来说价值几何？”

决策权问题：

• “还有谁需要参与这项决策？”
• “请介绍一下类似决策通常是如何做出的。”
• “这个价格区间的采购由谁审批？”

需求问题：

• “是什么促使您现在开始了解这件事？”
• “如果您不解决这个问题，会有什么后果？”
• “这个问题对 [指标/团队/目标] 有什么影响？”

时间线问题：

• “您希望何时落实解决方案？”
• “是什么因素决定了这个时间线？”
• “做出决定前还需要完成哪些事项？”

第 3 步：为每个组成部分打分

分数	标准
3	强——明确且已确认
2	中等——有迹象但尚未确认
1	弱——含糊不清
0	无——不存在或不符合资格

资格评估门槛：

• 10-12：具备销售跟进条件（SQL）
• 7-9：需要进一步培育（MQL）
• <7：不符合资格（培育/淘汰）

示例

示例 1：需求探索通话指南

输出：

## BANT Discovery Call Guide

### Call Structure (30 minutes)

| Phase | Time | Focus |
|-------|------|-------|
| Opener | 3 min | Rapport, agenda |
| Context | 5 min | Situation questions |
| Need | 8 min | Problem discovery |
| Authority | 5 min | Decision process |
| Budget | 4 min | Investment capacity |
| Timeline | 3 min | Decision timing |
| Wrap-up | 2 min | Next steps |

---

### 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:**
| Signal | Score |
|--------|-------|
| Clear, urgent problem with measurable impact | 3 |
| Problem acknowledged, some urgency | 2 |
| Problem exists but low priority | 1 |
| No clear problem or "just looking" | 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:**
| Signal | Score |
|--------|-------|
| Economic buyer, can sign contract | 3 |
| Key influencer, direct access to buyer | 2 |
| User/evaluator, no budget control | 1 |
| No influence, wrong contact | 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:**
| Signal | Score |
|--------|-------|
| Budget allocated, confirmed range | 3 |
| Budget not set but path to funding clear | 2 |
| "We'd need to find budget" | 1 |
| No budget, no path to funding | 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:**
| Signal | Score |
|--------|-------|
| Decision within 30 days, specific date | 3 |
| Decision within 90 days, general timeline | 2 |
| "This quarter" or "this year" | 1 |
| "No timeline" or "just exploring" | 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?"

示例 2：潜在客户评分

输入：

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

输出：

## BANT Qualification Score: Sarah @ TechCorp

### Overall Score: 11/12 ⭐ SALES QUALIFIED

---

### Component Breakdown

#### Need: 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 ✅
**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.

---

#### Budget: 3/3 ✅
**Evidence:**
- Budget explicitly set aside
- Range provided: $30-40K
- Indicates planning and approval

**Assessment:** Confirmed budget, specific range, ready to purchase.

---

#### Timeline: 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.

---

### Qualification Summary

| Component | Score | Status |
|-----------|-------|--------|
| Need | 3/3 | ✅ Strong |
| Authority | 3/3 | ✅ Strong |
| Budget | 3/3 | ✅ Strong |
| Timeline | 2/3 | ⚠️ Good |
| **Total** | **11/12** | **SQL** |

---

### 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

---

### Handoff Email Template

主题：SQL 交接：TechCorp - Sarah（销售副总裁）

您好，[AE]：

有一位符合资格的潜在客户，可以交由您跟进：

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

要点：

• 问题：由于预测不准确，连续 2 个季度未达目标
• 当前做法：手动使用电子表格
• 预算：已预留 $30-40K
• 时间线：第 1 季度末
• 决策者：Sarah + CEO
• 竞争情况：正在评估 1 家竞争对手

他们会购买的原因： Sarah 表示，这是“优先级前三的事项”。他们具备预算和决策权，也有紧迫需求。主要风险是时间线延后。

建议跟进方式： 重点介绍提高预测准确性的案例。尽早提出与 CEO 会面的请求。

[您用于安排暖介绍电话的日历链接]

— [SDR 姓名]

技能边界

此技能擅长的方面

• 梳理资格评估通话
• 客观地为潜在客户打分
• 识别资格评估中的信息缺口
• 创建交接文档

此技能无法做到的事

• 取代沟通技巧
• 了解您的具体门槛
• 实时处理异议
• 保证潜在客户质量

参考资料

• IBM BANT 原始框架
• TOPO SDR 资格评估指南
• Gartner B2B 采购研究
• SalesHacker 需求探索通话指南

相关技能

• 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