cs-strategist

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

CS Strategist

CS战略专家

Strategic Customer Success expertise for building and scaling world-class CS organizations — from team structure and segmentation to playbooks, metrics, and technology.

为打造并规模化世界级CS组织提供战略性客户成功专业知识——涵盖团队架构、客户细分、操作手册、指标体系与技术选型等全维度内容。

Philosophy

核心理念

Customer Success is not support with a different name. It's a strategic function that drives predictable revenue growth through proactive customer value delivery.

The best CS organizations:

Segment ruthlessly — One-size-fits-all is no-size-fits-any
Measure outcomes, not activities — Calls made ≠ value delivered
Scale before you hire — Technology enables, humans differentiate
Own the number — CS owns Net Revenue Retention, full stop

客户成功并非换了名字的支持服务，它是一项通过主动交付客户价值来推动可预测收入增长的战略职能。

优秀的CS组织具备以下特质：

精准细分客户 —— 一刀切等于完全不适用
衡量成果而非活动 —— 拨打的电话数量 ≠ 交付的价值
先规模化再招聘 —— 技术赋能效率，人力创造差异
对核心指标负责 —— CS全权负责净收入留存（NRR），这是不容置疑的

How This Skill Works

本技能的运作方式

When invoked, apply the guidelines in

rules/

organized by:

```
org-*
```
— CS org design, team structure, roles, hiring
```
segmentation-*
```
— Customer tiering, coverage models, resource allocation
```
metrics-*
```
— KPIs, health scores, forecasting, reporting
```
playbooks-*
```
— Lifecycle playbooks, automation, QBRs
```
executive-*
```
— Stakeholder management, EBRs, C-level relationships
```
technology-*
```
— CS platforms, tool stack, integration
```
value-*
```
— Value realization, ROI frameworks, success plans
```
journey-*
```
— Customer journey mapping, touchpoints, moments of truth

调用本技能时，请遵循

rules/

目录下按类别划分的指导原则：

```
org-*
```
—— CS组织设计、团队架构、角色定义、招聘策略
```
segmentation-*
```
—— 客户分层、覆盖模型、资源分配
```
metrics-*
```
—— KPI、健康评分、预测分析、报告体系
```
playbooks-*
```
—— 生命周期操作手册、自动化流程、季度业务回顾（QBRs）
```
executive-*
```
—— 利益相关方管理、高管业务回顾（EBRs）、C级客户关系维护
```
technology-*
```
—— CS平台、工具栈、集成方案
```
value-*
```
—— 价值实现、ROI框架、成功计划
```
journey-*
```
—— 客户旅程映射、触点管理、关键体验时刻

Core Frameworks

核心框架

The CS Maturity Model

CS成熟度模型

Stage	Characteristics	Focus
Reactive	Support-driven, firefighting	Basic retention
Proactive	Health monitoring, early intervention	Churn prevention
Strategic	Outcome-focused, expansion-driven	NRR growth
Transformational	Customer value embedded in product	Market leadership

阶段	特征	核心焦点
被动响应型	以支持服务为主，忙于救火	基础客户留存
主动预防型	客户健康监控、早期干预	流失预防
战略驱动型	聚焦成果、驱动业务扩张	NRR增长
转型引领型	客户价值深度嵌入产品	市场领导力

Customer Segmentation Tiers

客户细分分层

┌─────────────────────────────────────────────────────────┐
│                    HIGH TOUCH                           │
│  Enterprise / Strategic accounts ($100k+ ARR)           │
│  Dedicated CSM, EBRs, custom success plans              │
│  Ratio: 1:10-25 accounts                                │
├─────────────────────────────────────────────────────────┤
│                    LOW TOUCH                            │
│  Mid-market accounts ($15k-$100k ARR)                   │
│  Pooled CSMs, scaled programs, office hours             │
│  Ratio: 1:50-100 accounts                               │
├─────────────────────────────────────────────────────────┤
│                    TECH TOUCH                           │
│  SMB / Self-serve accounts (<$15k ARR)                  │
│  Automated journeys, community, self-service            │
│  Ratio: 1:500+ accounts (or no dedicated CSM)           │
└─────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────┐
│                    HIGH TOUCH                           │
│  Enterprise / Strategic accounts ($100k+ ARR)           │
│  Dedicated CSM, EBRs, custom success plans              │
│  Ratio: 1:10-25 accounts                                │
├─────────────────────────────────────────────────────────┤
│                    LOW TOUCH                            │
│  Mid-market accounts ($15k-$100k ARR)                   │
│  Pooled CSMs, scaled programs, office hours             │
│  Ratio: 1:50-100 accounts                               │
├─────────────────────────────────────────────────────────┤
│                    TECH TOUCH                           │
│  SMB / Self-serve accounts (<$15k ARR)                  │
│  Automated journeys, community, self-service            │
│  Ratio: 1:500+ accounts (or no dedicated CSM)           │
└─────────────────────────────────────────────────────────┘

The CS Metrics Hierarchy

CS指标层级

Category	Metrics	Owner
Business Outcomes	NRR, GRR, Logo Retention	CS Leadership
Leading Indicators	Health Score, Adoption, NPS	CS Operations
Activity Metrics	Touchpoints, QBRs, Time-to-Value	CSMs

类别	指标	负责人
业务成果	NRR、GRR、客户留存率	CS领导层
领先指标	健康评分、产品使用率、NPS	CS运营团队
活动指标	客户触点、QBRs、价值实现周期	CSMs

Net Revenue Retention Formula

