Customer Success (CS) is the post-sale function that makes sure customers reach the outcome they bought the product for — so they renew, adopt more, and expand. It is proactive and outcome-driven: a CSM (Customer Success Manager) works a defined book of accounts toward measurable goals, intervening before a renewal is at risk rather than after a customer complains. Its scoreboard is retention and expansion revenue, most often summarized as NRR (Net Revenue Retention) and GRR (Gross Revenue Retention).
What it is not
Customer Success is not support, and it is not account management — even though it overlaps both.
- Not support. Support is reactive and ticket-driven: a customer hits a problem, opens a ticket, support resolves it, the ticket closes. The unit of work is the issue. Support optimizes for fast, correct resolution (first-response time, CSAT on the ticket). CS optimizes for the customer’s outcome over the whole lifecycle, and most of its work happens when nothing is broken.
- Not classic account management. Traditional account management is a sales role that owns the commercial relationship and the renewal quota. CS owns the outcome that makes the renewal happen. In many orgs the two are split (CSM drives adoption and health; an AM or AE owns the renewal/expansion close); in others the CSM carries a renewal/expansion number directly. Either way, CS is judged on whether customers succeed, not just on whether the contract gets signed.
A simple test: if the work is triggered by a customer-reported problem, it’s support. If it’s triggered by a contract event or a commercial negotiation, it’s account management. If it’s triggered by a signal that a customer is — or isn’t — getting value (low adoption, a missed milestone, an unused seat block), it’s Customer Success.
What CS actually owns
The function’s job is to move three numbers:
- Retention — keeping the revenue you already have. Measured by GRR (churn and downsell only; capped at 100%). Strong B2B SaaS GRR is 90%+; below 85% is a retention problem CS owns.
- Adoption — getting customers to use the product deeply enough that the outcome is real. Measured by activation rate, feature adoption, and usage depth per account. Adoption is the leading indicator; retention is the lagging result.
- Expansion — growing the accounts that are healthy. Measured by the expansion component of NRR. Top-quartile NRR is 120%+; below 100% means expansion isn’t covering the leak.
Why CS owns NRR
NRR is the single metric that captures all three jobs in one number: it folds retention, downsell, and expansion into “how much of last year’s revenue is still here, plus how much it grew.” Because CS is the only function whose daily work touches all three of those levers post-sale, NRR is the metric it is held to.
That ownership is real, not nominal. A CS org with 130% NRR and 80% GRR is masking a churn problem with expansion revenue — the kind of thing that looks healthy on a board slide and breaks the moment the expansion engine stalls. Reading NRR and GRR together is the discipline that keeps CS honest about whether it is actually driving value or just riding a few large expansions. See NRR vs GRR for the formulas and stage-by-stage targets.
How it shows up in real ops work
In practice CS runs on a health-scoring model (usage signals, support volume, relationship strength, contract data) that flags at-risk accounts before renewal, a segmented coverage model (high-touch named CSMs for the top accounts, pooled or digital-led “tech-touch” CS for the long tail), and a lifecycle playbook with named milestones — onboarding, time-to-first-value, quarterly business reviews (QBRs), and renewal. Tooling is built around that model: platforms like Gainsight, ChurnZero, Vitally, and Catalyst ingest product usage and CRM data, compute health scores, and trigger CSM playbooks automatically.
Common pitfalls
- Running CS as escalation support. If CSMs spend their week clearing tickets, you have an expensive second support tier, not a success function. The guard: route reactive issues to support and protect CSM time for proactive, outcome-driving work measured against adoption and health, not ticket volume.
- Owning NRR without owning the levers. Holding CS to NRR while sales controls expansion pricing and product controls the roadmap is setting up a fall guy. The guard: give CS at least adoption and renewal motion, and a documented split with sales on who closes expansion.
- Health scores nobody acts on. A health score that doesn’t trigger a specific play is dashboard decoration. The guard: every red account fires a named playbook with an owner and a due date, not a quarterly review note.
Related
- NRR vs GRR — the metrics CS is judged on
- Activation — the leading adoption indicator
- LTV/CAC — why retention drives unit economics