Leadership asks "how is customer success doing?" and most CS teams answer with a screenshot of twenty charts. This guide gives you a short, defensible set of metrics, a one-page report template and a monthly routine, so your update drives decisions instead of questions.
Start with the audience, not the data
A CEO, a CFO and a head of product want different things from the same data. Before choosing metrics, write down the one decision each reader makes with your report:
- CEO or board: Is the existing customer base growing or shrinking, and how much revenue is at risk?
- CFO or RevOps: Can we trust the renewal forecast?
- Product and sales leaders: Which customers are struggling to get value, and why?
If a metric does not support any of those decisions, leave it out of the leadership view. Keep it on your team dashboard.
Pair leading and lagging indicators
Lagging indicators tell you what already happened. Leading indicators tell you what is likely to happen while you can still act. Whatfix describes lagging indicators as measures of concrete outcomes, such as retention, churn rate and renewal rate, and notes they offer little guidance on what to change. Leading indicators, such as time to activation, support ticket rate and NPS, connect behavior to later results. Its advice is to use them together.
Featurebase's CS KPI guide classifies health score, product adoption and time to value as leading, and churn, NRR and renewal rate as lagging. Its core rule is worth copying: pair every metric with an owner and an action threshold. A number that triggers no action is decoration.
The eight metrics to report
Pick these as a starting set. Adjust to your business model, but resist adding a ninth.
Outcomes (lagging)
- Gross revenue retention (GRR). Revenue kept from existing customers, ignoring expansion. Formula: (starting ARR - churned ARR - contraction ARR) / starting ARR. Our NRR vs GRR guide covers the calculation with a worked example.
- Net revenue retention (NRR). GRR plus expansion. Above 100% means the existing base grows without new logos.
- Logo churn rate. Share of customers lost in the period. Segment it, because a few large losses and many small ones call for different fixes.
- Renewal rate. Renewals won divided by renewals due in the period. Report it on the same cadence as your contracts, monthly for short SMB terms and quarterly for enterprise.
Early warnings (leading)
- ARR at risk. The annual recurring revenue of accounts flagged at risk or critical. This is the number leadership remembers.
- Health score distribution. How many accounts, and how much ARR, sit in each band. Show movement since last period, not just the snapshot.
- Time to value. Days from contract signature to the first outcome the customer cares about. Segment by plan or customer size, as Featurebase suggests.
- Adoption or usage trend. The share of accounts with rising, flat or falling usage over a fixed window.
NPS and CSAT are useful sentiment inputs. Keep them in the health score and on the team dashboard unless leadership specifically asks.
Put benchmarks in context, carefully
Executives will ask whether your numbers are good. Benchmarks help, but only if you name the source, the year and the population.
The Aleph and Benchmarkit 2026 SaaS & AI Performance Benchmarks, based on full-year 2025 data from 342 B2B SaaS and AI-native companies, report a median GRR of 84% (down from 88%), a top-quartile GRR of 91% and a median NRR of 102%. Their GRR sample was 226 companies.
Two cautions. First, a benchmark is a median across very different businesses, so a company with small contracts and one with large enterprise deals should not be compared directly. SaaS Capital publishes private B2B SaaS retention benchmarks that you can check against your own contract size. Second, benchmarks vary by survey, so avoid mixing figures from different studies in one chart.
One-page report template
Copy this structure for your monthly leadership update. Fill each line with a number, a change since last period and one sentence.
CUSTOMER SUCCESS UPDATE - [Month Year]
1. HEADLINE (2 sentences)
Retention is [up/down/flat]. Biggest risk: [account or theme], [ARR].
2. OUTCOMES (vs. last period and vs. target)
GRR: [__%] (target [__%])
NRR: [__%] (target [__%])
Logo churn: [__%]
Renewal rate: [__%] ([n] of [n] due)
3. EARLY WARNINGS
ARR at risk: [$__] ([n] accounts)
Health bands: Healthy [n] / At Risk [n] / Critical [n]
Accounts that moved down a band: [list top 3 by ARR]
Median time to value: [__ days] (target [__])
Accounts with falling usage: [n] ([$__ ARR])
4. NEXT 90 DAYS OF RENEWALS
Renewing: [$__] across [n] accounts
Forecast (probability-weighted): [$__]
Accounts needing exec help: [names]
5. WHAT WE DID / WHAT WE NEED
Actions taken: [2-3 bullets]
Decisions or help needed: [owner, by when]Define each metric once
Disagreements about data eat more meeting time than disagreements about strategy. Write a short definition sheet and keep it with the report:
- Period and cutoff: calendar month, snapshot taken on the last business day.
- ARR source: the system of record, usually the CRM or billing, never a spreadsheet copy.
- Churn date: the contract end date, not the date the customer told you.
- Expansion: only signed upsell or cross-sell, not pipeline.
- Segments: a fixed list, such as by plan or by contract-size band, used in every report.
Worked example (illustrative)
Imagine a 40-person SaaS company starting the quarter with $5,000,000 ARR. During the quarter, customers churn $150,000, downgrade by $50,000 and expand by $200,000.
- GRR = (5,000,000 - 150,000 - 50,000) / 5,000,000 = 96% for the quarter
- NRR = (5,000,000 - 150,000 - 50,000 + 200,000) / 5,000,000 = 100%
The headline, "NRR is flat at 100%", hides a story. Leadership needs to see that expansion offset $200,000 of losses. If the $200,000 came from one customer, retention is more fragile than NRR suggests. This is why GRR and NRR belong side by side, and why the report should name the biggest movers.
Set owners and thresholds
For each metric, fill in this table once, and review it every quarter:
- Metric: ARR at risk
- Owner: Head of CS
- Review cadence: weekly in the CS team meeting, monthly with leadership
- Action threshold: above [x]% of ARR triggers an executive sponsor call for the top three accounts
Featurebase suggests reviewing leading indicators often and revenue metrics less frequently. A sensible split is weekly for health and risk, monthly for churn and renewals, and quarterly for NRR and GRR trends. Their health bands are examples, and the article itself notes that you should validate bands against real renewal outcomes.
Reporting checklist
- Each metric has a written definition, an owner and an action threshold.
- Every number shows the change since last period and the target.
- GRR and NRR appear together.
- ARR at risk is expressed in dollars, with account names for the top movers.
- Benchmarks cite source, year and population.
- The report ends with decisions you need from leadership.
- Data comes from one system of record, pulled on a fixed date.
Try it in XPI CRM
XPI CRM's dashboard shows total ARR, ARR at risk, GRR, NRR, NPS and CSAT, with ARR movement and ARR-over-time reports, and the health score (0-100, bands Healthy, At Risk and Critical) is calculated for every client so the leading indicators sit next to the outcomes. Renewals have their own board with a forecast, so the next-90-days section of the template comes from the same data. Everything is included, free to use with no credit card, and the help guides cover setup.