Skip to content
Documentation

Customer Success — Health, Churn, and Expansion

FieldValue
TypeSkill Resource
Source~/.copilot/skills/exec/references/customer-success.md
DescriptionNot specified

Source Content

Customer Success — Health, Churn, and Expansion

When to use this

You’re running a SaaS customer success program and need to know the truth about each account — health, risk, expansion opportunity — and act on it before the renewal. QBRs, success plans, renewal coaching, onboarding design, or churn-risk triage.

The outcome-first principle

Every account has a job they hired you for. Not the features they use — the progress they’re trying to make. “Help us scale our support team without doubling headcount” (outcome) is different from “they use our API integration” (feature usage).

Start with the outcome, then look at the signals (usage, engagement, support interactions, relationship health) to see if they’re making progress on that job.

Health scoring framework

Health scoring works across four dimensions:

  1. Usage. Are they using the product the way they need to? Frequency, adoption breadth, core feature adoption.
  2. Engagement. Is there evidence of active use and value realization? Login frequency, session length, core-feature interactions.
  3. Support. What’s the health of your relationship through support? Ticket volume, ticket tone, escalations, resolution time.
  4. Relationship. Is there executive sponsorship? Champion satisfaction? Competitive mention risk? Buyer/user/champion satisfaction mismatch?

Each dimension gets a weighted score. Red (high churn risk), Yellow (watch closely), Green (stable/growth). The trend matters most — a declining Green is more urgent than stable Yellow.

Classification and intervention

Red accounts: Active intervention needed. Five-day response time. Escalate to management. Propose a restart plan or honest offboard.

Yellow accounts: Weekly check-in. Understand the friction. Propose a play (usage training, feature enablement, success planning) with a 30–60-day horizon.

Green accounts: Proactive outreach. Business reviews quarterly. Identify expansion opportunities (new use cases, new teams, upgrade paths).

Tier-matched plays matter: Enterprise accounts get exec-level attention; SMB accounts get playbook-driven interventions.

Churn-risk signals

Leading indicators (predict churn 60–90 days out):

  • Sponsor change or sponsor satisfaction drop.
  • Core feature adoption decline over 3 months.
  • Unresolved high-severity tickets.
  • Competitor mentions.

Lagging indicators (close to decision):

  • Reduced login frequency.
  • Finance team asking “do we need this?”
  • No exec participation in QBR.

Expansion opportunity signals

Upsell (higher tier, higher price):

  • Usage approaching plan limits.
  • New team/department adoption.
  • Positive NPS and high engagement.

Cross-sell (new product):

  • Mastery of existing product.
  • Stated need for adjacent capability.
  • Budget available.

Seat growth:

  • New team adoption.
  • Retention of new users hired into their org.

Renewal math

  • ARR at risk: Contract end date × annual contract value × churn probability.
  • Time to renewal: Days until contract end. Priority goes down as time increases (90 days out, act today; 30 days out, implement now).
  • Renewal sentiment: What did the last business review signal? Neutral? Positive? Do they have budget approved?

QBR and success-plan structure

Quarterly Business Review (QBR):

  1. The customer’s desired outcome (the job they hired you for).
  2. Evidence of progress (metrics, wins, milestones hit).
  3. Gaps or obstacles (what’s blocking further progress).
  4. The ask (what they need from you, what you need from them).

Success plan:

  1. Outcome.
  2. Current state (where they are today).
  3. Target state (where they need to be by renewal).
  4. Milestones and owner (with dates).
  5. Metrics and checkpoints (how you’ll know it’s working).

Renewal conversation playbook

For a save play (keep the account):

  1. Name the risk you’re seeing.
  2. Anchor on their outcome, not your product.
  3. Propose a reset with clear milestones.
  4. Get commitment on both sides (they commit to execution; you commit to support).
  5. Weekly check-in for 30 days, then monthly.

For a graceful offboard (mutual recognition it’s not working):

  1. Name the fit problem honestly.
  2. Thank them for the time together.
  3. Leave the door open (they may come back later).
  4. Offer migration support.

Who I learn from

  • Lincoln Murphy — success is the customer’s desired outcome through their interaction with your company.
  • Nick Mehta — CS is where company growth and customer growth meet. CS is a growth engine, not a cost center.
  • Indi Young — listen for understanding, not for responding. The why behind churn signals hides in what you didn’t ask.
  • Jeff Bezos — start with the customer and work backwards.
  • Tony Hsieh — customer service shouldn’t be a department, it should be the entire company.

Constraints

  • Deterministic scoring only — no ML, no magic. Thresholds are calibrated per business model.
  • Scripts analyze point-in-time JSON snapshots; CRM data must be exported manually.
  • This skill does not do new-logo GTM (→ GTM team or acquisition marketing).
  • Product roadmap requests dressed as customer asks belong in the product team (→ product-strategist / prd-generator).
  • Live incident response is not this skill’s job (→ incident-commander).