We caught the drop 6 weeks before renewal

$36k ARR stayed. Not because the health score looked nicer in a screenshot. Because someone caught a usage drop six weeks before renewal and did something specific.

This is a composite Revenue Save Story: catch → save → prove. Names are anonymized. The receipt shape is real. Use it as a template for your own prove notes, not as a FirstDistro customer claim.

Catch

Account: mid-market customer, $36k ARR, renewal in 42 days.

Signal: weekly active users down about 35% versus that account's own eight-week baseline. The composite health score had slipped from the high 70s into the low 60s. Not a fire drill red. A fade.

Secondary signal: the day-to-day admin still logged in. The champion who owned outcomes had gone quiet for three weeks. No angry tickets. No NPS collapse. Classic silent churn texture: polite on the surface, empty underneath.

What the dashboard said: "watch." What the Monday list should have said: work this week.

Without a triage habit, this account would have sat in "monitor" until renewal week. With one, it made the list on risk + silence + renewal clock. The habit is the same one in which customers need you this week: fifteen minutes, then a next step.

We also checked leading signals, not only the score. Login mix had shifted toward viewers. Feature depth on the paid module flattened. Those are leading indicators of churn, not noise.

Save

Day 0: CSM sent a short note tied to the signal ("usage vs your baseline") and booked a 25-minute call within 48 hours. No "just checking in." No newsletter.

On the call we learned the champion's team had paused a rollout after a messy internal reorg. They were not shopping competitors yet. They were stuck. Waiting until renewal week would have meant negotiating from a cold relationship and a half-implemented product.

Actions taken:

1. Restarted a scoped onboarding checklist with one success milestone in 14 days
2. Pulled an exec sponsor on our side into a 15-minute alignment note so the customer felt covered, not abandoned
3. Cleared two product friction items that blocked the milestone (one config, one access issue)

No discount. No panic multi-year deal. A save playbook, not theater. The general moves live in how to reduce SaaS churn and proactive customer success.

Day 14: milestone hit. Usage recovered partway, not fully. Champion was back in the product. That was enough to change the renewal conversation from "do we still need this" to "how do we finish the rollout in Q3."

Prove

Outcome window: through renewal.

Expected loss without intervention (directional): full churn of $36k ARR. Basis: fade + champion silence + renewal proximity + stalled rollout. Conservative enough that finance would not laugh.

Actual loss after intervention: $0. Account renewed at $36k.

Saved revenue ≈ $36k for that window.

We filed the receipt: catch signal, actions, dates, dollar line. That is saved revenue, not "health recovered +12 points." The score did improve later. Finance got the dollars first. If someone asks whether a better score proves ARR, the answer is no. See health scores vs saved revenue.

What we would have missed

If we had waited for a ticket, we would have met them in cancel mode. Tickets are lagging. This account never filed one.

If we had celebrated a temporary score bounce without a milestone, we would have walked into renewal with the same stalled rollout and a cheerful chart.

If we had sorted only by lowest score, a chronic red with $8k ARR would have stolen attention from this $36k fade. ARR on the list matters.

Six weeks of warning is a gift. Only if you treat it as a work order.

The other miss: treating prove as optional. Catch and save without a dollar line leave CS unable to answer finance. The next budget conversation will ask for charts again. Bring the receipt instead.

How to write the same receipt

1. Name at-risk ARR before you call.
2. Tie the opener to the signal, not to "just checking in."
3. Log the action the same day (who, what, when).
4. After renewal (or 30-90 days), write expected loss, actual loss, saved dollars.
5. Cut anything you cannot defend. Directional is fine. Fiction is not.

Dashboards help you catch. Calls help you save. Receipts help you prove. Category context: dashboards don't save accounts.

Try this on your next fade

Pick one account with a usage drop and a renewal inside 90 days. Build a one-page note: signal, at-risk ARR, next step, owner. Run the save. When the window closes, write the dollar line.

Get started if you want that loop closer to product, not only in a Monday checklist. The call and the receipt are still on you. Visibility without those two steps is just another dashboard.