A customer health score should show its work.

One number is useful only when the team can inspect the usage, support, billing, relationship, CRM, and delivery evidence beneath it. SixDegree keeps every signal connected to its source and observed time.

Start read-only. Keep your existing systems. Trace every answer to its source.

How to build a customer health score teams can trust.

There is no universal health-score formula. A useful model reflects how your customers receive value, renew, expand, and encounter risk, then makes every component explainable.

Choose evidence tied to customer outcomes

Common inputs include product adoption, active-seat ratio, support severity and age, invoice state, relationship coverage, executive engagement, implementation progress, renewal date, and contractual commitments. Use signals that can change an action, not fields that are merely available.

Normalize before weighting

Convert inputs measured on different scales into a consistent range, then weight them by their relationship to retention or expansion. A simple model can calculate health as the sum of each normalized signal multiplied by its weight.

Keep hard-stop conditions outside the weighted average. An unresolved critical incident or failed payment should not disappear because several low-value indicators are green.

Score change as well as state

A stable customer at 65 may be healthier than a customer that fell from 90 to 72 in two weeks. Preserve the prior score, current score, component changes, and observed times so the team can distinguish baseline from deterioration.

Expose disagreement instead of averaging it away

CRM, customer success, product, and support may reach different conclusions about the same account. Show those claims beside the evidence that produced them. The disagreement is a review queue, not a data-cleaning error to hide.

Which healthy accounts have evidence that no longer supports the score?

SixDegree returns the score, renewal, ARR, component signals, source records, observed times, and changes that explain why the account needs review.

SixDegree account view showing customer health, usage, billing, renewal, people, and the source behind each observation
Source record
Inspect the record that supports each risk signal.
Observed time
See when the source reported it and what changed.
Revenue connection
Follow why that record affects this account, opportunity, renewal, or ARR.

The CRM is one signal, not the whole account.

Each system keeps owning what it knows. SixDegree connects the signal to the account, renewal, opportunity, ARR, and owner it can change.

Product
Weekly active users fell 31 percent
Adoption component declines
Zendesk
Critical escalation open 11 days
Support hard stop activates
Stripe
Active seats below contract
Commercial mismatch appears
Gong
Primary champion departed
Relationship coverage weakens
Salesforce
Renewal remains healthy
Score and CRM disagree

From source change to revenue action.

  1. 01

    Define the decision

    Choose whether health should prioritize renewal, adoption, expansion, implementation, or another explicit customer outcome.

  2. 02

    Connect and normalize signals

    Resolve source observations to the same account and transform them into comparable components without losing the original values.

  3. 03

    Explain every change

    Show which component moved, what source record caused it, when it changed, and which renewal or owner needs attention.

Questions revenue teams ask

What is a customer health score?
A customer health score summarizes evidence about adoption, satisfaction, commercial state, relationships, and delivery into a value used to prioritize customer action. It should remain traceable to the underlying signals.
How do you calculate a customer health score?
Choose outcome-relevant inputs, normalize them to a common scale, multiply each component by an explicit weight, and sum the results. Treat critical conditions separately so a severe issue cannot be averaged away.
What data should be included?
Useful inputs often include product adoption, active-seat ratio, ticket severity and age, CSAT, invoice state, relationship coverage, engagement, implementation milestones, renewal timing, and contractual commitments.
How often should customer health update?
Update when a material source observation changes rather than only on a reporting schedule. Preserve history so teams can see direction, velocity, and what was known before a renewal outcome.

Bring one revenue question your CRM cannot answer.

We’ll map the systems behind it and use a read-only working session to show what becomes visible when the account and its signals are connected.

Book a working session