Customer Health Framework

Cancellations were processed accurately and studied rarely. The model existed to make the difference between a customer who is gone and a customer who is still deciding visible on a page, every week, to the same set of people.

Health was being inferred from whoever complained loudest. Quiet risk was invisible, intervention attempts lived in individual notes, and recurring drivers were described anecdotally instead of counted. Without a shared read, effort went to the noisiest case rather than the most recoverable one.

• A health signal is only useful if it points at a specific next action. A score with no route attached is decoration.
• Reason categories should describe the cause, not the outcome. Wait time, space, product fit, cost, and relocation each call for a different response.
• Record what was tried and what happened. Otherwise the team repeats strategies out of habit rather than evidence.
• The same signals that identify risk also identify engagement. That was the opening that later became the proposed engagement and advocacy extension.

1. 01

   A health state model

   Customer states from at risk through healthy, engaged, and advocating, each with an owner and a defined action rather than a label alone.

2. 02

   A reason taxonomy

   A consistent set of cancellation and return reasons, applied the same way every week, so patterns could be counted instead of remembered.

3. 03

   Intervention and outcome tracking

   Each at-risk customer carried the intervention attempted and the result: retained, still negotiating, declined, or proceeding.

4. 04

   A recurring operating view

   One regular update read by operations and leadership together, separating finalized loss from active recovery.

• Became the operating view behind the customer health and retention work.
• Routed recurring drivers to the teams that owned the underlying cause.
• Provided the structure that the proposed engagement and advocacy extension was built on.

The model earned its keep because it was small enough to maintain weekly. Every attempt I have seen to make health scoring more sophisticated before it was habitual has collapsed under its own upkeep. Get the cadence first. Add the math later.

• Enterprise Customer Success
  Adoption & Engagement Analysis →

  A standard way to read adoption, active usage, cohort retention, and growth loops across a portfolio of accounts, and to turn each read into a specific recommendation.

• Product Strategy

  Referral, Rewards & Advocacy

  Using engagement and satisfaction signals to identify likely promoters, and rewarding the behaviors that build a habit rather than only the purchase. Proposed as an extension of the customer health work.