Outreach Job Change Alerts: How to Trigger a Warm Sequence the Day a Champion Moves

Short answer: Outreach does not detect job changes on its own. To get an Outreach job change alert you need three pieces: an outside signal that catches the move, a prospect custom field that records it, and a Trigger under Workflow automations that enrolls the prospect into a dedicated sequence the moment that field changes. Outreach runs the outreach. Something else has to notice the move.

That gap is worth closing, because 2 to 3% of your B2B contacts change jobs every month and only about 6% of customers tell a vendor they moved. The other 94% just stop replying. If your reps live in Outreach, the fix is to make a job change behave like any other field change in your stack: it lands, a Trigger fires, and a warm sequence starts the same day.

What Outreach detects natively, and what it does not

Outreach does ship a signals layer. Smart Data Enrichment Signals pulls 20 signals sourced from ZoomInfo Copilot, configured under Administration, Data Enrichment, Enrichment Settings, then the Signals tab. The list covers things like anomalous hiring, layoffs, mergers and acquisitions, intent spikes, G2 visits, new product launches, senior job postings and CXO change (Outreach support documentation).

Read that list carefully and you will notice what is missing. Every one of those signals is about a company. The closest thing to a people signal is CXO change, which tells you a C-level seat turned over somewhere in the market. None of them watch the specific humans in your database and tell you when one of them moves.

That is a different job. It is not market intelligence, it is relationship monitoring, and it is the reason teams end up buying the signal rather than finding it in a settings tab. Outreach’s own go-to-market team is a published example: UserGems’ customer story describes Outreach using an external champion tracking signal to flag when their key contacts moved, after previously relying on account executives to watch for those moves by hand (UserGems).

Why this is the signal worth wiring in first

Before you build anything, it helps to know why a job change earns the Trigger over the dozen other events you could sequence on. A job change is not a faint intent spike on a cold account. It is someone who already bought from you, now sitting in a new seat with new budget and a mandate to show early wins.

The outcome gap is not small:

• Champion-sourced deals close at a 2.7x higher probability, in roughly half the sales cycle.
• You have a 60 to 70% chance of selling to an existing relationship, against 5 to 20% for a cold prospect.
• 65% of a company’s business comes from existing customers, and acquiring a new one costs 6x more than keeping one.

That is why a contact move belongs at the top of your buying signal stack rather than in a data-hygiene backlog. The relationship is already paid for. Outreach only has to be told it moved.

The four pieces of a working Outreach job change alert

1. A watched population. Not your whole database. Closed-won champions, economic buyers, power users on active deals, and evaluators from losses you want to re-open.
2. A detection layer. Something outside Outreach that notices the company and title change within a day, without a human refreshing LinkedIn.
3. A write path into Outreach. The move has to land on a prospect record as structured data, including the new company, the new title, a verified new email, and a date.
4. A Trigger that acts. Outreach’s own automation picks it up from there and enrolls the prospect into a job-change sequence.

Pieces one through three are where teams stall. Piece four is the part Outreach does genuinely well, so the design goal is to feed it a clean, timely signal and let it run.

Step 1: Define the watched population

Start deliberately narrow. Pull the people whose move changes a number this quarter:

• Champions and economic buyers on closed-won accounts.
• Named contacts on open opportunities. When one of them leaves mid-cycle that is a risk alert, not just an expansion opening.
• Evaluators from lost deals. A champion who liked you at Acme and now owns buying at NewCo is the warmest re-open your team will ever get.

A watched list of a few thousand real relationships produces a handful of high-quality moves a week. That is exactly the volume a sequence can absorb without reps learning to ignore it.

Step 2: Detect the move outside Outreach

This is the step no Outreach configuration solves, and the reason most teams never finish the build. Manually monitoring a few thousand people for a company change is not a job anyone holds for a full quarter.

A detection layer does three things: it watches the people you already know, it catches the company and title change within about a day of it going public, and it resolves a verified work email at the new employer so the first touch lands in an inbox instead of bouncing off the dead address still sitting in your CRM. That is what Champions is built to do, and the how it works walkthrough covers the monitoring end to end.

Verification matters more here than people expect. A job-change sequence that fires at a bounced address is worse than no sequence, because you burn sender reputation on your warmest list.

Step 3: Write the move onto the prospect record

