mcpField
Q
qbr-preparation

qbr-preparation

github.com/guia-matthieu营销与增长150196 次安装4 周前更新
代码仓库

关于 qbr-preparation

qbr-preparation 是帮助客户成功团队准备季度业务回顾材料的技能,适用于客户评审、续约讨论和战略账户规划。它整理账户历史、价值指标、健康状况、风险与机会,并起草后续季度建议。

主要功能

  1. 01汇总账户历史与关键信息
  2. 02记录价值成果和指标
  3. 03评估账户健康状况
  4. 04分析风险与机会
  5. 05起草战略建议和谈话要点

适用场景

  1. 01准备季度客户评审材料
  2. 02为续约讨论整理账户价值
  3. 03规划客户年度战略会议

安装

复制下面的命令,在终端中运行。

$npx skills add https://github.com/guia-matthieu/clawfu-skills --skill qbr-preparation

安装后在 Claude Code 中输入/qbr-preparation确认已加载。

详细介绍

QBR 准备

生成全面的季度业务回顾材料,包括客户历史、成功指标、挑战和战略建议。

何时使用此技能

  • 准备季度客户回顾
  • 高管业务回顾(EBR)
  • 与客户开展年度规划会议
  • 续约讨论
  • 战略客户规划

方法论基础

基于 Gainsight QBR 最佳实践和战略客户管理,围绕以下内容组织回顾:

  • 已交付的价值(回顾过去)
  • 当前健康状况和互动情况
  • 未来机遇和风险
  • 战略建议

Claude 负责什么,你来决定什么

Claude 负责由你决定
汇总客户历史战略定位
计算成功指标要提出的建议
识别风险和机遇定价和条款
起草谈话要点关系动态
创建演示文稿结构会议主持

此技能的功能

  1. 客户摘要 - 关键信息和历史
  2. 价值记录 - 指标和成就
  3. 健康状况评估 - 当前状态和趋势
  4. 风险/机遇分析 - 需要关注和争取的事项
  5. 战略建议 - 下一季度的优先事项

使用方法

Prepare QBR materials for:

Account: [Company Name]
Contract: $[ARR], Started: [Date], Renewal: [Date]
Primary Contact: [Name, Title]
CSM: [Your name]

Account History:
- [Major milestones, implementations, expansions]
- [Key wins and challenges]

Usage/Success Metrics:
- [Key metrics with current values and trends]
- [Goals they set vs. achieved]

Recent Activity:
- [Support tickets, calls, meetings last quarter]
- [Any escalations or issues]

Relationship Status:
- Champion: [Name, engagement level]
- Exec Sponsor: [Status]
- Other stakeholders: [List]

Known Opportunities/Risks:
- [Expansion potential, concerns mentioned, competitors]

说明

第 1 步:汇总客户概况

关键信息部分:

Account Snapshot
- Company: [Name]
- Industry: [Sector]
- Size: [Employees/Revenue]
- Product: [What they bought]
- Contract: $X ARR | Since [Date] | Renews [Date]
- Health: [Score] | [Status]
第 2 步:记录已交付的价值

成果部分(至关重要):

类别格式
量化 ROI“节省 X 小时、$Y 美元、Z%”
已实现目标客户提出的目标 → 我们的影响
里程碑重要成果
值得引用的评价可引用的成功案例

结构:

"When you started with us, you wanted to [GOAL].
In Q[X], you achieved [RESULT]."
第 3 步:评估当前健康状况

健康状况仪表板:

| Dimension | Score | Trend | Notes |
|-----------|-------|-------|-------|
| Product | X/25 | ↗️↘️→ | Key metric |
| Support | X/25 | ↗️↘️→ | CSAT, tickets |
| Financial | X/25 | ↗️↘️→ | Payment, growth |
| Relationship | X/25 | ↗️↘️→ | Engagement |
| **Overall** | **X/100** | | |
第 4 步:识别风险和机遇

风险评估:

风险可能性影响缓解措施
[Risk]H/M/LH/M/L[Action]

机遇评估:

机遇价值时间线下一步
[Opp]$XQ1/Q2[Action]
第 5 步:制定建议

战略建议框架:

  1. 继续 - 哪些做法有效,应继续保持
  2. 开始 - 下一季度的新计划
  3. 停止 - 应该调整或降低优先级的事项

示例

示例 1:完整的 QBR 准备

输入:

