关于 customer-success
面向客户成功经理的工作技能,提供客户引导、关系管理、留存和扩展账户的框架与模板,并用健康评分辅助风险识别。
主要功能
- 01客户引导与实施规划
- 02账户健康评分框架
- 03QBR 与客户关系管理
- 04流失预警与挽留计划
- 05续约及扩展机会识别
适用场景
- 01规划客户上线和首次价值达成
- 02根据使用与参与指标评估账户健康
- 03准备季度业务回顾
- 04识别流失风险或扩展机会
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ dengineproblem/ agents-monorepo --skill customer-success安装后在 Claude Code 中输入/customer-success确认已加载。
README 原文English
来自项目 READMEREADME 暂无中文译文,以下为英文原文;中文介绍见上方。
Customer Success Manager
Эксперт по обеспечению ценности клиента, retention и росту.
Core Competencies
Customer Onboarding
- Implementation planning
- Kick-off meetings
- Training and enablement
- Go-live support
- Time-to-value acceleration
Relationship Management
- Executive business reviews
- Account health monitoring
- Stakeholder mapping
- Champion development
- Escalation handling
Retention & Expansion
- Renewal management
- Upsell identification
- Churn prevention
- Account expansion
- Advocacy development
Health Score Framework
const healthScoreWeights = {
productUsage: 0.30, // 30%
engagement: 0.25, // 25%
supportMetrics: 0.20, // 20%
businessOutcomes: 0.15, // 15%
relationshipStrength: 0.10 // 10%
};
function calculateHealthScore(account) {
const scores = {
productUsage: calculateUsageScore(account),
engagement: calculateEngagementScore(account),
supportMetrics: calculateSupportScore(account),
businessOutcomes: calculateOutcomesScore(account),
relationshipStrength: calculateRelationshipScore(account)
};
let totalScore = 0;
for (const [metric, weight] of Object.entries(healthScoreWeights)) {
totalScore += scores[metric] * weight;
}
return Math.round(totalScore);
}
function getHealthCategory(score) {
if (score >= 80) return { status: 'green', action: 'expand' };
if (score >= 50) return { status: 'yellow', action: 'nurture' };
return { status: 'red', action: 'save' };
}
Health Score Components
Product Usage (30%)
Metrics:
- DAU/MAU ratio
- Feature adoption breadth
- Usage frequency trend
- Active seats vs purchased
Scoring:
90-100: Usage exceeds benchmarks
70-89: Healthy usage patterns
50-69: Below average usage
0-49: At risk - low engagement
Engagement (25%)
Metrics:
- Meeting attendance
- Response rates
- Training completion
- Community participation
- NPS responses
Scoring:
90-100: Highly engaged champion
70-89: Regular engagement
50-69: Sporadic engagement
0-49: Disengaged - outreach needed
Support Metrics (20%)
Metrics:
- Ticket volume trend
- Escalation frequency
- Resolution satisfaction
- Self-service adoption
Scoring:
90-100: Minimal support needs, high CSAT
70-89: Normal support pattern
50-69: Elevated issues
0-49: Critical - many unresolved issues
Business Outcomes (15%)
Metrics:
- ROI achieved vs promised
- KPI improvements
- Goals met
- Value realization
Scoring:
90-100: Exceeding expected outcomes
70-89: On track to meet goals
50-69: Partial value realization
0-49: Not achieving expected value
Relationship Strength (10%)
Metrics:
- Executive sponsor access
- Multi-threaded contacts
- Champion strength
- Competitive mentions
Scoring:
90-100: Strong multi-threaded relationship
70-89: Good sponsor relationship
50-69: Single-threaded
0-49: No executive access
Customer Lifecycle
Phase 1 - Onboarding (Days 0-90):
Goals:
- Complete implementation
- Train key users
- Achieve first value milestone
Touchpoints:
- Kick-off call (Day 1)
- Weekly check-ins (Weeks 1-4)
- Training sessions
- Go-live celebration
Metrics:
- Time to value
- Training completion %
- Feature adoption
Phase 2 - Adoption (Days 90-180):
Goals:
- Expand usage
- Identify champions
- Document success stories
Touchpoints:
- Bi-weekly check-ins
- Usage reviews
- Advanced training
Metrics:
- DAU/MAU
- Feature depth
- NPS
Phase 3 - Optimization (Days 180-270):
Goals:
- Maximize ROI
- Identify expansion opportunities
- Strengthen relationships
Touchpoints:
- Monthly reviews
- QBR preparation
- Executive alignment
Metrics:
- ROI metrics
- Expansion pipeline
- Health score
Phase 4 - Renewal (Days 270-365):
Goals:
- Secure renewal
- Execute expansion
- Build advocacy
Touchpoints:
- Renewal kickoff (90 days out)
- Business case review
- Contract negotiation
Metrics:
- Renewal rate
- Expansion ARR
- References
QBR Template
# Quarterly Business Review
**Customer:** [Company Name]
**Date:** [Date]
**Attendees:** [Names]
## Executive Summary
- Overall health: [Green/Yellow/Red]
- Key wins this quarter
- Areas of focus for next quarter
## Value Delivered
| Goal | Target | Actual | Status |
|------|--------|--------|--------|
| [Goal 1] | [#] | [#] | ✅/⚠️/❌ |
| [Goal 2] | [#] | [#] | ✅/⚠️/❌ |
## Product Usage
- Active users: [#] / [#] licensed
- Most used features: [List]
- Adoption opportunities: [List]
## Support Summary
- Tickets: [#] opened, [#] resolved
- CSAT: [#]%
- Open issues: [List]
## Next Quarter Priorities
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
## Expansion Opportunities
- [Opportunity 1]: [Details]
- [Opportunity 2]: [Details]
## Action Items
| Action | Owner | Due Date |
|--------|-------|----------|
| [Action 1] | [Name] | [Date] |
| [Action 2] | [Name] | [Date] |
Churn Prevention Playbook
Early Warning Signals
Red Flags:
- Health score drop > 20 points
- Executive sponsor left
- Competitive RFP
- Support escalations increasing
- Usage declining > 30%
- Missed QBRs
- Delayed renewal conversation
Immediate Actions:
1. Schedule executive touchpoint
2. Conduct root cause analysis
3. Create save plan
4. Involve executive sponsor (internal)
5. Offer concessions if justified
Save Plan Template
# Account Save Plan
**Customer:** [Name]
**Risk Level:** [Critical/High/Medium]
**Renewal Date:** [Date]
## Situation Analysis
- Root cause: [Description]
- Stakeholder sentiment: [Details]
- Competitive threat: [Yes/No - Details]
## Action Plan
| Week | Action | Owner | Goal |
|------|--------|-------|------|
| 1 | Executive call | CSM + VP | Understand concerns |
| 2 | Value assessment | CSM | Document ROI |
| 3 | Roadmap review | Product | Address gaps |
| 4 | Proposal | CSM + Sales | Present solution |
## Success Criteria
- [ ] Executive meeting completed
- [ ] Concerns documented and addressed
- [ ] Renewal commitment obtained
## Escalation Path
- Day 1-7: CSM owner
- Day 8-14: CS Manager involved
- Day 15+: VP CS + Executive sponsor
Expansion Playbook
Identifying Opportunities
Signals:
- Usage hitting limits
- New use cases emerging
- Organizational growth
- Champion promotion
- Positive NPS/feedback
- Successful QBR
Expansion Types:
- Upsell: Higher tier, more features
- Cross-sell: Additional products
- Seat expansion: More users
- Department expansion: New teams
Expansion Conversation
## Discovery Questions
1. "What new initiatives is the company focused on?"
2. "Are there other teams facing similar challenges?"
3. "How has your usage evolved since we started?"
4. "What would make [product] even more valuable?"
## Value Positioning
- Current ROI: [quantified impact]
- Additional value opportunity: [projected impact]
- Success story: [relevant case study]
## Proposal Framework
- Start with achieved outcomes
- Connect to business priorities
- Present expansion as natural next step
- Include ROI projection
Performance Metrics
Team Metrics:
Net Revenue Retention: > 110%
Gross Retention: > 90%
Average Health Score: > 75
NPS: > 50
Time to Value: < 30 days
Individual Metrics:
Book of Business: $[X]M ARR
Accounts: [X] customers
Renewals On-Time: > 95%
Expansion Rate: > 15%
Health Score Improvement: +5 points/quarter
Customer Segmentation
Enterprise (> $100k ARR):
Touch model: High-touch
CSM ratio: 1:8
Touchpoints: Weekly/Bi-weekly
QBRs: Quarterly
Mid-Market ($25k-$100k ARR):
Touch model: Medium-touch
CSM ratio: 1:25
Touchpoints: Monthly
QBRs: Bi-annually
SMB (< $25k ARR):
Touch model: Tech-touch
CSM ratio: 1:100+
Touchpoints: Automated + triggered
QBRs: On-demand
Tools & Systems
CRM: Salesforce / HubSpot
- Account data
- Opportunity tracking
- Activity logging
CS Platform: Gainsight / ChurnZero
- Health scores
- Playbook automation
- Journey orchestration
Analytics: Amplitude / Mixpanel
- Product usage
- Feature adoption
- Engagement tracking
Communication: Slack / Teams
- Customer channels
- Internal escalation
- Quick updates
Лучшие практики
- Proactive > Reactive — предвосхищайте проблемы
- Data-driven — решения на основе метрик
- Multi-threaded — отношения на всех уровнях
- Document everything — история взаимодействий
- Collaborate — работайте с Sales, Product, Support
- Celebrate wins — отмечайте успехи клиентов
评论
支持 Markdown