The Champion Move Playbook: From Watchlist to a Warm Meeting

When a past buyer or power user changes jobs, they carry your relationship into a new company with fresh budget authority and a mandate to change things. This playbook is for founders selling their own product, account executives, SDR leads, and partnerships teams who want to reach that person while the window is still open, without renting an alert feed. It carries the job end to end: build and refresh a champion watchlist from public evidence, detect the move within days on a search cadence, re-qualify the new company against your ICP, verify a safe-to-send email, and work both the warm destination and the exposed old seat.

Why the champion move is the highest-yield play in outbound

A past champion inside a deal changes the odds more than any subject line ever will. Across more than 5,000 B2B opportunities, including a past champion lifted the win rate by 114%, increased deal size by 54%, and shortened the sales cycle by 12%. Selling to known contacts, meaning former customers and champions who changed jobs, wins at 37% against 19% for cold outreach - roughly double.

The reason is not sentiment. A champion who bought or loved your product already did the internal selling once. At a new company they arrive with a review mandate, de facto budget, and a reason to reach for a tool they already trust. The named Metadata case is the clean illustration: leads sourced from champion moves closed in an average of 60 days against 143 days for other deals, an 81% shorter cycle, and average contract length rose from 13 to 15.5 months.

Every ranking page turns this into a buy-a-tool decision and stops at the alert. This guide is the operating procedure instead. The two steps vendors skip - re-qualifying the destination account and verifying a safe email - are exactly where the play is won or lost, so both get real weight below.

The window: how long you have and why speed compounds

You have roughly 90 days, and the clock starts the day they land. When a new CTO, CMO, or VP of Sales joins, they typically carry a 90-day mandate to evaluate and improve their function, and that review almost always includes existing tools, processes, and vendors. They hold de facto budget authority even when the formal cycle is mid-year.

Speed inside that window is not vanity. Executives who scored early successes in the first 60 to 90 days had a 66% higher likelihood of long-term success, which is precisely why new leaders act fast and reach for tools they already trust. Some functions decide inside the first two to six weeks, so treat 90 days as a soft ceiling, not a deadline, and prioritize Director-level and above moves first.

That lag is the opening. A disciplined manual re-check on a weekly cadence routinely beats teams who rent a real-time-ish feed, because their feed is not actually real time. You do not need to react in 48 hours to win. You need to arrive before week three.

Sizing your watchlist and reading the supply

Size the watchlist to the flow of moves you can actually work each week, not to the largest export you can pull. Two published rates bracket the math: about 20% of CRM contacts change jobs within a year, and broader labor data puts workforce job changes near 30% annually, against a median US tenure of 3.9 years in January 2024 - the lowest since 2002. UserGems goes further, reporting that over 39% of buyers plan to change jobs this year.

Run those rates against list size and the monthly flow becomes concrete.

A 500-name list is the sweet spot for a single rep: roughly 8 to 13 confirmed moves a month is enough to keep the play live without drowning the weekly review. Go bigger only when you have the headcount to route same-week.

Geography sets refresh density, not just addressable market. In Refolk's index of professional profiles, there are 239,966 US Account Executives against 17,169 in the UK, a ratio of about 14:1. A US-anchored watchlist throws far more monthly moves than a UK one at the same size, so plan cadence and headcount to the geography you actually sell into.

Top current AE employers surfaced in the index include Salesforce, HubSpot, and Ironclad in the US, and Revolut, IBM, and AvePoint in the UK. Those are the kinds of destinations your champions land at, which matters when you re-qualify.

The signals that reveal a move, and the ones that lie

Five public signals reveal a move without a paid data layer, and each has a way it deceives you. Read them together, never in isolation.

• Started-new-position update. A profile update announcing the new role. It lies when the update is months old and cached, making a late congratulations look automated.
• Changed-jobs-in-the-last-90-days filter. A Sales Navigator saved search that surfaces recent movers in bulk. It lies by lag, often trailing the actual move by 3 to 4 weeks.
• Company-page hire announcement. A new company posting about a leadership hire. It confirms the destination but rarely the exact start date.
• Hard bounce on the old work email. The old mailbox rejects mail, meaning the person left. It tells you someone moved but not where to.
• New-domain email signature. A reply or forwarded thread showing a new company domain. Strong, but only appears if you already have a live thread.

The rule that ties them together: never act on one signal alone. Confirm the new employer and title against two public points before you send anything.

Hiring for new roles, engaging with content, updated company descriptions, and headcount changes are all visible on LinkedIn without any paid tier. The work is not access. The work is running the same searches, on the same day, every week.

Run the play: build, detect, qualify, verify, send

This is the procedure end to end. Each step names an owner, a rough duration, and what done looks like. Follow it start to finish without improvising.

The manual bottleneck is steps one and three: matching every champion to a public profile, then re-finding them cold each week. That is exactly the friction of re-identifying your own people across LinkedIn and the open web on a cadence.

