sales-narrative

Dunford 销售推介

掌握 April Dunford 在《Sales Pitch》（2023）中提出的 8 步销售叙事。将你的定位转化为引人入胜、助你赢得企业级交易的故事。

何时使用此技能

• 组织 B2B 销售演示和产品演示
• 为复杂产品制作推介材料
• 培训销售团队，掌握以叙事为驱动的销售方式
• 将定位策略转化为销售对话
• 战胜根基深厚的竞争对手
• 向决策周期较长的企业买家销售

方法论基础

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

核心原则：销售推介是定位的叙事化呈现。稳健的定位策略如果只停留在 PowerPoint 幻灯片里，就毫无用处。推介必须遵循特定的叙事脉络，先建立背景，再介绍产品。

为何重要：如果没有以定位为主导的叙事，销售代表就会退回到“功能倾倒”——打开笔记本电脑，逐项罗列功能。这会迫使客户自行判断这些功能的价值，导致他们拿产品与错误的对象进行比较、关注价格，最终使交易停滞。

Claude 会做什么 vs 由你决定什么

Claude 会做什么	由你决定什么
组织制作工作流	最终创意方向
提出技术方案	设备和工具选择
创建模板和检查清单	质量标准
识别最佳实践	品牌/表达风格决策
生成脚本大纲	最终脚本审批

此技能的用途

1. 组织 8 步叙事脉络 - 从洞察到成交
2. 将定位与对话联系起来 - 将策略转化为推介
3. 构建“铺垫”阶段 - 先建立背景，再介绍产品
4. 创建“跟进呈现”阶段 - 展示解决方案并提供证据
5. 让市场营销与销售保持一致 - 同一套故事，不同的呈现形式

使用方法

制作完整的销售推介

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

将定位转化为推介

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

Create an 8-step sales narrative from this positioning.

审查销售演示文稿

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 步叙事结构：

两阶段结构

┌─────────────────────────────────────────────────────┐
│           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                                │
│                                                     │
└─────────────────────────────────────────────────────┘

---

阶段 1：铺垫（建立背景）

目的： 在介绍产品之前，营造紧迫感并确立购买标准。

第 1 步：洞察

## Step 1: The Insight

**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.

第 2 步：替代方案

## Step 2: The Alternatives

**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."

第 3 步：理想世界

## Step 3: The Perfect World

