sales-revenue

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<objective> Comprehensive B2B sales skill covering cold outreach (email sequences, domain warming, lead scoring), revenue operations (pipeline metrics, forecasting, LTV:CAC), and sales execution (MEDDIC qualification, SPIN discovery, demo delivery, objection handling). </objective>
<quick_start> Lead scoring: Hot: 70+ | Warm: 40-69 | Nurture: <40
Pipeline coverage: 3-4x quota (SMB), 4-5x (Enterprise)
LTV:CAC ratio: Target >3:1
MEDDIC: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion
Cold email: Under 100 words, problem-forward, clear single CTA </quick_start>
<success_criteria> Sales process is successful when:
  • Leads scored and tiered (Gold/Silver/Bronze) before outreach
  • Pipeline coverage at 3-4x quota minimum
  • LTV:CAC ratio >3:1
  • MEDDIC criteria documented for each qualified opportunity
  • Demo follows RECAP → AGENDA → SHOW VALUE → SUMMARIZE → NEXT STEPS
  • Objections handled with LAER (Listen, Acknowledge, Explore, Respond) </success_criteria>
<core_content> Comprehensive B2B sales skill: outreach, revenue operations, and demo execution.
<objective> 全面的B2B销售技能,涵盖陌生开发(邮件序列、域名预热、线索评分)、营收运营(销售管道指标、预测、LTV:CAC)以及销售执行(MEDDIC资格审核、SPIN需求挖掘、产品演示交付、异议处理)。 </objective>
<quick_start> 线索评分: 高意向:70分以上 | 中意向:40-69分 | 培育:低于40分
销售管道覆盖: 3-4倍配额(中小企业SMB),4-5倍(大型企业Enterprise)
LTV:CAC比值: 目标>3:1
MEDDIC: Metrics(衡量指标)、Economic Buyer(经济决策人)、Decision Criteria(决策标准)、Decision Process(决策流程)、Identify Pain(识别痛点)、Champion(内部支持者)
陌生开发邮件: 字数少于100字,以痛点为切入点,明确单一行动号召(CTA) </quick_start>
<success_criteria> 销售流程成功的标志:
  • 开展开发前已完成线索评分与分层(金牌/银牌/铜牌)
  • 销售管道覆盖至少达到配额的3-4倍
  • LTV:CAC比值>3:1
  • 每个合格机会都已记录MEDDIC审核标准
  • 产品演示遵循RECAP(复盘)→ AGENDA(议程)→ SHOW VALUE(展示价值)→ SUMMARIZE(总结)→ NEXT STEPS(下一步)流程
  • 采用LAER法(倾听、认可、探究、回应)处理异议 </success_criteria>
<core_content> 全面的B2B销售技能:开发、营收运营与产品演示执行。

Quick Reference

快速参考

DomainKey ComponentsReference File
OutreachCold email, sequences, domain warming, lead scoring
reference/outreach.md
Revenue OpsPipeline metrics, forecasting, dashboards, attribution
reference/revenue-ops.md
DiscoveryMEDDIC, SPIN, demo flow, objection handling
reference/discovery.md

领域核心组件参考文件
开发陌生开发邮件、邮件序列、域名预热、线索评分
reference/outreach.md
营收运营销售管道指标、预测、仪表盘、归因
reference/revenue-ops.md
需求挖掘MEDDIC、SPIN、演示流程、异议处理
reference/discovery.md

Part 1: Sales Outreach

第一部分:销售开发

The GTM Pipeline

GTM销售管道

Lead Scraping → Lead Scoring → Domain Warming → Sequences → Reply Detection
     ↓              ↓              ↓               ↓             ↓
 dealer-scraper  sales-agent   cold-reach     cold-reach    sales-agent
线索抓取 → 线索评分 → 域名预热 → 邮件序列 → 回复检测
     ↓              ↓              ↓               ↓             ↓
 dealer-scraper  sales-agent   cold-reach     cold-reach    sales-agent

Lead Tiering

线索分层

TierCriteriaPriorityAction
GOLDMulti-trade, $5-50M, website, reviewsImmediatePersonalized sequence
SILVERSingle trade, has reviews or websiteWeek 1Standard sequence
BRONZEBasic listing onlyNurtureDrip campaign
层级标准优先级行动
金牌多业务线、企业规模500万-5000万美元、有官网、有客户评价立即处理个性化邮件序列
银牌单一业务线、有客户评价或官网第一周内标准邮件序列
铜牌仅基础信息列表培育跟进drip campaign(持续培育邮件)

Lead Scoring (0-100)

