mcpField
E
expansion-signals

expansion-signals

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

关于 expansion-signals

expansion-signals 是客户成功技能,通过使用情况、增长、行为和时机信号评估账户扩展准备度。它为机会评分和排序、估算潜在价值,并建议沟通时机与切入方式。

主要功能

  1. 01识别扩展信号
  2. 02准备度评分与排序
  3. 03估算潜在价值
  4. 04推荐沟通时机
  5. 05基于信号的沟通建议

适用场景

  1. 01检查月度扩展商机管道
  2. 02确定追加销售联系优先级
  3. 03估算潜在扩展收入
  4. 04制定账户扩展沟通方案

安装

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

$npx skills add https://github.com/guia-matthieu/clawfu-skills --skill expansion-signals

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

详细介绍

扩张信号

通过分析使用模式、增长指标和行为信号,发现预测客户已准备好扩大采购的扩张机会。

何时使用此技能

  • 每月审查扩张销售管道
  • 识别增购候选客户
  • 为 CSM 的扩张工作排定优先级
  • 制定扩张手册
  • 预测扩张收入

方法论基础

基于 Lincoln Murphy 的扩张收入框架和 Gainsight 扩张手册,重点关注:

  • 使用上限信号
  • 增长触发因素
  • 购买意向指标
  • 时机优化

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

Claude 负责你来决定
识别扩张信号推进哪些机会
评估扩张准备度定价和套餐
建议对话开场白客户关系处理方式
为机会排定优先级资源分配
计算潜在价值折扣/激励方案

此技能的功能

  1. 信号检测 - 识别扩张指标
  2. 机会评分 - 对扩张准备度进行排序
  3. 规模估算 - 估算潜在扩张价值
  4. 时机建议 - 确定何时接洽
  5. 对话指导 - 指导如何接洽

使用方法

Analyze expansion signals for:

Account: [Company Name]
Current Contract: $[ARR]
Products: [What they have]
Contract End: [Date]

Usage Data:
- Seats: [Used] / [Licensed]
- Feature usage: [Which features, how much]
- Usage trend: [Growing/Flat/Declining]
- Power users: [How many, what they do]

Account Context:
- Company growth: [Hiring, funding, news]
- Stakeholder changes: [New decision makers]
- Requests: [Feature requests, complaints about limits]

Available Expansion:
- Additional seats: $[Price]
- New modules: [List with prices]
- Higher tier: $[Price difference]

说明

第 1 步:识别扩张信号类别

使用上限信号(强):

信号含义
>90% 席位使用率需要更多许可证
达到 API 限制需要更高档位
提出套餐范围之外的功能请求已准备好升级
使用变通方法绕过限制痛点 = 机会
高级用户已用尽功能可推动扩张的倡导者

增长触发因素(强):

信号含义
公司招聘需要更多席位
新办公室/地点地域扩张
宣布融资有可用预算
新举措/项目新使用场景
并购活动集成机会

行为信号(中):

信号含义
管理员查看定价信息正在积极评估
多次询问功能对升级感兴趣
请求客户推荐/案例研究满意且有扩张空间
高管参与度上升战略优先事项
QBR 议程涉及“后续步骤”愿意展开讨论

时机信号:

信号最佳时机
预算周期临近提前 30-60 天
合同续约提前 90 天
刚刚达成里程碑之后立即
提及竞争对手立即采取防御性行动
第 2 步:评估扩张准备度

扩张评分(0-100):

因素权重评分
使用上限25>90% = 25,80-90% = 15,<80% = 5
增长触发因素20强 = 20,一般 = 10,无 = 0
功能请求15多项 = 15,部分 = 8,无 = 0
客户关系健康度20健康 = 20,尚可 = 10,有风险 = 0
时机契合度20完美 = 20,良好 = 12,较差 = 5

准备度区间:

评分状态行动
75-100🔥 热本周接洽
50-74🟢 温本月接洽
25-49🟡 培育为扩张创造条件
0-24⏸️ 等待专注于采用情况/客户健康度
第 3 步:评估机会规模

扩张规模估算:

Potential Value =
  (Additional Seats × Seat Price) +
  (Module Upgrade Value) +
  (Tier Upgrade Delta)

Example:
- 20 additional seats × $100/month = $24K ARR
- Premium module = $12K ARR
- Potential: $36K ARR (20% of base)
第 4 步:规划接洽方式

针对不同信号的对话开场白:

信号开场白
席位上限“我注意到您已达到 95% 的使用容量。您的团队一定正在壮大!”
功能请求“您已经几次询问 X 了。我来给您展示一下我们的 [upgrade] 如何满足这一需求。”
公司增长“恭喜完成 B 轮融资!这对您的团队架构有什么影响?”
高级用户“Sarah 已经成为一位真正的高级用户。您考虑过我们的高级功能吗?”

示例

示例 1:扩展分析