**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:**
1. [Capability that solves pain point 1]
2. [Capability that solves pain point 2]
3. [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.

---

阶段 2：跟进呈现（解决方案）

目的： 将你的产品作为满足理想世界标准的答案。

第 4 步：介绍

## Step 4: The Introduction

**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:**
1. Product Name
2. Market Category (from Positioning Canvas Component 5)
3. 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.

第 5 步：差异化价值

## Step 5: Differentiated Value

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

**Structure:**
For each Perfect World criterion, show:
1. The capability (what it does)
2. The unique attribute (how it works)
3. 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.

第 6 步：证据

## Step 6: Proof

**Purpose:** Provide evidence that your claims are real.

**Types of Proof:**

1. **Customer Stories**
"Here is [Company] that [achieved result]."
- Specific numbers preferred
- Named customers if possible
- Similar industry/size to prospect

2. **Third-Party Validation**
- Analyst reports (Gartner, Forrester)
- Industry awards
- Certifications

3. **Demos/Trials**
"Let me show you exactly how this works..."
- Self-evident proof is powerful
- Seeing is believing

4. **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

第 7 步：异议

## Step 7: Objections (Pre-Handling Resistance)

**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:**

1. **Integration/Implementation**
"How long does this take to implement?"
"Will it work with our existing tools?"

2. **Security/Compliance**
"Is this SOC 2 compliant?"
"Where is data stored?"

3. **Cost/ROI**
"What's the total cost of ownership?"
"How do we measure success?"

4. **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.

第 8 步：请求行动

## Step 8: The Ask

**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:**
1. Summarize mutual fit
2. Propose specific next step
3. 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

---

将定位转化为推介

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

示例

示例 1：B2B SaaS 安全平台

背景： 向企业 CISO 销售统一安全平台

完整推介：

步骤 1 - 洞察： “今年我们一直在和 CISO 交流，发现了一个规律。如今，企业平均运行着 76 种不同的安全工具。然而，安全漏洞发生率却前所未有地高。工具更多并不会让你更安全，只会让你行动更慢。”

步骤 2 - 替代方案： “我们看到各团队在做的事：添加更多单点解决方案、雇用更多分析师、构建内部仪表板。但结果是：

• 工具更多 = 警报更多 = 疲劳感更强
• 分析师更多 = 陷入你无法取胜的人才争夺战
• 内部工具 = 维护噩梦”

步骤 3 - 理想状态： “理想情况下，你可以拥有：

• 一个统一界面，查看所有工具
• AI 将真实威胁与噪声区分开来
• 以分钟而非天为单位的响应时间
• 让现有团队的效率提升 10 倍”

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

步骤 5 - 差异化价值： “我们通过以下方式实现这些目标：

• 统一视图：我们的集成层能在几天而非几个月内连接 200 多种工具。你可以在一个仪表板中查看所有信息。
• AI 分诊：我们的 ML 模型会学习你的环境，并过滤掉 95% 的噪声。你的团队只会看到重要信息。
• 快速响应：自动化操作手册可将响应时间从数小时缩短至数分钟。”

步骤 6 - 证明： “别光听我说。Acme Financial——规模和技术栈都与你们相似——上个季度部署了 ThreatHub。他们将平均响应时间从 4 小时缩短至 12 分钟。他们的 CISO 说：‘我们终于觉得自己领先于攻击者，而不是一直疲于追赶。’”

步骤 7 - 异议处理： “你可能会想：‘我们以前试过平台——它们从来无法按承诺完成集成。’这很合理。不同之处在于：我们保证在 14 天内集成你最常用的 20 种工具，否则我们会暂停合同。我们已经成功实施过 150 次。”

步骤 8 - 邀约： “根据你分享的当前挑战，双方显然很契合。下一步是与贵方安全架构师进行技术会议，将方案映射到你们的具体技术栈。你能安排他们下周二或周三参加电话会议吗？”

---

示例 2：HR 科技平台

背景： 向 HR 副总裁销售员工体验平台

步骤 1 - 洞察： “远程和混合办公彻底改变了员工体验企业文化的方式。当一半团队分散在各地时，旧的一套做法——办公室福利、现场全员大会、随意交谈——已经行不通了。”

步骤 2 - 替代方案： “大多数公司会尝试通过 Slack 频道、偶尔开展的调查和线上欢乐时光来适应。但我们听到的情况是：

• 敬业度评分正在下降
• 新员工感到疏离
• 企业文化正因地点不同而变得支离破碎”

步骤 3 - 理想状态： “如果你能够：

• 持续而非每年一次地了解文化脉搏
• 让管理者实时了解团队状态
• 无需增加会议，就能促进不同地点员工之间的联系”

步骤 4 - 介绍： “这就是我们打造 CultureOS 的原因——一个专为分布式工作场所设计的员工体验平台。”

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

检查清单与模板

推介准备检查清单

## Before the Pitch

### Positioning Foundation
- [ ] Positioning Canvas completed
- [ ] Competitive alternatives identified
- [ ] Unique attributes documented
- [ ] Value clusters defined
- [ ] Market category chosen

### Pitch Construction
- [ ] Insight relevant to THIS prospect
- [ ] Alternatives match their actual options
- [ ] Perfect World criteria favor our strengths
- [ ] Introduction is concise (30 seconds max)
- [ ] Differentiation tied to their specific pain
- [ ] Proof relevant to their industry/size
- [ ] Top 2-3 objections pre-handled
- [ ] Clear, specific ask prepared

### Prospect Research
- [ ] Their current solution/stack
- [ ] Recent news or changes
- [ ] Key decision criteria
- [ ] Timeline and budget cycle

---

推介结构模板

## [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:
1. [Capability that solves pain 1]
2. [Capability that solves pain 2]
3. [Capability that solves pain 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?"

---

常见推介错误检查清单

## 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
- [ ] Introduction too long (more than 30 seconds)
- [ ] Differentiation not tied to Perfect World
- [ ] Proof is generic (not relevant to prospect)
- [ ] No objection handling
- [ ] Vague ask ("let me know...")

### Wrong Order
- [ ] Introducing product before establishing context
- [ ] Jumping to proof before differentiation
- [ ] Handling objections only when raised

技能边界

此技能擅长的事项

• 组织音频制作工作流
• 提供技术指导
• 创建质量检查清单
• 提出创意方案

此技能无法完成的事项

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

参考资料

• Dunford, April。《Sales Pitch》（2023）
• Dunford, April。《Obviously Awesome》（2019）
• 《定位论述》中的第五部分：执行层
• Dunford 为 B2B 销售团队制定的咨询方法论

相关技能

• positioning-dunford - 定位基础
• copy-frameworks - 用于提案结构的 AIDA/PAS
• persuasion-cialdini - 影响力心理学
• storytelling-storybrand - 叙事框架

---

技能元数据（内部使用）

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