chief-customer-officer-advisor
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseChief Customer Officer Advisor
首席客户官（CCO）咨询顾问
Strategic customer leadership for startup CCOs and founders without one. Four decisions, no generic CS survey:
- What's our retention architecture — and is gross retention vs NRR honest? — decomposition into gross retention, contraction, expansion + churn root-cause taxonomy
- How do we segment customers for differential investment? — tier design + ICP fit scoring + investment-per-segment math
- What's the CS team's coverage model — and when do we go pooled vs named? — coverage ratio calculator + transition thresholds
- What CS role do we hire next? — stage-to-role map (CS ≠ Support ≠ AM ≠ Implementation)
This skill does not cover tactical CS implementation. For health-score tooling, CRM workflows, NPS survey infrastructure, or onboarding automation, see and adjacent tactical skills.
business-growth/customer-success-management/面向初创公司CCO及未配备CCO的创始人提供客户领导力战略建议。四大决策，无通用CS调研：
- 我们的留存架构是什么——总留存率与NRR的数据是否真实？——拆解为总留存率、收缩率、扩张率+流失根因分类体系
- 如何通过客户细分实现差异化投入？——分层设计+ICP匹配评分+各细分投入测算
- CS团队的覆盖模型是什么——何时采用共享式vs专属模式？——覆盖比率计算器+转型阈值
- 我们下一步应招聘哪种CS岗位？——阶段-岗位映射表（CS ≠ 支持 ≠ AM ≠ 实施）
本技能不涵盖CS战术实施内容。如需健康评分工具、CRM工作流、NPS调研基础设施或自动化入职流程相关内容，请查看及相关战术技能。
business-growth/customer-success-management/Keywords
关键词
CCO, chief customer officer, customer success, retention strategy, gross retention, net retention, NRR, GRR, logo retention, dollar retention, churn, contraction, expansion, downsell, customer lifetime value, CLV, LTV, time-to-value, TTV, time-to-first-value, customer health score, NPS, CSAT, customer effort score, segmentation, ICP fit, tier design, low-touch, high-touch, tech-touch, pooled CSM, named CSM, customer success manager, account manager, AM, implementation manager, IM, customer success operations, CS ops, book of business, ratio, ARR-per-CSM, customer marketing, advocacy, expansion playbook, voice of customer, VoC
CCO, chief customer officer, customer success, retention strategy, gross retention, net retention, NRR, GRR, logo retention, dollar retention, churn, contraction, expansion, downsell, customer lifetime value, CLV, LTV, time-to-value, TTV, time-to-first-value, customer health score, NPS, CSAT, customer effort score, segmentation, ICP fit, tier design, low-touch, high-touch, tech-touch, pooled CSM, named CSM, customer success manager, account manager, AM, implementation manager, IM, customer success operations, CS ops, book of business, ratio, ARR-per-CSM, customer marketing, advocacy, expansion playbook, voice of customer, VoC
Quick Start
快速开始
bash
undefinedbash
undefinedDecision A: Decompose retention honestly
决策A：真实拆解留存率
python scripts/retention_decomposition_analyzer.py # embedded B2B SaaS sample
python scripts/retention_decomposition_analyzer.py path/to/cohorts.json
python scripts/retention_decomposition_analyzer.py # 内置B2B SaaS样本
python scripts/retention_decomposition_analyzer.py path/to/cohorts.json
Decision B: Design customer segmentation + differential investment
决策B：设计客户细分+差异化投入
python scripts/customer_segmentation_designer.py # embedded 4-tier sample
python scripts/customer_segmentation_designer.py path/to/customers.json
python scripts/customer_segmentation_designer.py # 内置4分层样本
python scripts/customer_segmentation_designer.py path/to/customers.json
Decision C: Calculate CS team coverage model
决策C：计算CS团队覆盖模型
python scripts/cs_coverage_calculator.py # embedded 350-customer sample
python scripts/cs_coverage_calculator.py path/to/book.json
undefinedpython scripts/cs_coverage_calculator.py # 内置350客户样本
python scripts/cs_coverage_calculator.py path/to/book.json
undefinedKey Questions (ask these first)
核心问题（优先询问）
- What's your GROSS retention rate? (Not NRR — NRR hides churn behind expansion. Ask gross first.)
- What's the #1 reason customers leave? (If you can't name it, you don't understand churn.)
- What's the median time-to-value (TTV) by segment? (Long TTV in low tier = misfit; long TTV in high tier = onboarding broken.)
- Which customer would you fire today? (If "none" — your segmentation is broken; some accounts cost more than they earn.)
- What's your ARR-per-CSM ratio, and what's the model — pooled or named? (Stage and ACV determine the right answer.)
- Is CS in your comp plan, and how is it different from Sales comp? (CS comp on retention; misalignment is a leading indicator of failure.)
- 你的总留存率（GROSS retention rate）是多少？（不是NRR——NRR会用扩张数据掩盖流失问题，先问总留存率。）
- 客户流失的首要原因是什么？（如果答不上来，说明你还不了解流失问题。）
- 各细分客户的中位价值实现时间（TTV）是多少？（低分层TTV过长=匹配度差；高分层TTV过长=入职流程存在问题。）
- 你今天会放弃哪类客户？（如果回答“没有”——说明你的细分体系有问题；部分客户的成本高于其带来的收益。）
- 你的ARR-per-CSM比率是多少，采用的是哪种模型——共享式还是专属式？（发展阶段和ACV决定了正确答案。）
- CS岗位是否纳入薪酬计划，与销售薪酬有何区别？（CS薪酬与留存挂钩；薪酬错位是失败的主要预兆。）
Core Responsibilities
核心职责
1. Retention Decomposition
1. 留存率拆解
The trap: "Our NRR is 115%, retention is great."
The truth: NRR = Gross Retention − Contraction + Expansion. A 115% NRR with 85% gross retention is a leaky bucket masked by upsells. A 115% NRR with 98% gross retention is a healthy product.
Mandatory decomposition every quarter:
| Metric | What it measures | Health threshold (B2B SaaS) |
|---|---|---|
| Gross Retention (GRR) | $ from existing customers minus churn + contraction | ≥ 90% at growth stage; ≥ 95% at scale |
| Logo Retention | % of customers who renewed | ≥ 85% at growth; ≥ 90% at scale |
| Net Revenue Retention (NRR) | GRR + expansion | ≥ 110% at growth; ≥ 120% at scale |
| Contraction | $ from existing customers reducing seats/usage | < 5% annually |
| Expansion | $ from existing customers growing | 15-25% annually at healthy |
Run with cohort data for honest decomposition + churn root-cause categorization.
retention_decomposition_analyzer.pySee for the 7-category churn taxonomy + leading indicator playbook.
references/retention_decomposition.md误区：“我们的NRR是115%，留存情况很好。”
**真相：**NRR = 总留存率 − 收缩率 + 扩张率。总留存率85%但NRR115%的情况，是用追加销售掩盖了漏洞百出的客户留存；总留存率98%且NRR115%的情况，才是健康的产品表现。
每季度必须进行拆解：
| 指标 | 衡量内容 | B2B SaaS健康阈值 |
|---|---|---|
| 总留存率（GRR） | 现有客户收入减去流失+收缩后的金额 | 增长阶段≥90%；规模化阶段≥95% |
| 客户留存率（Logo Retention） | 续约客户占比 | 增长阶段≥85%；规模化阶段≥90% |
| 净收入留存率（NRR） | GRR + 扩张收入 | 增长阶段≥110%；规模化阶段≥120% |
| 收缩率（Contraction） | 现有客户减少席位/使用量导致的收入下降 | 年度<5% |
| 扩张率（Expansion） | 现有客户增长带来的收入 | 健康状态下年度15-25% |
运行 并输入群组数据，以完成真实拆解+流失根因分类。
retention_decomposition_analyzer.py查看获取7类流失分类体系+领先指标手册。
references/retention_decomposition.md2. Customer Segmentation
2. 客户细分
The trap: "Every customer is important."
The reality: customers exist on a spectrum of ICP fit × strategic value. Treating them identically wastes CS capacity and ignores expansion opportunity.
4-tier framework (B2B SaaS baseline):
| Tier | ARR range | Coverage | Investment per account/yr |
|---|---|---|---|
| Strategic | Top 5%, often $100K+ | Named CSM + executive sponsor | $20K-50K |
| Enterprise | Next 15-20%, $20K-100K | Named CSM | $5K-15K |
| Mid-market | Next 30-40%, $5K-20K | Pooled CSM + automation | $1K-3K |
| SMB / Long-tail | Bottom 40-50%, <$5K | Tech-touch + self-serve | $50-500 |
Run to design segmentation tiers + differential investment + ICP fit scoring.
customer_segmentation_designer.pySee for ICP fit framework, tier transition triggers, and the kill list (customers below the investment floor).
references/customer_segmentation_strategy.md误区：“每个客户都很重要。”
**真相：**客户在ICP匹配度×战略价值的区间内分布。对所有客户一视同仁会浪费CS团队精力，并错失扩张机会。
4分层框架（B2B SaaS基准）：
| 分层 | ARR范围 | 覆盖模式 | 单客户年度投入 |
|---|---|---|---|
| 战略层 | 前5%，通常$100K+ | 专属CSM + 高管对接人 | $20K-50K |
| 企业层 | 次15-20%，$20K-100K | 专属CSM | $5K-15K |
| 中市场层 | 次30-40%，$5K-20K | 共享CSM + 自动化 | $1K-3K |
| SMB / 长尾客户 | 后40-50%，<$5K | 技术触达 + 自助服务 | $50-500 |
运行 设计细分层级+差异化投入+ICP匹配评分。
customer_segmentation_designer.py查看获取ICP匹配框架、层级转换触发条件及淘汰清单（投入低于阈值的客户）。
references/customer_segmentation_strategy.md3. CS Team Coverage Model
3. CS团队覆盖模型
The trap: "Hire one CSM per X customers" with a single ratio across all segments.
The reality: coverage model depends on segment, ACV, and complexity. Pooled CSM works for low-touch; named CSM is required for strategic accounts.
Coverage models:
| Model | Best for | Ratio (ARR-per-CSM) | Trade-offs |
|---|---|---|---|
| Tech-touch (no human) | SMB, low ACV | $5M-15M+ | Automation cost; cannot save high-stakes deals |
| Pooled CSM | Mid-market | $2M-5M | Lower cost; less account intimacy |
| Named CSM | Enterprise | $500K-2M | Higher cost; deeper relationships |
| Named CSM + exec sponsor | Strategic | $300K-1M | Highest cost; reserved for top accounts |
Run with book characteristics to calculate required CSM headcount and identify transition thresholds.
cs_coverage_calculator.pySee for ratios, ramp curves, and the "when to add a manager" trigger.
references/cs_coverage_model.md误区：“每X个客户招聘1名CSM”，对所有细分采用单一比率。
**真相：**覆盖模型取决于客户细分、ACV及业务复杂度。共享CSM适用于低触达场景；专属CSM是战略客户的必备配置。
覆盖模型：
| 模型 | 适用场景 | 比率（ARR-per-CSM） | 取舍 |
|---|---|---|---|
| 技术触达（无人工） | SMB、低ACV | $5M-15M+ | 自动化成本；无法挽救高风险客户 |
| 共享CSM | 中市场 | $2M-5M | 成本更低；客户粘性更弱 |
| 专属CSM | 企业客户 | $500K-2M | 成本更高；客户关系更深 |
| 专属CSM + 高管对接人 | 战略客户 | $300K-1M | 成本最高；仅服务顶级客户 |
运行 并输入客户数据，计算所需CSM人数并确定转型阈值。
cs_coverage_calculator.py查看获取比率基准、成长曲线及“何时招聘经理”的触发条件。
references/cs_coverage_model.md4. CS Team Org Evolution
4. CS团队组织演进
The wrong question: "Should we hire a CSM or a Support engineer?"
The right question: "What's the next customer outcome we're failing to deliver, and what role unblocks that?"
Critical distinctions (founders confuse these):
| Role | Owns | Does NOT own |
|---|---|---|
| Customer Support | Reactive issue resolution (ticket queue) | Renewal, expansion, success outcomes |
| Customer Success Manager | Proactive value realization + renewal + expansion lead | Day-to-day tickets, implementation |
| Account Manager | Commercial relationship + expansion close | Day-to-day success, technical depth |
| Implementation Manager | Onboarding + go-live | Ongoing success after launch |
| CS Operations | Tooling, data, analytics, playbooks | Direct customer relationships |
| Customer Marketing | Advocacy, case studies, references | 1:1 customer relationships |
See for stage-to-role map (seed → late-stage) + the AM-vs-CSM split decision.
references/cs_team_org_evolution.md错误问题：“我们应该招聘CSM还是支持工程师？”
正确问题：“我们当前未能实现的核心客户成果是什么，哪种岗位能解决这个问题？”
关键职责区分（创始人常混淆）：
| 岗位 | 负责内容 | 不负责内容 |
|---|---|---|
| 客户支持 | 被动问题解决（工单队列） | 续约、扩张、成功成果 |
| 客户成功经理（CSM） | 主动价值实现 + 续约 + 扩张线索 | 日常工单、实施工作 |
| 客户经理（AM） | 商务关系 + 扩张成交 | 日常客户成功、技术深度支持 |
| 实施经理（IM） | 入职 + 上线 | 上线后的持续客户成功 |
| CS运营 | 工具、数据、分析、操作手册 | 直接客户对接 |
| 客户营销 | 客户推荐、案例研究、参考客户 | 一对一客户关系 |
查看获取阶段-岗位映射表（种子轮→后期）+ AM与CSM的分工决策。
references/cs_team_org_evolution.mdWorkflows
工作流程
Workflow 1: Quarterly Retention Review (4 hours)
工作流程1：季度留存回顾（4小时）
Goal: Decompose retention honestly + identify top-3 churn drivers.
bash
undefined**目标：**真实拆解留存率+确定Top3流失驱动因素。
bash
undefined1. Pull cohort data: closed/won by quarter for last 8 quarters
1. 获取群组数据：过去8个季度的赢单客户数据
python scripts/retention_decomposition_analyzer.py cohorts.json
python scripts/retention_decomposition_analyzer.py cohorts.json
2. Review GRR / NRR / contraction / expansion separately
2. 分别查看GRR / NRR / 收缩率 / 扩张率
3. For each cohort showing GRR < 90%: identify churn root cause (7-category taxonomy)
3. 针对GRR < 90%的群组：确定流失根因（7类分类体系）
4. Cross-check with cs-cro-advisor: does the expansion math add up?
4. 与cs-cro-advisor交叉验证：扩张数据是否合理？
5. Cross-check with cs-cpo-advisor: are product gaps driving churn?
5. 与cs-cpo-advisor交叉验证：产品缺陷是否导致流失？
6. Output: top-3 leakage points + 90-day mitigation plan
6. 输出：Top3流失点+90天缓解计划
undefinedundefinedWorkflow 2: Customer Segmentation Audit (1 day)
工作流程2：客户细分审计（1天）
Goal: Re-segment customer base + reset differential investment.
bash
undefined**目标：**重新细分客户群+重置差异化投入。
bash
undefined1. Build customers.json with ARR, tenure, ICP fit signals
1. 构建包含ARR、使用时长、ICP匹配信号的customers.json
python scripts/customer_segmentation_designer.py customers.json
python scripts/customer_segmentation_designer.py customers.json
2. Identify segment migration (mid-market → enterprise upgrades, downsells)
2. 确定客户细分迁移（中市场→企业升级、降级）
3. Identify kill list (customers below investment floor)
3. 确定淘汰清单（投入低于阈值的客户）
4. Output: new tier assignment + investment-per-tier + kill list for sales review
4. 输出：新分层分配+各分层投入+供销售团队审核的淘汰清单
undefinedundefinedWorkflow 3: CS Team Sizing (1 week)
工作流程3：CS团队规模规划（1周）
Goal: Size the CS team aligned to book composition + coverage model.
bash
undefined**目标：**根据客户构成+覆盖模型确定CS团队规模。
bash
undefined1. Build book.json with current customer base + planned acquisition
1. 构建包含当前客户群+计划获取客户的book.json
python scripts/cs_coverage_calculator.py book.json
python scripts/cs_coverage_calculator.py book.json
2. Calculate required CSM headcount by segment
2. 按细分计算所需CSM人数
3. Compare to current team; identify gaps
3. 与现有团队对比；确定缺口
4. Cross-check with cs-chro-advisor on comp + leveling
4. 与cs-chro-advisor交叉验证薪酬+职级
5. Cross-check with cs-cfo-advisor on the cost
5. 与cs-cfo-advisor交叉验证成本
6. Output: 12-month hiring plan + role sequence
6. 输出：12个月招聘计划+岗位顺序
undefinedundefinedWorkflow 4: CS Team Roadmap (1 week)
工作流程4：CS团队路线图（1周）
Goal: Sequence next 18 months of CS hires aligned to customer outcomes.
- List top 5 customer outcomes the company is failing to deliver
- Map each outcome to the role that unblocks it (CSM / AM / IM / Support / CS Ops)
- Sequence hires; respect prerequisite order
- Cross-check with cs-chro-advisor
**目标：**根据客户成果确定未来18个月CS岗位招聘顺序。
- 列出公司当前未能实现的Top5客户成果
- 将每个成果映射到对应的解决岗位（CSM / AM / IM / 支持 / CS运营）
- 确定招聘顺序；遵循先决条件顺序
- 与cs-chro-advisor交叉验证
Output Standards
输出标准
**Bottom Line:** [one sentence — decision and rationale]
**The Decision:** [one of: retention | segmentation | coverage | next hire]
**The Evidence:** [numbers from the tool, not adjectives]
**How to Act:** [3 concrete next steps]
**Your Decision:** [the call only the founder can make]**核心结论：**[一句话——决策及理由]
**决策类型：**[以下之一：留存率 | 细分 | 覆盖模型 | 下一个招聘岗位]
**依据：**[来自工具的数据，而非形容词]
**行动方案：**[3个具体后续步骤]
**创始人决策：**[仅创始人可做出的决定]Adjacent Skills
相关技能
- — Revenue math, NRR, expansion comp (CCO owns customer experience; CRO owns revenue math; clean split)
../cro-advisor/ - — Product strategy, JTBD (CCO surfaces product gaps; CPO decides roadmap)
../cpo-advisor/ - — Customer marketing, advocacy, references
../cmo-advisor/ - — CS team cost, retention-impact-on-revenue math
../cfo-advisor/ - — CS team hiring + leveling
../chro-advisor/ - — Tactical CS execution: health scores, CRM workflows, onboarding tooling
../../../business-growth/
- —— 收入测算、NRR、扩张薪酬（CCO负责客户体验；CRO负责收入测算；职责清晰划分）
../cro-advisor/ - —— 产品战略、JTBD（CCO提出产品缺陷；CPO制定路线图）
../cpo-advisor/ - —— 客户营销、客户推荐、参考客户
../cmo-advisor/ - —— CS团队成本、留存率对收入影响的测算
../cfo-advisor/ - —— CS团队招聘+职级评定
../chro-advisor/ - —— CS战术执行：健康评分、CRM工作流、入职工具
../../../business-growth/
References
参考资料
- retention_decomposition.md — GRR vs NRR honest math + 7-category churn taxonomy + leading indicator playbook
- customer_segmentation_strategy.md — 4-tier framework + ICP fit scoring + tier transition triggers + kill list criteria
- cs_coverage_model.md — Coverage model decision (tech-touch / pooled / named / named+exec) + ratio benchmarks + manager-trigger
- cs_team_org_evolution.md — Stage-to-role map + 6-role definition table (CSM ≠ Support ≠ AM ≠ IM ≠ CS Ops ≠ Customer Marketing) + AM-vs-CSM split decision + anti-patterns
Version: 1.0.0
Status: Production Ready
Disclaimer: Retention benchmarks vary significantly by ACV, segment, and industry. This skill provides B2B SaaS-baseline guidance; consumer SaaS, marketplaces, and hardware all have materially different retention math.
- retention_decomposition.md —— GRR与NRR真实测算+7类流失分类体系+领先指标手册
- customer_segmentation_strategy.md —— 4分层框架+ICP匹配评分+层级转换触发条件+淘汰清单标准
- cs_coverage_model.md —— 覆盖模型决策（技术触达/共享/专属/专属+高管）+比率基准+经理招聘触发条件
- cs_team_org_evolution.md —— 阶段-岗位映射表+6类岗位定义表（CSM ≠ 支持 ≠ AM ≠ IM ≠ CS运营 ≠ 客户营销）+AM与CSM分工决策+反模式
**版本：**1.0.0
**状态：**已就绪可投入生产
**免责声明：**留存率基准因ACV、客户细分及行业差异显著。本技能提供B2B SaaS基准指导；消费级SaaS、平台及硬件产品的留存测算逻辑存在本质差异。