Salesloft is where your reps actually live. Cadences, calls, and emails all run through it, so it is the natural place to act on a buying signal the moment it appears. The problem is that the single highest-intent signal in your funnel never originates inside Salesloft. It happens out in the world, when a champion you already sold to changes jobs, and by default nobody in your Rhythm ever hears about it.
That gap matters because 2 to 3% of your contacts change jobs every month, and only about 6% of customers tell a vendor they moved. The other 94% just disappear from your reach. If your go-to-market runs on Salesloft, the fix is to pipe a job change alert into the platform itself, so every move lands as a warm cadence the same day it happens instead of a bounced email three months later.
Here is how to build that alert, what it should do at each stage, and where the build-versus-buy line actually falls.
Why the job change is the signal worth wiring in first
Before you automate anything in Salesloft, it helps to know why this signal earns the effort over the dozen other things you could trigger a cadence on. A job change is not a cold account showing a faint intent spike. It is someone who already bought from you, now landing somewhere new with fresh 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 one.
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. Salesloft just has to be told the moment it moves.
What you are actually building
A working job change alert for Salesloft has four moving parts. Miss one and the signal either never fires or fires into a void where no rep ever sees it.
- A watched list of people who matter. Not every contact. Your closed-won champions, active-deal power users, and past evaluators are the population worth monitoring. Everyone else is noise.
- A detection layer that catches the move. Something has to notice the title and company change, ideally within a day, without a human checking LinkedIn.
- A hand-off into Salesloft. The detected move needs to become a person record with the new company, new title, and a tag or field that says why they are here.
- An enrollment rule that puts a rep on it. The person should auto-enroll into a dedicated job-change cadence, not sit in a report nobody opens.
The first three are where teams usually stall. The fourth is where Salesloft is genuinely excellent, so the goal is to let Salesloft do the part it is best at and feed it a clean, timely signal from outside.
Step 1: Define the population you watch
Start narrow. Pull the people whose move would actually change a number this quarter:
- Champions and economic buyers on closed-won accounts.
- Named contacts on open opportunities who then leave mid-cycle, because that departure is a churn risk you want to catch, not just an expansion opening.
- Evaluators from deals you lost, since a champion who liked you at company A and now runs buying at company B is the warmest re-open you will ever get.
Keep this list small enough that every alert is worth a rep’s time. A watched list of a few thousand high-value relationships produces a handful of high-quality moves per week, which is exactly the volume a cadence can absorb.
Step 2: Detect the move without a human checking LinkedIn
This is the step Salesloft cannot do on its own, and the reason most teams never build the alert. Manually watching a few thousand people for a title change is not a job anyone can hold. You need a detection layer that monitors your watched list and flags a move within a day of it going public.
That is precisely what Champions is built to do. It tracks the people you already know across the web, catches the company-and-title change, and enriches the new record with a verified work email so the hand-off into Salesloft lands on a deliverable address rather than the dead one still sitting in your CRM. If you want the mechanics of how that monitoring works end to end, the how it works walkthrough covers it.
Step 3: Hand the move off to Salesloft cleanly
Once a move is detected, it has to become a Salesloft person with three things attached:
- The new company and new title, so the rep opens the record already knowing where the champion landed.
- A verified new email, because a job-change cadence that fires at the old bounced address is worse than no cadence at all.
- A tag or custom field such as
job-changeand the detection date, so you can build the enrollment rule and later measure what the signal produced.
Do the enrichment before the person hits Salesloft, not after. A clean record in means a rep can act on the first touch instead of pausing to hunt for the right address. Feeding stale or unverified data into a cadence is the fastest way to torch both deliverability and rep trust in the signal.
Step 4: Auto-enroll into a job-change cadence
Now let Salesloft do what it is best at. Build one cadence dedicated to job changes and set an automation rule that enrolls any person tagged job-change the day the tag lands. The cadence should read nothing like your cold outbound:
- Touch one, same day. A short, human note that names the move and congratulates them, with zero pitch. You are re-opening a relationship, not cold-emailing a stranger.
- Touch two, day two or three. Connect the dots to their new role and one concrete outcome you drove for them at the last company.
- Touch three, later that week. A soft call to action such as a quick reconnect, sized to how warm the relationship actually was.
Because the person already knows you, this cadence consistently outperforms cold outreach on reply and meeting rates. The whole point of wiring the alert into Salesloft is that the rep never has to notice the move, look up the new email, or decide what to send. It is already queued.
Build versus buy: where the line falls
You can approximate parts of this by hand. A rep can watch a saved LinkedIn search, or you can export a contact list monthly and eyeball it for changes. Both fall apart at any real scale: manual checks miss most moves, catch the rest weeks late, and produce unverified emails that quietly kill your sender reputation.
The build-versus-buy line falls on detection and enrichment, not on the cadence. Salesloft already runs the outreach beautifully. What it needs is a reliable, same-day feed of verified job-change records, and maintaining that feed by hand across thousands of relationships is not a project that survives a busy quarter. Buying the detection layer and letting Salesloft own the enrollment is the split that actually holds up.
If you want the signal to be trustworthy end to end, the new addresses that flow into your cadence also have to be real. Pairing job-change detection with an email verification pass before enrollment keeps the warmest cadence you run out of the spam folder.
The bottom line
A job change is the highest-intent signal your team will ever get, and Salesloft is the right place to act on it, but only if something outside Salesloft catches the move first. Watch the relationships that matter, detect the move within a day, enrich the record with a verified email, and auto-enroll into a dedicated cadence. Do that and every champion who moves becomes a warm conversation the same day, instead of a bounced email you find months too late.
When you are ready to wire the signal into your Rhythm, book a demo and we will map it to your watched list.
