How do I monitor for job changes and champion moves?

Monitor job changes by watching your contacts for role and employer changes, tagging both sides of the event (a champion leaving an account is a risk, a champion landing somewhere new is an opening), and pushing each into a Revenue Play in Salesforce so a rep acts while it matters. A contact moving is one of the strongest, most perishable signals in your CRM, and it is a contact-level event, not an account score.

This is the SignalRx pattern in miniature: it researches and tags the right data on both accounts and contacts, external and internal, and turns those tags into Revenue Plays and lists native in Salesforce for action. Fit scoring is one input; the job here is catching the signal and routing it.

Why do job changes matter on both sides?

A departing champion is a retention risk: the person who believed in you is gone, and their replacement may bring a preferred vendor, even while usage still looks healthy, which is exactly why a usage-only view is blind to it. The same event elsewhere is an opportunity: a champion who valued you and lands at a new company is a warm opening at an account that may not even be on your list yet. One data event, two plays.

How fast do I need to act?

In the first weeks, not at renewal. An arriving champion rebuilds their stack and has the mandate and budget to bring in what worked before during their first ninety days, so reach them in week one, before an incumbent relationship forms. A departing champion should trigger a save the week they leave, before the replacement arrives with a vendor already chosen. An alert that surfaces the move a quarter later is noise; the move routed as a play the week it happens is pipeline, and it is the lowest-cost, fastest-cycle pipeline you will ever source, on both sides.

Where does the signal come from, and where does SignalRx act?

The move is detected first on LinkedIn. A role or employer change on a person's own profile is the primary and most perishable source of a champion move, so SignalRx watches your contacts' LinkedIn profiles for exactly that. It confirms the change against the new employer's website leadership and team pages and against any press or news covering the executive appointment, and it reads your own internal engagement history and email hard bounces to verify the departure from the old account. This is triangulation in practice: many named sources synthesized into one validated event before anything fires. No government registry is involved; a job move shows up on LinkedIn and in company communications long before it ever reaches a filing.

SignalRx tags the contact (departed, new role, new employer) and reflects it on the account (champion gap). Because the tag lives in Salesforce, a Revenue Play can fire: the at-risk account routes to the CSM as a save, and the champion's new company routes to sales as a warm lead, each on a list your team already works.

This signal fires more often in healthcare than in most markets, and it pays off more. Consolidation moves people within your addressable market, so a champion who leaves a physician group for a PE-backed platform or another MSO very often lands at another high-fit account you already wanted to work. Buying committees here span clinical, operations, finance, and IT, so a departing champion takes hard-won knowledge of how the decision gets made, which is what makes them so valuable arriving somewhere new and so damaging leaving.

Illustrative example

Illustrative, based on how SignalRx customers work. A VP Operations who championed your rollout at a 12-location dermatology group leaves. SignalRx picks up the move from a change on her LinkedIn profile, corroborates it against her new employer's team page, and tags the old account with a champion gap, opening a save play for the CSM that week; it also tags the VP's new employer, a physician group not yet a customer, and routes it to sales in the first days with the context that a known champion just arrived and is rebuilding their stack.

What do I do when a champion leaves?

Detection is only half the save. The other half is identifying and engaging the successor fast, before the replacement settles in with preferences of their own. The week the departure fires, name the new decision maker on the account, reach them with a fresh value case rather than a renewal reminder, and re-establish why the product earns its place, because the person who defended you internally is gone and the account can still read healthy on usage while the ground shifts beneath it.

How hard you push depends on why the champion left, and the two flavors call for different responses.

• A routine role change. The champion was promoted, changed teams, or moved on, but the account's ownership did not change. The replacement is a re-engageable blank slate: they inherited the relationship without a preferred alternative, so a strong week-one value case usually wins them, and this is where the save play pays off most.
• An acquisition- or consolidation-driven departure. The champion left because the account was acquired or rolled up, and the new owner frequently arrives with a vendor already chosen. These are often unwinnable no matter how fast you move, so triage accordingly: make the case, but do not spend a full save motion on an account where the decision was made above your contact's head.

Key takeaways

• A job change is a perishable, contact-level signal, not an account score, and usage looks healthy the day a champion leaves.
• The move is detected first on LinkedIn, then confirmed against the new employer's website and press and your own engagement and hard-bounce data.
• One move is two plays: a save at the old account, a warm opening at the new one, both worked in the first weeks.
• In healthcare, people move within your market, so a departure is often an arrival at another high-fit account.
• On a departure, engage the successor in week one, and triage by cause: a routine role change is winnable, an acquisition-driven exit often is not.

See it in action: Increase Customer Revenue with SignalRx.

Related: How do I catch at-risk customers?