Champion Job-Change Engine
When a past champion changes jobs they carry trust into a brand-new account. Detects the move, ICP-checks the new company, drafts a warm re-intro, and hands the rep their highest-odds opportunity of the week.
Champion Job-Change Engine — warm-play detector
Past champions changed jobs. Scan, ICP-check the new company, draft the warm intro.
Run detection — the scanner finds moves and writes the warm re-intros for you.
34.4% vs 11.6% at ~$32k ACV.
Problem
Every quarter, champions who loved your product quietly leave for new companies — and your team finds out months later, if ever. That's the warmest pipeline in B2B evaporating. The motion is obvious; the system to catch it at scale doesn't exist in most orgs.
Who it's for
Any SaaS company with a base of closed-won customers and power users — especially land-and-expand and seat-based products.
How it works
- Weekly: pull the champion watchlist (closed-won contacts + power users).
- Detect job changes (Apollo re-match, hard-bounce-as-signal, or LinkedIn re-scrape).
- ICP-check the NEW company; skip non-fit moves.
- LLM drafts a warm re-intro that sounds like the rep who knew them (no generic 'congrats!').
- Create a CRM opportunity, alert the original rep, and push the move into P1 as a top-strength signal.
Outcome
38 champion job-changes detected, of which 35 land at A/B-fit accounts → 35 warm plays queued.
Warm plays win at 34.4% vs 11.6% for the cold control — roughly 3x — at a comparable ~$32k ACV.
Each play arrives as a ready-to-send draft on the desk of the rep who already has the relationship, so time-to-first-touch is minutes, not 'whenever someone notices.'
How it scales with paid data
- Add Clay/PhantomBuster LinkedIn monitoring for champions who don't surface in Apollo.
- Auto-enroll the draft into a 2-step warm sequence (rep approves, then it sends).
- Expand the watchlist to second-degree champions (people who worked alongside a champion).