customer-success

Overview

Customer success ensures customers achieve their desired outcomes with your product — because successful customers renew, expand, and refer. This skill covers the CS operating system: onboarding, health scoring, proactive outreach, QBRs, expansion plays, and churn prevention.

Success is proactive and outcome-focused; support is reactive and ticket-focused. Both matter; they are different jobs.

When to use

• Reducing churn or improving retention

• Designing an onboarding program

• Building customer health scores

• Planning QBRs (quarterly business reviews)

• Creating expansion/upsell plays

• Segmenting customers for scaled vs. high-touch CS

• Designing executive sponsorship programs for strategic accounts

• Building a customer advisory board

• Creating health-score-driven playbooks

• Reducing churn in a SaaS business

• Building onboarding programs

• Creating customer advocacy initiatives

Core concepts

Desired outcomes. Every customer bought a result, not software. Document each account's desired outcome and success criteria at onboarding. Everything CS does ladders up to delivering it.

Customer health scores. Composite of product usage (breadth, depth, trend), support burden, payment health, engagement (QBR attendance, NPS responses), and relationship strength. Score red/yellow/green; act on trends, not snapshots.

Onboarding. The highest-churn-risk period. Structured onboarding: kickoff (align on outcomes and timeline), configuration, training, first value milestone, and handoff to ongoing success. Time-to-first-value is the metric that matters.

Segmentation. High-touch (top accounts, dedicated CSM), low-touch (scaled programs, automation), tech-touch (self-serve, in-app guidance). Match cost-to-serve with account value.

QBRs. Quarterly reviews with stakeholders: outcomes achieved (with their data), value delivered (ROI), roadmap alignment, and expansion discussion. QBRs you skip are renewals you risk.

Expansion. Land-and-expand: usage growth → upsell; new teams → cross-sell; proven ROI → multi-year renewal. Expansion should feel like success, not sales pressure.

Churn prevention. Leading indicators (usage decline, champion departure, support spikes, missed QBRs) trigger save plays: executive outreach, success plans with committed milestones, or commercial flexibility.

Time-to-value (TTV) by segment. The single most predictive onboarding metric: how long from contract to first meaningful outcome. Segment TTV by customer profile — enterprise with complex integrations needs a different target than self-serve SMB. Every week of TTV reduction measurably lifts retention.

Commercial alignment. CS should own leading indicators (health, adoption, NPS) while sharing lagging ones (renewal, expansion) with sales. Clear rules of engagement prevent the classic CS-vs-sales conflict over who owns the renewal conversation.

Health scoring. Combine product usage (depth, breadth, frequency), support patterns (ticket volume, sentiment), commercial signals (payment health, contract timeline), and relationship data (executive engagement, NPS). Weight by what actually predicts churn in your data — not by opinion. Validate quarterly: do low-health accounts actually churn more? Recalibrate relentlessly. Segmentation and coverage models. High-touch (enterprise: dedicated CSM, QBRs, success plans) → low-touch (mid-market: pooled CSMs, automated playbooks) → tech-touch (SMB: fully digital, in-product guidance). Match coverage cost to account value — high-touch on $5k ACV accounts destroys unit economics. Review segmentation annually as ACVs and product complexity evolve. Expansion motions. Adoption expansion (more seats, more usage) → cross-sell (additional products) → advocacy (referrals, reviews, case studies). Expansion follows value realization — pitching upsells before customers see ROI breeds resentment. Track net revenue retention as the ultimate CS metric; everything else is a leading indicator.

Practical workflow

1. Define outcomes and segments. For each segment: desired outcomes, success criteria, and the right touch model. Document the ideal customer journey from sale to renewal.
2. Build onboarding. Checklist-driven, time-bound (30/60/90-day milestones), with clear ownership between sales, implementation, and CS. Measure time-to-first-value per cohort.
3. Instrument health scoring. Pick 5–8 signals, weight them, set thresholds. Review red accounts weekly. Automate alerts on sharp declines.
4. Run proactive plays. Playbooks for: onboarding risk, low adoption, champion change, renewal (start 120 days out), expansion trigger, at-risk save. Each play: trigger, steps, owner, timeline, exit criteria.
5. Execute QBRs. Template: outcomes review, value quantification, product updates relevant to them, success plan for next quarter. Always leave with agreed next steps.
6. Measure and improve. Gross retention, net retention (includes expansion — best-in-class exceeds 110%), NPS, time-to-value, CSM capacity. Review playbook effectiveness quarterly.

Save play template: trigger → assess (why are they at risk? what's the real issue?) → plan (3–5 committed actions with dates) → execute with executive sponsor → review at 30/60/90 days → close or escalate.

QBR template: 1) outcomes achieved since last quarter (their metrics, not your feature list), 2) ROI summary (value delivered vs. cost), 3) adoption and health review, 4) roadmap items relevant to their goals, 5) success plan for next quarter (3–5 agreed actions with owners), 6) expansion discussion (only after value is established).

Onboarding program (30-60-90): days 1–30: technical setup + first value milestone → days 31–60: workflow integration + power-user training → days 61–90: value review + success plan for year one. Define the first-value milestone precisely ("first report shared with team," not "account configured") — vague milestones produce vague outcomes. Churn post-mortem template: account profile → health history → timeline of events → root cause (product? service? fit? champion loss?) → could we have seen it earlier? → systemic fix. Run for every churned account above a value threshold; aggregate quarterly for pattern analysis.

Common pitfalls

• Reactive CS. Waiting for customers to complain. By the time they complain, they've often decided to leave.
• No health scoring. Managing by gut feel misses quiet at-risk accounts. Instrument early.
• Onboarding as training. Teaching button-clicks instead of driving to first value. Onboarding ends at outcome, not at "training complete."
• Renewal surprises. First discussing renewal 30 days out. Start 120 days out with value proof.
• Champion-only relationships. Single-threaded accounts churn when the champion leaves. Multi-thread from day one.
• CS as support overflow. Loading CSMs with tickets crowds out proactive work. Separate the functions.
• Ignoring expansion. Retention without expansion leaves money on the table. Successful customers want to do more — help them.
• CSMs as firefighters. Spending all time on escalations, none on proactive value. Protect proactive capacity or the function degrades into support.
• No executive relationships. CSM-only relationships die when the CSM or champion leaves. Build multi-threaded executive alignment early.
• Reactive CS. Only engaging when accounts are already red. By the time health scores flash red, save plays rarely work — invest in leading-indicator playbooks.
• Success theater. Celebrating activity (calls held, QBRs delivered) instead of outcomes (adoption, retention, expansion). Measure what matters.