Prepare QBR for CloudTech Industries:

Account: CloudTech Industries (Manufacturing)
Contract: $180K ARR, Started: Jan 2024, Renewal: Jan 2027
Primary: Sarah Chen, VP Operations
CSM: Alex

History:
- Implemented in 60 days (target was 90)
- Added 50 seats in Q2 ($30K expansion)
- Had a major support escalation in Q3 (resolved)
- Reduced production downtime by 35%

Metrics:
- DAU: 145/200 seats (73%)
- Key feature (alerts): 89% adoption
- CSAT: 4.3 (was 3.8 during escalation)
- NPS: 8

Recent Activity:
- 3 support tickets (minor)
- Monthly check-in calls
- Sarah attended user conference

Relationship:
- Champion: Sarah Chen (strong)
- Exec Sponsor: COO Mike Johnson (met once)
- Also engaged: IT Director, 3 plant managers

Opportunities/Risks:
- They're opening 2 new plants (expansion?)
- Competitor demo'd to IT last month
- Sarah mentioned "budget review" for next year

输出:

## QBR Preparation: CloudTech Industries
### Q4 2025 Business Review

---

## 📋 Executive Summary

**Account Health: 78/100 🟢 Healthy**

CloudTech has achieved significant operational improvements, including **35% reduction in production downtime**. The Q3 support escalation was resolved and CSAT has recovered. Two key opportunities: **new plant expansion** and **deepening executive relationship**. One risk to monitor: competitor activity and budget review timing.

**Recommended QBR Focus:**
1. Celebrate the 35% downtime reduction (ROI story)
2. Discuss new plant rollout plan
3. Secure executive sponsor re-engagement

---

## 🏢 Account Snapshot

| Attribute | Value |
|-----------|-------|
| Company | CloudTech Industries |
| Industry | Manufacturing |
| Contract Value | $180,000 ARR |
| Customer Since | January 2024 (11 months) |
| Renewal Date | January 2027 |
| Health Score | 78/100 🟢 |
| CSM | Alex |

**Key Contacts:**
| Name | Title | Role | Engagement |
|------|-------|------|------------|
| Sarah Chen | VP Operations | Champion | High |
| Mike Johnson | COO | Exec Sponsor | Low (1 meeting) |
| [IT Director] | IT Director | Technical | Medium |
| 3 Plant Managers | Operations | Users | High |

---

## 📈 Value Delivered

### Headline Metric
> **35% reduction in production downtime**
> *"Before [Product], we were losing 12 hours/month to unplanned downtime. Now it's under 8 hours."*

### Quarterly Achievements

| Goal | Target | Achieved | Status |
|------|--------|----------|--------|
| Reduce downtime | 25% | 35% | ✅ Exceeded |
| Implementation | 90 days | 60 days | ✅ Exceeded |
| User adoption | 70% | 73% | ✅ Met |
| Alert response time | <15 min | 11 min avg | ✅ Exceeded |

### ROI Calculation (Talking Point)

停机成本:约 $5,000/小时 节省时间:每月 4 小时 × 11 个月 = 44 小时 交付价值:44 × $5,000 = $220,000 合同金额:$180,000 ROI:122%(已收回成本)


### Journey Milestones
- ✅ Jan 2024: Implementation (30 days early!)
- ✅ Q2 2024: Added 50 seats ($30K expansion)
- ⚠️ Q3 2024: Support escalation (resolved)
- ✅ Q4 2024: 35% downtime reduction achieved

---

## 🎯 Current Health

### Score Breakdown

| Dimension | Score | Trend | Notes |
|-----------|-------|-------|-------|
| Product | 29/40 | → | 73% DAU, strong adoption |
| Support | 12/15 | ↗️ | Recovered from escalation |
| Financial | 20/25 | → | Current, expanded once |
| Relationship | 17/20 | → | Strong champion, weak exec |
| **Total** | **78/100** | | 🟢 Healthy |

### Engagement Metrics

| Metric | Q3 | Q4 | Trend |
|--------|----|----|-------|
| DAU | 140 | 145 | ↗️ +4% |
| Feature adoption | 85% | 89% | ↗️ |
| CSAT | 3.8 | 4.3 | ↗️ Recovering |
| Support tickets | 8 | 3 | ↗️ Improved |
| NPS | 6 | 8 | ↗️ |

---

## ⚠️ Risks & Opportunities

### Risks to Discuss