线索评分(0-100分)

python
scoring_factors = {
    'icp_fit': 0-30,        # Match to ideal customer profile
    'intent_signals': 0-25, # Buying signals detected
    'engagement': 0-20,     # Email opens, clicks, replies
    'timing': 0-15,         # Budget cycle, seasonality
    'budget_signals': 0-10  # Company size, funding
}
python
scoring_factors = {
    'icp_fit': 0-30,        # 与理想客户画像匹配度
    'intent_signals': 0-25, # 检测到的购买信号
    'engagement': 0-20,     # 邮件打开、点击、回复情况
    'timing': 0-15,         # 预算周期、季节性因素
    'budget_signals': 0-10  # 企业规模、融资情况
}

Thresholds: Hot: 70+ | Warm: 40-69 | Nurture: <40

阈值:高意向: 70分以上 | 中意向: 40-69分 | 培育: 低于40分

undefined
undefined

6-Agent Architecture

6-Agent架构

AgentRoleOutput
RESEARCHERCompany intel, tech stackEnriched company data
QUALIFIERICP fit scoring0-100 score + tier
ENRICHERContact discoveryVerified emails, org chart
WRITERPersonalized sequencesMulti-step email campaign
ANALYZERReply intentRoute to next action
ROUTEROrchestrationNext-best-action
Agent角色输出
研究员企业情报、技术栈丰富后的企业数据
审核员理想客户画像匹配度评分0-100分评分+层级
信息补充员联系人信息挖掘验证后的邮箱、组织架构
文案撰写员个性化邮件序列多步骤邮件营销活动
分析员回复意向判断引导至下一步行动
调度员流程编排最佳后续行动建议

Cold Email Principles

陌生开发邮件原则

  1. Short and specific - Under 100 words
  2. Problem-forward - Lead with their pain
  3. Clear CTA - One ask (usually 10-min call)
  4. Personalization - Company name, specific detail
  1. 简短具体 - 字数少于100字
  2. 痛点前置 - 以客户的痛点作为开头
  3. 明确CTA - 仅一个行动请求(通常是10分钟电话)
  4. 个性化 - 包含企业名称、具体细节

Email Sequence Structure

邮件序列结构

StepTimingPurpose
1Day 0Initial outreach - problem statement
2Day 3Follow-up - different angle
3Day 7Value add - insight or resource
4Day 10Break-up - last chance

步骤时间目的
1第0天首次开发 - 提出痛点问题
2第3天跟进 - 不同切入角度
3第7天提供价值 - 行业洞察或资源
4第10天收尾 - 最后一次尝试

Part 2: Revenue Operations

第二部分:营收运营

Core Metrics

核心指标

Pipeline Metrics

销售管道指标

yaml
pipeline_coverage:
  formula: "Pipeline Value / Quota"
  healthy: "3-4x for SMB, 4-5x for Enterprise"
  warning: "Below 3x"

pipeline_velocity:
  formula: "(# Opps x Win Rate x Avg Deal) / Cycle Days"
  use: "Predict monthly revenue"

weighted_pipeline:
  formula: "Sum of (Deal Value x Stage Probability)"
yaml
pipeline_coverage:
  formula: "Pipeline Value / Quota"
  healthy: "3-4x for SMB, 4-5x for Enterprise"
  warning: "Below 3x"

pipeline_velocity:
  formula: "(# Opps x Win Rate x Avg Deal) / Cycle Days"
  use: "Predict monthly revenue"

weighted_pipeline:
  formula: "Sum of (Deal Value x Stage Probability)"

Conversion Funnel

转化漏斗

StageFormulaBenchmark
Lead to MQLMQLs / Total Leads15-30%
MQL to SQLSQLs / MQLs30-50%
SQL to OppOpportunities / SQLs50-70%
Opp to WinClosed Won / Opportunities20-30%
OverallClosed Won / Total Leads1-5%
阶段公式基准值
线索到营销合格线索(MQL)MQL数量 / 总线索数量15-30%
MQL到销售合格线索(SQL)SQL数量 / MQL数量30-50%
SQL到销售机会机会数量 / SQL数量50-70%
机会到成交成交数量 / 机会数量20-30%
整体转化率成交数量 / 总线索数量1-5%

Unit Economics

单位经济效益

