sales-narrative

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Sales Pitch Dunford

Dunford销售叙事法

Master April Dunford's 8-step sales narrative from "Sales Pitch" (2023). Transform your positioning into a compelling story that wins enterprise deals.

掌握April Dunford在《Sales Pitch》（2023）中提出的8步销售叙事法。将你的定位转化为有说服力的故事，拿下企业订单。

When to Use This Skill

适用场景

Structuring B2B sales presentations and demos
Creating pitch decks for complex products
Training sales teams on narrative-driven selling
Converting positioning strategy into sales conversations
Winning against entrenched competitors
Selling to enterprise buyers with long decision cycles

构建B2B销售演示与展示内容
为复杂产品创建推介PPT
培训销售团队掌握叙事驱动型销售方法
将定位策略转化为销售对话
击败占据市场优势的竞争对手
向决策周期较长的企业客户推销产品

Methodology Foundation

方法论基础

Source: April Dunford - "Sales Pitch" (2023) + "Obviously Awesome" (2019)

Core Principle: The sales pitch is the narrative implementation of positioning. A robust positioning strategy is useless if it dies in a PowerPoint deck. The pitch must follow a specific arc that establishes context before presenting the product.

Why This Matters: Without a positioning-led narrative, sales reps revert to the "Feature Dump"—opening the laptop and listing features. This forces the customer to figure out why those features matter, leading to comparison against the wrong things, focus on price, and stalled deals.

来源：April Dunford - 《Sales Pitch》（2023）+ 《Obviously Awesome》（2019）

核心原则：销售叙事是定位策略的落地表达。如果强大的定位策略只停留在PPT里，那它毫无用处。推介内容必须遵循特定的叙事逻辑，先建立背景，再推出产品。

重要性：如果没有以定位为核心的叙事逻辑，销售代表就会陷入“功能罗列”的误区——打开电脑就开始列产品功能。这会迫使客户自己去思考这些功能的价值，导致客户用错误的标准做对比、过度关注价格，最终让交易停滞。

What Claude Does vs What You Decide

Claude的工作与你的决策

Claude Does	You Decide
Structures production workflow	Final creative direction
Suggests technical approaches	Equipment and tool choices
Creates templates and checklists	Quality standards
Identifies best practices	Brand/voice decisions
Generates script outlines	Final script approval

Claude负责的工作	由你决定的事项
构建产出工作流	最终创意方向
提出技术实现思路	设备与工具选择
创建模板与检查清单	质量标准
梳理最佳实践	品牌/话术风格决策
生成脚本大纲	最终脚本审批

What This Skill Does

本技能的作用

Structures the 8-step narrative arc - From insight to close
Connects positioning to conversation - Strategy becomes pitch
Builds "The Setup" phase - Establishes context before product
Creates "The Follow-Through" - Presents solution with proof
Aligns Marketing and Sales - Same story, different formats

构建8步叙事逻辑 - 从洞察到成交的完整流程
连接定位与对话 - 让策略转化为可落地的推介内容
打造“铺垫”阶段 - 在介绍产品前先建立背景
设计“落地执行”环节 - 结合证据呈现解决方案
对齐营销与销售 - 用统一的叙事逻辑，适配不同呈现形式

How to Use

使用方法

Build a Complete Sales Pitch

构建完整销售叙事

