Value-to-Health Loop
Fold realized value back into the health score, so onboarding milestones and outcomes raise health and stalls lower it.
Included with cscron . A seat without it sees an upsell here instead of the page.
Overview
Value-to-Health Loop connects two things that usually live apart: the value a customer is realizing and the health score you track. It scores realized value from an account's value events, onboarding milestones, feature adoption, outcomes achieved, stalls, and folds that score back into the health signals, so an account making real progress reads healthier and one that has stalled reads more at risk, even before raw usage moves.
What it is for, on the page. Under the headline, this page says what it produces, what makes it run, and where the output lands. Every Work page reads that line from one registry, so the three answers cannot drift from the page.
How value is scored
Each value event carries points by kind (an outcome counts more than an onboarding step) and a magnitude, and recent events count more than old ones on a decay curve. Positive events push the value score above a neutral fifty; stalls and inactivity pull it below. Momentum, accelerating, steady, or stalling, is read from the last month of events. An account with no dated value events keeps an honest null value score rather than a fabricated one.
How it folds into health
The loop is conservative and honest: realized value fills in engagement and adoption only when you have no telemetry for them, so real usage data always wins over the value proxy. A stalling value trend registers as a usage-drop decline signal even when raw usage looks flat, which is exactly the early warning a CSM wants. The panel shows the base health, the health with value folded in, and the lift, so the effect of the loop is always visible.
Deterministic
Both the value score and the health fold are deterministic: the same events always produce the same result, so the loop is auditable and a CSM can trust the number in a renewal conversation.