> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Champion Tracking — Job Change Signals
> How do I track when former buyers change jobs and re-engage them at their new company? Use it to pilot, verify output, and scale safely.
Past champions who move to new companies win deals at **37% vs 19%** for cold outbound, based on 230K champions and \$256M in pipeline ([Champify](https://www.champify.io/resources/the-impact-of-tracking-job-changes-value-report)). They convert at **3x** the rate of cold prospects ([UserGems](https://www.usergems.com/blog/signal-based-marketing)). 30% of B2B contacts switch jobs annually ([Cognism](https://www.cognism.com/blog/data-decay)), so automated champion tracking pays for itself fast.
## How do I detect job changes with Claude Code?
The core prompt pulls your CRM, detects who moved, finds new emails, and updates your records in a single pass.
In Claude Code, type:
```
/deepline-gtm Find contacts in my HubSpot who changed jobs, get their new work emails, update HubSpot, and add job changers to my re-engagement campaign
```
**With Codex:**
```
codex "Pull my closed-won contacts from HubSpot, check which ones changed companies, find their new work emails, and flag them for re-engagement"
```
Uses the **[deepline-gtm](https://github.com/getaero-io/gtm-eng-skills/tree/main/skills/deepline-gtm)** skill.
## What does the champion tracking workflow do step by step?
**Priority:** P0-P1 | 90-day decay | 48h SLA | Route to original AE
Extract contacts from HubSpot/Salesforce via MCP. Focus on closed-won
contacts, active champions, and power users from the last 24 months.
Check each contact's current employer against their CRM record using
LinkedIn profile data or enrichment providers.
Identify contacts whose company no longer matches. Tag with previous
company, previous deal value, and relationship strength.
Run email waterfall for new company domain. Use the multi-provider waterfall
to improve hit rate.
Update CRM records with new company info, create a new contact record at the
new company, and trigger re-engagement campaign via MCP.
## Which sub-plays should I run for different champion scenarios?
Route each champion through the right sub-play based on their new company's relationship with you.
* **1A: Champion moves to a new logo** — Not yet a customer, but the company fits your ICP. Send a personal congratulations within 48 hours. A warm intro from someone who already believes in your product is the best new-logo entry point.
* **1B: Champion moves to an existing customer** — Alert the CSM and AE immediately. The champion can push expansion from inside.
* **1C: Champion moves to an active deal** — Tell that AE today. The champion validates your product internally and can shorten the evaluation cycle.
* **1D: Key contact leaves an active deal** — A risk signal, not an opportunity. Map the remaining buying committee immediately. Single-threaded deals win at roughly 5% ([Gong](https://www.gong.io/blog/data-shows-top-reps-dont-just-sell-they-orchestrate-with-ai)).
## What email template works for champion re-engagement?
> Subject: The move to \[New Company]
>
> \[First Name],
>
> Saw you joined \[New Company] as \[Title]. Good move.
>
> I keep thinking about what your team built at \[Previous Company] — the \[specific result]. I'd imagine the first 90 days at \[New Company] are about \[rebuilding/scaling/standing up]. If \[product] makes sense there, I'm around.
>
> Either way, congrats.
**Timing matters:** Day 1-2 feels like a bot. Day 3-5 feels human. After day 7, you are one of many.
## When should I upgrade a champion signal to P0?
Stack champion tracking with other signals to prioritize your outreach queue.
**Upgrade triggers:**
* Job change + new company raised funding = **P0** (see [Fundraising Signals](/docs/plays/signal-fundraising))
* Job change + new company hiring relevant roles = **P0** (see [Hiring Signals](/docs/plays/signal-hiring))
* Job change + previous deal was Lost = P2 (see [Lead scoring and signal discovery](/docs/plays/play-qualify-lead-fit))
## Frequently Asked Questions
### How often should I scan for job changes?
Weekly. Daily scans burn credits without meaningful lift since most job changes are detectable within a few days. Monthly is too slow. The 48-hour SLA matters because the first seller to reach out after a job change is **5x more likely to win** ([Autobound](https://www.autobound.ai/blog/signal-based-selling-complete-guide)).
### What if the champion moved to a company that is too small or outside my ICP?
Still send the congratulations. Champions talk to other champions. Even if their new company is not a fit, they may refer you to peers at companies that are. Track the relationship in your CRM as "non-ICP champion" for future reference.
### Should I reassign the champion to a new AE or keep the original relationship?
Route to the original AE. The existing relationship is the whole point. If territory rules conflict, make an exception. Relationship continuity drives conversion.
### How do I handle a champion who left on bad terms?
If the champion churned or had a negative experience, flag for manager review before outreach. A bad re-engagement attempt burns the bridge permanently. Consider whether the product issues that caused the negative experience have been resolved.
### What CRM fields should I track for champion monitoring?
At minimum: original deal value, relationship strength (champion/user/evaluator), last interaction date, and original AE. These fields let you prioritize which job changes to act on first.
***
**Related:** [Hiring Signals](/docs/plays/signal-hiring) | [Fundraising Signals](/docs/plays/signal-fundraising) | [Deal Risk Signals](/docs/plays/signal-deal-risk) | [Job changes and CRM cleanup](/docs/plays/play-job-change-alerts)