How should we structure a customer health score that tracks both product engagement and commercial indicators?
Health Score Architecture
A robust health score combines three pillars: product adoption, financial velocity, and support engagement. Weight these signals at 40% product, 35% financial, 25% support—but adjust by segment; enterprise customers may weight support at 40%.
Product Engagement Layer
- Monthly Active Users (MAU) relative to seat count
- Feature velocity: logins, key feature adoption, API calls
- Adoption breadth: percentage of product modules used
- Session trends: declining logins signal risk
Financial Health Layer
- Expansion ARR: upsell rate and module adoption
- Renewal probability: contract end-date proximity, payment history
- Usage-to-price alignment: under-consumed licenses indicate churn risk
- Support ticket severity: increase in P1 issues = technical debt
Support Engagement Layer
- CSM interaction frequency: quarterly business reviews completed
- NPS trajectory: point-in-time vs. trend matters more
- Response time to issues: escalations and resolution SLAs
- Stakeholder diversity: single point of contact = risk
Scoring Formula
Red (0–35): Immediate save play required. Yellow (36–70): Quarterly attention. Green (71–100): Expansion pipeline.
OpenView and Pavilion both recommend real-time scoring refreshed daily, triggered by product events (logins, errors) and CRM updates (payment, support tickets). Tools like Gainsight, Totango, and Vitally automate this; others use Salesforce flows + custom APIs.
TAGS: health-score,product-adoption,churn-prevention,saas-metrics,customer-success,saas-finance