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
Anchor Citations
- CB Insights State of Venture / Sales Tech: https://www.cbinsights.com/research/
- Bessemer Cloud Index + State of the Cloud: https://www.bvp.com/atlas/state-of-the-cloud
- Crunchbase News (funding + M&A): https://news.crunchbase.com/
- SaaS Capital industry survey + valuation: https://www.saas-capital.com/research/
- PitchBook venture + private markets: https://pitchbook.com/news
- a16z Marketplace / SaaS frameworks: https://a16z.com/category/saas/
Operator Benchmarks (2025 Data)
| Metric | Verified figure | Source |
|---|---|---|
| Median SDR fully-loaded cost | $95K-$130K/yr | Pavilion + BLS |
| Median outbound SDR meetings/mo | 8-14 | Bridge Group 2025 |
| Median LinkedIn InMail response | 8-14% | LinkedIn Sales |
| Median cold email reply (warm list) | 6-11% | Outreach/Apollo |
| Median demo-to-close (mid-market) | 24-32% | OpenView |
| Median deal cycle ($25-100K ACV) | 45-90 days | Bridge Group |
| Median pipeline-to-quota coverage | 3.5-4.5x | Pavilion |
| Median CAC inbound-led SaaS | $8K-$15K | OpenView PLG |
| Median CAC outbound-led SaaS | $22K-$45K | Bridge + OpenView |
The Bear Case (Operational Concentration)
Three concentration risks:
- Customer concentration — any single >20% of revenue is asymmetric.
- Channel concentration — 60%+ from one channel is existential.
- Geographic concentration — NA-centric exposed to NA macro/regulatory.
Mitigation: customer top-1 < 20%, channel top-1 < 40%, geography top-region < 70%.
See Also (related library entries)
Cross-references for adjacent operator topics drawn from the current 10/10 library set, ranked by tag overlap with this entry:
- q1782 — How does Outreach onboarding compare to Salesloft?
- q1723 — What does Datadog churn math look like under AI pressure?
- q1672 — Why did Datadog growth slow in 2024-25?
- q1621 — What is ServiceNow net revenue retention in 2026?
- q1597 — What does Snowflake churn math look like under AI pressure?
- q1594 — What is Snowflake gross margin trajectory through 2028?
Follow the q-ID links to read each in full.