输入:

Analyze expansion for DataFlow Inc:

Current: $48K ARR (50 seats @ $80/seat/month)
Products: Core Platform only
Renewal: 8 months away

Usage:
- Seats: 48/50 (96%)
- Core features: 85% adoption
- API calls: 92% of limit
- Power users: 12 (doing advanced workflows)

Context:
- Just raised Series A ($15M)
- Hiring 20 engineers this quarter
- VP Data asked about analytics module 3 times
- NPS: 9

Available:
- Additional seats: $80/seat/month
- Analytics module: $15K ARR
- API tier upgrade: $6K ARR
- Enterprise tier: +$20K ARR (includes above)

输出:

## Expansion Analysis: DataFlow Inc

### 🔥 Expansion Score: 88/100 - HOT

**This account is primed for expansion.**

---

### Signal Analysis

| Signal | Strength | Points |
|--------|----------|--------|
| 96% seat utilization | 🔥 Strong | 25/25 |
| Series A + hiring 20 | 🔥 Strong | 20/20 |
| Analytics requests (3x) | 🔥 Strong | 15/15 |
| NPS 9 + healthy | 🔥 Strong | 18/20 |
| 8 months to renewal | 🟡 Medium | 10/20 |
| **Total** | | **88/100** |

---

### Opportunity Sizing

**Conservative Estimate:**

20 个新增席位 × $80 × 12 = $19,200 ARR 分析模块 = $15,000 ARR ───────────────────────────────── 保守总计:$34,200 ARR(扩展 71%)


**Aggressive Estimate (Enterprise Tier):**

20 个新增席位 × $80 × 12 = $19,200 ARR 企业版升级 = $20,000 ARR (包含分析功能 + API) 企业版新增席位 = $24,000 ARR ───────────────────────────────── 激进总计:$63,200 ARR(扩展 132%)


**Recommended Target: $40-50K expansion**

---

### Why Now?

1. **Capacity Ceiling** - 96% seat usage, hiring 20 more
   - They will literally run out of seats in weeks

2. **Feature Demand** - VP Data asked 3x about analytics
   - Not if, but when they'll need it

3. **Budget Available** - Series A just closed
   - Flush with cash, growth mindset

4. **Relationship Strong** - NPS 9
   - Trust is high, easy conversation

5. **Power Users as Champions** - 12 heavy users
   - Internal advocates for expansion

---

### Recommended Approach

**Timing: This week**
Don't wait. Seat ceiling + hiring = urgent need.

**Who to Engage:**
1. VP Data (analytics interest) - Decision Maker
2. Champion (current) - Internal advocate
3. Head of Engineering (new hires) - User expansion

**Conversation Strategy:**

**Opening:**
"Congrats on the Series A! I saw you're hiring 20 engineers—exciting growth. I also noticed you're at 96% seat capacity, and [VP Data] has been asking about our analytics module. I'd love to get ahead of your growth and make sure you're set up for scale."

**Value Framing:**
"Given your expansion, I want to show you our Enterprise tier. It includes the analytics module you've been interested in, unlimited API calls, and room to grow. Many companies at your stage find it's more cost-effective than à la carte."

**Offer:**
- Enterprise tier upgrade: +$20K ARR
- 30 additional seats at enterprise rate: $28.8K ARR
- **Total: $48.8K expansion** (102% growth)
- Incentive: Lock multi-year, 10% discount

---

### Next Steps

| Action | Owner | Timeline |
|--------|-------|----------|
| Email VP Data re: analytics | CSM | Tomorrow |
| Prep enterprise comparison | CSM | This week |
| Discovery call: growth plans | CSM | Within 5 days |
| Pricing approval for discount | Sales | Before call |
| Executive intro if needed | CS Director | If VP Data engaged |

---

### Risk Considerations

| Risk | Mitigation |
|------|------------|
| Budget not allocated | Reference Series A, show ROI |
| Competitor evaluation | Emphasize switching cost, existing ROI |
| VP Data not decision maker | Map buying committee |
| "We'll wait until renewal" | Show urgency (seat ceiling) |
示例 2:客户组合扩展优先级排序

输入:

Rank these 5 accounts for expansion priority:

1. AlphaTech: 70% seats, stable usage, renewal in 3 months, asked about premium once
2. BetaCorp: 95% seats, growing 20%, just promoted champion, raised Series B
3. GammaCo: 60% seats, declining usage, renewal in 12 months, no feature requests
4. DeltaInc: 85% seats, stable, renewal next month, CFO mentioned "reviewing vendors"
5. EchoLLC: 100% seats, workarounds everywhere, renewal 6 months, NPS 4

输出:

## Expansion Prioritization: Top 5 Accounts

### Ranked by Expansion Readiness