MetricFormulaHealthy
CAC(Sales + Marketing) / New CustomersDepends on ACV
LTV(ARPU x Gross Margin) / Churn Rate-
LTV:CACLTV / CAC>3:1
PaybackCAC / (ARPU x Gross Margin)<12 months
指标公式健康标准
CAC(客户获取成本)(销售费用 + 营销费用) / 新客户数量取决于ACV(平均客户生命周期价值)
LTV(客户生命周期价值)(ARPU x 毛利率) / 客户流失率-
LTV:CACLTV / CAC>3:1
回收期CAC / (ARPU x 毛利率)<12个月

Pipeline Stages

销售管道阶段

StageProbabilityEntry Criteria
Lead5%Contact captured
MQL10%Meets ICP
SQL20%BANT confirmed
Discovery30%Meeting scheduled
Demo50%Demo completed
Proposal70%Proposal sent
Negotiation85%Terms discussed
Closed Won100%Contract signed
阶段成交概率进入标准
线索5%已获取联系人信息
MQL10%符合理想客户画像
SQL20%BANT标准已确认
需求挖掘30%已安排会议
产品演示50%已完成产品演示
提案70%已发送提案
谈判85%已讨论合作条款
成交100%已签署合同

Forecasting Methods

预测方法

MethodFormulaBest For
Pipeline-basedSum(Deal x Stage Probability)Simple, data-driven
HistoricalHistorical conversion x PipelinePast performance
Commit-basedRep commits + Manager adjustmentIncorporates judgment

方法公式适用场景
基于销售管道求和(单机会价值 x 阶段成交概率)简单、数据驱动
基于历史数据历史转化率 x 当前销售管道参考过往表现
基于承诺销售代表承诺业绩 + 经理调整结合主观判断

Part 3: Demo & Discovery

第三部分:产品演示与需求挖掘

Call Structure

电话流程

StageGoalDuration
OpeningBuild rapport, set agenda2-3 min
DiscoveryUncover pain, qualify15-20 min
DemoShow relevant value15-20 min
CloseAgree next steps5 min
阶段目标时长
开场建立信任、设定议程2-3分钟
需求挖掘挖掘痛点、资格审核15-20分钟
产品演示展示相关价值15-20分钟
收尾确认下一步5分钟

SPIN Questioning

SPIN提问法

TypePurposeExample
SituationUnderstand context"Walk me through your current process..."
ProblemSurface pain"What challenges do you face with...?"
ImplicationDeepen pain"What happens when that goes wrong?"
Need-PayoffEnvision solution"If you could fix that, what would change?"
类型目的示例
Situation(现状)了解背景"请介绍一下你们当前的业务流程..."
Problem(问题)挖掘痛点"你们在[某方面]面临哪些挑战?"
Implication(影响)深化痛点认知"当这个问题出现时,会带来哪些后果?"
Need-Payoff(需求-收益)畅想解决方案价值"如果能解决这个问题,会给你们带来什么改变?"

MEDDIC Qualification

MEDDIC资格审核

LetterElementKey Question
MMetricsWhat's the measurable impact?
EEconomic BuyerWho controls budget?
DDecision CriteriaHow will they decide?
DDecision ProcessWhat are steps to buy?
IIdentify PainWhat's compelling reason to act?
CChampionWho's selling internally?
字母要素核心问题
MMetrics(衡量指标)可衡量的业务影响是什么?
EEconomic Buyer(经济决策人)谁掌控预算?
DDecision Criteria(决策标准)他们将以什么标准做决策?
DDecision Process(决策流程)采购流程有哪些步骤?
IIdentify Pain(识别痛点)促使他们采取行动的核心痛点是什么?
CChampion(内部支持者)谁会在内部推动合作?

Demo Best Practices

产品演示最佳实践

1. RECAP (2 min)
   "Based on our discovery, you mentioned [pain 1], [pain 2]..."

2. AGENDA (1 min)
   "I'll show how we address each. Stop me anytime."

3. SHOW VALUE (15-20 min)
   Pain -> Feature -> Benefit -> Proof (repeat for each pain)

4. SUMMARIZE (2 min)
   "So you'd be able to [benefit 1], [benefit 2]..."

5. NEXT STEPS (5 min)
   "What questions? What's our next step?"
1. RECAP(复盘,2分钟)
   "根据我们的需求挖掘,您提到了[痛点1]、[痛点2]..."

2. AGENDA(议程,1分钟)
   "我将展示我们如何解决这些问题,随时可以打断我。"

3. SHOW VALUE(展示价值,15-20分钟)
   痛点 -> 功能 -> 收益 -> 案例证明(针对每个痛点重复此流程)

4. SUMMARIZE(总结,2分钟)
   "所以您将能够实现[收益1]、[收益2]..."

