Your Salesforce org is a record of relationships you already earned. Every champion you sold, onboarded, and won over is sitting in there as a contact. The problem is that 2 to 3% of them change jobs every month, and the day one of them leaves, their record starts to rot. The email bounces, the title is stale, and the best relationship your team ever built is now behind an account you do not sell into yet.
Most teams find out too late, if at all. Only about 6% of customers tell a vendor they changed jobs; the other 94% just move on. If your go-to-market runs on Salesforce, the fix is to stop waiting for people to volunteer the news and instead wire a job change alert into the org itself, so every move lands as a warm lead the same day it happens.
Here is how to build that alert in Salesforce, what it should do at each step, and where the build-versus-buy line actually falls.
Why the job change is the signal worth wiring in first
Before you build anything, it helps to know why this signal earns the effort over everything else you could automate in Salesforce. A job change is not a cold prospect showing faint interest. It is someone who already bought from you, now landing somewhere new with budget and a mandate to show early wins.
The outcome gap is large:
- Champion-sourced deals close with a 2.7x higher probability, in roughly half the sales cycle.
- You have a 60 to 70% chance of selling to an existing relationship, versus 5 to 20% for a cold prospect.
- 65% of a company’s business comes from existing customers and their networks, and it is 6x more costly to acquire a new customer than to keep an existing relationship.
That is why the job change belongs at the top of your buying signal stack, not buried in a data-hygiene backlog. The relationship already exists. You just have to be told when it moves.
What you are actually building
A working job change alert in Salesforce has four moving parts. Miss one and the signal either never fires or fires into a void.
- A detection source that watches your contacts and flags when one changes companies.
- Custom fields on the Contact record to hold the new company, new title, detected date, and a source stamp.
- A record-triggered Flow that reacts the moment a move is detected: update the record, create the task, and route it to an owner.
- A report and dashboard that treat these moves as their own pipeline source so you can prove the channel is working.
The Flow is the easy part. Salesforce is built for exactly this kind of automation. The hard part is the detection source, and that is where most home-built alerts quietly fail. We will come back to that.
Step 1: Add the custom fields
In Setup, on the Contact object, create a small set of fields the alert will write to. At minimum:
- Job Change Detected (Date) so the Flow has something clean to trigger on.
- New Company and New Title (Text) to capture where they landed.
- Previous Company (Text) so customer success can see which account just lost its internal sponsor.
- Signal Source (Picklist) with a value like “Champion move” so every alert is attributable in reports.
Keeping these as first-class fields, rather than dropping the move into an activity note, is what makes the rest of the build possible. Flows can trigger on them, list views can filter on them, and reports can group by them.
Step 2: Build the record-triggered Flow
Create a record-triggered Flow on the Contact object, set to run when a record is created or updated and Job Change Detected is changed. Then chain the actions you want to happen every time a champion moves:
- Update the contact record. Copy the new company and title into your working fields, or keep them separate to preserve history. Reset the contact status back to a sales-ready state so it re-enters your funnel instead of sitting as a closed relationship.
- Create a Task for the owner. Assign it to the account owner or CS manager who held the original relationship, with a due date of today. This is the action that actually reaches the champion inside their first 90 days, while they are choosing tools, rather than after the seat is filled.
- Notify the team. Send an email alert or post to a Slack channel so the move is visible in real time, not just in a report someone opens on Monday.
- Flag the account they left. Every arrival is also a departure. Route the previous account to customer success as a renewal-risk signal the same day, because it just lost its champion.
That last step is the one most teams forget. A single move is two plays: a new-pipeline play on the destination and a renewal-defense play on the account left behind. If you track buying committees, updating the Opportunity Contact Roles on open deals at the old account keeps your forecast honest too.
Step 3: Report on it as its own channel
Because you stamped Signal Source on every alert, you can build a Salesforce report that filters to “Champion move” and watch the channel compound. This matters more than it looks. Warm pipeline sourced from job changes behaves differently from cold outbound, and once you can see it on its own dashboard, it becomes something RevOps can forecast rather than a lucky accident.
To size the opportunity before you turn anything on: take an org with 10,000 contacts. When you first switch detection on, roughly 20% surface as warm leads immediately, about 2,000 conversations available on day one. After that, expect 200 to 300 new warm leads every month as people keep moving. That is a self-refilling source of pipeline you already paid to acquire once.
The hard part: where the detection actually comes from
Everything above is standard Salesforce configuration. The piece that makes or breaks the alert is step one, the detection source that populates the Job Change Detected field in the first place. This is where build-versus-buy gets real, and the hard problems are rarely the Flow:
- Match rate. Correctly re-identifying a contact who changed their email, company, and sometimes their name is where most home-built pipelines leak. A miss means the move never reaches your Flow.
- Freshness and intent. Detecting the move fast, ideally catching intent-to-move signals before the change is public, so the task lands while the champion is still setting up their new stack.
- Write-back you do not have to babysit. Pushing the move into Salesforce cleanly, on every event, without creating duplicate contacts or overwriting good data.
You can wire a raw people-data source into Salesforce yourself and maintain the matching and enrichment on your own. Or you can point a managed feed at your org and let it keep the field populated. Champions runs that whole loop for you across Salesforce, HubSpot, Pipedrive, Zoho and others, with no app to install and no logins for reps. If you want to see how the detection and write-back fit together end to end, our how-it-works walkthrough lays out the flow.
Coverage is worth weighing here, even for a Salesforce shop. Many job change tools are Salesforce-first, which sounds ideal until your team adds a second system and the signal stops following your contacts. A feed that writes to Salesforce today and to HubSpot or Pipedrive tomorrow keeps working as your stack changes.
Why the managed path is easy to justify
Because the leads convert, Champions backs the signal with a contractual ROI guarantee: if champion-sourced revenue does not reach 2x your annual service fee, you are covered under our terms. Among the tools that track job changes, only Champions offers that. What you build and maintain in-house, you insure yourself.
Where to start
If you want to see the moves already hiding in your Salesforce org before you build anything, the fastest path is to run detection against your own contacts first. Book a demo and we will show you the champions who have already moved, live, then walk through how the feed and the Flow fit your org. Prefer email? Reach us at [email protected] and we will get you the details.
Your best future customers already know you. A job change alert in Salesforce is how your team finds out the day they move, while the relationship still counts.
