cs-operations
Installation
Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.
Install the "cs-operations" skill by following the instructions at https://skill123.me/install/cs-operations.
Run in your terminal — downloads and installs to ~/.claude/skills/.
curl -fsSL https://skill123.me/install/cs-operations.sh | bash
Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.
⬇ Download v1.0.0 · 23 KBNot live-tested yet — this skill is rated on static analysis only.
About this skill
Save churning customers through proactive health scoring and recovery plays. Use when red accounts pile up unpredictably, renewal conversations turn contentious, or expansion-ready accounts slip away. Builds a 5-dimension health score (product usage, relationship quality, support friction, commercial trends, outcomes) updated weekly, triages red accounts into rescue mode or renewal-risk mode, and activates save plays with executive sponsorship, backed by the full post-sale operating model (onboarding, QBRs, CS-Sales handoffs, renewal governance). Produces a weekly red-account triage list and recovery playbooks by churn cause. Rule: a customer does not turn red on one signal; red means 3 or more health dimensions breaking at once. Trigger phrases: we keep losing customers, red accounts, health scoring, save play, churn autopsy, renewal price increase resistance.
Customer Success Operations
You are a CS operations architect. CS Ops is the post-sale revenue engine. It sits in the ICP Value Loops layer of the revenue operating system, owning Adopt → Realize Value → Renew → Expand. Without it, you're relying on individual heroics instead of systems.
Documentation
Save churning customers through proactive health scoring and recovery plays. Use when red accounts pile up unpredictably, renewal conversations turn contentious, or expansion-ready accounts slip away. Builds a 5-dimension health score (product usage, relationship quality, support friction, commercial trends, outcomes) updated weekly, triages red accounts into rescue mode or renewal-risk mode, and activates save plays with executive sponsorship, backed by the full post-sale operating model (onboarding, QBRs, CS-Sales handoffs, renewal governance). Produces a weekly red-account triage list and recovery playbooks by churn cause. Rule: a customer does not turn red on one signal; red means 3 or more health dimensions breaking at once. Trigger phrases: we keep losing customers, red accounts, health scoring, save play, churn autopsy, renewal price increase resistance.
Customer Success Operations
You are a CS operations architect. CS Ops is the post-sale revenue engine. It sits in the ICP Value Loops layer of the revenue operating system, owning Adopt → Realize Value → Renew → Expand. Without it, you're relying on individual heroics instead of systems.
Stage check: do this before anything else in this skill
This skill was written for a company that already has a repeatable motion and named owners. Applied at face value to a company that does not, it prescribes governance, scoring and cadences the team cannot run, and it hides the one question that matters at that stage. Sort the company into one of four situations first, state the situation in the first paragraph of the deliverable, and run only the version the table names.
The four situations (full definitions and signals in references/stage-check.md):
1. Start-up, pre product-market fit: fewer than roughly 30 comparable customers, wins from the founders' network, no measured win rate, cycle time or retention, nobody on quota. The only question: do existing customers get the promised outcome and would they buy again? Run the minimum version, or do not run it.
2. Start-up, product-market fit: one segment with 10 or more customers won the same way, a known win rate and cycle time, retention measured monthly, one CRM owner. Run the skill for that one motion; thresholds are guidance, not rules.
3. Scale-up: named owners for sales, marketing, customer success and operations; trusted CRM stage history; reps on quota; a forecast someone is held to. Run the full skill.
4. Enterprise: situation 3 plus more than one revenue organisation, a governance layer above go-to-market decisions, and finance owning the board revenue target. Run the full skill with the enterprise deltas in the table.
View full documentation
If the evidence is thin, ask three yes or no questions: Is there a segment with 10 or more customers won the same way? Is retention measured monthly? Does someone own the CRM as part of their job? Three no answers means situation 1. One or two yes answers means situation 2. Three yes answers means situation 3 or 4; then ask three more: Is there more than one business unit or region with its own revenue plan and leader? Do go-to-market decisions pass through a formal governance layer? Does finance own the revenue target for board reporting? Two or more yes answers means situation 4; otherwise situation 3.
The full skill applies to both scale-up and enterprise. Not every skill applies at every stage; the table below says what this skill does at each, and "do not run" is a valid answer.
What this skill does per situation:
| Situation | What this skill does |
|---|---|
| Start-up, pre product-market fit | Build a basic success criteria checklist per customer (what success looks like, one page). Manually monitor health for your 3-5 earliest customers using one dimension you can observe: product usage, engagement, or support patterns. Weekly check-in on: which accounts are activated, which are stalling, and why? Skip segmentation, health scores, maturity models, and automation; your constraint is understanding whether customers get value, not process formality. |
| Start-up, product-market fit | Implement a Health Score Framework in manual mode: score each account 0-100 from product usage (primary indicator), relationship signals, and support trends. Set renewal timeline: start renewal discussions at T-60 days before contract end, not T-30. Manual tracking via Slack of at-risk accounts and intervention actions. Measure gross revenue retention quarterly; tier accounts by health (green/yellow/red) and conduct a monthly review of yellow and red accounts. |
| Scale-up | Automate health scores from product telemetry, CRM data, and support tickets; update weekly or real-time. Implement three-tier segmentation: high-touch (named CSM, quarterly EBR), mid-touch (pooled CSM, templated cadence), tech-touch (automated, AI-assisted). Renewal timeline: start at T-120 days. Measure time-to-first-value, net revenue retention by segment, and stall-to-churn correlation. Expansion motion: identify expansion signals per segment and trigger outbound expansion conversations for green-tier accounts. |
| Enterprise | Scale CS Ops to multiple business units or geographies, each with its own P&L and success metrics. The skill gains weight in multi-unit account hierarchy and handoff protocols, CS-Finance integration for shared service centre cost allocation across units, portfolio governance with CS health dashboards aggregated by business unit, and enterprise renewal mechanics including multi-stakeholder renewal gates and legal vendor management. Service delivery standardises across units whilst maintaining distinct unit-level accountability. |
Skip before product-market fit: CS Maturity Model; Segmentation & Coverage Models; Event-Based Playbooks; Key Metrics.
The CS Ops Operating Model
Four pillars. Neglect any one and the system breaks.
PROCESS DESIGN TECHNOLOGY & SYSTEMS
├─ Playbooks ├─ CS Platform: Gainsight (Horizon AI, 2024+), ChurnZero,
├─ Workflows │ Vitally; all support real-time ML scoring (2026)
├─ Escalation paths ├─ Product analytics (Pendo, Amplitude)
├─ Governance ├─ Support (Zendesk, Intercom)
├─ Swimlanes ├─ Survey tools (NPS, CSAT; note: Delighted shut 30 Jun 2026)
└─ AI agents └─ Data warehouse integration; reverse ETL (Hightouch, Census)
DATA & ANALYTICS ENABLEMENT
├─ Health scores ├─ CSM onboarding (2 weeks, not 2 months)
│ (ML-powered, real-time) ├─ Playbook documentation
├─ Churn prediction ├─ Tools training
│ (ML+NLP ensemble) ├─ Certification on key processes
├─ Expansion scoring ├─ Knowledge base
├─ Cohort analysis └─ AI-assisted customer signal synthesis
└─ Team efficiency
CS Maturity Model
┌────────────┬──────────────┬────────────────┬───────────────┬──────────────┐
│ Stage │ Health Score │ Renewals │ Expansion │ Governance │
├────────────┼──────────────┼────────────────┼───────────────┼──────────────┤
│ REACTIVE │ None. React │ Ad-hoc, │ Accidental │ CS isolated, │
│ │ to churn. │ customer-led │ │ no loops │
├────────────┼──────────────┼────────────────┼───────────────┼──────────────┤
│ DEFINED │ Manual, CSM │ Playbook, 60d │ Signals ID'd │ Handoff doc │
│ │ judgment │ before expiry │ inconsistently│ exists │
├────────────┼──────────────┼────────────────┼───────────────┼──────────────┤
│ PROACTIVE │ Composite, │ Automated 90d │ Scoring model │ Quarterly │
│ │ weekly auto │ process + save │ + targeted │ CS-Product │
│ │ alerts │ playbooks │ outreach │ forums │
├────────────┼──────────────┼────────────────┼───────────────┼──────────────┤
│ PREDICTIVE │ ML model, │ Preventive │ Expansion │ Real-time │
│ │ >80% churn │ interventions, │ scoring feeds │ feedback │
│ │ accuracy │ <5% churn │ Sales pipeline│ loops │
└────────────┴──────────────┴────────────────┴───────────────┴──────────────┘
If you're Reactive: stop everything else and move to Defined first.
Health Score Framework
The single most important CS Ops tool. Composite scores with weighted dimensions:
HEALTH SCORE = Weighted average of 5 dimensions
PRODUCT USAGE (35%)
Login frequency, feature adoption, depth of use, usage trend
Weight rationale: usage is the strongest churn predictor
RELATIONSHIP (25%)
Executive sponsor engaged, NPS response, meeting cadence, org adoption %
Weight rationale: champions save accounts
SUPPORT (18%)
Ticket volume trend, severity, resolution time, CSAT
Weight rationale: pain signals churn
COMMERCIAL (17%)
Contract value trend, payment history, expansion conversations
Weight rationale: money doesn't lie
OUTCOMES (5%)
Achieving st
Score breakdown
Assessment methodology
Version history
Imported from NEON-Rutger/B2B-revops-skills@main