Outreach Triggers fire off record events and field changes, so the signal has to arrive as a field, not as an email to a manager. Create prospect custom fields for the move and populate them when detection fires:

• Job Change Detected (date)
• Previous Company and Previous Title
• Champion Status, so the sequence can tell a champion from a casual contact

You have two clean ways to get the data in.

Through the CRM. If Salesforce or HubSpot is your system of record, write the move there and let the existing field mapping carry it into the matching Outreach custom field. This is the lowest-maintenance path for most teams, and it keeps one definition of the signal. The same pattern is covered in detail in the Salesforce job change alert and HubSpot job change alert guides.

Through the Outreach API. If you want the signal to reach reps without waiting on a CRM sync, patch the prospect directly. Outreach’s API v2 also supports outbound webhooks, so you can subscribe to the prospect resource with the updated action by posting to https://api.outreach.io/api/v2/webhooks and keep your own systems in step with whatever Outreach changes (Outreach developer docs). If you would rather consume the move as an event than poll for it, the general pattern is in our guide to job change webhooks.

Do the enrichment before the write, not after. A record that arrives complete lets a rep act on the first touch instead of pausing to hunt for an address.

Step 4: Build the Trigger

Now hand it to Outreach. Triggers live under Administration, Workflow automations, Triggers, and they support field-change conditions, including on custom fields, with actions that cover Add to Sequence, Create Task, Add or Remove Tags, Update Field, and round-robin Assign to Team (Outreach support documentation).

A working configuration looks like this:

• Event object: Prospect, on Updated.
• Condition: Job Change Detected changed, and Champion Status equals champion or buyer. The second condition is what keeps the sequence high signal.
• Actions, in order: add a job-change tag so the cohort is reportable later, assign the prospect to the right owner if the old owner no longer covers the new account, then Add to Sequence using the prospect owner’s default mailbox so the email comes from a human the contact recognizes.

Tag first, enroll last. If enrollment happens before assignment you can send a warm, personal note from the wrong rep, which wastes the one thing that makes this signal work.

Step 5: Write a sequence that does not read like outbound

The sequence is where most teams undo their own work by pointing the Trigger at an existing cold cadence. This person knows you. Write accordingly, and keep it short:

• Day one, email. Name the move, congratulate them, and pitch nothing. You are re-opening a relationship, not introducing yourself.
• Day two or three, email or LinkedIn. Connect their new mandate to one concrete outcome you drove for them at the last company. Specific beats flattering.
• Later that week, call or soft ask. Suggest a short reconnect, sized to how warm the relationship actually was.

Then stop. A job-change sequence that runs nine touches tells the contact this was automated, which destroys the only advantage the signal gave you. If you want templates for the first two emails, see job change outreach email templates.

Step 6: Make the cohort measurable

Tag the enrollment and the reporting takes care of itself. Because every prospect in this motion carries the job-change tag and a detection date, you can report on meetings booked, opportunities created and closed-won revenue for the cohort, and compare it against the same numbers for cold sequences. That comparison is what gets the program funded for a second year. The RevOps use cases page covers how teams structure that reporting.

Build versus buy: where the line actually falls

You can fake parts of this. A rep can watch a saved LinkedIn search. An ops lead can export contacts quarterly and eyeball the diff. Both break at any real scale: manual checks miss most moves, catch the rest weeks late, and produce unverified emails that quietly damage deliverability.

The build-versus-buy line is not the Trigger. Triggers are an afternoon of configuration and Outreach runs them well. The line is detection and email verification, maintained continuously across thousands of relationships. That is a data problem, not a workflow problem, and it does not survive a busy quarter as someone’s side project.

Worth noting on the buying side: Champions puts the outcome in the contract. If champion-sourced revenue does not reach 2x the annual service fee, you are covered under our terms. Among the job change tools teams usually compare, that guarantee is specific to us.

The bottom line

Outreach is the right place to act on a job change and the wrong place to find one. Its native signals watch companies, not the people in your database. So define a watched population, detect moves within a day with verified emails attached, write the move onto a prospect custom field, and let a Trigger enroll a short, human sequence from the right owner. Do that and every champion who moves becomes a conversation the same week, instead of a bounced email you discover three months late.

Ready to wire the signal into Outreach? Book a demo and we will map it to your watched list and your field schema. If you would rather just ask a question first, email [email protected].