Churn-Risk Save Playbook 2026
Your customers who renewed show you what steady use looks like. This play checks every account against that benchmark each week, catches the ones drifting further away while the gap is still worth closing, and puts the move on the account in your CRM: a save conversation, a re-engagement sequence your team chose to automate – or no move, with the reason noted.
The customers who renewed show you what steady use looks like: how many people are in the product, and which parts they use every week. When an established account drifts from that pattern, this play watches for the gradual kind: fewer active users, one feature going quiet, then another. Sudden drops matter too, and the trigger catches them.
This play catches that drift early, while the gap is still small and worth closing. It runs inside the weekly check: each week it finds the accounts whose gap to the benchmark grew, checks the records, and ends with a move your team decides on – a save conversation, a re-engagement sequence you chose to automate – or a note on why there isn't one.
Measure it on gross revenue retention, the share of widening gaps that close within eight weeks, and how long a gap sits before someone talks to the customer.
How it works9 steps
01SignalFind the accounts drifting away from your renewed customers
Build the benchmark once, refresh it quarterly:
- Comparison customers: same segment (plan tier, size band), 12+ months as customers, renewed at the same or higher revenue. Aim for 20; with fewer, label it low confidence.
- The measures: three to five things those customers share. Default: active users as a share of seats, and each feature they use in three of every four weeks.
- The pattern: the median on each measure. Your CS lead approves it.
Each week, count the measures where each account is below the benchmark – default, under 75% of the median. Default trigger: one more measure below than four weeks ago, or active users down by a fifth or more. Tune both to how often your product is used.
This play is for established accounts. Accounts still onboarding belong to the handoff play and the onboarding play; accounts renewing inside 90 days belong to the renewal play.
Say an account pays $24,000 a year and renews in seven months. Four weeks ago 14 of its 20 seats were active and it ran reports every week, like its peers. Now 8 are active and reports have gone quiet. (The numbers are illustrative.)
Run it as a weekly saved query in PostHog, Amplitude or Mixpanel, or a spreadsheet. Under about a hundred accounts, do it by hand.
02ScoreCheck the records before calling it a gap
- Seasonal or data blip? A renamed event, a holiday, or a gap between projects looks like a drop. Check the event log and last year's pattern.
- Champion still active? If your main contact stopped logging in or left, record it now. That changes who gets the conversation.
- Open tickets & talks: 60 days of tickets and CRM notes, plus any meeting already booked.
- Budget or org changes: a cut, a merger or a new tool mentioned in notes or calls.
03DecisionDecide whether there's a move worth making now
Leave it alone if the drop is seasonal or a data blip, the owner already has a live conversation about it (an open ticket being worked, a call in the next two weeks), or the account is below this week's cap on the weekly check – it stays ranked for next week. Everything else picks a move.
04ActionLeave it alone, and write down why
Set Recommended move to No move, write the reason in one line, and set Review date to when it could change – the end of the season, the day after the booked call. The leave-it-alone play covers the call in full.
05DecisionPick the move the evidence supports
Defaults to tune:
- High stakes: top quarter of the segment by ARR, two or more measures below the benchmark, or the champion is gone. Save conversation.
- The rest: the re-engagement sequence.
06ActionDraft a save conversation with the evidence
A task for the account owner with the gap, what changed, and the save note below. Lead with the specific change – "reports went quiet in August" beats "just checking in". If the champion left, write to whoever now runs the account.
07ActionRun the re-engagement emails your team chose to automate
Three short emails from HubSpot, each tied to the feature that went quiet, sent from the account owner. Every send is logged on the record. At first the owner enrolls each account from the task. Once the matches hold up, your team can choose to let a workflow enroll them. The sequence stops when anyone at the account replies. If the account gets back to the benchmark first, the owner unenrolls it, or a workflow does.
08Human stepYour team decides and runs the conversation
The CSM or AM reads the evidence and runs it as drafted, changes it, or passes. They own every customer conversation. Listen for the reason – a project ended, a champion moved, a budget review, work that moved to another tool – and record it. Before acting, record the success measure and the review date: active users back at the benchmark is progress; a renewal at the same ARR or more is the result.
09OutcomeReview what changed, then sharpen the benchmark
On the review date, record three answers: did use come back, is the account still paying the same, and what else played a part (a release, a new champion, a price change)? Emails sent are activity, not progress. If nothing moved, change the move, stop it, or give it time. Each quarter, check which moves worked for which accounts and which reasons you heard most, then update the benchmark.
Setup and templates
Sources: active users and feature use per account from a weekly saved query in PostHog, Amplitude or Mixpanel; seats, ARR and renewal date from billing or the CRM; tickets from your help desk; contacts and notes from the CRM. Account-level numbers need your analytics tool's account add-on (group analytics in PostHog, Accounts in Amplitude, Group Analytics in Mixpanel) and a group call in your app. Save the query, then subscribe to it (in Amplitude, add it to a dashboard and subscribe to that) so the result lands in your inbox or Slack each week. By hand: export each into one spreadsheet every Monday, one row per account, with this week's and four weeks ago's numbers side by side.
Company properties in HubSpot (Starter or above; free HubSpot allows 10 custom properties in total), or your CRM's account object:
| Property | Type | Filled by |
|---|---|---|
| Measures below benchmark | Number | Weekly check |
| Below benchmark four weeks ago | Number | Weekly check |
| Features dropped | Single-line text | Weekly check |
| Recommended move | Dropdown select: Save conversation · Re-engagement sequence · No move | Weekly check |
| Move reason | Single-line text | Weekly check |
| Success measure | Single-line text | Account owner |
| Review date | Date picker | Weekly check, then account owner |
| Review result | Dropdown select: Back at benchmark · Recovering · No change · Left or downgraded | Account owner |
The automation here uses HubSpot workflows (any Professional hub). On Free or Starter, run the same saved view and create the tasks by hand. The weekly list is a saved view: Recommended move is known and Review date is this week or overdue. In HubSpot that's two filter groups: Review date is This week, or Review date is before Today. Holds whose review date has come up show here too. Each move creates a task for the owner, "Widening gap: [move]", with the draft in the body. HubSpot's Slack app sends the task notification as a nudge; a custom message needs a workflow (Professional or Enterprise). The work happens on the record.
The emails are a HubSpot sequence (Sales Hub or Service Hub Professional), enrolled by the owner so they go from the owner's connected inbox. Letting a workflow enroll or unenroll accounts needs Sales Hub or Service Hub Enterprise. Turn on the sequence's option to unenroll contacts from the same company, so a reply from anyone at the account stops it. The re-engagement emails are marketing, whether the owner or a workflow sends them: check you have permission to send, use accurate sender details and your postal address, include an easy unsubscribe, and skip anyone on your suppression list. Keep required service notices separate.
Save note (High stakes):
Hi [name] – I noticed [feature] has gone quiet at [company] since [date], and [n] fewer people are using [product] than last month. Teams like yours use it to [job]. Has something changed on your side? If there's a better way to set it up now, I'm happy to help.
Re-engagement emails (The rest):
- Day 0 – "A quicker way to [job]": "Hi [name] – teams like yours use [feature] to [job]. Here's the two-minute version: [link]."
- Day 7 – "How [similar company] does [job]": "Hi [name] – [similar company] uses [feature] to [result]. Here's how they set it up: [link]."
- Day 14 – "Want a hand?": "Hi [name] – if it would help, I can spend thirty minutes on [job] with your own [data]. [booking link]"
No move: "No move – [reason]. Recheck [date]."
How Accoil fits
Accoil is a customer-success consultancy with our own tooling, and this is a play we run with you, not for you. We build the benchmark from your renewed customers with your team, and you approve it. Every week we check every account in the agreed segment, and the recommended move and its evidence land on the account record in your CRM – we recommend HubSpot – at a pace your team can actually run. Your team makes every call, including which moves run on their own. Nobody from Accoil contacts your customers. After the agreed window we review what changed together, and you keep the playbook, the benchmark and the analysis.
Running it yourself? Swap HubSpot for Salesforce or Pipedrive. The play stays the same. On Salesforce, the field writes need API access (Enterprise and up, or an add-on on Professional). On Pipedrive, automations and date triggers need the Growth plan. On Salesforce, the emails need Sales Engagement (included in Unlimited, a paid add-on otherwise), or send them from Customer.io. On Pipedrive, sequences run on deals, so enroll the account's renewal deal. `
Thirty minutes with Kate, Simon or Peter on one example segment: what a successful customer looks like, where the gaps are, and whether there's work worth doing this quarter.
Talk to a founder →Keep reading
Renewal-Risk Radar Playbook 2026
Renewals go best when the account already looks like your customers who renewed. From 90 days out, this play compares every renewing account with them each week – usage and revenue – checks the records, and puts one move on the account in your CRM: an expansion look, a value review, a save plan with the CSM – or no move, with the reason noted.
Customer Layoffs Counter-Play 2026
When a customer cuts staff, the goal is to keep the logo and an expansion path for when they rehire. Layoff news starts this play; the check compares seats and usage with the account's pre-news level and your successful customers. Real impact gets a right-size-and-retain offer and a revised forecast on the CRM record; no impact yet gets no move and a 30-day recheck.
Monday-Morning Account Triage Playbook 2026
Your best customers show you what good looks like. Every Monday, this play compares each account in a segment with that benchmark, ranks what each gap is worth, caps the list at what your team can run, and puts the week's moves on the account records in your CRM: close a gap, grow the upside, or leave it alone with the reason noted.
Every playbook, one download
All 32 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.