5. NEXT STEPS(下一步,5分钟)
   "您有什么问题?我们接下来的计划是什么?"

Demo Rules

产品演示规则

  1. Show, don't tell - Open the product, demonstrate
  2. Connect to pain - Every feature tied to their problem
  3. Pause for reactions - "How does that compare to current?"
  1. 演示而非说教 - 打开产品,实际操作展示
  2. 关联痛点 - 每个功能都要和客户的问题挂钩
  3. 暂停互动 - "这和你们当前的方案相比如何?"

Objection Handling (LAER)

异议处理(LAER法)

L - Listen (fully, don't interrupt)
A - Acknowledge (validate the concern)
E - Explore (understand the root)
R - Respond (address specifically)
ObjectionResponse Framework
"Too expensive"Acknowledge -> "Compared to what?" -> Show ROI
"Not ready"Acknowledge -> "What would need to change?" -> Pilot option
"Looking at [competitor]"Acknowledge -> "What draws you?" -> Differentiate
"Need boss approval"Acknowledge -> "What will they ask?" -> Offer to join

L - Listen(倾听,不打断)
A - Acknowledge(认可,验证顾虑)
E - Explore(探究,了解根源)
R - Respond(回应,针对性解决)
异议回应框架
"太贵了"认可 -> "和什么相比?" -> 展示投资回报率(ROI)
"还没准备好"认可 -> "需要哪些条件才会考虑?" -> 提供试点方案
"正在对比[竞品]"认可 -> "您看重他们的哪一点?" -> 突出差异化优势
"需要老板批准"认可 -> "老板会关注哪些问题?" -> 提议共同沟通

Call Prep Checklist

电话准备清单

markdown
undefined
markdown
undefined

Research (10 min)

调研(10分钟)

  • Company website - recent news
  • LinkedIn - prospect background
  • Tech stack - BuiltWith, job postings
  • Competitors they might use
  • 企业官网 - 近期新闻
  • LinkedIn - 客户背景
  • 技术栈 - BuiltWith、招聘信息
  • 他们可能使用的竞品

Preparation (5 min)

准备(5分钟)

  • Hypothesis: Why might they need us?
  • 3 discovery questions ready
  • Demo environment ready
  • Clear next step in mind
  • 假设:他们为什么需要我们的产品?
  • 准备3个需求挖掘问题
  • 演示环境就绪
  • 明确预期的下一步

Mindset

心态

  • Curiosity, not pitch mode
  • Understand their world first

---
  • 保持好奇心,而非推销模式
  • 先了解他们的业务场景

---

Weekly Pipeline Review Template

每周销售管道复盘模板

markdown
undefined
markdown
undefined

Coverage Check

覆盖情况检查

  • Current pipeline: $___
  • Quota this month: $___
  • Coverage ratio: ___x (target: 3-4x)
  • 当前销售管道金额:$___
  • 本月配额:$___
  • 覆盖倍数:___x(目标:3-4x)

Stage Movement

阶段流转

StageStartEndNet
Discovery
Demo
Proposal
阶段期初数量期末数量净变化
需求挖掘
产品演示
提案

Deals at Risk

风险机会

DealAmountDays in StageRisk
机会金额停留天数风险点

Action Items

行动项

  • Stalled deals to address
  • Proposals to follow up
  • Deals to close this week

---
  • 跟进停滞的机会
  • 跟进已发送的提案
  • 本周需成交的机会

---

Integration Notes

集成说明

  • Email Tools: Instantly.ai, Apollo.io, custom SMTP
  • CRM: Salesforce, HubSpot, Airtable
  • Enrichment: Clearbit, ZoomInfo, LinkedIn, Hunter.io
  • Related Projects: cold-reach, sales-agent, dealer-scraper-mvp
  • 邮件工具: Instantly.ai, Apollo.io, 自定义SMTP
  • CRM: Salesforce, HubSpot, Airtable
  • 信息补充: Clearbit, ZoomInfo, LinkedIn, Hunter.io
  • 相关项目: cold-reach, sales-agent, dealer-scraper-mvp

Reference Files

参考文件

  • reference/outreach.md
    - Email templates, domain warming, agent architecture
  • reference/revenue-ops.md
    - Metrics, dashboards, forecasting
  • reference/discovery.md
    - MEDDIC scorecard, demo scripts, objection library </core_content>
  • reference/outreach.md
    - 邮件模板、域名预热、Agent架构
  • reference/revenue-ops.md
    - 指标、仪表盘、预测
  • reference/discovery.md
    - MEDDIC评分卡、演示脚本、异议处理库 </core_content>