SLOs for Customer Outcomes - Revision history

BrettFullmer: Merged into the 5-phase Playbook restructure — redirect to Renew

2026-09-01T18:07:33Z

Merged into the 5-phase Playbook restructure — redirect to Renew

← Older revision		Revision as of 18:07, 1 September 2026
Line 1:		Line 1:
	~~Part of~~ [[The Playbook]]. [[Observability (Customer Health Scoring)\|A health score]] tells you an account's state. An SLO (service level objective) tells you what state you actually promised to deliver — a measurable target, not a vibe. Borrowed straight from infrastructure: an SRE doesn't say "the site should be pretty reliable," they say "99.9% uptime, measured monthly, with an error budget." Customer Success needs the same discipline.		#REDIRECT [[Renew]]

	~~==Set targets, not aspirations==~~

	~~Vague goals ("delight the customer," "drive adoption") aren't SLOs — they can't be measured or missed. Real SLO candidates:~~

	* '''Time-to-first-value''' — days from contract signature to the customer hitting a defined "aha" milestone, not just "onboarding complete." There's no honest single universal number — benchmarks split sharply by segment (roughly 7 days for SMB, 12 for enterprise, sub-2-days for fast self-serve categories) — but the retention cliff behind the number is real and worth setting a target against: customers who reach first value within 14 days retain at 80%+ a year later, while those who miss the 30-day mark retain at only 35–50%. Onboarding speed is close to the single biggest lever a CS org has over year-one churn.
	* '''Adoption depth by day 90''' — percentage of licensed seats or core workflows actively used, measured against a stated target, not just "some usage."
	* '''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 SLOs — one target does not fit every tier==~~

	An enterprise account with a named CSM, a technical champion, and a six-figure contract should have a tighter, higher target and more play intensity than a self-serve SMB account managed at scale. Setting one SLO 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==~~

	Google's SRE book defines an error budget as the quarterly allowance of acceptable unreliability implied by a service's SLO: 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 the 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==~~

	SLO misses are what should trigger a [[The Play Library\|play]] proactively, not just a reactive health-score dip. A pattern of SLO misses across a segment is a [[The Postmortem (Churn and Save Retros)\|postmortem]]-worthy signal even before any single account churns.

	~~==Sources==~~

	* [https://www.saas-capital.com/research/ SaaS Capital — private B2B SaaS retention benchmark research] — NRR/GRR by ACV segment
	* [https://sre.google/sre-book/embracing-risk/ Google — ''Site Reliability Engineering'', "Embracing Risk"] — error budget definition
	* [https://userpilot.com/blog/time-to-value-benchmark-report-2024/ Userpilot — 2024 Time-to-Value Benchmark Report] — TTV medians and the 14-/30-day retention cliff

	~~[[Category:Customer Success Manager]]~~
	~~[[Category:Technical Account Manager~~]]

BrettFullmer: Add ACV-segmented NRR/GRR data, sourced error budget, TTV benchmarks and retention cliff, Sources section

2026-09-01T17:48:05Z

Add ACV-segmented NRR/GRR data, sourced error budget, TTV benchmarks and retention cliff, Sources section

← Older revision		Revision as of 17:48, 1 September 2026
Line 5:		Line 5:
	Vague goals ("delight the customer," "drive adoption") aren't SLOs — they can't be measured or missed. Real SLO candidates:		Vague goals ("delight the customer," "drive adoption") aren't SLOs — they can't be measured or missed. Real SLO candidates:

	* '''Time-to-first-value''' — days from contract signature to the customer hitting a defined "aha" milestone, not just "onboarding complete."		* '''Time-to-first-value''' — days from contract signature to the customer hitting a defined "aha" milestone, not just "onboarding complete." There's no honest single universal number — benchmarks split sharply by segment (roughly 7 days for SMB, 12 for enterprise, sub-2-days for fast self-serve categories) — but the retention cliff behind the number is real and worth setting a target against: customers who reach first value within 14 days retain at 80%+ a year later, while those who miss the 30-day mark retain at only 35–50%. Onboarding speed is close to the single biggest lever a CS org has over year-one churn.
	* '''Adoption depth by day 90''' — percentage of licensed seats or core workflows actively used, measured against a stated target, not just "some usage."		* '''Adoption depth by day 90''' — percentage of licensed seats or core workflows actively used, measured against a stated target, not just "some usage."
	* '''Net Revenue Retention (NRR)''' — [(starting recurring revenue + expansion − contraction − churn) ÷ starting recurring revenue] × 100. ~~The 2025 SaaS Capital benchmark~~ for ~~private B2B SaaS at~~ $~~25–50K~~ ACV: median 102%, top quartile ~~111~~%.		* '''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.		* '''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.

Line 18:		Line 18:
	==The error budget idea, applied to CS==		==The error budget idea, applied to CS==

	In SRE~~, the~~ error budget is the ~~amount~~ of unreliability you're allowed to spend before ~~you have to stop~~ shipping features and ~~fix~~ reliability instead. 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 the at-risk accounts pile up quietly while chasing this quarter's expansion number. Naming the budget forces the conversation before it becomes a crisis.		Google's SRE book defines an error budget as the quarterly allowance of acceptable unreliability implied by a service's SLO: 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 the 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==		==Where this feeds==

	SLO misses are what should trigger a [[The Play Library\|play]] proactively, not just a reactive health-score dip. A pattern of SLO misses across a segment is a [[The Postmortem (Churn and Save Retros)\|postmortem]]-worthy signal even before any single account churns.		SLO misses are what should trigger a [[The Play Library\|play]] proactively, not just a reactive health-score dip. A pattern of SLO misses across a segment is a [[The Postmortem (Churn and Save Retros)\|postmortem]]-worthy signal even before any single account churns.

			==Sources==

			* [https://www.saas-capital.com/research/ SaaS Capital — private B2B SaaS retention benchmark research] — NRR/GRR by ACV segment
			* [https://sre.google/sre-book/embracing-risk/ Google — ''Site Reliability Engineering'', "Embracing Risk"] — error budget definition
			* [https://userpilot.com/blog/time-to-value-benchmark-report-2024/ Userpilot — 2024 Time-to-Value Benchmark Report] — TTV medians and the 14-/30-day retention cliff

	[[Category:Customer Success Manager]]		[[Category:Customer Success Manager]]
	[[Category:Technical Account Manager]]		[[Category:Technical Account Manager]]

BrettFullmer: Publish SLOs for Customer Outcomes page

2026-09-01T16:58:42Z

Publish SLOs for Customer Outcomes page

New page

Part of [[The Playbook]]. [[Observability (Customer Health Scoring)|A health score]] tells you an account's state. An SLO (service level objective) tells you what state you actually promised to deliver — a measurable target, not a vibe. Borrowed straight from infrastructure: an SRE doesn't say "the site should be pretty reliable," they say "99.9% uptime, measured monthly, with an error budget." Customer Success needs the same discipline.

==Set targets, not aspirations==

Vague goals ("delight the customer," "drive adoption") aren't SLOs — they can't be measured or missed. Real SLO candidates:

* '''Time-to-first-value''' — days from contract signature to the customer hitting a defined "aha" milestone, not just "onboarding complete."
* '''Adoption depth by day 90''' — percentage of licensed seats or core workflows actively used, measured against a stated target, not just "some usage."
* '''Net Revenue Retention (NRR)''' — [(starting recurring revenue + expansion − contraction − churn) ÷ starting recurring revenue] × 100. The 2025 SaaS Capital benchmark for private B2B SaaS at $25–50K ACV: median 102%, top quartile 111%.
* '''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 SLOs — one target does not fit every tier==

An enterprise account with a named CSM, a technical champion, and a six-figure contract should have a tighter, higher target and more play intensity than a self-serve SMB account managed at scale. Setting one SLO 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==

In SRE, the error budget is the amount of unreliability you're allowed to spend before you have to stop shipping features and fix reliability instead. 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 the at-risk accounts pile up quietly while chasing this quarter's expansion number. Naming the budget forces the conversation before it becomes a crisis.

==Where this feeds==

SLO misses are what should trigger a [[The Play Library|play]] proactively, not just a reactive health-score dip. A pattern of SLO misses across a segment is a [[The Postmortem (Churn and Save Retros)|postmortem]]-worthy signal even before any single account churns.

[[Category:Customer Success Manager]]
[[Category:Technical Account Manager]]