Renew
Part of The Playbook — phase 4 of 5: Onboard → Adopt → Risk → Renew → Grow.
Should never be a surprise
[edit]If health scores and this phase's targets have been tracked honestly through the earlier phases, the renewal conversation is confirming a decision that was already visible weeks out — not making the case for the first time at the eleventh hour.
Set targets, not aspirations
[edit]Vague goals ("delight the customer," "drive adoption") can't be measured or missed. Real targets for this phase:
- Net Revenue Retention (NRR) — [(starting recurring revenue + expansion − contraction − churn) ÷ starting recurring revenue] × 100. Segment by ACV before comparing anything — it's the single most reliable lens for NRR benchmarking, and the spread is wide: SMB tiers run roughly 90–105%, the $25K–50K ACV band sits at a median of 102% (111% top quartile), and enterprise tiers reach 115–125% on the strength of expansion. A single blended company-wide number hides which tier is actually carrying it and which is dragging it down.
- Gross Revenue Retention (GRR) — the same formula without expansion in the numerator, so it can never exceed 100%. This is where a leaky base shows up even when a few big upsells are making NRR look fine. 95%+ is the generally accepted healthy floor.
GRR and NRR are reported side by side on purpose: a strong NRR built on expansion inside a shrinking base is a warning sign the top-line number hides.
Segment your targets — one number does not fit every tier
[edit]An enterprise account with a named CSM, a technical champion, and a six-figure contract should have a tighter, higher target than a self-serve SMB account managed at scale. Setting one target across every tier either starves your top accounts of attention or burns your team chasing SMB accounts to a standard they were never priced to receive.
The error budget idea, applied to CS
[edit]Google's SRE book defines an error budget as the quarterly allowance of acceptable unreliability implied by a service's target: hit a 99.9% uptime target and the budget is the roughly 8.77 hours a year you're allowed to spend on downtime before the team stops shipping features and pivots to fixing reliability instead. It's an explicit, pre-agreed trade-off, not an after-the-fact excuse.
The CS equivalent: how much acceptable churn/contraction risk exists in the base before the team throttles new-logo onboarding intake or expansion pushes and redirects capacity to shoring up existing accounts. Most CS orgs never make this trade-off explicit — they just let at-risk accounts pile up quietly while chasing this quarter's expansion number. Naming the budget, the same concrete way Google names it in hours and percentages, forces the conversation before it becomes a crisis.
Where this feeds
[edit]Target misses should trigger a play proactively, not just a reactive health-score dip. A clean renewal is the gate to Grow.
Sources
[edit]- SaaS Capital — private B2B SaaS retention benchmark research — NRR/GRR by ACV segment
- Google — Site Reliability Engineering, "Embracing Risk" — error budget definition