Customer Success Analytics & Reporting

A CS analytics framework operates at three levels: portfolio health, team performance, and commercial impact. Portfolio health metrics: Gross Renewal Rate (GRR) — the percentage of ARR renewed excluding expansion (downgrades and churned ARR are the denominators); Net Revenue Retention (NRR) — GRR + expansion ARR, the ultimate measure of CS commercial performance; Customer Health Distribution — the percentage of the portfolio in green, yellow, and red health tiers (and trend direction); At-Risk ARR — the total ARR of all accounts in red health tier, used to quantify the churn risk pool; Adoption Rate — the percentage of accounts actively using the core product features at a defined frequency. Team performance metrics: QBR completion rate — the percentage of accounts due for a QBR in the quarter that received one by the end of the quarter; Health score improvement rate — the percentage of yellow and red accounts that improved to the next health tier after CS intervention; CSM portfolio NRR — NRR broken down by individual CSM portfolio; Oncall response SLA — for CS plans with defined response time commitments to specific tiers. Commercial impact: Expansion ARR sourced — the ARR from upsell and cross-sell opportunities identified and facilitated by CS; Churn-prevented ARR — the ARR from accounts that were red health, received intervention, and renewed (attribution model required).

CS dashboards fail adoption when they are designed for leadership consumption rather than CSM workflow support. CSM-centric dashboard design: the CSM dashboard should answer three questions that guide daily action: "Which of my accounts need attention today?" (based on health score changes, overdue tasks, and upcoming renewal dates); "Which accounts are at risk of churning?" (red health tier with renewal within 90 days, flagged highest); "What actions do I have open?" (the complete task list organized by due date and priority). The dashboard must update in real time or daily — a weekly refresh is too infrequent for CSMs who use it to guide daily prioritization. Data density: the CSM view should be a single screen without scrolling, showing the portfolio sorted by priority with the critical context (account name, health tier, ARR, renewal date, last activity date, and open CTA count). A cluttered dashboard with 30 columns is never used; a focused dashboard with 7 critical columns becomes a daily workflow tool. Leadership dashboards have different needs: trend charts, segment comparisons, and forecast accuracy — but they should be built in a BI tool separate from the CSM operational view, not crammed into the same interface.

CS expansion revenue forecasting is immature at most companies — expansion is tracked by marketing as "upsell" in the MRR bridge but rarely forecasted with the accuracy applied to new business pipeline. Building a CS expansion forecast: expansion pipeline stages: CS Ops designs a 3–5 stage expansion pipeline parallel to the sales pipeline — from "expansion signal identified" to "expansion conversation initiated" to "proposal sent" to "committed to expand" to "closed." Each stage has a defined probability weight for call rate application. Pipeline inputs: CSMs log expansion opportunities in the CS platform or CRM when they identify an expansion signal (seat ceiling approach, adjacent use case conversation, QBR milestone achieved). Expansion opportunities with defined amounts (est. ACV) and expected close dates are the raw forecast material. Forecast calculation: sum of (opportunity amount × stage probability) = weighted expansion forecast. Historical close rate calibration: compare predicted vs. actual close rates for each stage quarterly and adjust probability weights to reflect actual conversion patterns. Accuracy tracking: forecast accuracy at 90 days (the expansion committed in month-3 forecasts vs. what actually closed in month 3). Target accuracy bracket: ±15%. A CS Ops expansion forecast that achieves < 20% variance vs. actual is considered strong for most mid-market SaaS companies.