Retention Insights
Definition
Free-form commentary from the CS / Sales leadership on retention trends, cohort behavior, and underlying drivers of loyalty (or its absence). Pairs with the quantitative retention KPIs (NRR, GRR, logo retention) and gives the board the "why" behind the numbers — which cohorts are strong, which are weak, what feature engagement correlates with retention, what onboarding changes are landing. Common pitfall: filler prose that restates the numbers without adding causal insight — a board reader should learn something here they could not infer from the metrics page alone.
Why it matters
Adds causal explanation to the retention numbers — boards optimize for diagnoses, not just descriptions. Reading "NRR slipped from 115% to 108%" is half the story; reading "NRR slipped because two large customers cut seat counts as they integrated us with an acquired vendor — non-recurring" is the actionable version.
How it's calculated
Qualitative — no calculation. Free-form narrative commentary, typically 100–300 words, with concrete cohort references (e.g. "Q3 2024 cohort showing 12% better NRR than Q2 2024 cohort, driven by adoption of feature X within 30 days of go-live"). How to interpret it
Anti-pattern: prose that restates the numbers ("NRR was 108% this quarter, down from 115%") without explaining drivers. Strong content names specific cohorts, customer segments, or product surfaces and ties them to the metric movement. If the team cannot articulate the "why" yet, write "diagnosis in progress — investigating with CS team, update next board" rather than padding.
Source
imboard Editorial
Stage relevance
Typically owned by
Related KPIs
Recurring revenue retained from the cohort of customers present at the start of the period, including expansion (upsell, cross-sell, price increases) and net of churn and contraction — but excluding revenue from net-new logos acquired in-period. Per the SaaS Metrics Standards Board (SMSB) NRR standard. NRR above 100% means the cohort grew faster than it lost — a hallmark of strong product-led expansion. The board reads NRR alongside GRR (`customers.gross_revenue_retention`) to separate the "keep + expand" signal from the "just keep" signal. Common pitfall: mixing GAAP revenue and ARR in numerator vs. denominator, or letting net-new logo revenue leak in — both inflate the number; SMSB is explicit that the cohort is closed at period start.
Recurring revenue retained from the cohort of customers present at the start of the period, excluding expansion — so the metric captures only churn and contraction. Per the SaaS Metrics Standards Board (SMSB) GRR standard. GRR is bounded at 100% (cannot exceed it) and reads as the "no-defense-against-churn" floor on retention. The board reads GRR alongside NRR (`customers.net_revenue_retention`) — the gap between them is the expansion contribution. Common pitfall: treating GRR and NRR as substitutes — they answer fundamentally different questions, and a healthy NRR with sliding GRR signals churn masked by upsell.
Share of customer logos retained from the prior period, counted by logo (not by revenue). Per the SaaS Metrics Standards Board (SMSB) Logo Retention standard: numerator is logos present at both period start and period end; denominator is logos present at period start. New logos acquired during the period are excluded from both. The board reads this as a "stickiness" signal independent of ACV: high logo retention with weak NRR points to flat/contracting expansion; weak logo retention with strong NRR points to high concentration risk. Common pitfall: conflating logo retention with revenue retention — they answer different questions and routinely diverge.
Identified upsell, cross-sell, and seat-expansion opportunities inside the existing customer base, with deal size and timing where known. This is the qualitative narrative behind the expansion component of NRR — what the CS / Sales team sees in the pipeline that has not yet converted. The board reads this as forward-looking signal on whether NRR will trend up or down next quarter. Common pitfall: confusing "opportunities" (real conversations with named accounts) with "addressable upside" (theoretical TAM uplift) — keep this field anchored in actual pipeline.
Named at-risk accounts, root-cause analysis of why they're at risk, and the mitigation plan in flight. Pairs with the quantitative `arr_at_risk` and `percent_arr_at_risk` and gives the board the names + the playbook. Common pitfall: listing the at-risk accounts without the diagnosis or the plan — the board reader needs to see what the team is doing about it, not just what the team is worried about. Also: avoid using this surface as a generic "things are bad" venting forum — keep it account-specific and action-specific.
Track these KPIs with your board
I'mBoard helps startup CEOs report the metrics that matter, track resolutions, and run better board meetings.