Cs Operations

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 → Realise Value → Renew → Expand. Without it, you're relying on individual heroics instead of systems.

The CS Ops Operating Model

Four pillars. Neglect any one and the system breaks.

PROCESS DESIGN          TECHNOLOGY & SYSTEMS
├─ Playbooks            ├─ CS Platform (Gainsight, ChurnZero, Vitally, Planhat)
├─ Workflows            ├─ Product analytics (Pendo, Amplitude)
├─ Escalation paths     ├─ Support (Zendesk, Intercom)
├─ Governance           ├─ Survey tools (NPS, CSAT)
└─ Swimlanes            └─ Data warehouse integration

DATA & ANALYTICS        ENABLEMENT
├─ Health scores        ├─ CSM onboarding (2 weeks, not 2 months)
├─ Churn prediction     ├─ Playbook documentation
├─ Expansion scoring    ├─ Tools training
├─ Cohort analysis      ├─ Certification on key processes
└─ Team efficiency      └─ Knowledge base

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     │ €50K ARR       │ Named CSM        │ 1:10-30    │
│ (Strategic)  │ Complex product │ Quarterly EBRs   │            │
│              │ High expansion  │ Dedicated onboard│            │
├──────────────┼─────────────────┼─────────────────┼────────────┤
│ MID-TOUCH    │ €10-50K ARR     │ Pooled CSM       │ 1:30-80    │
│ (Scaled)     │ Moderate complex│ Templated touches│            │
│              │ Growth potential│ Triggered playbks│            │
├──────────────┼─────────────────┼─────────────────┼────────────┤
│ LOW-TOUCH    │ 50% ACV):  Sales owns, CS supports

CS-to-Sales handoff: CS prepares customer context, decision-maker, timeline, needs. Sales accepts or declines. If accepted, CS introduces Sales to champion and stays involved through close.

Onboarding Orchestration

DAY 1-7: ACTIVATION
  Welcome email (within 2 hours), license activation, kickoff scheduled
  Success criteria defined: "What does success look like?"

DAY 8-30: IMPLEMENTATION
  Configuration, data migration, user training
  Weekly status calls, blocker resolution
  Milestone: Go-live readiness confirmed

DAY 31-60: STABILIZATION
  Go-live, first-week support surge (daily check-ins)
  Usage monitoring, issue resolution, user adoption tracking
  First value delivered: "Here's the impact you're seeing"

DAY 61-90: OPTIMIZATION
  Performance vs. success criteria, advanced feature rollout
  Executive check-in, health score baseline set
  Transition to business-as-usual CSM cadence

Automation triggers: No kickoff by day 3 → reminder. Not go-live by day 30 → alert manager. Usage 30% week-over-week) Action: CSM outreach within 24 hours Root cause: Change, vacations, budget freeze, support issue?

NPS DETRACTOR (Score 90% Onboarding NPS/CSAT Target: > 8/10 Feature adoption at T+30 Target: > 3 core features

### Renewal Process Timeline

T-120 DAYS: Renewal flag auto-created in CRM CSM reviews account health, usage, and expansion signals If health 80% utilisation)

• New departments/teams using the product
• Feature requests for premium-tier functionality
• Champion promoted or new exec sponsor engaged
• Positive health trend (score increasing 3+ months)
• Customer referral or case study participation

EXPANSION SCORING MODEL: Score 0-100 based on: Usage growth (30%) — is usage increasing month-over-month? Stakeholder breadth (25%) — are new people engaging? Feature depth (20%) — are they using advanced features? Health trajectory (15%) — is health score trending up? Contract headroom (10%) — is there room to expand (seats, usage, products)?

EXPANSION OWNERSHIP: Score 0-40: CSM monitors. No active sell. Score 41-70: CSM plants seeds. Shares relevant content. Mentions capabilities. Score 71-100: CSM initiates expansion conversation. If deal > threshold → hand to AE.

Handoff threshold: Varies by org. Typical: expansion > 30% of current ACV → AE involved. Below threshold: CSM closes expansion directly (with approval).

WHITESPACE ANALYSIS: For each account, map: Products purchased vs available → product whitespace Users/seats vs potential → seat whitespace Departments using vs total → department whitespace Features adopted vs available → feature whitespace Stakeholders engaged vs org chart → relationship whitespace

