The health score wraps five scattered data sources — logins, feature usage, support tickets, payment history and email engagement — into a single 0–100 scale the whole team reads the same way.
How the score is calculated
Each signal is normalised to a 0–100 scale, then multiplied by the weight you set. The defaults below suit most daily-use software; periodic service businesses usually lower the login weight and raise the payment one.
| Signal | Data source | Default weight |
|---|---|---|
| Login frequency | System logs | 30% |
| Features in use | Usage events | 25% |
| Open support tickets | Support inbox | 20% |
| Payment history | Invoices & payment gateway | 15% |
| Email engagement | Outreach campaigns | 10% |
The weights are yours, not ours
Every weight is editable in Settings → Health score, and can differ per customer segment. Changing a weight recalculates twelve months of history so you can compare straight away.
Three bands and what each one triggers
1
70–100 · HealthyThe customer is using it steadily. This is the group to ask for a case study, a referral, or an upgrade.
2
40–69 · Worth watchingAt least one signal has turned. The system creates a check-in task for the owner, due in seven days, with a suggested angle based on which signal slipped.
3
Below 40 · High riskThree or more signals bad at once. The task is escalated, an alert goes to the team channel and it surfaces on the manager’s dashboard.
How it works with everything else
SPECIFICATIONS
See the score for your own customers
Upload your customer list and we score it for free within 48 hours.
They go together
Three features usually switched on together
Score your own customers once and see
Nothing to install. Send the list and we send back a scoreboard plus the three customers to call first.

