Skip to main content
Intempt
Coming soon

Follow a champion who moves

Given a known contact job change, routes two task plays: an AE task to protect the old account and an SDR task to pursue the new account.

Authored by Sid Chaudhary

Founder & CEO at Intempt

Agentic workflow

Coming soon

9 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Run both plays on a move

    Coming soon

    Blu builds a step

  2. 2

    Scan champions every Monday

    Coming soon

    Blu builds a step

  3. 3

    Refresh where they work

    Coming soon

    Blu builds a step

  4. 4

    Split by kind of account

    Coming soon

    Blu builds a step

  5. 5

    Find who replaces them

    Coming soon

    Blu builds a step

  6. 6

    Tell the CSM or AE to act

    Coming soon

    Blu builds a step

  7. 7

    Check if we know the new firm

    Coming soon

    Blu builds a step

  8. 8

    Chase them at the new place

    Coming soon

    Blu builds a step

  9. 9

    Publish and track both sides

    Coming soon

    Blu builds a step

About this recipe

When to use it

A decision-maker changing companies is either a risk or an opportunity depending on how fast you move. This detects the change and branches into both plays at once.

What it delivers

Detects when a decision-maker at a customer account changes jobs, then branches into two plays - re-establishing at the old account with a replacement contact and an AE task, or pursuing the person at their new account as a warm-intro opportunity.

How you prompt this

Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.

Tell Blu Agent what you want

“Given a known contact job change, routes two task plays: an AE task to protect the old account and an SDR task to pursue the new account.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.

Outputs

    How the recipe runs

    Blu follows the steps in order and shows you each one before anything goes live.

    1. 01Run both plays on a moveCreate a workflow 'Job-change detection and dual response' triggered when a contact at an existing customer/deal account changes employer (detected via scheduled enrichment refresh OR signal provider webhook). Branches into two parallel plays: protect the old account, pursue the new account.
    2. 02Scan champions every MondayConfigure scheduled trigger: every Monday morning, scan all contacts marked as 'champion' or 'economic buyer' on active deals + customer accounts. The job-change-detection cadence is the key infrastructure for this workflow. Use the result of "Run both plays on a move".
    3. 03Refresh where they workThis step builds a workflow. Configure enrich step that refreshes employment data for tracked contacts. Most providers (Clearbit, Apollo, LinkedIn-feeds) flag when an email-domain to company mapping changes: that's the signal. Output: list of contacts whose company changed since last refresh. Use the result of "Run both plays on a move", "Scan champions every Monday".
    4. 04Split by kind of accountThis step builds a workflow. Branch: was the contact at a CUSTOMER account, OPEN-DEAL account, or PROSPECT account? Each gets different downstream treatment. Customer to champion-departure rescue. Open-deal to urgent multi-threading. Prospect to warm-follow at new company. Use the result of "Run both plays on a move", "Refresh where they work".
    5. 05Find who replaces themThis step builds a workflow. AI research step on the customer/deal branch: scrape the old company's leadership page + LinkedIn-via-public-search to identify likely replacement decision-makers in similar roles. Outputs 2-3 candidate names with titles and inferred contact info. Saves AE the manual hunt. Use the result of "Run both plays on a move", "Split by kind of account".
    6. 06Tell the CSM or AE to actThis step builds a workflow. Create urgent task for the assigned CSM (customer) or AE (open deal): 'Your champion [Name] just left for [New Company]. Replacement candidates identified: [list]. Suggested action: warm intro through [Departed champion] if relationship is good, else cold outreach to replacement.' SLA: contact within 5 business days: champion-gone deals stall fast. Use the result of "Run both plays on a move", "Find who replaces them".
    7. 07Check if we know the new firmThis step builds a workflow. Find-records step on the departed-to-new-company branch: is the new company already in our CRM? If yes (link the contact, surface the relationship to the assigned AE. If no) create new Account + contact record with 'warm signal: ex-customer champion now here' flag. Use the result of "Run both plays on a move", "Split by kind of account".
    8. 08Chase them at the new placeThis step builds a workflow. Create SDR task for the new-company outreach: 'Warm signal: [Champion name] (your ally at [Old company]) just joined [New company]. Suggested outreach: congratulate the move, ask if they could use the same approach at their new role.' Priority: HIGH (warm signals decay; reach out within 30 days of job change). Use the result of "Run both plays on a move", "Check if we know the new firm".
    9. 09Publish and track both sidesThis step builds a workflow. Validate and publish. Monitor: job-change detection volume per quarter, old-account-save rate (champion-departure deals that DIDN'T stall), new-account-conversion rate (departed-champion pursuits that became meetings). These are some of the highest-quality signals in B2B. Use the result of "Run both plays on a move", "Tell the CSM or AE to act", "Chase them at the new place".

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /job-change-detection-workflow in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Sid Chaudhary

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Return rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe