discovery-caller

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Discovery Caller

发现式沟通策略专家

Strategic discovery call expertise for B2B sales teams — from preparation and question frameworks to qualification and documentation.
为B2B销售团队提供专业的发现式沟通策略支持——从沟通准备、提问框架到客户资质审核和成果记录全流程覆盖。

Philosophy

核心理念

Discovery isn't about pitching. It's about understanding deeply before you ever propose a solution.
The best discovery calls:
  1. Listen more than talk — Aim for 70/30 prospect-to-rep ratio
  2. Quantify everything — Pain without numbers is just complaining
  3. Map the buying committee — One champion doesn't close deals
  4. Earn the next step — Every call ends with commitment or disqualification
发现式沟通的核心不是推销,而是在提出解决方案之前深度理解客户需求
优秀的发现式沟通具备以下特征:
  1. 多听少说 — 目标是客户与销售的沟通占比为70/30
  2. 量化所有信息 — 没有数据支撑的痛点只是抱怨
  3. 梳理采购决策委员会 — 仅靠一个支持者无法完成交易
  4. 明确下一步行动 — 每一次沟通都要以获得承诺或排除不合格客户收尾

How This Skill Works

本技能的使用方式

When invoked, apply the guidelines in
rules/
organized by:
  • preparation-*
    — Pre-call research, agenda setting, hypothesis building
  • questions-*
    — SPIN framework, situational, implication questions
  • listening-*
    — Active listening, note-taking, clarification techniques
  • qualification-*
    — Budget, authority, need, timeline (BANT) and modern alternatives
  • discovery-*
    — Pain identification, stakeholder mapping, competition
  • documentation-*
    — CRM notes, next steps, handoff
调用本技能时,请遵循
rules/
目录下的相关指南,这些指南分为以下类别:
  • preparation-*
    — 沟通前调研、议程设置、假设构建
  • questions-*
    — SPIN框架、情境问题、隐含问题
  • listening-*
    — 积极倾听、记录技巧、澄清方法
  • qualification-*
    — 预算、权限、需求、时间线(BANT)及现代替代框架
  • discovery-*
    — 痛点识别、利益相关者梳理、竞品调研
  • documentation-*
    — CRM记录、下一步行动、工作交接

Core Frameworks

核心框架

The Discovery Call Arc

发现式沟通流程

┌─────────────────────────────────────────────────────────────────────┐
│                         DISCOVERY CALL ARC                          │
├─────────────────────────────────────────────────────────────────────┤
│                                                                     │
│  OPEN (5 min)         BUILD RAPPORT                                 │
│  ─────────────        Set agenda, confirm time                      │
│                                                                     │
│  SITUATION (10 min)   UNDERSTAND CONTEXT                            │
│  ─────────────────    Current state, tools, process                 │
│                                                                     │
│  PROBLEM (15 min)     UNCOVER PAIN                                  │
│  ─────────────────    Challenges, frustrations, gaps                │
│                                                                     │
│  IMPLICATION (10 min) QUANTIFY IMPACT                               │
│  ─────────────────    Cost of inaction, business impact             │
│                                                                     │
│  NEED-PAYOFF (5 min)  VISION OF SUCCESS                             │
│  ─────────────────    Ideal future state, ROI potential             │
│                                                                     │
│  CLOSE (5 min)        NEXT STEPS                                    │
│  ─────────────        Commitment, stakeholders, timeline            │
│                                                                     │
└─────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│                         DISCOVERY CALL ARC                          │
├─────────────────────────────────────────────────────────────────────┤
│                                                                     │
│  OPEN (5 min)         BUILD RAPPORT                                 │
│  ─────────────        Set agenda, confirm time                      │
│                                                                     │
│  SITUATION (10 min)   UNDERSTAND CONTEXT                            │
│  ─────────────────    Current state, tools, process                 │
│                                                                     │
│  PROBLEM (15 min)     UNCOVER PAIN                                  │
│  ─────────────────    Challenges, frustrations, gaps                │
│                                                                     │
│  IMPLICATION (10 min) QUANTIFY IMPACT                               │
│  ─────────────────    Cost of inaction, business impact             │
│                                                                     │
│  NEED-PAYOFF (5 min)  VISION OF SUCCESS                             │
│  ─────────────────    Ideal future state, ROI potential             │
│                                                                     │
│  CLOSE (5 min)        NEXT STEPS                                    │
│  ─────────────        Commitment, stakeholders, timeline            │
│                                                                     │
└─────────────────────────────────────────────────────────────────────┘

SPIN Question Framework

SPIN提问框架

TypePurposeExample
SituationUnderstand current state"Walk me through your current process for..."
ProblemSurface challenges"What's the biggest frustration with that approach?"
ImplicationQuantify impact"When that happens, what's the downstream effect on...?"
Need-PayoffEnvision solution"If you could solve that, what would it mean for...?"
类型目的示例
情境型(Situation)了解客户当前状态“请介绍一下你们目前的[某流程]运作方式?”
问题型(Problem)挖掘客户挑战“这种方式下你遇到的最大困扰是什么?”
隐含型(Implication)量化影响“当这种情况发生时,会对[某业务环节]产生哪些后续影响?”
需求-回报型(Need-Payoff)畅想解决方案价值“如果这个问题能解决,对[某业务指标]意味着什么?”

Qualification Frameworks

客户资质审核框架

FrameworkComponentsBest For
BANTBudget, Authority, Need, TimelineTransactional, lower ACV
MEDDICMetrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, ChampionEnterprise, complex
SPICEDSituation, Pain, Impact, Critical Event, DecisionModern SaaS
CHAMPChallenges, Authority, Money, PrioritizationCustomer-centric
框架组成部分适用场景
BANT预算(Budget)、权限(Authority)、需求(Need)、时间线(Timeline)交易型、低客单价业务
MEDDIC指标(Metrics)、经济决策者(Economic Buyer)、决策标准(Decision Criteria)、决策流程(Decision Process)、识别痛点(Identify Pain)、内部支持者(Champion)企业级、复杂业务
SPICED情境(Situation)、痛点(Pain)、影响(Impact)、关键事件(Critical Event)、决策(Decision)现代SaaS业务
CHAMP挑战(Challenges)、权限(Authority)、预算(Money)、优先级(Prioritization)以客户为中心的业务

Stakeholder Mapping

利益相关者梳理

                    ┌─────────────────┐
                    │ ECONOMIC BUYER  │
                    │ (Signs check)   │
                    └────────┬────────┘
              ┌──────────────┼──────────────┐
              │              │              │
     ┌────────▼────────┐     │     ┌────────▼────────┐
     │   CHAMPION      │     │     │   TECHNICAL     │
     │ (Internal sell) │     │     │   EVALUATOR     │
     └─────────────────┘     │     └─────────────────┘
                    ┌────────▼────────┐
                    │    END USERS    │
                    │  (Day-to-day)   │
                    └─────────────────┘
                    ┌─────────────────┐
                    │ ECONOMIC BUYER  │
                    │ (Signs check)   │
                    └────────┬────────┘
              ┌──────────────┼──────────────┐
              │              │              │
     ┌────────▼────────┐     │     ┌────────▼────────┐
     │   CHAMPION      │     │     │   TECHNICAL     │
     │ (Internal sell) │     │     │   EVALUATOR     │
     └─────────────────┘     │     └─────────────────┘
                    ┌────────▼────────┐
                    │    END USERS    │
                    │  (Day-to-day)   │
                    └─────────────────┘

Discovery Output Metrics

发现式沟通成果指标

MetricTargetWhy It Matters
Talk ratio<30% rep timeProspect should talk more
Questions asked10-15 per callEnough depth without interrogation
Pain points quantified2-3 minimumNumbers drive urgency
Stakeholders identified3+ rolesMulti-thread the deal
Next step commitment100%Every call earns an outcome
指标目标值重要性
销售说话占比<30%应让客户主导沟通
提问数量每次沟通10-15个足够深入且避免审问式提问
量化痛点数量至少2-3个数据能提升客户紧迫感
识别的利益相关者角色3个以上多线程推进交易
下一步行动承诺率100%每次沟通都要有明确结果

Anti-Patterns

避坑指南

  • Feature dumping — Pitching before understanding pain
  • Single-threaded — Only talking to one person
  • Surface-level discovery — Accepting first answer without going deeper
  • Unquantified pain — "It's frustrating" without business impact
  • Assumptive qualification — Guessing budget/timeline instead of asking
  • Weak close — "I'll send you some info" instead of next meeting booked
  • No preparation — Showing up without researching the prospect
  • Interrogation mode — Firing questions without building rapport
  • 盲目介绍功能 — 未理解客户痛点就开始推销
  • 单线沟通 — 仅对接一个联系人
  • 表面化沟通 — 满足于客户的第一个回答,未深入挖掘
  • 未量化痛点 — 仅停留在“这很麻烦”,未关联业务影响
  • 假设式资质审核 — 猜测预算/时间线而非直接询问
  • 模糊收尾 — 用“我会发些资料给你”代替预约下次沟通
  • 毫无准备 — 未调研客户就参与沟通
  • 审问式沟通 — 只顾提问而不建立信任关系