Review in QBR. Update quarterly. Use to prioritise expansion plays.

## CS-Product Feedback Loop

QUARTERLY ADVISORY BOARD 3-5 key customer executives + Product VP Topics: Roadmap, feature priorities, competitive gaps Output: Customer priorities feed product planning

CHURN AUTOPSY (100% of churned accounts) Owner: CS Manager + Product Manager Questions: Why? When was decision made? Could we prevent it? Output: Product backlog item, process change, or competitive intel

FEATURE REQUEST TAGGING Every request tagged with: customer ARR, use case, competitive pressure, expansion impact, adoption blocker (Y/N) Product uses tags to prioritize backlog

ADOPTION BLOCKER LOG (Monthly review) Features blocking renewal/expansion get separate Product queue Quick fixes (90% (>95% enterprise) NRR >110% Logo retention rate >90% Expansion rate (% ARR growth) >15%/year

OPERATIONAL Time to first value 70% green QBR completion (high-touch) 100% Renewal on-time rate >90% Save rate (red accounts) >40%

EFFICIENCY Accounts per CSM (by tier) See coverage model Admin time (% of total) 70%

## Diagnostic Assessment

Score your CS Ops maturity. Count YES answers:

PROCESS: Documented playbooks? Defined renewal timeline? Health scoring framework? Escalation paths? QBRs for all high-touch? TECHNOLOGY: Dedicated CS platform? Integrates with product analytics? Automated health scoring? Usage data visible to CSMs? DATA: Can forecast churn 30+ days out? Health dashboards? Track expansion signals? Segment by tier? Measure team efficiency? ENABLEMENT: Structured CSM onboarding? Accessible playbooks? Process certification? Monthly training? GOVERNANCE: CS-Product feedback loop? CS-Sales handoff process? Exec reviews CS metrics monthly? Churn autopsies? Expansion ownership clear? Discount sunset tracking in place?

0-6 YES = Reactive. Fix: Define playbooks, build basic health scoring 7-13 YES = Defined. Fix: Integrate tech, automate playbooks 14-19 YES = Proactive. Fix: Build predictive models, optimize coverage 20-25 YES = Predictive. Fix: AI-assisted coaching, autonomous workflows

## Structured Onboarding-to-Renewal Process

Health scoring and renewal frameworks answer "who is at risk?" and "how do we retain them?" But they depend on a structured operational process from handoff to renewal. This section covers the end-to-end CS process model.

### Handoff and Onboarding Process (Sales → CS Transition)

The handoff is where retention is won or lost. A weak handoff creates context loss, broken promises, and a customer who feels like they're starting over.

**Pre-handoff (Sales responsibility):**
- Complete the SPICED summary in CRM (especially: Situation, Pain, Impact, Critical Event)
- Document committed outcomes — what did the customer buy the product to achieve?
- Identify the champion and economic buyer — who owns success internally?
- Flag any non-standard terms, pricing exceptions, or promised professional services

**Handoff meeting (Sales + CS):**
- Three-way call: Sales rep, CS lead, and customer champion
- Agenda: review committed outcomes, introduce CS team, confirm implementation timeline
- Transfer of relationship, not just account

**Onboarding process (CS responsibility):**
- Week 1: Kick-off call with success criteria defined (use SPICED Impact as baseline)
- Week 2-4: Implementation milestones tracked and reported to customer
- Day 30: First value checkpoint — has the customer experienced any tangible outcome?
- Day 60: Adoption checkpoint — is the product embedded in their workflow?
- Day 90: First health score review; confirm or redefine success criteria for Year 1

### Customer Health Monitoring Cadence

Health scoring defines the score. The cadence defines what you do with it.

FREQUENCY ACTIVITY OWNER ───────── ──────── ───── Weekly Review accounts with score drop > 10pts CSM (automated alert) Flag any Green → Yellow or Yellow → Red CSM + CS Lead Monthly Full health score review for all accounts CSM per account Escalation: any Red account reviewed with CS Lead + AE CS Lead and AE Update health scores based on new data CSM Quarterly Portfolio health review (CS team) CS Lead QBR preparation for T1 accounts CSM Red account recovery planning CS Lead + AE

A health score without a review cadence is a dashboard no one acts on. The cadence is the operating system; the score is the signal.

### Process for Unhealthy Customers (Red Account Playbook)

Signals aren't enough. Define the playbook triggers — what happens automatically when a customer turns Red.

**Immediate actions (within 24 hours of Red flag):**
1. CSM notifies CS Lead
2. CS Lead reviews health breakdown — which dimension is driving Red? (Usage? Engagement? NPS? Adoption?)
3. CS Lead and AE jointly decide: rescue mode or renewal risk conversation

**Rescue mode (if > 90 days until renewal):**
- Executive outreach: CS Lead or Head of CS calls the economic buyer directly
- Root cause session: structured call to understand what went wrong
- Recovery plan: documented list of 3-5 actions with owners and deadlines
- Weekly check-in until back to Yellow

**Renewal risk mode (if  Built by [Neon Triforce](https://neontriforce.com)

---

## WbD Impact Journey — CS Action Framework

The Impact Journey maps the post-Mutual Commit customer journey into structured CS actions. Source: WbD Operating Model PDF, Chapter 08, pages 143-148.

### The 8 Stages (post-Mutual Commit focus)

| Stage | What's happening | CS Action |
|---|---|---|
| Mutual Commit | Contract signed — ownership transfers from Sales to CS | O1. Handoff from Sales |
| Onboarding | Setup, training, implementation begins | O2. Customer Kickoff; O3. Joint Impact Plan; O4. Achieve First Impact |
| Adoption / Retention | Customer uses product, realises core value | A1. Drive Impact Process; A2. Impact Review; A3. Health Scoring; A4. Trigger Plays |
| Renewal | Customer decides whether to continue | A5. Renewal using SPICED reassessment |
| Expansion | Customer adds scope, users, or capabilities | E1–E5: Whitespace Planning → Expansion Execution |
| Advocacy | Customer becomes promoter and reference | Implied: reference requests, case study participation |

### Health score interpretation by stage

- **Onboarding:** Track against Joint Impact Plan milestones. Red flag: first impact not achieved within agreed timeline.
- **Adoption:** Monitor active usage, CRM engagement, champion responsiveness. Score drops ≥20% in 30 days = trigger play.
- **Expansion readiness:** Customer has achieved consistent impact AND has whitespace (additional use cases or departments).

### Trigger plays by stage

| Trigger | Signal | Play |
|---|---|---|
| First Impact at risk | Onboarding >120% of agreed timeline | Executive sponsor call + revised Joint Impact Plan |
| Adoption plateau | Usage flat for 60+ days post-onboarding | Impact Review meeting, identify blockers |
| Churn risk | Health score <40, no champion engagement | Escalation play: CS + Sales + exec touch |
| Expansion signal | Consistent adoption, stakeholder growth, whitespace identified | Whitespace Planning session |

### Expansion timing guardrail

**Do not expand before First Impact (Stage O4).** Customers who are still in onboarding and asked about expansion create distrust. The signal to start expansion conversations: customer has achieved the core Impact documented in the Joint Impact Plan AND usage is spreading across the team (multiple stakeholders engaged).

Customers achieving impact in a **single area only** are more at risk of churn than customers with **widespread stakeholder usage** — expand to cover multiple Impact areas wherever possible.

---

## Operator Templates — Forecasting Worksheet (Renewals Tab)

The Renewals tab of the forecasting worksheet is specifically useful for CS operations modelling:
`Frameworks/Templates/cro-school/forecasting-worksheet-neon.xlsx`

Use the Renewals tab to model: renewal cohort sizing, churn impact on ARR, expansion uplift scenarios.

Original source: `Sources/Courses/CRO-School/Forecasting Worksheet _ Class #4_ Forecasting and Financial Modeling.xlsx`
Attribution: Adapted from Pavilion CRO School. Original author: Carter/Nalbandian/Dick.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [NEON-Rutger](https://github.com/NEON-Rutger)
- **Source:** [NEON-Rutger/B2B-revops-skills](https://github.com/NEON-Rutger/B2B-revops-skills)
- **License:** MIT
- **Homepage:** https://www.neontriforce.com

Install and usage instructions live in the source repository linked above.