Three months ago I audited the job-change alert workflow at a 12-person SaaS team. They were using UserGems to track when past users and buyers changed companies. Alerts were firing daily. Their champion-alert-to-reply rate: 3.1%.
That's not a tool problem. That's a workflow problem.
The gap isn't in detection — it's in the 22 minutes between "alert fires" and "first message sent." Every article I've read on job change signals spends 2,000 words comparing UserGems to Champify to Apollo and zero words on what you actually do after the Slack ping lands.
This is that article.
Why 89% of champion alerts go nowhere
When a champion leaves your best account and lands at a Series B company that fits your ICP perfectly, you have a window. That window isn't 30 days. It's closer to 48 hours.
Here's what I observed across the team's alert history: alerts that triggered a same-day reply attempt converted at 18%. Alerts that triggered outreach 24–48 hours later converted at 9%. Alerts actioned after 72 hours: 4%. Longer than a week: indistinguishable from cold outreach.
The decay happens for a concrete reason. In their first 48 hours at a new company, a new VP or Director is context-building — talking to the team, auditing the stack, making a mental list of "gaps I need to fill." After 72 hours, they've moved into execution mode. The mental slot for "tools to evaluate" is filling up with internal priorities. You're no longer a timely coincidence — you're noise.
Champify publishes that they refresh contacts every 14 days. LinkedIn Sales Navigator job alerts can lag 3–7 days behind the actual LinkedIn update. If your alert pipeline has that much latency baked in, the 48-hour window is already closed before you open Slack.
This is why detection speed matters — but it's the second-order problem. The first-order problem is: once you have a real-time alert, what do you do in the next hour?
The enrichment step nobody talks about
The alert tells you Jane Doe, former Director of Marketing at Acme Corp (closed-won, $45K ARR, power user), just became VP Marketing at Northstar AI.
What it doesn't tell you: her new work email.
This is where most teams stall. They get the alert, open LinkedIn, confirm the job change, then open a sequence... and have no deliverable email. So the alert sits. A day passes. The window closes.
Here's the enrichment workflow I now run for every champion alert, in order:
- Pull the new company domain from the alert (or from LinkedIn Sales Navigator if checking manually).
- Run an email pattern guess — most companies use firstname@domain.com or firstname.lastname@domain.com. Hunter.io will show you the domain's email pattern in seconds.
- Verify the address — Hunter.io has a verifier built in; pipe it to ZeroBounce for a second pass on anything critical.
- If Hunter draws a blank, run the new LinkedIn URL through Clay's enrichment waterfall. Clay will hit People Data Labs, RocketReach, and Lusha sequentially and return a verified email in ~45 seconds.
- Log everything back to CRM before writing a single word of outreach.
Total time if you've pre-built the Clay workflow: about four minutes per alert. Without it: 15–20 minutes of manual tab-hopping, which is why most reps skip the enrichment step entirely and use a stale email from 18 months ago.
Apollo has its own enrichment layer if you're on a paid plan, but coverage on newly-changed roles is spotty — it takes 2–3 weeks for Apollo's index to catch up to the actual LinkedIn update, which makes it unreliable for the 48-hour window specifically.
Writing a message that doesn't sound like a template
This is where every other guide collapses into generic advice, so I'll be specific.
Champion re-engagement copy has three jobs: prove you know who they are, acknowledge their new context, make the ask minimal.
Subject line: Reference their old company, not their new one. "How [OldCompany] used [Product] for X" lands better than "Congrats on the new role!" because everyone sends congratulations and nobody reads them.
Opening line: One sentence, past tense, specific. "When you were at Acme, your team built [specific workflow] using [feature]" beats any opener that starts with "I noticed you recently joined..."
Bridge to new context: Ask one question about their new situation. "Wondering if [problem you solved] is on your radar at Northstar." Not a pitch — a question.
CTA: One sentence. Calendar link or a yes/no question. Never "let me know if you'd be open to a call sometime."
Here's a real message I used that got a same-day reply from a champion who'd left a churned account:
Subject: How Acme's growth team ran attribution without a BI hire
Hey Jane — when you were leading growth at Acme, your team put together a pretty clean attribution setup using [feature]. Saw you're at Northstar now — is building out the measurement layer something you're looking at in Q2? Happy to share what worked and what didn't.
38 words in the body. No pitch. Response came in 4 hours.
What you should not do: add them to your standard cold sequence. I've seen a rep get a champion alert, drop the contact into a default Apollo sequence, and fire a "Hi {{firstname}}, I help companies like yours..." email as touch 1. The champion replied: "We worked together for two years." Recoverable, but it costs you.
The cadence that doesn't burn the relationship
Champion re-engagement is not cold outreach. Treat it like a cold sequence and you'll convert the relationship to "annoyed former contact."
My cadence for every champion alert:
- Day 0 (alert fires): Enrichment + first email (above format)
- Day 2: LinkedIn connection request — no note, just connect
- Day 5: Follow-up email with one data point specific to their new company ("Saw Northstar is hiring a RevOps lead — that usually means attribution is being rebuilt")
- Day 10: One phone call attempt, no voicemail
- Day 14: Final email — leave something useful, not a goodbye. "I'll stop reaching out, but if [problem] comes up, here's the one thing I'd recommend..."
Five touches, 14 days. Not 30, not 45. Champions who want to re-engage will do it in the first 14 days. After that, move them to a marketing nurture track and stop touching them manually. The research backs this up: UserGems reports 11–20% reply rates on champion outreach vs. the 1–2% industry average for cold — but only when outreach happens fast. Delaying past day 3 pulls those numbers back toward cold territory.
Tool comparison: enrichment handoff after a job-change alert
| Tool | Email enrichment | Latency on new roles | Best for |
|---|---|---|---|
| Clay | Waterfall (PDL + RocketReach + Lusha) | Near real-time | Automated enrichment at scale |
| Hunter.io | Pattern + verification | Immediate on domain | Quick manual lookups |
| Apollo | Native database | 2–3 week lag on new roles | Existing accounts, not fresh job changes |
| Lusha | Direct lookup | Fast if indexed | Individual lookups, Chrome extension |
| RocketReach | Direct lookup | Moderate | Bulk enrichment fallback |
| People Data Labs | API | Real-time for indexed profiles | Developers building enrichment pipelines |
| LinkedIn Sales Navigator | No email (policy) | Real-time alerts | Signal detection only |
| UserGems | Built-in, auto-enriches | Fast | Full champion tracking + enrichment |
| Champify | Limited | 14-day refresh cadence | Alert detection, manual enrichment needed |
The short version: for the enrichment step specifically, Clay is the most reliable automated option. Hunter.io is the fastest for one-off lookups. UserGems is the only tool that handles detection, enrichment, and sequence enrollment in one motion — which matters if you're running more than a handful of alerts per week.
What I actually use
For detection, I run UserGems across closed-won and churned accounts. The auto-enrichment on job changes saves the manual four-minute loop for most alerts. Champify is a cheaper alternative if you're willing to handle enrichment yourself and can live with the 14-day refresh window.
For enrichment when UserGems doesn't return a clean email, Clay is my go-to. I built a table that takes a LinkedIn URL plus new company domain, hits three providers in sequence, and returns the best-confidence email in under a minute.
For writing the first message, I still write manually. I've tried Phantombuster for LinkedIn messaging automation but found it too blunt for a relationship-sensitive channel like champion re-engagement.
For finding LinkedIn profile URLs when I only have a name and new company — especially to see what someone has posted in their first week, which gives great opener fodder — Ziwa has been faster for me than People Data Labs's direct API for profile-level lookups. Though for pure email enrichment, Clay's waterfall still wins.
The single metric I'd tell any SDR to track: time from alert to first message sent. Get that under 90 minutes and your champion conversion rate will look nothing like the 3–5% averages most teams live with. Get it under 30 minutes and you're playing a different game than everyone else working from the same LinkedIn Sales Navigator feed.
Top comments (0)