Create a Dunford-style sales pitch for:
Product: [description]
Category: [market category]
Unique value: [differentiation]
Target buyer: [persona]
Key competitors: [alternatives they'd consider]

为以下内容创建Dunford风格的销售叙事：
产品：[产品描述]
品类：[市场品类]
独特价值：[差异化优势]
目标客户：[用户画像]
核心竞品：[客户可能考虑的替代方案]

Transform Positioning into Pitch

将定位转化为推介内容

I have this positioning:
[paste positioning canvas or statement]

Create an 8-step sales narrative from this positioning.

我的定位如下：
[粘贴定位画布或定位声明]

基于此定位创建8步销售叙事。

Review a Sales Deck

审核销售推介PPT

Review this pitch against Dunford's 8-step framework:
[paste deck outline or key slides]

Identify what's missing or out of order.

对照Dunford的8步框架审核以下推介内容：
[粘贴PPT大纲或核心幻灯片内容]

指出缺失内容或逻辑顺序问题。

Instructions

操作说明

When creating sales pitches, follow Dunford's 8-step narrative structure precisely:

创建销售叙事时，请严格遵循Dunford的8步叙事结构：

The Two-Phase Structure

两阶段结构

┌─────────────────────────────────────────────────────┐
│           THE DUNFORD SALES NARRATIVE               │
├─────────────────────────────────────────────────────┤
│                                                     │
│  PHASE 1: THE SETUP (Establishing Context)          │
│  ├── Step 1: The Insight                            │
│  ├── Step 2: The Alternatives                       │
│  └── Step 3: The Perfect World                      │
│                                                     │
│  PHASE 2: THE FOLLOW-THROUGH (The Solution)         │
│  ├── Step 4: The Introduction                       │
│  ├── Step 5: Differentiated Value                   │
│  ├── Step 6: Proof                                  │
│  ├── Step 7: Objections                             │
│  └── Step 8: The Ask                                │
│                                                     │
└─────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────┐
│           DUNFORD销售叙事框架                       │
├─────────────────────────────────────────────────────┤
│                                                     │
│  第一阶段：铺垫（建立背景）                          │
│  ├── 步骤1：行业洞察                                │
│  ├── 步骤2：现有解决方案                            │
│  └── 步骤3：理想状态                                │
│                                                     │
│  第二阶段：落地执行（呈现解决方案）                  │
│  ├── 步骤4：产品介绍                                │
│  ├── 步骤5：差异化价值                              │
│  ├── 步骤6：案例佐证                                │
│  ├── 步骤7：异议处理                                │
│  └── 步骤8：行动请求                                │
│                                                     │
└─────────────────────────────────────────────────────┘

Phase 1: THE SETUP (Establishing Context)

第一阶段：铺垫（建立背景）

Purpose: Create tension and establish buying criteria BEFORE introducing your product.

目的：在介绍产品前制造紧张感，明确客户的采购标准。

Step 1: The Insight

步骤1：行业洞察

undefined

undefined

Step 1: The Insight

步骤1：行业洞察

Purpose: Start with a statement about the customer's world that creates tension.

Format: "We've noticed that [trend or market shift]..." "There's been a fundamental change in [customer's domain]..." "[Industry] is facing a new reality: [insight]..."

What Makes a Good Insight:

Based on market research or data
Hints at a problem or opportunity
Creates tension or curiosity
Customer nods in recognition

Examples:

B2B SaaS: "We've noticed that data volumes in healthcare are doubling every 18 months, but IT budgets are staying flat."

Cybersecurity: "The average enterprise now has 76 different security tools—yet breach rates have never been higher."

HR Tech: "Remote work has fundamentally changed how employees experience culture. The old playbook doesn't work anymore."

Warning: Don't introduce your product here. Build tension first.

undefined

目的：从客户所在领域的趋势切入，制造紧张感。

表达格式： "我们注意到[行业趋势或市场变化]……" "[客户所在领域]正在发生根本性的变化……" "[行业]正面临新的现实：[洞察内容]……"

优质洞察的标准：

基于市场调研或数据
暗示问题或机遇
制造紧张感或好奇心
能让客户点头认同

示例：

B2B SaaS领域： "我们注意到医疗行业的数据量每18个月就会翻一番，但IT预算却保持不变。"

网络安全领域： "如今企业平均使用76种不同的安全工具，但数据泄露率却创下历史新高。"

人力资源科技领域： "远程办公从根本上改变了员工对企业文化的体验。旧的管理方法已经不再适用。"

注意：不要在此阶段介绍产品。先制造紧张感。

undefined

Step 2: The Alternatives

步骤2：现有解决方案

undefined

undefined

Step 2: The Alternatives

步骤2：现有解决方案

Purpose: Discuss current ways of coping. Validate the customer's pain and set up the "villain."

Format: "Most teams try to handle this by [alternative 1], [alternative 2], or [alternative 3]..." "The typical approaches are..." "What we see companies doing today is..."

Key Principle: The alternatives come directly from your Positioning Canvas (Component 1: Competitive Alternatives). This is NOT about listing competitors—it's about what customers do if your solution doesn't exist.

Common Alternatives:

The Status Quo ("living with the pain")
Manual Processes ("Excel," "the intern," "email")
In-house Solutions ("some script the CTO wrote")
Competitor Products (only if actually considered)

Examples:

Data Platform: "Most teams try to manage this with spreadsheets and manual data entry. Some hire consultants. Others build internal tools that become maintenance nightmares."

Security: "Teams typically respond by adding more point solutions—another tool for endpoints, another for cloud, another for email. Or they hire more analysts and hope they can keep up."

Then Show Why Alternatives Fail: "But here's the problem with these approaches..."

Spreadsheets: "Errors creep in, versions conflict, no real-time view"
More tools: "Creates more complexity, more alerts, more fatigue"
Hiring: "Talent is scarce and expensive; doesn't scale"

Purpose: Customer thinks "Yes, that's exactly my situation. None of those work well for me."

undefined

目的：讨论客户当前应对问题的方式，认可客户的痛点，并引出“反面角色”。

表达格式： "大多数团队会尝试通过[方案1]、[方案2]或[方案3]来应对……" "常见的做法是……" "我们观察到企业目前的应对方式是……"

核心原则：这里的解决方案直接来自你的Positioning Canvas（定位画布）的第一部分：竞争替代方案。这不是列出竞品，而是描述如果没有你的产品，客户会怎么做。

常见的现有解决方案：

维持现状（“忍受痛点”）
手动流程（“Excel表格”、“实习生处理”、“邮件沟通”）
内部自研方案（“CTO写的某个脚本”）
竞品产品（仅当客户确实会考虑时提及）

示例：

数据平台领域： "大多数团队会尝试用电子表格和手动数据录入来管理。有些会聘请咨询顾问，还有些会构建内部工具，但这些工具最终会变成维护噩梦。"

安全领域： "团队通常会添加更多单点解决方案——用于终端的工具、用于云的工具、用于邮件的工具。或者他们会雇佣更多分析师，希望能跟上节奏。"

随后说明现有方案的不足： "但这些方案存在以下问题……"

电子表格：“容易出错、版本混乱、无法实时查看数据”
更多工具：“增加复杂度、产生更多警报、导致团队疲劳”
雇佣人员：“人才稀缺且成本高昂，无法规模化”

目的：让客户觉得“没错，这就是我的处境。这些方案对我都没用。"

undefined

Step 3: The Perfect World

步骤3：理想状态

undefined

undefined

Step 3: The Perfect World

步骤3：理想状态

Purpose: Define the buying criteria BEFORE introducing your product. This "rigs the game" in your favor.

Format: "In a perfect world, you would be able to..." "What if you could..." "Ideally, a solution would..."

Key Principle: The "Perfect World" describes capabilities that YOUR product delivers uniquely well. You're setting up criteria that favor your differentiation.

Structure:

[Capability that solves pain point 1]
[Capability that solves pain point 2]
[Capability that solves pain point 3]

Examples:

Data Platform: "In a perfect world, you could:

Handle this volume automatically without adding headcount
Get real-time visibility instead of monthly reports
Trust the data without manual verification"

Security: "Ideally, you'd have:

A single view across all your tools
AI that filters real threats from noise
Response times in minutes, not days"

Why This Matters: When you later present your product, the customer evaluates it against the criteria YOU just established—not criteria from RFPs or competitors.

---

目的：在介绍产品前明确客户的采购标准。这会“引导”客户用对你有利的标准做判断。

表达格式： "在理想情况下，你希望能够……" "如果你可以……会怎么样？" "理想的解决方案应该能够……"

核心原则： “理想状态”描述的是你的产品能独特满足的能力。你要设定对你的差异化优势有利的判断标准。

结构：

[解决痛点1的能力]
[解决痛点2的能力]
[解决痛点3的能力]

示例：

数据平台领域： "在理想情况下，你可以：

无需增加人员就能处理数据量增长
获取实时数据可见性，而非月度报告
无需手动验证就能信任数据"

安全领域： "理想情况下，你希望拥有：

跨所有工具的统一视图
能区分真实威胁与无效警报的AI
以分钟而非天为单位的响应速度"

重要性：当你后续介绍产品时，客户会用你刚刚设定的标准来评估，而不是用RFP或竞品的标准。

---

Phase 2: THE FOLLOW-THROUGH (The Solution)

第二阶段：落地执行（呈现解决方案）

Purpose: Present your product as the answer to the Perfect World criteria.

目的：将产品定位为理想状态的答案。

Step 4: The Introduction

步骤4：产品介绍

undefined

undefined

Step 4: The Introduction

步骤4：产品介绍

Purpose: Now—and ONLY now—introduce your product.

Format: "That's exactly why we built [Product Name]." "[Product Name] is a [Market Category] that [one-line value prop]." "We created [Product Name] specifically to [deliver Perfect World]."

Key Elements:

Product Name
Market Category (from Positioning Canvas Component 5)
One-line connection to the Perfect World

Examples:

"That's exactly why we built DataSync—a real-time data operations platform that gives you complete visibility without adding headcount."

"Introducing SecurityHub—a unified threat intelligence platform that turns 76 tools into one command center."

Warning: Keep it brief. This is not the feature dump. Just enough to categorize what you are and bridge to the differentiation.

undefined

目的：在此阶段——且仅在此阶段——介绍你的产品。

表达格式： "这正是我们打造[产品名称]的原因。" "[产品名称]是一款[市场品类]产品，[一句话价值主张]。" "我们打造[产品名称]就是为了[实现理想状态]。"

核心要素：

产品名称
市场品类（来自Positioning Canvas的第5部分）
与理想状态的一句话关联

示例：

“这正是我们打造DataSync的原因——一款实时数据运营平台，无需增加人员就能让你获得完整的数据可见性。"

“向你介绍SecurityHub——一款统一威胁情报平台，能将76种工具整合为一个指挥中心。"

注意：保持简洁。这不是功能罗列，只需明确产品品类，并关联到理想状态即可。

undefined

Step 5: Differentiated Value

步骤5：差异化价值

undefined

undefined

Step 5: Differentiated Value

步骤5：差异化价值

Purpose: Show how the product delivers the "Perfect World" using your Unique Attributes.

Structure: For each Perfect World criterion, show:

The capability (what it does)
The unique attribute (how it works)
The value (why it matters)

Format: "We do this via our [Unique Attribute], which means [Value]." "Unlike [alternative], we [differentiation], so you get [benefit]."

Template:

Perfect World Criterion	Unique Attribute	Delivered Value
[From Step 3]	[Technical differentiator]	[Business outcome]
[From Step 3]	[Process differentiator]	[Business outcome]
[From Step 3]	[Model differentiator]	[Business outcome]

Examples:

DataSync: "Remember we said you'd want to handle volume without headcount? We do this via our AI-powered data matching engine, which runs continuously and learns your data patterns. This means you can process 10x the data with the same team."

Key Principle: Every element of Differentiated Value comes from your Positioning Canvas:

Unique Attributes → Component 2
Value → Component 3
This ensures Marketing (Canvas) and Sales (Pitch) tell the same story.

undefined

目的：展示产品如何通过独特属性实现“理想状态”。

结构：针对每个理想状态标准，展示：

能力（产品能做什么）
独特属性（实现方式）
价值（对客户的意义）

表达格式： "我们通过[独特属性]实现这一点，这意味着[价值]。" "与[现有方案]不同，我们[差异化优势]，因此你能获得[收益]。"

模板：

理想状态标准	独特属性	交付价值
[来自步骤3]	[技术差异化优势]	[业务成果]
[来自步骤3]	[流程差异化优势]	[业务成果]
[来自步骤3]	[模式差异化优势]	[业务成果]

示例：

DataSync： "还记得我们提到的无需增加人员就能处理数据量增长吗？我们通过AI驱动的数据匹配引擎实现这一点，它能持续运行并学习你的数据模式。这意味着你可以用现有团队处理10倍的数据量。"

核心原则：所有差异化价值要素都来自你的Positioning Canvas：

独特属性 → 第2部分
价值 → 第3部分
这能确保营销（画布）与销售（推介）用统一的叙事逻辑。

undefined

Step 6: Proof

步骤6：案例佐证

undefined

undefined

Step 6: Proof

步骤6：案例佐证

Purpose: Provide evidence that your claims are real.

Types of Proof:

Customer Stories "Here is [Company] that [achieved result]."

Specific numbers preferred
Named customers if possible
Similar industry/size to prospect

Third-Party Validation

Analyst reports (Gartner, Forrester)
Industry awards
Certifications

Demos/Trials "Let me show you exactly how this works..."

Self-evident proof is powerful
Seeing is believing

Data

Benchmarks
Performance metrics
Before/after comparisons

Format: "Don't just take my word for it. Here's what happened when [Customer] implemented this..."

"[Customer Name], a [similar company], saw [specific result] within [timeframe]. Here's their quote: [testimonial]"

Examples:

"Memorial Hospital implemented DataSync last year. They reduced their data processing time from 4 days to 4 hours—a 24x improvement. Their VP of Operations said: 'We finally trust our numbers.'"

Warning:

Proof must be relevant to THIS prospect
Generic case studies don't convince
Match proof to prospect's industry/size/situation

undefined

目的：提供证据证明你的主张真实可信。

佐证类型：

客户案例 "[客户公司]实现了[具体成果]。"

优先用具体数据
尽可能提及客户名称
选择与目标客户行业/规模相似的案例

第三方验证

分析师报告（Gartner、Forrester）
行业奖项
认证资质

演示/试用 "让我给你展示具体的操作方式……"

直观的证据最有说服力
眼见为实

数据对比

基准数据
性能指标
前后对比数据

表达格式： "别只听我说，看看[客户公司]使用后的效果……"

"[客户公司]，一家[相似企业]，在[时间周期]内实现了[具体成果]。他们的评价是：[客户证言]"

示例：

“纪念医院去年部署了DataSync。他们将数据处理时间从4天缩短到4小时——效率提升了24倍。他们的运营副总裁说：‘我们终于能信任自己的数据了。’"

注意：

佐证内容必须与目标客户相关
通用案例无法说服客户
匹配目标客户的行业/规模/场景

undefined

Step 7: Objections

步骤7：异议处理

undefined

undefined

Step 7: Objections (Pre-Handling Resistance)

步骤7：异议处理（提前化解顾虑）

Purpose: Address concerns BEFORE they derail the conversation.

Format: "You might be wondering about [common objection]..." "A question we often get is..." "I know what you're thinking: [objection]. Here's how we handle that..."

Common Objection Categories:

Integration/Implementation "How long does this take to implement?" "Will it work with our existing tools?"
Security/Compliance "Is this SOC 2 compliant?" "Where is data stored?"
Cost/ROI "What's the total cost of ownership?" "How do we measure success?"
Change Management "How do we get the team to adopt this?" "What about training?"

Pre-Handling Template:

"You might be worried about implementation time. Most of our customers go live in [timeframe]. Here's why: [reason]. And we provide [support]."

Examples:

"You might be thinking: 'This sounds great, but we've tried platforms before and they take forever to implement.' I get it. That's why we built a 14-day rapid deployment program. We've done this 200 times. Here's exactly what the first two weeks look like..."

Key Principle: Address the top 2-3 objections. Don't try to cover everything. Focus on objections that actually kill deals.

undefined

目的：在客户提出顾虑前主动解决，避免对话中断。

表达格式： "你可能会担心[常见异议]……" "我们经常被问到……" "我知道你在想：[异议]。我们的解决方式是……"

常见异议类别：

集成/实施 "实施需要多长时间？" "它能和我们现有工具兼容吗？"
安全/合规 "是否符合SOC 2标准？" "数据存储在哪里？"
成本/投资回报 "总拥有成本是多少？" "我们如何衡量成功？"
变更管理 "如何推动团队采用？" "培训支持是什么样的？"

提前化解模板：

"你可能担心实施时间。我们的大多数客户能在[时间周期]内上线。原因是：[具体原因]。而且我们提供[支持服务]。"

示例：

“你可能会想：‘这听起来不错，但我们之前试过类似平台，实施时间很长。’我理解。这就是为什么我们打造了14天快速部署方案。我们已经完成了200次这样的部署。以下是前两周的具体流程……"

核心原则：解决前2-3个最常见的异议。不要试图覆盖所有问题。聚焦那些会直接导致交易失败的异议。

undefined

Step 8: The Ask

步骤8：行动请求

undefined

undefined

Step 8: The Ask

步骤8：行动请求

Purpose: Close for the next step. Clear, specific, easy to say yes.

Format: "Based on what we've discussed, here's what I'd recommend as a next step..." "The logical next step would be..." "Shall we..."

Types of Asks (Progressive):

Deal Stage	The Ask
Discovery	"Can I schedule a technical deep-dive with your team?"
Demo	"Would you like to see this with your own data?"
Evaluation	"Can we set up a pilot with your team?"
Proposal	"Should I send over a formal proposal?"
Close	"Are you ready to move forward?"

Effective Ask Structure:

Summarize mutual fit
Propose specific next step
Make it easy to say yes

Examples:

"Based on what you've shared about your data challenges and what you've seen today, it sounds like there's a fit here. The next step would be a 2-hour technical session with your data team where we can map this to your specific use case. Do you have time next week?"

"You mentioned Q2 is your planning cycle. To make that timeline work, I'd recommend we do a 30-day pilot starting January 15th. I can have a proposal to you by Friday. Sound good?"

Warning:

Always have a clear next step
Make the ask specific (not "let me know")
Match urgency to their timeline

---

目的：明确提出下一步动作，内容具体、易于客户同意。

表达格式： "基于我们的讨论，我建议下一步……" "合理的下一步是……" "我们要不要……"

递进式行动请求：

交易阶段	行动请求
需求探索	"我可以和你的团队安排一次技术深度沟通吗？"
产品演示	"你想看看用你的数据演示的效果吗？"
方案评估	"我们可以和你的团队启动试点项目吗？"
提案阶段	"我给你发一份正式提案可以吗？"
成交阶段	"你准备好推进了吗？"

有效行动请求结构：

总结双方匹配点
提出具体下一步动作
让客户容易同意

示例：

“基于你分享的数据挑战和今天的演示，我们的方案非常匹配。下一步是和你的数据团队开展2小时的技术沟通，我们可以将方案映射到你的具体场景。你下周有时间吗？"

“你提到Q2是你的规划周期。为了赶上这个时间，我建议从1月15日开始启动30天试点项目。我可以在周五前给你发提案。可以吗？"

注意：

始终要有明确的下一步动作
动作要具体（不要说“等你消息”）
匹配客户的时间节奏

---

Positioning to Pitch Translation

定位到推介的转化逻辑

undefined

undefined

How Canvas Maps to Pitch

定位画布与推介内容的对应关系

Every pitch element comes from the Positioning Canvas:

Positioning Component	Pitch Element
Component 1: Competitive Alternatives	Step 2: The Alternatives
Component 2: Unique Attributes	Step 5: Differentiated Value
Component 3: Value	Step 5: Differentiated Value
Component 4: Target Market	Who you're pitching to
Component 5: Market Category	Step 4: The Introduction
Component 6: Trends	Step 1: The Insight

Result: Marketing (Canvas) and Sales (Pitch) tell the exact same story.

undefined

每个推介要素都来自Positioning Canvas：

定位画布组件	推介内容要素
组件1：竞争替代方案	步骤2：现有解决方案
组件2：独特属性	步骤5：差异化价值
组件3：价值	步骤5：差异化价值
组件4：目标市场	推介对象
组件5：市场品类	步骤4：产品介绍
组件6：行业趋势	步骤1：行业洞察

结果：营销（画布）与销售（推介）用完全统一的叙事逻辑。

undefined

Examples

示例

Example 1: B2B SaaS Security Platform

示例1：B2B SaaS安全平台

Context: Selling unified security platform to enterprise CISO

The Complete Pitch:

Step 1 - Insight: "We've been talking to CISOs all year, and there's a pattern. The average enterprise now runs 76 different security tools. And yet—breach rates have never been higher. More tools isn't making you safer. It's making you slower."

Step 2 - Alternatives: "What we see teams doing: adding more point solutions, hiring more analysts, building internal dashboards. But here's what happens:

More tools = more alerts = more fatigue
More analysts = talent wars you can't win
Internal tools = maintenance nightmare"

Step 3 - Perfect World: "Ideally, you'd have:

A single pane of glass across all your tools
AI that separates real threats from noise
Response times in minutes, not days
Your existing team 10x more effective"

Step 4 - Introduction: "That's exactly why we built ThreatHub—a unified security intelligence platform that turns your 76 tools into one command center."

Step 5 - Differentiated Value: "Here's how we deliver on that:

Single View: Our integration fabric connects to 200+ tools in days, not months. You see everything in one dashboard.
AI Triage: Our ML models learn your environment and filter 95% of noise. Your team only sees what matters.
Rapid Response: Automated playbooks cut response from hours to minutes."

Step 6 - Proof: "Don't take my word for it. Acme Financial—similar size, similar stack—deployed ThreatHub last quarter. They reduced their mean time to respond from 4 hours to 12 minutes. Their CISO said: 'We finally feel like we're ahead of the attackers instead of chasing them.'"

Step 7 - Objections: "You might be thinking: 'We've tried platforms before—they never integrate as promised.' That's fair. Here's what's different: we guarantee integration with your top 20 tools in 14 days or we pause the contract. We've done this 150 times."

Step 8 - Ask: "Based on what you've shared about your current challenges, there's clearly a fit. The next step would be a technical session with your security architects where we map this to your specific stack. Can you get them on a call next Tuesday or Wednesday?"

场景：向企业CISO推销统一安全平台

完整叙事：

步骤1 - 行业洞察： "我们今年和很多CISO交流，发现一个共性问题。如今企业平均使用76种不同的安全工具，但数据泄露率却创下历史新高。更多工具并没有让你更安全，反而让你更慢。"

步骤2 - 现有解决方案： "我们看到团队的应对方式：添加更多单点解决方案、雇佣更多分析师、构建内部仪表盘。但会出现以下问题：

更多工具 = 更多警报 = 团队疲劳
更多分析师 = 陷入人才争夺战
内部工具 = 维护噩梦"

步骤3 - 理想状态： "理想情况下，你希望拥有：

跨所有工具的统一视图
能区分真实威胁与无效警报的AI
以分钟而非天为单位的响应速度
现有团队效率提升10倍"

步骤4 - 产品介绍： "这正是我们打造ThreatHub的原因——一款统一安全情报平台，能将你的76种工具整合为一个指挥中心。"

步骤5 - 差异化价值： "我们是如何实现的：

统一视图：我们的集成框架能在数天内连接200+工具，而非数月。你可以在一个仪表盘中查看所有数据。
AI分诊：我们的机器学习模型会学习你的环境，过滤95%的无效警报。你的团队只需关注重要内容。
快速响应：自动化剧本将响应时间从小时缩短到分钟。"

步骤6 - 案例佐证： "别只听我说。Acme Financial——规模和工具栈和你相似——上个季度部署了ThreatHub。他们将平均响应时间从4小时缩短到12分钟。他们的CISO说：‘我们终于感觉能领先攻击者一步，而不是一直在追赶。’"

步骤7 - 异议处理： "你可能会想：‘我们之前试过类似平台，但集成效果从未达到承诺。’这很合理。我们的不同之处在于：我们保证在14天内完成你前20个工具的集成，否则暂停合同。我们已经完成了150次这样的集成。"

步骤8 - 行动请求： "基于你分享的当前挑战，我们的方案非常匹配。下一步是和你的安全架构师开展技术沟通，我们可以将方案映射到你的具体工具栈。你下周二或周三能安排他们参会吗？"

Example 2: HR Tech Platform

示例2：人力资源科技平台

Context: Selling employee experience platform to VP HR

Step 1 - Insight: "Remote and hybrid work changed everything about how employees experience culture. The old playbook—office perks, in-person town halls, casual conversations—doesn't work when half your team is distributed."

Step 2 - Alternatives: "Most companies try to adapt with Slack channels, occasional surveys, and virtual happy hours. But what we're hearing is:

Engagement scores are dropping
New hires feel disconnected
Culture is becoming fragmented by location"

Step 3 - Perfect World: "What if you could:

Pulse-check culture continuously, not annually
Give managers real-time visibility into team health
Create connection across locations without more meetings"

Step 4 - Introduction: "That's why we built CultureOS—an employee experience platform designed for the distributed workplace."

[Continue through Steps 5-8...]

场景：向HR副总裁推销员工体验平台

步骤1 - 行业洞察： "远程和混合办公从根本上改变了员工对企业文化的体验。旧的方法——办公室福利、线下全员大会、随意的面对面交流——在团队一半成员分布各地时已经不再适用。"

步骤2 - 现有解决方案： "大多数企业会尝试用Slack频道、偶尔的调研和线上欢乐时光来适应。但我们听到的反馈是：

员工参与度持续下降
新员工感到孤立
企业文化因地域而分裂"

步骤3 - 理想状态： "如果你可以：

持续追踪企业文化，而非仅每年一次
让管理者实时了解团队健康状况
无需增加会议就能实现跨地域连接"

步骤4 - 产品介绍： "这就是我们打造CultureOS的原因——一款为分布式办公场景设计的员工体验平台。"

[继续步骤5-8...]

Checklists & Templates

检查清单与模板

Pitch Preparation Checklist

推介准备检查清单

undefined

undefined

Before the Pitch

推介前准备

Positioning Foundation

定位基础

Pitch Construction

推介内容构建

Prospect Research

客户调研

Their current solution/stack
Recent news or changes
Key decision criteria
Timeline and budget cycle

---

客户当前解决方案/工具栈
客户近期动态
核心决策标准
时间节奏与预算周期

---

Pitch Structure Template

销售叙事模板

undefined

undefined

[Product Name] Sales Narrative

[产品名称]销售叙事

THE SETUP

铺垫阶段

Step 1: The Insight "We've noticed that [market trend/shift]..."

Step 2: The Alternatives "Most [target audience] try to solve this by:

[Alternative 1]: But [why it fails]
[Alternative 2]: But [why it fails]
[Alternative 3]: But [why it fails]"

Step 3: The Perfect World "In a perfect world, you could:

[Capability that solves pain 1]
[Capability that solves pain 2]
[Capability that solves pain 3]"

步骤1：行业洞察 "我们注意到[行业趋势/变化]……"

步骤2：现有解决方案 "大多数[目标客户]会尝试通过以下方式解决：

[方案1]：但[不足]
[方案2]：但[不足]
[方案3]：但[不足]"

步骤3：理想状态 "在理想情况下，你可以：

[解决痛点1的能力]
[解决痛点2的能力]
[解决痛点3的能力]"

THE FOLLOW-THROUGH

落地执行阶段

Step 4: The Introduction "That's exactly why we built [Product]—a [Category] that [one-liner]."

Step 5: Differentiated Value

Perfect World	How We Deliver	Unique Attribute
[Capability 1]	[Mechanism]	[Technical differentiator]
[Capability 2]	[Mechanism]	[Technical differentiator]
[Capability 3]	[Mechanism]	[Technical differentiator]

Step 6: Proof "[Customer Name], a [similar company], achieved [specific result]. Quote: '[testimonial]'"

Step 7: Objections "You might be wondering about [objection]. Here's how we handle that: [response]"

Step 8: The Ask "Based on what we discussed, the next step would be [specific action]. Does [day/time] work?"

---

步骤4：产品介绍 "这正是我们打造[产品]的原因——一款[品类]产品，[一句话价值主张]。"

步骤5：差异化价值

理想状态	实现方式	独特属性
[能力1]	[机制]	[技术差异化优势]
[能力2]	[机制]	[技术差异化优势]
[能力3]	[机制]	[技术差异化优势]

步骤6：案例佐证 "[客户公司]，一家[相似企业]，实现了[具体成果]。评价：‘[客户证言]’"

步骤7：异议处理 "你可能会担心[异议]。我们的解决方式是： [应对方案]"

步骤8：行动请求 "基于我们的讨论，下一步是[具体动作]。 [日期/时间]可以吗？"

---

Common Pitch Mistakes Checklist

常见推介错误检查清单

undefined

undefined

Red Flags to Avoid

需避免的红色预警

The Feature Dump

功能罗列

Opening with product screenshots
Listing features before establishing context
Making the customer figure out why features matter

开场就展示产品截图
在建立背景前罗列功能
让客户自己思考功能的价值

Weak Setup

铺垫薄弱

Insight is generic ("digital transformation...")
Alternatives don't match customer's reality
Perfect World doesn't favor your strengths

行业洞察过于通用（如“数字化转型……”）
现有解决方案与客户实际情况不符
理想状态标准未突出我方优势

Poor Follow-Through

落地执行不佳

Wrong Order

逻辑顺序错误

Introducing product before establishing context
Jumping to proof before differentiation
Handling objections only when raised

undefined

在建立背景前介绍产品
在展示差异化价值前先放案例佐证
仅在客户提出异议时才处理

undefined

Skill Boundaries

技能边界

What This Skill Does Well

本技能擅长

Structuring audio production workflows
Providing technical guidance
Creating quality checklists
Suggesting creative approaches

构建销售叙事工作流
提供技术指导
创建质量检查清单
提出创意方向建议

What This Skill Cannot Do

本技能无法做到

Replace audio engineering expertise
Make subjective creative decisions
Access or edit audio files directly
Guarantee commercial success

替代音频工程专业能力
做出主观创意决策
直接访问或编辑音频文件
保证商业成功

References

参考资料

Dunford, April. "Sales Pitch" (2023)
Dunford, April. "Obviously Awesome" (2019)
Part V: The Execution Layer from the Positioning Treatise
Dunford's consulting methodology for B2B sales teams

Dunford, April. 《Sales Pitch》(2023)
Dunford, April. 《Obviously Awesome》(2019)
定位论第五部分：执行层
Dunford为B2B销售团队提供的咨询方法论

Related Skills

Skill Metadata (Internal Use)

技能元数据（内部使用）

yaml

name: sales-narrative
category: sales
subcategory: pitching
version: 1.0
author: MKTG Skills
source_expert: April Dunford
source_work: Sales Pitch (2023)
difficulty: intermediate
estimated_value: $2,000 sales training workshop
tags: [sales, pitch, positioning, B2B, enterprise, narrative]
created: 2025-01-24
updated: 2025-01-24

yaml

name: sales-narrative
category: sales
subcategory: pitching
version: 1.0
author: MKTG Skills
source_expert: April Dunford
source_work: Sales Pitch (2023)
difficulty: intermediate
estimated_value: $2,000 sales training workshop
tags: [sales, pitch, positioning, B2B, enterprise, narrative]
created: 2025-01-24
updated: 2025-01-24