How to Build a Customer Health Scorecard for B2B SaaS
A practical, operator-tested guide to building a health scoring model that your team will actually trust and use. Five inputs, three thresholds, and a clear implementation path.
What Is a Customer Health Scorecard?
A customer health scorecard is a composite metric that combines multiple signals into a single account-level assessment of how likely a customer is to renew, expand, or churn. For B2B SaaS companies, it is the primary early warning system that tells your CS team where to focus their attention.
The best health scorecards are simple enough that any CSM can explain them, specific enough to drive action, and connected to real business outcomes. If your team does not trust the scores or cannot explain what drives them, the scorecard is not working.
The Five Inputs That Matter
After years of building these models inside B2B SaaS companies, I've found that five inputs capture the signal that matters most for predicting retention and growth. Each input is weighted based on its predictive strength:
| Input | Weight | What It Measures |
|---|---|---|
| Product Usage | 30% | Active users, feature utilization, login frequency, and workflow activity relative to license count. This is your strongest leading indicator. |
| Stakeholder Engagement | 25% | How many stakeholders are engaged, at what level, and how recently. Single-threaded accounts are high risk regardless of usage. |
| Support Patterns | 15% | Ticket volume trend, severity distribution, and resolution satisfaction. Rising high-severity tickets are a risk signal. |
| Onboarding / Adoption | 15% | Progress through onboarding milestones and depth of feature adoption. Slow onboarding correlates strongly with early churn. |
| Commercial Signals | 15% | Contract status, renewal timeline, expansion conversations, billing issues, and any commercial friction. |
Threshold Model: Green, Yellow, Red
A health score is only useful if it drives specific actions. Use a three-tier threshold model:
| Status | Score Range | What It Means | Action |
|---|---|---|---|
| Green | 75 – 100 | Account is healthy across most dimensions. No immediate risk. | Maintain cadence. Look for expansion signals. Prioritize for QBRs and case studies. |
| Yellow | 50 – 74 | One or more dimensions show concern. Not yet critical, but trending in the wrong direction. | Investigate the primary driver. Increase touchpoint frequency. Address the root cause within 2 weeks. |
| Red | 0 – 49 | Significant risk. Multiple dimensions are declining or a single critical dimension has collapsed. | Intervention plan within 48 hours. CS Director involved. Escalate to cross-functional stakeholders if needed. |
How to Score Each Input
Each input produces a score from 0 to 100, which is then multiplied by its weight to contribute to the composite score. Here is how to evaluate each one:
Product Usage (30%)
Calculate a normalized usage score based on: the percentage of licensed users who are active (DAU/MAU relative to seats), the depth of feature utilization (are they using core workflows or just logging in?), and the trend direction (improving, stable, or declining over the past 30 days). A customer using 80% of their seats with consistent core feature activity scores 85-100. A customer with declining logins and shallow feature use scores 20-40.
Stakeholder Engagement (25%)
Evaluate based on: number of engaged stakeholders (more than one is critical), seniority of engagement (is the executive sponsor active?), recency of interaction (when did you last have a meaningful conversation?), and breadth across departments (single-department vs. multi-department adoption). An account with 3+ engaged stakeholders including an executive sponsor, with interaction within the past 30 days, scores 80-100. A single-threaded account with a champion you have not spoken to in 60+ days scores 20-40.
Support Patterns (15%)
Track: ticket volume trend (stable, increasing, or decreasing), severity distribution (are high-severity tickets increasing?), resolution time and satisfaction, and whether the same issues recur. Declining or stable low-severity tickets with high satisfaction scores 80-100. Rising high-severity tickets with recurring issues scores 20-40.
Onboarding / Adoption (15%)
For accounts still in onboarding: are they hitting milestones on time? For accounts past onboarding: are they deepening adoption (new features, new user groups, expanding use cases)? On-track onboarding or deepening adoption scores 80-100. Stalled onboarding or flat adoption scores 20-40.
Commercial Signals (15%)
Consider: renewal timeline (how far out?), any billing disputes or payment issues, active expansion conversations, competitive mentions, budget review signals, and contract terms. Clean commercial status with expansion interest scores 80-100. Active billing dispute with competitive evaluation scores 20-40.
Implementation: Start Simple
Do not try to automate everything on day one. The most effective approach for B2B SaaS companies at the $2M to $20M ARR stage:
- Score manually first. Have each CSM score their accounts using the five inputs and a simple spreadsheet. This takes 2-3 hours for a typical book of business and produces immediate value.
- Calibrate as a team. In your first team meeting after scoring, review the results. Are there accounts where two CSMs would score differently? Discuss the edge cases and align on standards.
- Review weekly. Add health score review to your weekly 1:1s and team meetings. CSMs should be prepared to discuss any status changes since last week.
- Automate later. Once you have been scoring manually for one full cycle (90 days), you will know which inputs actually predict outcomes in your business. That is when you select a CS platform and configure automated scoring — not before.
What Good Looks Like
A well-functioning health scorecard produces three outcomes: your team can identify risk before it becomes a fire, your leadership can see portfolio health at a glance, and your renewal conversations start from a position of knowledge rather than guesswork. If your scorecard is not producing those outcomes, the inputs, weights, or thresholds need adjustment.
Want the operating system, not just the framework?
CS Ramp delivers a full Customer Success operating system — playbooks, scorecards, reporting decks, cadence guides, and a 90-day implementation roadmap — calibrated to your company's stage. Every decision ships with its reasoning attached.
See CS Ramp →