2 min lesson
Account health scoring
Make the call in this situation: "An account shows strong weekly-active usage but you only have one contact, the original champion. How should the health model treat it?" Explain what supports it.
Step 1 of 2
A health score isn't a grade you assign at quarter-end. It's a tripwire system that tells you which account to call today and what to say when you do.
Usage alone is a thin signal. An account can have strong weekly-active seats and still be one resignation away from churn. A real health view blends three inputs, because each one fails in a way the others catch.
Activation, weekly-active, depth, acceptance.
The objective layer - telemetry, not opinion.
Strong here can still hide relationship risk.
Multi-threaded or single-champion?
Do you reach the economic buyer at all?
The layer usage can't see.
EBR tone, support tickets, escalations.
What people say about the rollout.
The early-warning layer when usage is still fine.
Relationship strength deserves its own weight. Single-threaded accounts feel easy because one champion smooths every meeting and that comfort is the danger. Champion departure is one of the most common ways an enterprise account dies and when your only thread walks out you have no economic buyer and no power-user base to carry the renewal.
A green usage score on a single-threaded account is a false green. Telemetry can be excellent right up to the week your champion changes jobs and then the relationship score collapses with no warning in the usage layer. Multi-thread deliberately on every key account - economic buyer, champion and at least one power-user contact - before you're forced to.