7 steps · 14 min read

Former champion job-change outreach playbook

A seven-step workflow for reconnecting after a former champion changes jobs without assuming prior trust, product fit, permission, or success transfers.

Who this is for: B2B founders and lean GTM teams deciding whether a verified former champion move supports a genuine check-in, an account-owner handoff, research, or no outreach.

A former champion’s job change is a relationship event, not transferred buyer intent. Verify the move, reconstruct the prior relationship, test the new account and current job independently, then ask one low-pressure question only when current facts make it useful. Old familiarity does not prove new fit, authority, budget, access, or permission.

This workflow owns the relationship-specific route after the broader job-change verification guide has identified a possible move. For a newly appointed sales leader with no meaningful prior relationship, use the new VP Sales outreach workflow instead.

Step 1. Verify the person, move, and current role

Reopen the underlying source before using the old relationship. Record the person, previous company, new company, exact role, move type, public wording, role start date, announcement date, alert date, and source owner. A job-change notification is discovery evidence, not complete employment verification.

Observed source	What it can support	What remains unknown	First route
Member profile or role announcement	The member’s stated employer, title, start context, and public description	Complete scope, current systems, priorities, authority, and purchase plans	Preserve the source and compare it with company evidence
New employer announcement	A named appointment, effective date, reporting context, and stated mandate	Execution order, operating owner, inherited stack, and vendor evaluation	Translate only stated work into a provisional current job
Job-change or enrichment alert	A provider detected a possible record change	Correct identity, freshness, employer, title, start date, and whether the move is real	Research; do not write from the alert summary
Former colleague or account-owner update	A relationship owner may know that the person moved and how they worked together	Current role, new-account fit, contact preference, and whether the person wants an introduction	Verify the move and keep the relationship owner involved
Conflicting or stale records	Only that one or more systems disagree	Current company, role, start state, source ownership, and contact route	Resolve the conflict or close the route

Step 2. Reconstruct the prior relationship without inflating “champion”

Do not give every historic contact the same champion label. Preserve what the person actually did, who owned the relationship, what product context they had, how recently it was true, and which consent, complaint, bounce, or suppression state applies.

Prior state	What is known	What must not transfer automatically	Relationship route
Buyer, admin, or accountable owner	A documented role in selecting, implementing, governing, or renewing the product	Authority, budget, ownership, product access, or need at the new company	Use the named relationship owner and prior facts only
Active and successful user	A documented workflow, feature, outcome, support history, or product preference	That the same workflow exists or that the person can introduce a vendor	Ask how the new environment differs before mentioning reuse
Executive sponsor or internal advocate	The person previously supported a business case or helped an account navigate a decision	Current sponsorship, political capital, influence, or willingness to advocate again	Continue the human relationship without assigning a new role
Open or closed-lost prospect	A prior evaluation, objection, timing issue, or incomplete conversation	Customer status, product advocacy, permission, or satisfaction	Call it a former conversation, not a champion relationship
End user with no direct relationship	Product-use evidence may exist at the former account	Personal familiarity, contact preference, decision authority, or permission to reach out	Research or use an account-owner introduction when invited
Opt-out, complaint, bounce, or suppression	A stop already exists	Nothing; a new employer does not erase the person-level stop	Preserve the stop across alerts, enrichment, and channels

Keep the previous account’s confidential details out of the new message. Use only the minimum prior context that the person already knows and that your team is permitted to use. Do not expose private usage, commercial terms, support history, internal stakeholder notes, or the former employer’s operating data to create familiarity.

Step 3. Qualify the new account and current job independently

A strong past relationship does not repair poor fit. Re-run the account, role, geography, market, team shape, exclusions, current work, and operating-owner checks as if the new employer had never appeared in your CRM.

Current evidence	Useful interpretation	Do not infer	Next check
The new account fits the ICP	The company could plausibly benefit from the category	That the former champion owns, wants, or can buy it	Map the person’s current job and the actual operator
The role has a stated relevant mandate	One current business job may deserve research	That the old product is missing, approved, remembered, or preferred	Look for visible execution and relationship-safe context
The account previously evaluated your product	An account history may need an owner-led handoff	That the mover knows about the evaluation or should be enrolled automatically	Route through the current opportunity or account owner
The person asks about an old workflow or product	First-person interest can support a useful reply	Budget, authority, procurement, or a wider buying project	Answer the question, then learn who owns the current job
No current job or execution evidence	The relationship may support a genuine personal check-in	A pipeline opportunity, urgent timing, or permission for a sales sequence	Congratulate without a pitch, or wait

Use the free Buyer Intent Signal Prioritizer to compare current fit, evidence, freshness, ownership, and next action. Keep prior familiarity in the relationship field; do not use it to inflate account fit or current intent.

Step 4. Choose the relationship, permission, and owner route

The person-level relationship, the old account relationship, and the new account relationship are three separate states. Resolve all three before opening a channel. The cleanest route may be a personal check-in, an existing account-owner handoff, an invited introduction, research, or no action.

