One Signal, Two Plays
A champion leaves your best account. In most revenue orgs, this triggers a flurry of Slack messages, a rushed account review, and a rep manually Googling where they landed. By the time anyone acts, the window is gone.
Clay's published workflow flips the script. A LinkedIn job-change event automatically triggers two plays in parallel: an outbound sequence to the departing champion at their new employer, and an at-risk flag on the original account for re-engagement. Zero manual rep involvement. Both plays fire within minutes of the signal.
This is what RevOps automation is supposed to look like—a single real-world event generating compounding pipeline rather than compounding admin work.
Why Most Teams Miss This
The blocker isn't data. Most CRMs already log job changes if your enrichment layer is running. The blocker is workflow architecture. Teams treat champion departure as a retention problem and route it to CSM. They never close the loop to create a new business trigger at the destination company.
The Clay approach treats the champion as the unit of value, not the account. That reframe matters operationally. It means your ICP criteria travel with the person, and your outreach catches them in the first 30 days at a new role—when they're most likely to buy tools they already trust.
How to Implement This Week
The Clay post includes the exact table structure, enrichment steps, and message templates—it's genuinely copy-paste ready. A few decisions you'll need to make before deploying:
- Define your champion tier. Not every contact warrants both plays. Limit this to contacts who were active in an opportunity or held a specific title threshold—otherwise you'll generate noise.
- Set the re-engagement owner. The at-risk flag on the original account needs a routing rule. CSM or AE? A blank owner field means the play dies in the queue.
- Cap your enrichment spend. Clay runs on credits. If you have a large contact base, scope the trigger to accounts above a revenue or recency threshold first, then expand.
The underlying architecture—signal in, dual action out, no human in the loop for routing—is the pattern worth internalizing. Champion departure is one application. The same structure applies to funding announcements, headcount spikes, or any enrichment signal you're already capturing but not acting on systematically.
If your team has Clay and a CRM with contact history, there's no reason this isn't running by Friday.