cs-strategy
Define customer success strategy — segmentation, coverage model, motions, and outcomes — aligned to retention and expansion goals. Use when designing or resetting a CS org model, coverage, or success philosophy.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- cs-strategy
- description
- Define customer success strategy — segmentation, coverage model, motions, and outcomes — aligned to retention and expansion goals. Use when designing or resetting a CS org model, coverage, or success philosophy.
03 SKILL.md 正文
Customer Success Strategy
Overview
CS strategy decides which customers get which level of help, what “success” means, and how CS creates retention and expansion value without becoming unscalable concierge service.
When to Use
- Building or restructuring a CS function
- Choosing high-touch vs tech-touch vs hybrid coverage
- Aligning CS goals with revenue retention targets
- Defining the CS role versus Support, Sales, and Product
Core Practices
- Segment customers by value, potential, and needs
- Match coverage model (1:1, pooled, digital) to segments
- Define success outcomes per segment (not only activity metrics)
- Set clear handoffs with Sales, Support, and Professional Services
- Align CS capacity to book-of-business reality
- Measure leading indicators of retention and expansion
Principles
- Not every customer needs a dedicated CSM
- Success is customer outcomes, not email volume
- CS strategy must match product complexity and ACV
- Scale requires product-led success paths, not only headcount
Verification
- [ ] Segments and coverage model are explicit
- [ ] CS outcomes tie to retention/expansion goals
- [ ] Role boundaries with adjacent teams are clear
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.