| Risk | Level | Details | Mitigation |
|------|-------|---------|------------|
| Competitor | 🟡 Medium | Demo'd to IT last month | Competitive defense, exec engagement |
| Budget review | 🟡 Medium | Sarah mentioned "budget discussions" | Reinforce ROI before budget cycle |
| Exec relationship | 🟡 Medium | COO met only once | Request exec-to-exec call |

### Opportunities to Pursue

| Opportunity | Value | Probability | Next Step |
|-------------|-------|-------------|-----------|
| 2 new plants | $60-90K | 60% | Discuss rollout timeline |
| Additional modules | $40K | 40% | Demo predictive features |
| Case study | N/A | 80% | Request with 35% stat |

---

## 💬 QBR Agenda (Suggested)

**Duration: 60 minutes**

| Time | Topic | Lead |
|------|-------|------|
| 0:00 | Welcome, agenda | CSM |
| 0:05 | Their priorities for 2026 | Sarah |
| 0:15 | Value recap: 35% downtime story | CSM |
| 0:25 | Health dashboard review | CSM |
| 0:35 | New plant expansion discussion | Both |
| 0:45 | Product roadmap preview | CSM |
| 0:55 | Next steps and actions | Both |

---

## 📝 Talking Points

### Opening
"Sarah, before we dive in, I want to acknowledge the incredible progress your team has made. A 35% reduction in downtime is exceptional—most customers see 20-25% in their first year."

### Competitive Defense (if needed)
"I heard [Competitor] came by. Happy to do a side-by-side comparison, but I'd also point out: you've already achieved ROI with us. Switching has real costs—time, retraining, risk. Let's talk about what's driving the evaluation."

### Budget Concern
"You mentioned budget reviews coming up. Would it help if I prepared a one-page ROI summary your team could use internally? The 35% downtime number plus the $220K in savings is a strong story."

### Expansion Ask
"With two new plants opening, I want to make sure we're ahead of the curve. What's the timeline? We could do a phased rollout to minimize disruption."

### Executive Engagement
"I'd love to get Mike more involved. Would it make sense to schedule a brief executive update—maybe 20 minutes—where we share the ROI story and get his input on strategic priorities?"

---

## ✅ Pre-QBR Checklist

- [ ] Confirm attendees (Sarah + who else?)
- [ ] Send agenda 3 days before
- [ ] Prepare one-page health summary
- [ ] Update ROI calculation with latest numbers
- [ ] Review competitor battle card
- [ ] Prepare new plant rollout options
- [ ] Draft follow-up email template

---

## 📊 Supporting Materials

### Attachment 1: Health Score Trend
[Include chart showing Q1-Q4 trend]

### Attachment 2: ROI One-Pager
[One-page summary of 35% stat + dollar value]

### Attachment 3: Product Roadmap Preview
[2-3 upcoming features relevant to their use case]

技能边界

此技能擅长的事项
  • 组织 QBR 内容
  • 计算 ROI 和指标
  • 识别风险和机遇
  • 起草谈话要点
此技能无法做到的事项
  • 了解客户内部的政治关系
  • 直接访问你的 CRM/分析数据
  • 主持实际会议
  • 做出定价决策
需要升级给人工处理的情况
  • 定价/合同谈判
  • 需要升级处理的问题
  • 高管关系策略
  • 竞争定位

迭代指南

后续提示词
  • “为他们的 CFO 起草一页 ROI 摘要。”
  • “为这次 QBR 编写一份竞争防御话术。”
  • “关于新工厂,我应该问哪些问题?”
  • “撰写这次 QBR 之后的跟进邮件。”

清单和模板

QBR 准备清单
  • 已核实客户概况
  • 已提取并验证指标
  • 已计算 ROI
  • 已识别风险/机遇
  • 已起草议程
  • 已准备谈话要点
  • 已附上材料
  • 已确认日历安排

参考资料

  • Gainsight QBR 最佳实践
  • Miller Heiman 战略销售
  • 客户成功 QBR 模板
  • 高管业务回顾指南

相关技能

  • account-health - 健康评分输入
  • expansion-signals - 机遇识别
  • churn-prediction - 风险评估

技能元数据

  • 领域:客户成功
  • 复杂度:中级
  • 模式:cyborg
  • 价值实现时间:每次 QBR 需 30-60 分钟
  • 前置条件:客户历史记录、指标、关系背景

评论

支持 Markdown