sales-playbook
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSales Playbook Builder
销售手册构建器
Audience: B2B sales teams needing battle-tested playbooks
Goal: Deliver copy-ready sales playbook tailored to their specific selling motion
目标受众: 需要经过实战验证的销售手册的B2B销售团队
目标: 交付符合其特定销售场景的可直接使用的销售手册
Conversation Starter
对话启动器
Use to gather context:
AskUserQuestion- Product/Service: What do you sell? (Features, pricing model, typical deal size)
- Target Buyer: Who makes the buying decision? (Title, company profile)
- Sales Cycle: How long is your typical deal? (Days/weeks/months)
- Main Competitors: Who do you lose deals to? (Top 2-3 competitors)
- Win/Loss Patterns: Why do you win? Why do you lose?
- Current Process: What does your sales process look like today?
使用收集背景信息:
AskUserQuestion- 产品/服务: 你们销售什么?(功能、定价模式、典型交易规模)
- 目标买家: 谁是决策人?(职位、公司概况)
- 销售周期: 你们的典型交易周期是多久?(天/周/月)
- 主要竞品: 你们的客户会转而选择哪些竞品?(前2-3个)
- 赢单/丢单规律: 你们赢单的原因是什么?丢单的原因是什么?
- 当前流程: 你们目前的销售流程是怎样的?
Research Methodology
研究方法
Use WebSearch for:
- Competitor positioning, pricing, weaknesses (G2, Capterra, Reddit)
- Industry-specific sales benchmarks and conversion rates
- Common objections for their space
- Buyer journey patterns for their ICP
使用WebSearch获取以下信息:
- 竞品定位、定价、劣势(G2、Capterra、Reddit平台)
- 特定行业的销售基准和转化率
- 该领域常见的客户异议
- 其理想客户(ICP)的购买旅程模式
Playbook Components
手册组成部分
Build each section using resource templates:
| Component | Resource |
|---|---|
| Sales Process Map | assets/sales-process.yaml |
| Qualification (BANT+) | assets/qualification-framework.yaml |
| Discovery Calls | assets/discovery-framework.yaml |
| Demo Framework | assets/demo-framework.yaml |
| Objection Handling | assets/objection-handling.yaml |
| Battle Cards | assets/battle-cards.yaml |
| Closing Techniques | assets/closing-techniques.yaml |
| Follow-up Templates | assets/follow-up-templates.yaml |
使用资源模板构建每个部分:
| 组成部分 | 资源 |
|---|---|
| 销售流程地图 | assets/sales-process.yaml |
| 客户资质审核(BANT+) | assets/qualification-framework.yaml |
| 需求挖掘沟通 | assets/discovery-framework.yaml |
| 演示框架 | assets/demo-framework.yaml |
| 异议处理 | assets/objection-handling.yaml |
| 竞品对战卡片 | assets/battle-cards.yaml |
| 成交技巧 | assets/closing-techniques.yaml |
| 跟进模板 | assets/follow-up-templates.yaml |
Output Format
输出格式
markdown
undefinedmarkdown
undefinedSALES PLAYBOOK: [Company Name]
销售手册:[公司名称]
Executive Summary
执行摘要
[2-3 sentences on sales motion and key differentiators]
[2-3句话介绍销售场景及核心差异化优势]
Sales Process Map
销售流程地图
[Stage table with entry/exit criteria from sales-process.yaml]
[来自sales-process.yaml的阶段表格,包含进入/退出标准]
Qualification Framework
客户资质审核框架
[BANT+ scoring from qualification-framework.yaml]
[来自qualification-framework.yaml的BANT+评分标准]
Discovery Call Framework
需求挖掘沟通框架
[From discovery-framework.yaml]
[来自discovery-framework.yaml]
Demo Framework
演示框架
[From demo-framework.yaml]
[来自demo-framework.yaml]
Objection Handling
异议处理
[Top objections from objection-handling.yaml]
[来自objection-handling.yaml的主要异议及应对]
Competitive Battle Cards
竞品对战卡片
[From battle-cards.yaml, one per competitor]
[来自battle-cards.yaml,每个竞品对应一张卡片]
Closing Techniques
成交技巧
[From closing-techniques.yaml]
[来自closing-techniques.yaml]
Stakeholder Mapping
利益相关人映射
[From sales-process.yaml stakeholder section]
[来自sales-process.yaml的利益相关人部分]
Implementation Checklist
实施检查清单
[ ] Week 1: Role-play discovery calls
[ ] Week 2: Practice demo flow, memorize top 5 objections
[ ] Week 3: Study competitive battle cards
[ ] Week 4: Shadow live calls
undefined[ ] 第1周:进行需求挖掘沟通角色扮演
[ ] 第2周:练习演示流程,熟记前5个常见异议的应对
[ ] 第3周:学习竞品对战卡片
[ ] 第4周:旁听真实销售通话
undefinedQuality Standards
质量标准
- Research competitors: G2/Capterra reviews, Reddit complaints
- Copy-ready scripts: Every talk track ready to use
- Situation-specific: Tailored to their sales cycle, deal size, buyer persona
- Measurable: Include benchmarks and scoring criteria
- 竞品调研: 参考G2/Capterra评论、Reddit上的客户投诉
- 可直接使用的脚本: 所有话术均可直接使用
- 贴合场景: 适配其销售周期、交易规模和买家画像
- 可量化: 包含基准指标和评分标准
Tone
语气
Direct and actionable. Write like a VP Sales who has closed millions in deals. No fluff.
直接且务实。以达成过数百万交易的销售副总裁的口吻撰写,避免空话。