champion-tracking
Use case 02 · Expand · Champion Tracking

Your champion moved. Your next deal moved with them.

Someone who already bought from you just landed somewhere that has never heard of you. Rudy catches the move, rebuilds what happened on the last deal, and runs the play before a competitor notices.

Try for free Book a demo
Champion moves this week3 detected
MW
Marcus WebbLinkedInHalcyon to Siemens Healthineers. Ran your rollout.
In ICP
DO
Dana OyelaranLinkedInRecruiterflow to Vanta. Power user, forty tickets, all resolved.
In ICP
TR
Tom ReillyLinkedIn1mind to a forty-person startup. Below your floor for now.
Watching

Your best buyers already bought from you once.

Watch every champion

Not a list somebody maintains. Every contact who ever advocated for you, tracked across your CRM, your calendars and the Slack channels you share with customers.

Know which moves matter

Scored against your ICP and their old deal. A power user landing in your target segment is not the same as a name changing jobs.

Re-engage with the real context

A note that references what they actually cared about last time, not a template with their new company pasted in.

Catch

Three champions moved this week. Two landed inside your ICP.

Rudy watches every past advocate across every account, and tells you the day one turns up somewhere worth selling to.

Champion moves this week3 detected
MW
Marcus WebbLinkedInHalcyon to Siemens Healthineers. Ran your rollout.
In ICP
DO
Dana OyelaranLinkedInRecruiterflow to Vanta. Power user, forty tickets, all resolved.
In ICP
TR
Tom ReillyLinkedIn1mind to a forty-person startup. Below your floor for now.
Watching
Watch

The first sign a champion left is not LinkedIn. It is your Slack channel.

Rudy sits in the channels you already share with customers. A deactivation shows up there the day it happens, weeks before a profile changes. And because he has been in the room the whole time, he knows who that person actually worked with and how the account read when they left. A calendar cannot tell you that.

#Shared customer channelsthis week
Marcus Webb deactivated#halcyon-boomerang. Eleven days before his profile changed.
Departure
+
Anika Roy addedSame channel, same week. Took over his programme.
Arrival
Dana Oyelaran deactivated#recruiterflow-boomerang. No second champion on the account.
Single threaded
WHO HE ACTUALLY WORKED WITHPriya Raman41 of his 63 messages, and every thread he opened.
HOW THE ACCOUNT READPositive, steadyNo drop in the eight weeks before he left.
Rebuild

He remembers the last deal better than the rep who ran it.

What they bought, what they pushed for internally, what the deal turned on. Pulled from your CRM and call history, then written into the ask.

Re-engagement, draftready
TOMarcus Webb, Director of Product Security
SUBJCongrats on the move, Marcus

Saw you landed at Siemens Healthineers. Congratulations.

When we worked together at Halcyon, the thing you cared about was cutting security review from six weeks to two. I suspect that problem followed you.

CONTEXT RUDY PULLED

Halcyon closed Q2 last year. Marcus scored the rollout 9 at close. Two call recordings flag security review time as the blocker he personally owned.

SendEdit
Reconcile

The old record does not get deleted. It gets told the truth.

Old contact flagged as moved and kept for history. New contact created at the new account with the new email and phone. The owner hears about it the same day.

Marcus Webb, recordsynced
Marcus Webb at HalcyonStill attached to the Q2 opportunity, kept for history.No longer here
Marcus Webb at Siemens HealthineersNew work email and mobile, on the right account.Contact created
Priya Raman notifiedIn Slack, the morning the change was detected.Owner pinged
Roll up

Enrichment agents keep the new record worth having.

A new contact with a name and nothing else is not much use. Rudy enriches on creation: seniority, function, location, time in role, and whether they sit inside a buying group you already care about.

Enrichment on the new recordautomatic
what did you fill in on Marcus?
SE
Seniority and functionDirector, Product Security. Mapped to your own picklist values.
Filled
LO
Location and regionMunich. Routed to the EMEA Enterprise owner.
Filled
TR
Time in roleSix weeks. Flagged as still in the window where new tools get bought.
Filled
BG
Buying groupAdded to the Siemens Healthineers committee as Champion.
Linked
SalesforceHubSpotSlack
Proof

Champion tracking across a PLG motion.

"In two weeks, two meetings and a 12 percent reply rate."

Nalin Senthamil · Founder · Storylane

Watch the Storylane story →
12%reply rate on re-engaged champions
2meetings booked inside the first two weeks
0list building or manual tracking
What it reads

Nothing for anyone to maintain.

Read-only on ingest, connected once, then kept current on its own. Writes go back through your own schema, into your own objects and fields.

Salesforce HubSpot Slack Google Calendar Gong Outreach
The other two plays

Same agent. Same graph. Different revenue problem.

01 · Acquire

Path to Power

Reach the person who signs, through someone they trust.

See the play →
03 · Multithread

Buying Group Intelligence

A champion is one voice. The decision needs six.

See the play →

Every champion you ever won is still worth something.

Connect your stack and see the graph you already own. Live in about 30 minutes.

Try for free Book a demo →