$48k ARR: one call after the champion went quiet

One call. $48k ARR kept.

Not a multi-threaded war room. Not a discount spiral. A quiet champion, a clear signal, and a conversation that happened before cancel language showed up.

Composite story. Directional receipt. The shape is what matters. This is not a named FirstDistro customer case. It is a prove pattern you can copy.

Catch

Account: $48k ARR. Renewal in five weeks.

Signal: champion login streak broke. Fourteen days with no session from the person who had driven the last two QBRs. Broader usage was soft, not collapsed. Health sat in "watch," not "critical." The admin still showed up. The economic buyer was silent in CRM notes.

Most teams would have waited. The last NPS was fine. The last meeting was polite. That is how surprise churn gets scheduled: green-looking books with hollow ownership.

We treated champion silence as a first-class risk, the same way we treat a hard score drop. Silence is often the earliest tell in silent churn. Scores alone are not enough. See health scores vs saved revenue.

Monday triage put this name on the list: silence + renewal clock + meaningful ARR. Without that ritual, it would have waited for a "QBR reminder" email that nobody answers.

Save

The CSM did not send a newsletter. They asked for 20 minutes with the champion and one economic buyer optional.

Opener: "We noticed you have been offline in the product after a steady quarter. Before renewal, we want to know what changed and whether we are still mapped to the outcome you bought."

What we learned: the champion was overloaded after a reorg. The team still needed the workflow. Nobody had restated ROI for the new VP. Procurement had already asked for a "do we still need this" note. That note would have been written without us in the room if we had waited another week.

On that single call we:

1. Rebuilt a one-page value summary in their language (outcomes, not feature list)
2. Booked a 30-minute VP briefing for the following week
3. Assigned an internal owner to unblock one integration issue raised live

No pricing concession on the call. The commercial conversation stayed clean because the value conversation happened first. That is proactive CS, not reactive discounting. Habits like this live in proactive vs reactive customer success and how to reduce SaaS churn.

The VP briefing happened. The integration unblocked. Renewal moved from "reviewing options" to "standard renewal path" with one commercial clarification on seats. Still no fire sale.

Prove

Expected loss without intervention (directional): $48k full churn. Basis: champion silence + soft usage + renewal inside 60 days + no exec map after reorg + procurement already sniffing.

Actual loss after the window: $0. Renewed at $48k. Expansion deferred, not lost. We did not count deferred expansion as saved revenue. That would have been dishonest.

Saved revenue ≈ $48k.

Receipt filed under saved revenue: signal, action, window, dollars. Leadership did not get "NPS stable." They got a line item. NRR still mattered for the book. This receipt answered a different question: did this intervention protect named ARR?

Why one call worked

Timing. Specificity. A human.

An alert without a call is a badge. A call without a dollar frame is a nice chat. Together they become a prove story.

It also worked because we did not invent urgency. Procurement was already moving. We matched that clock with a value reset before the cancel narrative hardened.

What would have failed: a generic "checking in" email, a QBR deck full of product roadmap, or a health score screenshot as the agenda.

What we almost did wrong

Almost waited for the score to go red. Almost assumed the admin login meant the account was fine. Almost offered a discount before we understood the reorg. Almost counted "good vibe on the call" as the win without writing expected vs actual loss.

Those almosts are why prove needs a receipt.

Champion risk is also a portfolio pattern. When several logos lose their buyer at once after a market reorg wave, triage by ARR and renewal clock, not by who emailed last. One call per at-risk logo beats one newsletter to the book.

Try this when a champion goes dark

1. Do not wait for a second quiet week if renewal is near.
2. Ask what changed organizationally before you pitch features.
3. Leave the call with a dated next step and an ARR number you are protecting.
4. After renewal, write the dollar line even if the number is directional.
5. Keep expansion out of the saved-revenue cell unless you truly prevented a contraction.

Ask FirstDistro can help surface who went quiet. The call is still on you. The receipt is still on you. Quiet champions do not wait for your next QBR slot.