Skip to content
Outbound Plays

Champion and new-hire tracking

The repeatable motion off a job change, whether a champion of yours moved or a new decision-maker just arrived.

A handful of well-timed touches, inside the window that still converts.

By Rahul · Updated June 2026 · 7 min read
Play Snapshot
Signal-driven
Outcome
Booked conversations with warm, high-context buyers
When to run it
A past champion or a new exec lands in your ICP
Signals it uses
Job changes, new executive hires
Channel mix
LinkedIn + email, light touch, inside the window
~4 to 5 touches Over 2 to 3 weeks

Champion and new-hire tracking is the motion you run when a decision-maker changes seats, whether it is a champion of yours who moved or a new leader who just arrived. You reach them while budget and mandate are fresh, and turn a job change into a booked meeting. It is champion tracking, widened to every senior move worth acting on.


When to run it

Run it when all three are true

Miss any one of these and you are not running this play, you are sending a cold email with a friendly subject line.

1

A real relationship

They were a user, a buyer, or a genuine advocate. A name in the same CRM does not count.

2

A role with power

The new seat carries budget and scope, so they can actually act on a yes inside the window.

3

A company that fits

The new company matches your ICP. A great contact at a no-fit account is a nice note, not pipeline.

The point is not to reach more people. It is to reach the few who will take the meeting, at the one moment they are most likely to say yes.


The signals it uses

This is a signal-driven play. Two triggers feed it, and the opener changes depending on which one fired.

The read

The two triggers run the same cadence but need different openers. A moved champion is warm, so you lean on the shared history and the result you drove together. A new executive is a stranger, so you lean on their fresh mandate and the gap they were hired to close. There is also a defensive version, reconnecting when your champion leaves an account you already serve, which the job change signal covers in full.

Already have a list of warm contacts going cold?

Book a Fit Check

The sequence

How we run it, touch by touch

Four to five touches over two to three weeks, all inside the window. Light, specific, and easy to stop if they do not engage.

Step Channel Timing Goal
1 Reconnect
LinkedIn Days 1 to 3 A warm note on the move, referencing the shared past. No ask.
2 The opener
Email Days 2 to 4 Tie the past result to the new mandate. One soft, specific ask.
3 Engage their world
LinkedIn Days 5 to 8 Genuinely engage a post about their new role. Stay visible, no pitch.
4 Useful follow-up
Email Days 7 to 10 Offer something useful, like a short teardown. Ask for a catch-up.
5 The break
Email or LinkedIn Days 14 to 20 One last light touch, then stop. Re-enter later with a fresh reason.
The one rule

Automate the detection and the routing so you act fast. Never automate the first line. The opener has to name a specific shared history, and that is written by a person, every time.


Where it wins, and when it fails

A play is only useful if you know when not to run it. Here is the honest read on both.

Where it wins
  • Highest reply quality of any outbound play we run
  • Cheap, you can start from your own CRM
  • Fast to value, the window rewards speed
  • Compounds, today's buyer is tomorrow's champion
When it fails
  • !Low volume, it cannot be your only motion
  • !Dies the moment you automate the message
  • !Wasted on thin or imagined relationships
  • !Useless if you find the move months too late

Common mistakes

What kills the play

Four ways teams turn a warm signal cold. Each one is avoidable, and each one is common.

The generic congrats

A "congrats on the new role" with no specific hook reads as a pitch in disguise, and gets ignored like one. Name the shared history instead.

Automating the opener

A templated first line kills the one thing that makes this warm. Automate the alert and the routing, write the opener by hand.

Single-threading the account

Betting on one contact means losing the account when they leave. Use the move to build a second relationship, not just chase the first.

Missing the window

Find the move months late and the mandate, budget, and warmth are gone. Speed is the play, so detection has to be fast.

Want this play set up and run for you?

Book a Fit Check

How we would run it

The play in motion

An illustrative walkthrough of the method, not a specific client result. We report real numbers only when they are real.

  1. 1
    The list

    Watch the warm

    Set a monitor on people who ran pilots or gave great feedback but could not buy at their last company.

  2. 2
    The move

    One surfaces

    A contact lands as Head of Revenue at a company that fits the ICP. The alert hits the CRM within days.

  3. 3
    The touches

    Reconnect, add value

    Reconnect on the pilot, tie it to their new stage, comment on their first post, then offer a short teardown.

  4. 4
    The meeting

    Compare notes

    A 20-minute catch-up, framed as comparing notes, not a sales call. The cadence stops at the fourth touch by design.


Plays like this fed pipeline we've built inside these companies
Palm.aiPalm.ai
AlcméonAlcméon
MindflowMindflow
CEF.AICEF.AI
BooleeBoolee
CoachHubCoachHub
InrōInrō
Buster.AIBuster.AI
Palm.aiPalm.ai
AlcméonAlcméon
MindflowMindflow
CEF.AICEF.AI
BooleeBoolee
CoachHubCoachHub
InrōInrō
Buster.AIBuster.AI

FAQ

Questions founders ask

How is this different from emailing anyone who changed jobs?
Champion tracking only targets people who already have a relationship with you, past users, buyers, or strong advocates. Emailing anyone who changed jobs is cold outreach with a timing excuse. The whole edge here is the warm history, so if there is no real relationship, this is not the play to run.
How many touches should the champion tracking play have?
Keep it light, around four to five touches across email and LinkedIn over two to three weeks. This is a warm motion, not a cold sequence, so a long automated drip works against you. If they do not engage, stop and re-enter later with a fresh reason rather than grinding the cadence.
Can you automate champion tracking?
Automate the detection and the routing, not the message. A monitor can flag the move and push it to your CRM in near real time, which is where speed matters. But the opener has to reference a specific shared history, and that part is manual by design. Automate the trigger, write the first line yourself.
When does the champion tracking play not work?
It fails when the relationship was thin, when the new role has no budget or scope, when the new company is a bad fit for your category, or when you find the move months late. In all four cases the warmth that makes the play work is not there, so treat the account as normal pipeline instead.
How is the play different for a new executive versus a moved champion?
The cadence is the same, the opener is not. For a moved champion you open on the shared history, the result you drove together before, because the relationship is what makes it warm. For a new executive you have no relationship, so you open on their mandate, the thing they were hired to fix, and the gap you can help close inside their first ninety days. Warm leans on the past, cold leans on the future.
How do you know if the champion tracking play is working?
Judge it on reply quality and meetings booked, not on volume. This is a low-volume, high-context play, so a handful of warm conversations beats a hundred ignored emails. Track how many flagged moves turn into a real conversation, and how many of those become pipeline. If the replies are warm and specific rather than polite brush-offs, the play is working, even at small numbers.

Keep going

The signal and the scoring behind it

Want this play run for you, not just read about?

Book a fit check. We'll look at who already knows you, set the tracking up, and run the window for you, so the warm moves turn into booked meetings.

Book a Fit Check

No hard sell. No fake numbers. Real good work speaks for itself.