The Churn Risk Play

Someone from the original buying group leaves, and the renewal loses its advocate months before usage shows it. Six moves to find those accounts and reach the rest of the committee first.

Get the play
Video Poster

Churn risk models are usually built on lagging indicators. Product usage and login frequency only move once an account has started to disengage, so a health score turning amber is telling you about something that began weeks or months earlier.The leading indicator is personnel change inside the buying group. When the person who championed the purchase leaves, the account loses its internal advocate. Whoever inherits the relationship often has no history with you and no particular reason to defend the renewal. This play runs across every account renewing in the quarter. It rebuilds the committee as it stands today, then names everyone on it with no engagement history, so outreach can start while the renewal is still months out.

1. Pull every account renewing this quarter

The audience here is your own customer base, filtered to contracts with a renewal date inside the current quarter. Keep the whole book in scope at this stage.Data this step needs

  • Renewal date

  • Contract value

  • Account owner

  • Product line

Timing. The play is only preventative if it runs before the renewal window opens. Accounts inside the last 30 days need a more direct save motion.

List scope. Don't pre-filter to accounts you already consider at risk. You're looking for the risk your health score has missed, so screening first removes the accounts you most want to find.

2. Find the accounts that lost a buying group member

Run job change detection across every contact attached to those renewal accounts, and flag any account where someone from the original buying group has left the business or moved into a different role internally.

Data this step needs

  • Job change alerts

  • Internal role change

  • Departure date

  • Original buying group

Any member counts. Seniority is a poor guide to impact here. The admin who ran the day to day implementation can be a bigger loss than the VP who signed the contract and never logged in, so flag the departure whatever the title.

Internal moves. A champion who transfers to another team is as absent from your renewal as one who left the company.

Time since departure. The gap between someone leaving and the renewal landing tells you how much runway you have to rebuild the relationship.

3. Rebuild the buying committee as it stands today

Map the account as it looks today. Pull the current org chart and identify everyone with a say in the renewal: the budget holder, the operational owner, the team using the product day to day, and whoever picked up the departed member's remit.Data this step needs

  • Org charts

  • Contact data

  • Reporting lines

  • Role seniority

The backfill. If the departed champion has been replaced, that new hire is the most important contact on the account, and almost certainly has no relationship with you.

Growth since signature. Accounts that expanded often have stakeholders who were never part of the original evaluation and have no idea why the product was chosen.

4. Name and flag every unengaged contact

Cross-reference the rebuilt committee against your own engagement records and produce a named list of the people on it with no meaningful contact history. That list is what the rest of the play acts on.

Data this step needs

  • CRM activity history

  • Email history

  • Call and meeting history

  • Signed contract

Two kinds of unengaged. Some of these contacts sit in your CRM with no logged activity. Others were never captured at all, because they arrived after the deal closed. Step 3 surfaces both, so the flag rests on engagement history and not on whether a record already exists.

The signatory. If the person who signed has gone and nobody else on the committee has engaged, the account has no internal advocate left.

5. Research each flagged account before writing anything

Run automated research across the flagged accounts so the outreach has something specific to say.

What the research pulls

  • Product and usage data

  • Hiring signals

  • Competitor research

Product and usage context. How the account is actually using what they bought, and which teams have adopted it. This is what makes a first message credible to someone who has never spoken to you.

Hiring signals. Open roles show where the account is investing, and whether the departed member's role is being backfilled or absorbed.

Competitor research. Activity on review sites like G2 changes a renewal conversation into a defense, and it's better to know going in.

6. Write and send a message to every unengaged contact

Generate one message per contact. The unengaged people on a committee each have a different reason to care: the budget holder is thinking about cost and outcome, while the person who inherited the departed champion's work is mostly wondering whether this is about to become their problem.

The renewal date. State it plainly, so the reason for the message is obvious.

Their specific role. What their remit has to do with the account, drawn from the org mapping in step 3.

Something the account actually did. A usage detail or a change in the business, so the message could not have been sent to anyone else.

Route to whoever owns the renewal, then refresh the play monthly. Job changes happen continuously, and an account that looked well covered in January can lose its champion in March.

How to run this play in GTM Studio

Video Poster

FAQs for renewal risk

Why use job changes to predict churn instead of product usage?

Usage is a lagging indicator. It only moves once the account has started to disengage, which is late in a process that began earlier. A departure inside the buying group happens before any of it reaches the product.


What counts as the original buying group?

Everyone who shaped the original purchase: the signatory, the budget holder, the person who ran the evaluation, and the operational owner who implemented it. If any of them has left or moved internally, the account has lost part of the reason it bought.


What if an account has no unengaged contacts?

Then it's in better shape than most and drops down the priority order. Still worth re-running as the committee changes, since a single resignation can undo good coverage.


How far ahead of the renewal should this run?

A full quarter ahead. Building a relationship with a committee member who has never spoken to you takes several touches, and accounts inside the last 30 days need a more direct save motion instead.


Does it matter how senior the departed contact was?

Not for triggering the play. Flag the account whenever anyone from the original buying group leaves, then judge the impact when you rebuild the committee in step 3. Operational owners often leave a bigger gap than the executive who signed, because they were the ones actually using the product.


Do I need product usage data to run this play?

No. The core build runs on your CRM records plus job change and contact data. Usage data makes the research step richer, though the play works without it.