Most customer success dashboards are built for the people working accounts. They answer questions like "Who should I call today?" and "Which tickets are open?" A VP of Customer Success needs something different: a short set of numbers that shows whether the team is protecting and growing revenue, where that revenue is exposed, and whether the team has the capacity to do anything about it.
This guide covers the three metrics that belong at the top of a CS leader's dashboard (net revenue retention, at-risk ARR and team capacity), the supporting metrics that explain them, and how to turn all of it into a weekly review and a board-ready story.
Why VPs Need a Different Set of CS Metrics
Account-level metrics such as logins, ticket counts and last-touch dates are essential for CSMs, but they don't roll up into decisions a leader can make. A VP is accountable for outcomes Finance and the board care about: retained revenue, expansion and the cost of delivering both. That means the leadership view should answer four questions at a glance:
- Are we on plan? Is retained and expanded revenue tracking to the target for the year?
- Where is revenue exposed? How much ARR is at risk, in which accounts, and how soon?
- Can the team respond? Do CSMs have the capacity to work the accounts that need them?
- What is CS worth? Which saves and expansions can be credited to the team's work?
Each question maps to a metric. Get those right and most other reporting becomes a drill-down rather than a separate dashboard.
Net Revenue Retention: The Headline Number
Net revenue retention (NRR) measures how much recurring revenue you keep and grow from an existing group of customers over a period, usually twelve months. It is the closest thing CS has to a single scorecard, because it captures churn, downgrades and expansion in one figure.
How to calculate it
Take the recurring revenue from a cohort of customers at the start of the period. Add expansion from those same customers, subtract contraction (downgrades and seat reductions) and churned revenue, then divide by the starting figure. New customers acquired during the period are excluded. A result above 100% means expansion from existing customers outpaced what you lost.
Report it against plan, not in isolation
A raw NRR figure tells you where you are. Comparing it to plan tells you whether to act. Quivly's VP Customer Success view puts the two side by side; its example dashboard shows NRR of 115% against a 112% plan, alongside a six-month NRR run rate indexed quarter over quarter. Treat those figures as an illustration of the layout, not a benchmark.
Two habits make NRR far more useful:
- Break it down by segment. A healthy blended number can hide an enterprise segment that is expanding and an SMB segment that is quietly churning.
- Watch the trend. A trailing run rate shows whether retention is improving or slipping well before the annual number moves.
At-Risk ARR: Turning Account Health Into Dollars
NRR is a lagging indicator. By the time it drops, the renewals behind the drop have already been lost. At-risk ARR is the forward-looking companion: the recurring revenue sitting in accounts that show signs of churn or contraction.
Weight risk by probability
Adding up the full ARR of every account with a low health score overstates the problem. A better approach is probability-weighted ARR at stake, where each account's revenue is weighted by its likelihood of churning. That gives Finance a number they can plan around rather than a worst case.
Bucket it by renewal window
Risk that renews next month needs a different response than risk that renews next year. Quivly's portfolio view groups ARR at stake into three windows: the next 90 days, 91 to 180 days, and 181 days or more. In the example dashboard, the near-term bucket holds $2.1M of probability-weighted ARR, with smaller amounts in the later windows. The near-term bucket is where leadership attention and escalations should go first.
Keep a named watchlist
Dollar totals are easier to act on when they map to named accounts. Pair the at-risk figure with the number of accounts behind it, so a leadership review can move straight from "$2.1M at risk" to "these 13 accounts, these owners, these next steps." For a deeper look at catching risk early, see how to identify at-risk customers before renewal.
Team Capacity: The Leading Indicator Most Dashboards Miss
A VP can see every at-risk account and still lose renewals if the CSMs who own them are overloaded. Capacity is often the earliest warning sign of future churn, because overloaded books get reactive coverage long before any health score moves.
What to measure
- Book load vs. target: accounts per CSM compared with the target for their segment. Quivly's example shows each CSM's account count against a target, for example 51 accounts against a target of 50, which makes overload visible immediately.
- ARR per CSM: account counts alone can mislead when one book holds several large renewals.
- Health distribution per book: a CSM with many accounts in the at-risk or critical bands needs more support than one with the same count of healthy accounts.
- Activity and outcomes: touchpoints sent, playbooks run and QBRs scheduled, alongside saves, expansions and churns.
How to use it
Review capacity before assigning new accounts, not after a renewal slips. Rebalance books when one CSM is consistently over target, and use activity-versus-outcome data as a coaching tool rather than a leaderboard. If the team is stretched across the board, capacity data also becomes your case for headcount or automation. For context on realistic book sizes, see post-sales accounts-per-rep benchmarks.
Supporting Metrics That Explain the Big Three
The headline metrics tell you what is happening. A small set of supporting metrics tells you why.
- Portfolio health index: a single blended health figure for the whole book, tracked quarter over quarter.
- Health band distribution: the share of accounts in each band, such as healthy, watch, at risk and critical. A shift from healthy to watch often precedes a rise in at-risk ARR.
- Active escalations: how many issues have reached leadership, and how many have been open longer than a set number of days.
- Renewal forecast: expected renewals built from real signals (health trends, engagement, stakeholder activity and historical churn patterns) rather than notes typed into the CRM.
- Health heatmap: segments crossed with regions, so you can spot whether risk is concentrated in one part of the business.
These metrics are only as good as the health score underneath them. If your team doesn't trust the score, start with how to build a weighted customer health score.
Proving the Impact of Customer Success
Retention numbers show how the customer base performed. They don't, on their own, show what the CS team contributed. To make the case for budget and headcount, leaders need attribution: a record of each intervention and the revenue tied to it.
- Saved ARR: revenue retained from accounts that were at risk and recovered after a CS intervention, tracked per CSM and per playbook.
- CS-attributed expansion: expansion revenue that followed a CS-initiated play, such as a QBR follow-up or a usage workshop.
- ARR protected through churn saves: a rolling view, for example over the last 90 days, of revenue defended at renewal.
Per-playbook rollups are especially useful. They show which motions actually move revenue, so you can invest in the plays that work and retire the ones that don't. Exported as a scheduled digest, the same data gives Finance a recurring, consistent view of CS as a revenue function rather than a cost center.
How to Run a Weekly VP Review
Metrics matter only if they change decisions. A simple weekly cadence keeps the leadership view tied to action:
- Start with NRR vs. plan. Note the trend and any segment that moved.
- Walk the near-term at-risk bucket. Review every account in the next 90 days, its owner and the agreed next step.
- Check escalations. Focus on anything open longer than your threshold.
- Review capacity. Look for CSMs over target or carrying an unusual share of at-risk accounts, and rebalance if needed.
- Close with impact. Log saves and expansions from the week so attribution stays current for the next board or Finance review.
Keep the review short. If the data is live, the meeting should be about decisions, not about reconciling spreadsheets.
FAQ
Net revenue retention is the best single summary because it combines churn, contraction and expansion. On its own it lags, so pair it with at-risk ARR to see what is coming and team capacity to know whether you can respond.
Churned ARR is revenue already lost. At-risk ARR is revenue still under contract in accounts showing churn or contraction signals. Weighting it by probability and grouping it by renewal window turns it into a forecast you can act on.
Compare each CSM's book against a target for their segment, using account count, total ARR and the health mix of the book. Add activity and outcome data to see whether a heavy book is still being covered well or is slipping into reactive work.
Ideally in real time or close to it. A dashboard that refreshes monthly will show risk only after the window to act has narrowed. Live health scores and continuously updated renewal forecasts let a weekly review focus on current conditions. Want a live view of NRR, at-risk ARR and team capacity without stitching spreadsheets together? See how Quivly's VP Customer Success view brings portfolio health, renewal risk and CSM workload into one dashboard, with the revenue impact of every play tracked along the way.
