It was a Tuesday. The kind of Tuesday you remember.
Our champion at Northwind Capital sent a 2-line email at 4:47 PM. "Moving on. New role at Stripe. Best of luck."
That was it. 14 days to renewal. $10M on the line. No champion.
What we missed before that email
For 8 months we treated Northwind like a healthy account. NPS was 9. Usage was up 23% YoY. QBRs ran on schedule.
Here is what we missed:
- 0 product feedback tickets in 60 days
- 1 active user out of 47 paid seats
- Champion reply time slipped from 2 hours to 24
Healthy on paper means nothing if only one person on paper still cares.
— Maya R.
We were tracking lagging indicators. The three above are leading. They live on the home dashboard now, not buried in CRM notes.
The 72-hour playbook
When the email landed, we ran a sprint. Exact sequence below.
Hour 0 to 4: map the org
Pulled Northwind from our internal tooling. Listed every user who had logged in at least once in 90 days. 12 names. Ranked by:
- Seniority (VP and above first)
- Login frequency in the last 30 days
- Usage of the feature tied to their expansion case
Top of the list: Director of Engineering Productivity. 14 logins last month. Never spoken to us.
Hour 4 to 24: warm intro, not cold email
Two reasons we did not cold email. One, vendor cold email in a churn moment screams panic. Two, we already had a shared-workspace footprint inside her team.
We asked the SE who had built dashboards for her group to make the intro. One line. "Maya is the person you should know on our side. She helped Helix cut their on-call escalation rate by 40%."
Reply in 2 hours.
Hour 24 to 72: the 30-minute meeting
Not a demo. Not a QBR. One slide.
The slide had three numbers:
1. What Northwind paid us last year: $8.2M 2. What her team shipped using the product: 488 internal tools, ~$94M in eliminated vendor spend by their own finance team's count 3. The gap: 11x
We never said "ROI." We said "this is what your team shipped using us. This is what you pay us." She did the math herself in real time.
She forwarded the slide to her CFO inside an hour. Renewal closed 9 days later. 23% expansion. $12.3M for the next term.
The lesson, in one line
Churn is a decision latency problem, not a data problem.
If you have the data and cannot move on it in under 72 hours, the data did not save you. You got lucky.
We rebuilt our health score the next quarter around 3 leading indicators:
- DAU as a percent of paid seats
- Champion reply time, rolling 14-day median
- Feature adoption velocity for anything shipped in the last 90 days
3 numbers. Every account. Every Monday.
What I would do differently
- Build the org map on day 1, not day 240. The second relationship should start in month 2, not week 3 of a save.
- Kill the QBR. Replace it with a 15-minute weekly Loom from us. Effort flips from customer to vendor. Engagement goes up.
- Treat champion silence as a churn signal at week 2, not week 8.
Steal what you want. The numbers will be different. The pattern will not.