Champion Departure Early-Warning Playbook 2026
Your best accounts rest on more than one person: several active users and a senior sponsor. Each week this play counts relationships for every account in a segment against that benchmark, with the champion's silence and job-change data as evidence, and puts one move on the account in your CRM: a second-contact ask, a sponsor intro, a successor welcome – or no move.
Look at the customers who renew and grow: count the people who use the product each week, and check whether someone senior knows why they bought it. Then build relationships beyond one champion.
This play counts relationships each week for every account in a segment, against your best-connected customers. When an account falls short, it checks the records and puts one move on the account record, or a written reason for no move. Usage falling across the account is the churn-risk play; healthy usage with nobody talking to you is the ghosted-account play; a new executive is the new-executive play.
Measure it on the share of accounts at the benchmark for relationships, days from a departure to the first successor meeting, and the renewal rate on accounts that lost a champion.
How it works10 steps
01SignalCompare every account with your best-connected 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.
- What an active relationship is: default, a named contact who used the product in three of the last four weeks, or met or replied to your team in the last 90 days. A contact who has left doesn't count.
- What senior means: manager or above, from job titles on CRM contacts.
- The champion: the contact the account owner names on the record. Default, if nobody is named: the most active user.
- The pattern: the median number of active relationships, and whether one of them is senior. Your CS lead approves it. With too few customers to measure, start from three, one of them senior – a default to tune.
Each week, the account comes up if it has fewer active relationships than the benchmark, no active senior user, or a champion who has gone quiet: 14 days with no product activity (a default to tune). Someone working their notice may stop logging in well before their CRM record or public profile reflects the change. Say an account pays $40,000 and renews in five months. Your best accounts that size have four active relationships, one senior; this one has two, and the champion was last active 16 days ago. (The numbers are illustrative.)
Under about a hundred accounts, do it by hand.
02ScoreCheck job changes and records before calling it
- New job confirmed? A new company or title recorded on the champion's CRM contact, from UserGems or the account owner's own check.
- Successor named? The CRM contact list, the latest email thread, or an out-of-office reply.
- Away or data change? Time away, a new login method or a new workspace can all look like silence. Ask the account owner. Record Away, with an expected return date only if known. Don't record the reason.
- Budget or org changes: 90 days of CRM notes and tickets, plus the renewal stage.
03DecisionDecide whether there's a move worth making now
Leave it alone if the champion is quiet under 28 days (default) with no job change confirmed, if the records explain the gap, or if a move is still inside its review window. After 28 days, ask the owner to check the champion's status. Until a departure is confirmed, keep the status Quiet or Away and set a review date; record an expected return date only if it's known. A budget or org change doesn't hold this play; it goes in the note. Everything else picks a move.
04ActionLeave it alone, recheck at next week's check
Set Recommended move to No move, write the reason in one line, and set Review date a week out. A "sorry to see you go" note to someone who's away costs more trust than a week's wait. The leave-it-alone play covers the decision in full.
05DecisionPick the move the evidence supports
- Still here: the champion is active, but the account is short of the benchmark. Ask them for a second contact.
- Gone: departure confirmed by the owner, and no successor named. Sponsor intro.
- Successor: departure confirmed, successor named. Successor welcome.
06ActionDraft an ask to the champion for a second contact
The note below, framed as cover for when they're away – the cheapest time to ask is while they're still there. If the gap is a senior user, ask who above them should be in the loop. Add whoever they name to the record.
07ActionDraft a sponsor intro with the evidence
The intro below, to the champion's manager or the most senior active user. A departure is the one time this note is expected, not awkward. Silence alone doesn't confirm a departure. If nobody has confirmed it, skip the opening line and ask who the best contact is now.
08ActionDraft a successor welcome and re-onboarding plan
Treat the successor as a new customer. They didn't choose your product and they have none of the champion's context. The welcome below, then a short onboarding: first value in week one, the work their team depends on by week three. Once these drafts have been right for a few weeks, your team may choose to automate this move; the record shows what went out.
09Human stepYour team decides and runs the move
The CSM or AM runs the move as drafted, changes it, or passes. They own every customer conversation. Before acting, record the success measure and review date: a new contact active within four weeks is progress; a renewal, flat or up, is the result. A successor alone only keeps the count level – the goal is the benchmark.
10OutcomeReview what changed, then sharpen the benchmark
Eight weeks on, record in Review result whether active relationships went up, and what else played a part. If nothing moved, change the move, stop it, or give it time; the eight-week review covers how. The renewal deal records the result. Each quarter, compare renewals on champion-loss accounts with the rest, and update the benchmark.
Setup and templates
Sources: product activity per user from a weekly saved query in PostHog, Amplitude or Mixpanel; contacts, titles, meetings and renewal date from the CRM; job changes from UserGems, which checks the customer contacts you give it each week or month. 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 on the schedule you set. By hand: a spreadsheet of active users per account beside the CRM contacts, and LinkedIn for quiet champions. Check profiles manually or through an authorized source. Record only the relevant role, employer, source and check date. Where Article 14 applies, give the privacy information by the first contact or within one month, whichever comes first.
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 |
|---|---|---|
| Active relationships | Number | Weekly check |
| Benchmark relationships | Number | Weekly check |
| Senior user active | Single checkbox | Weekly check |
| Champion last active | Date picker | Weekly check |
| Champion status | Dropdown select: Active · Quiet · Left · Away | Weekly check, then account owner |
| Champion back on | Date picker | Account owner, only if known |
| Recommended move | Dropdown select: Second-contact ask · Sponsor intro · Successor welcome · 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: At benchmark · More relationships · No change · Stopped | Account owner |
Mark the champion and successor on the contacts themselves: association labels Champion and Successor on the company–contact association (Professional or Enterprise). On Starter, use a Single-line text property with the person's name and email.
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. Each move creates a task for the owner, "Relationships: [move]", with the draft in the body.
Second-contact ask (Still here):
Hi [name] – you've set up most of how [team] uses [product]. If you're ever out, who else should know how it runs? Happy to give [them] a twenty-minute walkthrough.
Sponsor intro (Gone):
Hi [name] – [champion] has moved on from [company], and they were our main contact. [Number] people on your team use [product] for [job]. I'd like to make sure you have someone on our side. Twenty minutes in the next two weeks?
Successor welcome (Successor):
Hi [name] – I hear you've taken over [area] from [champion]. Your team uses [product] for [job], and [what's set up] is running. Could we do thirty minutes on what's working and what you'd change?
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 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. 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, and UserGems for Clay. On Pipedrive, use Clay for this play. 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.
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
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.
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.
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.
Every playbook, one download
All 32 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.