| Rank | Account | Score | Opportunity | Priority |
|------|---------|-------|-------------|----------|
| 1 | BetaCorp | 92 | High | 🔥 This week |
| 2 | EchoLLC | 68* | High | ⚠️ Fix first |
| 3 | AlphaTech | 55 | Medium | 🟢 This month |
| 4 | DeltaInc | 45 | Low | 🛡️ Defend first |
| 5 | GammaCo | 22 | Low | ⏸️ Adopt first |

---

### Detailed Analysis

#### #1: BetaCorp 🔥 Score: 92
**Status: HOT - Engage immediately**

| Signal | Value |
|--------|-------|
| Seat usage | 95% ✅ |
| Growth | 20% ✅ |
| Champion | Just promoted ✅ |
| Funding | Series B ✅ |
| Health | High ✅ |

**Why #1:** Perfect storm—growth, budget, champion momentum.
**Action:** Schedule this week. Lead with growth planning.

---

#### #2: EchoLLC ⚠️ Score: 68 (with asterisk)
**Status: FIX HEALTH FIRST, then expand**

| Signal | Value |
|--------|-------|
| Seat usage | 100% ✅ |
| Workarounds | Everywhere ✅ |
| Health | NPS 4 ⚠️ |
| Renewal | 6 months |

**Why #2:** High expansion potential BUT health issue.
NPS 4 suggests frustration, likely from hitting limits.

**Action:**
1. First: Address frustration (call, understand issues)
2. Then: Position upgrade as solution to pain
3. Risk: If we don't fix, they'll churn

---

#### #3: AlphaTech 🟢 Score: 55
**Status: WARM - Nurture this month**

| Signal | Value |
|--------|-------|
| Seat usage | 70% ⚠️ |
| Feature ask | Once (weak) |
| Renewal | 3 months |
| Health | Stable |

**Why #3:** Interest exists but not urgent.
**Action:** Explore premium interest, build case before renewal.
**Risk:** Don't push too hard before adoption improves.

---

#### #4: DeltaInc 🛡️ Score: 45
**Status: DEFEND - Not expansion, retention**

| Signal | Value |
|--------|-------|
| Seat usage | 85% OK |
| Renewal | Next month! |
| CFO signal | "Reviewing vendors" 🚨 |

**Why #4:** Expansion is wrong play here.
"Reviewing vendors" before renewal = churn risk.

**Action:**
1. Defensive posture
2. ROI documentation
3. Executive outreach
4. Do NOT discuss expansion until secured

---

#### #5: GammaCo ⏸️ Score: 22
**Status: WAIT - Focus on adoption**

| Signal | Value |
|--------|-------|
| Seat usage | 60% ⚠️ |
| Usage trend | Declining ⚠️ |
| Feature requests | None |
| Renewal | 12 months |

**Why #5:** Not ready—fix adoption first.
Declining usage + low utilization = at-risk, not expandable.

**Action:**
1. Adoption review call
2. Success planning
3. Understand declining usage
4. Table expansion for 6+ months

---

### Summary Matrix

| Account | Expansion | Timing | Play |
|---------|-----------|--------|------|
| BetaCorp | ✅ Yes | Now | Growth planning |
| EchoLLC | ✅ Yes | After fix | Solve + expand |
| AlphaTech | 🟡 Maybe | 30 days | Build interest |
| DeltaInc | ❌ No | N/A | Retention |
| GammaCo | ❌ No | 6+ mo | Adoption |

### This Week's Actions

1. **BetaCorp**: Schedule growth planning call
2. **EchoLLC**: Urgent health check call
3. **DeltaInc**: Pull ROI data, prep retention
4. **AlphaTech**: Send premium feature case study
5. **GammaCo**: Assign to adoption review queue

技能边界

此技能擅长的事项
  • 系统地识别扩展信号
  • 对机会进行评分和优先级排序
  • 估算潜在价值
  • 建议沟通方式
此技能无法做到的事项
  • 访问实际使用数据
  • 了解竞争动态
  • 做出定价决策
  • 取代关系判断
需要升级至人工处理的情况
  • 定价例外
  • 多产品捆绑
  • 战略客户
  • 需要扩展的风险客户

迭代指南

后续提示词
  • “为 BetaCorp 起草扩展邮件。”
  • “数据副总裁可能会提出哪些异议?”
  • “为这个客户比较企业版与按需购买。”
  • “制定一份 30 天扩展计划。”

参考资料

  • Lincoln Murphy 扩展收入
  • Gainsight 扩展手册
  • SaaStr 扩展收入指南
  • ChurnZero 扩展信号

相关技能

  • account-health - 扩展的健康状况背景
  • churn-prediction - 不要向风险客户扩展
  • qbr-preparation - 在 QBR 中讨论扩展

技能元数据

  • 领域:客户成功
  • 复杂度:中级
  • 模式:centaur
  • 价值实现时间:每个客户 15–20 分钟
  • 前置条件:使用数据、客户背景

评论

支持 Markdown