Saved revenue as a receipt

Health scores are useful. They are also easy to overclaim.

A score can climb because one power user came back, because the season got busy, or because someone retuned the thresholds. None of that proves you kept the money.

While building FirstDistro I needed a cleaner finish line than “the tile turned green.” The name I use for that finish line is saved revenue: a receipt for intervention, not another chart.

Scores warn. Dollars settle.

Catch → save → prove is the loop.

Catch is the signal: usage fade, champion silence, stalled onboarding, a score drop that actually means something.

Save is the human (or the play) that changes the trajectory: a call, a restart, an exec sponsor, a commercial reset.

Prove is what you can put in a table afterward: what was at risk, what stayed, under which assumptions.

Saved revenue lives in prove. It answers a different question than NRR. NRR tells you whether the existing base grew or shrank over a period. Saved revenue tells you which interventions you believe protected named ARR.

You need both. One is the portfolio. The other is the receipt for work you claim mattered.

The three-line receipt

Keep it boring on purpose.

1. Signal: What fired, and when?
2. Action: Who did what?
3. Dollars: What ARR was at stake, and what stayed after the window?

Example sketch (composite, not a customer case study):

• Signal: Weekly active use down ~35% vs the account’s own baseline. Six weeks to renewal.
• Action: Focused renewal call plus a short value reset with the remaining champion.
• Dollars: At-risk ARR $36K. Account renewed. Directional saved revenue $36K if you believe full churn was the counterfactual.

Finance can argue with the counterfactual. That is fine. Arguing with assumptions is healthier than accepting vibes.

Why “health recovered” fails as proof

If your weekly update is “average health +12,” you are still selling dashboard theater.

Scores are leading indicators. They help you prioritize. They do not close the books.

A recovery without a named action is luck or noise. A recovery with an action but no dollar trail is folklore in Slack. A dollar claim with no catch trail looks like storytelling after the fact.

The receipt forces the three lines into the same row. Incomplete rows stay incomplete.

Design rules that keep you honest

Directional is allowed. Invented is not. Prefer conservative estimates. If you only believe you protected half the ARR, write half. If you cannot state a counterfactual, leave prove blank and say you had activity, not proof.

Time-box the window. Saved revenue needs a before and after. Pick a window tied to renewal or to 30/60/90 days after the intervention. Endless “we saved them somehow” is not a metric.

Separate the metric from the marketing claim. The design of the number is: signal, action, dollars. How you present it to leadership is a second problem. Do not let the slide rewrite the math.

Do not confuse with expansion. Upsell is not saved revenue. Keeping what was going to leave is the point of this receipt.

How to use it on Monday

After you run triage (health, silence, renewal), work the list.

On Friday, for each account you touched, ask:

1. Did we catch a real signal?
2. Did someone do a real thing?
3. Can we state directional saved revenue without lying?

Three yes answers earn a row in the monthly prove table. Anything less stays out.

Four weeks of honest rows beat one heroic cancel-week story.

Closing

I did not invent “care about churn.” Everyone already cares.

What was missing, for me, was a finish line that survived contact with finance: not a greener score, a receipt. Signal. Action. Dollars. Argue with the assumptions if you want. Do not pretend the job ended when the badge changed color.

This is the loop I ship in FirstDistro.