demo-specialist
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseDemo Specialist
产品演示专家
Strategic expertise for delivering product demonstrations that convert prospects into customers.
助力将潜在客户转化为付费用户的专业演示策略。
Philosophy
核心理念
A demo isn't a feature tour. It's a story about your prospect's future told through your product.
The best product demos:
- Start with their problem — Not your solution
- Show, don't tell — Features are boring; outcomes are compelling
- Match the audience — Executives need different things than end-users
- Create urgency — Show the cost of inaction
- End with a clear next step — Never let momentum die
演示不是功能罗列,而是通过你的产品讲述一个关于潜在客户未来的故事。
优秀的产品演示需遵循以下原则:
- 从他们的问题切入——而非你的解决方案
- 展示,而非说教——功能枯燥乏味,成果才引人入胜
- 匹配受众需求——高管与终端用户的关注点截然不同
- 制造紧迫感——展示不作为的代价
- 以明确的下一步收尾——切勿让势头戛然而止
How This Skill Works
技能使用方式
When invoked, apply the guidelines in organized by:
rules/- — Demo flow, storytelling arc, timing
structure-* - — Stakeholder mapping, persona-based demos
audience-* - — Live demo execution, objection handling
technique-* - — Demo prep, sandbox vs live, technical setup
environment-* - — Post-demo actions, next steps
followup-*
调用本技能时,请遵循目录下的分类指南:
rules/- — 演示流程、叙事结构、时间把控
structure-* - — 利益相关方梳理、基于用户画像的演示
audience-* - — 实时演示执行、异议处理技巧
technique-* - — 演示准备、沙箱与实时环境对比、技术配置
environment-* - — 演示后行动、后续步骤
followup-*
Core Frameworks
核心框架
The Demo Hierarchy of Needs
演示需求层级
┌─────────────────┐
│ CONVICTION │ ← "I need this NOW"
│ (Urgency) │
├─────────────────┤
│ VISION │ ← "I see how this transforms us"
│ (Future) │
├─────────────────┤
│ RELEVANCE │ ← "This solves MY problem"
│ (Personalized) │
├─────────────────┤
│ CREDIBILITY │ ← "This actually works"
│ (Proof) │
└─────────────────┘ ┌─────────────────┐
│ CONVICTION │ ← "I need this NOW"
│ (Urgency) │
├─────────────────┤
│ VISION │ ← "I see how this transforms us"
│ (Future) │
├─────────────────┤
│ RELEVANCE │ ← "This solves MY problem"
│ (Personalized) │
├─────────────────┤
│ CREDIBILITY │ ← "This actually works"
│ (Proof) │
└─────────────────┘Demo Structure Arc
演示结构脉络
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ HOOK │───▶│ PROBLEM │───▶│ SOLUTION │───▶│ PROOF │───▶│ CLOSE │
│ (2 min) │ │ (5 min) │ │ (15 min) │ │ (5 min) │ │ (3 min) │
└──────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘
│ │ │ │ │
Attention Pain point Core value Social proof Next step
+ agenda validation demonstration + ROI case + timeline┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ HOOK │───▶│ PROBLEM │───▶│ SOLUTION │───▶│ PROOF │───▶│ CLOSE │
│ (2 min) │ │ (5 min) │ │ (15 min) │ │ (5 min) │ │ (3 min) │
└──────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘
│ │ │ │ │
Attention Pain point Core value Social proof Next step
+ agenda validation demonstration + ROI case + timelineStakeholder Demo Matrix
利益相关方演示矩阵
| Stakeholder | Primary Need | Demo Focus | Success Metric |
|---|---|---|---|
| Executive | Strategic value, ROI | Business outcomes, dashboards | "How does this move our KPIs?" |
| Manager | Team efficiency, reporting | Workflows, collaboration | "How does this make my team faster?" |
| End User | Daily workflow, ease of use | UX, common tasks | "How does this make my job easier?" |
| Technical | Integration, security, scale | APIs, architecture, compliance | "How does this fit our stack?" |
| Finance | Cost, ROI, TCO | Pricing, value metrics | "What's the business case?" |
| 利益相关方 | 核心需求 | 演示重点 | 成功衡量标准 |
|---|---|---|---|
| 高管 | 战略价值、投资回报率(ROI) | 业务成果、数据仪表盘 | "这如何推动我们的关键绩效指标(KPI)?" |
| 管理者 | 团队效率、报告能力 | 工作流、协作功能 | "这如何提升我的团队效率?" |
| 终端用户 | 日常工作流、易用性 | 用户体验(UX)、常见任务处理 | "这如何简化我的工作?" |
| 技术人员 | 集成能力、安全性、扩展性 | API、架构、合规性 | "这如何适配我们的技术栈?" |
| 财务人员 | 成本、投资回报率(ROI)、总拥有成本(TCO) | 定价、价值指标 | "商业可行性如何?" |
The SHOW Framework
SHOW框架
- Situation — Confirm their current state
- Hurdle — Highlight the specific challenge
- Outcome — Paint the future with your solution
- Wow — Demonstrate the "aha moment"
- Situation — 确认他们当前的业务状态
- Hurdle — 突出具体面临的挑战
- Outcome — 描绘采用解决方案后的未来图景
- Wow — 展示“惊喜时刻”
Demo Types
演示类型
| Type | Duration | Audience | Depth | Goal |
|---|---|---|---|---|
| Teaser | 5-10 min | Cold leads | Surface | Generate interest |
| Discovery Demo | 15-20 min | Qualified leads | Moderate | Validate fit |
| Full Demo | 30-45 min | Buying committee | Deep | Advance deal |
| Technical Deep-Dive | 45-60 min | IT/Dev team | Very deep | Technical validation |
| Executive Briefing | 15-20 min | C-suite | Strategic | Executive buy-in |
| POC Kickoff | 60+ min | Project team | Implementation | Start evaluation |
| 类型 | 时长 | 受众 | 深度 | 目标 |
|---|---|---|---|---|
| Teaser演示 | 5-10分钟 | 冷线索客户 | 表层 | 激发兴趣 |
| Discovery Demo(发现式演示) | 15-20分钟 | 合格线索客户 | 中等 | 验证适配性 |
| Full Demo(完整演示) | 30-45分钟 | 采购委员会 | 深入 | 推进交易 |
| Technical Deep-Dive(技术深度解析) | 45-60分钟 | IT/开发团队 | 极深入 | 技术验证 |
| Executive Briefing(高管简报) | 15-20分钟 | 高管层 | 战略层面 | 获取高管认可 |
| POC Kickoff(POC启动会) | 60分钟以上 | 项目团队 | 实施层面 | 启动评估 |
Environment Strategy
环境策略
| Environment | Best For | Pros | Cons |
|---|---|---|---|
| Production | Mature product, confidence | Real data, authentic | Risk of bugs/latency |
| Sandbox | Complex demos, new features | Controlled, safe | Less authentic |
| Customer's Data | Late-stage deals | Highly relevant | Requires prep |
| Recorded | Consistency, scale | Perfect execution | No interaction |
| 环境类型 | 适用场景 | 优势 | 劣势 |
|---|---|---|---|
| Production(生产环境) | 成熟产品、信心充足时 | 真实数据、场景真实 | 存在bug/延迟风险 |
| Sandbox(沙箱环境) | 复杂演示、新功能展示 | 可控、安全 | 场景真实性不足 |
| Customer's Data(客户自有数据) | 后期交易阶段 | 高度贴合需求 | 需要提前准备 |
| Recorded(录播演示) | 保持一致性、规模化推广 | 完美呈现 | 无互动性 |
Anti-Patterns
反模式
- Feature dumping — Showing everything instead of what matters
- No discovery — Demoing before understanding their needs
- One-size-fits-all — Same demo for every audience
- Demo theater — Overly scripted, no room for questions
- Technical rabbit holes — Getting lost in implementation details
- No next step — Ending without a clear action
- Ignoring the room — Not reading reactions and adjusting
- Over-promising — Showing roadmap items as current features
- Feature dumping(功能堆砌) — 展示所有功能而非关键内容
- No discovery(缺乏调研) — 未了解客户需求就进行演示
- One-size-fits-all(千篇一律) — 对所有受众使用相同演示内容
- Demo theater(演示表演化) — 过度脚本化,不给提问空间
- Technical rabbit holes(技术细节陷阱) — 陷入实现细节无法自拔
- No next step(无明确后续) — 结束时未给出清晰行动方向
- Ignoring the room(忽视现场反应) — 不关注受众反应并调整内容
- Over-promising(过度承诺) — 将规划中功能当作现有功能展示