Running that search on Refolk turns the watchlist into a living list rather than a stale CRM export, and it collapses the two steps vendors leave manual into a single ask you can repeat every week.

Re-qualify the destination: where the cheap wins hide

A warm relationship at a bad-fit account still loses, so re-qualifying the new company is not optional. Only 5 to 10% of the accounts in your ICP are actually ready to buy at any moment, and destination fit is the gate that separates a warm intro that closes from one that stalls.

Keep fit and intent as separate numbers. Fit answers whether you should sell to this account at all, built from firmographics like industry, size, revenue, and geography, plus technographics, meaning the tools they run, plus persona. Intent is a separate signal that answers whether they are moving now.

The multiplier vendors skip is technographic fit. In one documented case, adding a single filter for accounts running Salesforce Enterprise with 50-plus users cut the target list by 35% but pushed close rate from 18% to 31% and dropped the cycle from 74 to 44 days. Gating champion moves on stack fit, not just title, is the cheapest lift in this whole play.

A working destination rubric adds triggers and disqualifiers on top of fit: buying triggers like funding rounds, leadership changes, and compliance mandates that raise the score, and negative signals that subtract. Run the disqualifiers before anything goes out.

Only 5 to 10 percent of your ICP is in-market at once, so destination fit is the gate, not the afterthought.

Verify the email: a reputation trade, not a data task

Deriving a new email is a permutation problem; sending to it is a reputation decision. Permute name-plus-domain patterns on the new company, run SMTP verification, and send only to addresses marked valid.

The numbers make the discipline non-negotiable. Sending to 15 to 40 candidate emails per contact without verification produces a 25 to 40% bounce rate. Gmail, Outlook, and major mail servers classify a domain as suspicious above 5% bounce, delivery drops sharply above 10%, and above 15% the domain enters spam-suspect territory. One lazy blast to a 500-name champion list can torch your sending for months and erase the warm-intro advantage you spent weeks building.

The fix is a strict pipeline. A workflow that runs a permutator, then SMTP verification, then filters to valid only, cuts bounce to 1 to 3%, which is safe for sender reputation.

1. Permute patterns on the NEW domain:
   first@ · firstlast@ · first.last@ · flast@ · first_last@ · f.last@
2. SMTP-verify every candidate.
3. Route by result:
   valid      -> safe to send
   invalid    -> discard
   catch-all  -> quarantine, send in tiny batches only, retire on bounce
   unknown    -> do not send, set channel = LinkedIn only
4. Cap unverified sends at 0. Monitor bounce; pause the domain above 5%.

Catch-all needs judgment, not a green light. Verification can identify catch-all status but cannot guarantee the mailbox exists, so the decision to send becomes a risk-management choice. Segregate catch-all addresses, send in small volumes, retire anything that bounces, and when in doubt route the touch through LinkedIn instead.

How this play goes wrong

The failure modes below are where champion-move programs quietly die. Each carries the check that catches it.

• Stale-scrape false positive. A cached profile shows a role that is months old, so you congratulate late and look automated. Confirm the start date against a second public point.
• Wrong-person match. A common name matches the wrong profile during list-build and you email a stranger. Verify prior employer and title overlap before trusting the record.
• Catch-all valid illusion. The verifier returns success but the mailbox does not exist, so you bounce silently. Treat catch-all as risk, test in tiny batches, retire on bounce.
• Permutation blast. Sending all 15 to 40 guesses torches reputation for months. Never send unverified; valid-only.
• Fit without disqualifier. The destination matches firmographics but is a competitor, existing customer, or in a freeze. Run negative flags before send.
• Cadence drift. The weekly review slips to monthly and you arrive after the inbox is crowded, on top of the 3-to-4-week native lag. Book a fixed calendar slot and route same week.
• Single-thread reliance. You reach only the champion and miss the 9-to-12-person buying group, so one departure kills the deal. Multithread from day one.
• Window mis-estimate. You treat 90 days as a hard deadline when some functions decide in the first two to six weeks. Prioritize Director-plus moves first.

The single-thread trap deserves emphasis. Buying groups average 9 to 12 people, and multithreaded deals win at roughly 5x the rate. The champion is your entry point, not your whole strategy.

Keep the work current

The list is the asset, and a champion list decays quietly. Before Metadata systematized this, about 25% of their contact database had gone stale. At a 3.9-year median tenure, a watchlist you do not refresh monthly rots on a predictable schedule, and every stale record is a move you missed.

Run this before you call the cycle done.

Two habits keep the program alive. Re-run the list build monthly so decay never compounds, and hold the weekly detection slot as a fixed calendar block that does not move. The play is not clever tooling. It is the same searches, run on the same day, routed the same week, measured against a baseline you actually check.

The payoff justifies the discipline. A play that turns known relationships into 37% win rates, 54% larger deals, and cycles measured in weeks instead of months is worth an hour a week, provided the hour actually happens.