Relationship state	Primary owner	Eligible first action	Stop or correction
Direct, recent, positive personal relationship	The person who actually knows the mover	A genuine check-in that does not presume a sales project	Do not transfer the contact into an automated sequence
Relationship belongs to a CSM, AE, founder, or support owner	The documented relationship owner	Owner-led note or an introduction only when appropriate	Do not let an SDR impersonate the relationship
New employer is an active customer or opportunity	The current account or opportunity owner	Update the stakeholder map and ask whether contact is useful	Do not create a parallel champion campaign
Former user, no direct contact history	No assumed owner	Research or seek a real introduction when invited	Product usage alone is not a personal relationship
Former prospect, closed-lost contact, or stale conversation	The prior conversation owner, if still relevant	Recheck the old reason, current fit, and contact preference	Do not rewrite a loss as advocacy
Opt-out, complaint, bounce, suppression, or poor fit	The governance or suppression record	None	Stop across new-employer lists and every channel

If your lawful basis, contract, platform rule, contact preference, or internal ownership is uncertain, pause the outreach route. A known name and a new title do not supply permission.

Step 5. Set timing from relationship and evidence state

Current search results recommend both immediate contact and waiting a fixed number of weeks. Neither rule captures the important differences. Use the verified move, role start, relationship owner, new-account fit, current job, first-person interest, and stop state instead of one calendar.

Current state	Timing decision	Reason
Move is only an alert or future start	Verify and wait	The person, role, and start state are unresolved
Close relationship, move confirmed, no current sales job	Personal congratulations can stand alone	A relationship does not need a commercial payload
New account fits, but role and ownership are unclear	Research or watch	Fit does not establish a relevant recipient or message
Current job and owner are visible	Review one relationship-aware question	Current evidence now changes what useful contact can do
The person requests information or an introduction	Reply on the agreed path	First-person context outranks a preset schedule
Contradiction, poor fit, opt-out, complaint, or suppression	Close and preserve the stop	The newer state overrides the job-change alert

Do not use a gift, congratulations note, or fast follow-up to hide weak relevance. If the only reason to contact the person is that automation found the move, the route is not ready.

Step 6. Write one check-in that leaves the old relationship intact

The first message should sound like the real relationship. Name the move only when verified, use the minimum appropriate prior context, ask how the new environment differs, and let the person decide whether the old product or an introduction belongs in the conversation.

Message part	Useful job	Avoid
Relationship opener	Reflect how you genuinely worked together	“Former champion detected” or surveillance language
Current context	Name a verified role or public current job	Assuming the old problem, stack, or budget followed them
Difference question	Ask what changed in the new environment	“Do you miss our product?” as a loaded premise
Small offer	Share a checklist, migration note, or example when useful	A demo, gift, intro request, or referral ask by default
Exit	Make no-project, wrong-owner, or not-now easy to say	A preset multichannel follow-up sequence

A relationship-aware note might say: “Congrats on the move to Northstar. We worked together on keeping account reasons reviewable at Acme, but I do not want to assume the same job exists in the new role. If outbound review is part of what you are building, I can send the one-page reason record we refined since then. If not, no sales follow-up from me—I would still love to hear how the first weeks are going.”

Step 7. Let the reply and current account state control follow-up

Recheck the move, relationship, new-account fit, current job, owner, channel, and suppression before every next action. The person’s reply and the current account state override the old relationship and any job-change cadence.

Friendly personal reply, no business context: keep the conversation personal. Do not turn warmth into a sales sequence.
Current job confirmed: answer the question or send the requested artifact before asking for more time.
Wrong owner: close the person route. Contact another owner only with an invited introduction or independent public reason.
Old product is irrelevant or not wanted: accept the correction and close the commercial path.
New account is already a customer or opportunity:hand the context to the current owner and avoid parallel contact.
Agreed revisit: preserve the date, current job, requested resource, owner, and next step in the person’s words.
No response: do not repeat the congratulations, send a gift, open another channel, or ask colleagues for introductions. Close or wait for genuinely new evidence.
Opt-out, complaint, bounce, contradiction, poor fit, or suppression: stop and preserve the state across future job-change alerts and imports.

Use the free Campaign Follow-up Planner to turn the latest reply and still-valid reason into a continue, hold, reroute, or stop decision.

Three former champion job-change routes

Known user, fitted account, no current job

A product user you knew well joins an ICP account. The move is verified, but no relevant workflow or responsibility is visible. Send a genuine personal congratulations if the relationship supports it. Do not ask for a demo, referral, or introduction.

Prior buyer, current job, owner-led check-in

A former buyer joins a fitted account and publicly describes work that overlaps a workflow you handled together. The original account owner still has a positive relationship and no stop state exists. Let that owner ask how the new environment differs and offer one useful artifact.

Former user, poor fit or preserved suppression

A former user joins an account outside the market, takes an unrelated role, or has an opt-out or complaint on record. Preserve the history and close the route. Prior product familiarity does not justify contact.

How Funkel AI fits this workflow

When verified public job-change context and an authorized relationship record enter a reviewed workflow, Funkel AI can keep the source, prior relationship, new-account fit, current job, likely owner, message reason, channel, approval, and stop conditions together. It does not independently verify employment, transfer consent, expose private customer data, declare every former user a champion, prove current product need, infer budget or authority, or make every job change buyer intent. See how Funkel AI keeps evidence and human review attached to outreach.