What is a SaaS Customer Health Score?

A SaaS health score is a metric that software-as-a-service (SaaS) businesses use to assess the overall value a customer gains from their software and to discover if that customer will renew, expand, or churn. Customer success teams may use the score, formed from multiple user signals, to approach account health tracking through an objective lens, rather than subjective judgments.

Data from a customer health index often correlates with efforts to shift a reactive customer service model towards a proactive customer success model. Companies may be able to detect indicators of customer disengagement sufficiently in advance of a cancellation event.

• Variations in health score can indicate impending usage changes, and data concerning these situations might materialize several weeks after the renewal date.
• Accounts identified as highly active and scoring in the “Green” (or 80-100 range) are often considered for upsell or expansion offers.
• A retrospective analysis of customer health trends across various cohorts provides data that can relate to onboarding experiences and influence customer lifetime value (LTV) outcomes.

Customer health scoring involves integrating data from various customer journey touchpoints. An approach focused solely on product usage may involve a limited scope of observation.

1. Product Usage and Depth Measures

• License Utilization Rate: The percentage of active users to assigned seats.
• Adoptie van functionaliteiten: Differentiation of whether clients use advanced attributes or only basic parts of the product.

2. Support and Relationship Health Indicators

• Ticket Volume: Variations in ticket volume and issue severity, particularly an uptick in high-priority concerns, can be observed to correlate with differing customer sentiment. In contrast, a reduced ticket volume might point to evolving customer engagement methods.
• Net Promoter Score (NPS): Direct, qualitative feedback that reflects customer sentiment and likelihood to promote.

3. Financial and Contractual Data Points

• Payment History: Payment history data, including delayed payments from creditworthy customers, can indicate a pattern alongside shifts in customer status, before additional investigation.
• Contractual Commitments: Multi-year contracts generally portray different health states than month-to-month subscriptions.

The key elements that influence customer retention should be considered when creating a health score framework with clear weights (percentage allocations).

Stap 1: Assign Weights to Your Core Metrics

Since signals vary in importance, you need to allocate percentages to various categories in such a way that the total equals 100%. Here is a basic distribution as an example:

Stap 2: Establish the Scoring Scale

Transform your raw metrics either to a simple 0 to 100 scale or sort them into distinct segments that are easy to act upon:

• A score in the 80–100 range indicates an account status that may permit expansion.
• Within the 50–79 average health range, accounts are observed to be functional, with usage patterns indicating less engagement with specific features and a diminished frequency of interaction.
• An association has been observed between health scores from 0 to 49 and customer churn, without specific interventions being applied.

The utility of a health score relates to the actions it influences. Customer success teams employ automated workflows, which are sometimes referred to as “playbooks,” to respond to changes in customer health.

• Churn Prevention Play: An automated alert assigns a high-priority task to the Customer Success Manager (CSM) to schedule a usage review and identify any blockages when an account falls below 50.
• Expansion Play: When an account has a score of 85 for 30 days or more, the system launches an expansion play that sends a prompt to the account executive to propose relevant add-ons or upgrades.
• Renewal Escalation Play: A standard play is initiated for accounts scoring between 50 and 70 within 90 days of renewal, which includes a formal executive business review (EBR) to pre-secure the account.

Update frequency is influenced by your product type and contract velocity. For fast-paced, low-touch self-service PLG (Product-Led Growth) platforms that require detecting drop-offs, real-time or daily recalculations are a must. On the other hand, enterprise SaaS with long implementation cycles should settle for weekly batch recalculation to avoid erratic price fluctuations caused by the typical weekend usage drop.