净收入留存（NRR）计算公式

        Starting MRR + Expansion - Contraction - Churn
NRR = ─────────────────────────────────────────────────── × 100
                        Starting MRR

Target NRR by segment:
- Enterprise: 115-130%+
- Mid-market: 105-115%
- SMB: 95-105%

        Starting MRR + Expansion - Contraction - Churn
NRR = ─────────────────────────────────────────────────── × 100
                        Starting MRR

Target NRR by segment:
- Enterprise: 115-130%+
- Mid-market: 105-115%
- SMB: 95-105%

The CS Tech Stack

CS技术栈

Layer	Function	Example Tools
Core Platform	Customer 360, health scores	Gainsight, ChurnZero, Totango
Data Layer	Product analytics, usage	Amplitude, Pendo, Mixpanel
Engagement	In-app, email automation	Intercom, Customer.io, Appcues
Feedback	Surveys, NPS	Delighted, Wootric, Satismeter
Intelligence	Churn prediction, next best action	Planhat, Catalyst

层级	功能	示例工具
核心平台	客户360视图、健康评分	Gainsight、ChurnZero、Totango
数据层	产品分析、使用数据	Amplitude、Pendo、Mixpanel
互动层	应用内互动、邮件自动化	Intercom、Customer.io、Appcues
反馈层	调研、NPS收集	Delighted、Wootric、Satismeter
智能层	流失预测、最佳行动建议	Planhat、Catalyst

Customer Journey Stages

客户旅程阶段

PRE-SALES → ONBOARDING → ADOPTION → VALUE → EXPANSION → ADVOCACY
     ↓           ↓           ↓        ↓          ↓           ↓
  Handoff    Time-to-    Feature   Outcome   Expansion   Reference
  Quality    Value       Adoption  Achieved  Opportunity Customer

PRE-SALES → ONBOARDING → ADOPTION → VALUE → EXPANSION → ADVOCACY
     ↓           ↓           ↓        ↓          ↓           ↓
  Handoff    Time-to-    Feature   Outcome   Expansion   Reference
  Quality    Value       Adoption  Achieved  Opportunity Customer

The Value Realization Framework

价值实现框架

Phase	Definition	Deliverable
Define	Agree on success criteria	Success Plan
Deliver	Execute implementation & onboarding	Go-Live
Demonstrate	Prove value with metrics	Value Report
Develop	Expand usage and outcomes	Growth Plan

阶段	定义	交付物
定义	达成成功标准共识	成功计划
交付	执行实施与上线流程	正式启用
验证	用数据证明价值	价值报告
拓展	扩大产品使用范围与成果	增长计划

Key Metrics Reference

关键指标参考

Metric	Definition	Good	Great
NRR	Net Revenue Retention	105%+	120%+
GRR	Gross Revenue Retention	90%+	95%+
Logo Retention	Customers retained	85%+	92%+
NPS	Net Promoter Score	30+	50+
CSAT	Customer Satisfaction	4.0/5	4.5/5
CES	Customer Effort Score	<3	<2
Time to Value	Days to first outcome	<30	<14
Health Score	Composite customer health	70+ avg	80+ avg

指标	定义	良好水平	优秀水平
NRR	净收入留存	105%+	120%+
GRR	总收入留存	90%+	95%+
客户留存率	留存的客户数量占比	85%+	92%+
NPS	净推荐值	30+	50+
CSAT	客户满意度	4.0/5	4.5/5
CES	客户努力值	<3	<2
价值实现周期	首次达成成果所需天数	<30	<14
健康评分	客户健康状况综合评分	平均70+	平均80+

Coverage Model Decision Framework

覆盖模型决策框架

Factor	High Touch	Low Touch	Tech Touch
ARR	$100k+	$15k-100k	<$15k
Complexity	High	Medium	Low
Strategic Value	High potential	Standard	Transactional
Touch Frequency	Weekly-Monthly	Monthly-Quarterly	Automated
CSM Ratio	1:10-25	1:50-100	1:500+
Cost to Serve	15-25% of ARR	5-10% of ARR	<3% of ARR

因素	高触达	低触达	技术触达
ARR	$100k+	$15k-100k	<$15k
复杂度	高	中	低
战略价值	高潜力	标准	交易型
触达频率	每周-每月	每月-每季度	自动化
CSM配比	1:10-25	1:50-100	1:500+
服务成本占比	ARR的15-25%	ARR的5-10%	ARR的<3%

Anti-Patterns

反模式

Measuring activities over outcomes — Calls logged ≠ customers retained
One playbook for all segments — Tech touch playbooks for enterprise fail
CS as support escalation — Reactive mode kills proactive capacity
Health scores without action — Red accounts need intervention, not dashboards
Siloed CS data — CS platform not integrated with CRM/Product
CSM as single thread — Champion leaves, relationship collapses
QBRs as PowerPoint theater — Value delivery, not presentation
Ignoring tech touch — 80% of customers, 20% of attention

衡量活动而非成果 —— 记录的通话数量 ≠ 留存的客户数量
单一操作手册适配所有细分客户 —— 技术触达操作手册不适用于企业客户
CS作为支持升级通道 —— 被动响应模式会扼杀主动服务能力
健康评分无后续行动 —— 红色预警客户需要干预，而非仅靠仪表盘
CS数据孤岛 —— CS平台未与CRM/产品系统集成
CSM作为唯一对接人 —— 关键联系人离职，客户关系随即破裂
QBR沦为PPT展示秀 —— 应聚焦价值交付，而非形式化演示
忽视技术触达客户 —— 80%的客户仅获得20%的关注