Skip to main content
Intempt
Coming soon

Champion change detection

Flags when a deal contact goes quiet using engagement recency, and triggers a rep re-engagement workflow before the deal stalls.

Authored by Sid Chaudhary

Founder & CEO at Intempt

Agentic workflow

Coming soon

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

  1. 1

    Track the champion daily

    Coming soon

    Blu builds a step

  2. 2

    Find deals that lost theirs

    Coming soon

    Blu builds a step

  3. 3

    Get the rep moving

    Coming soon

    Blu builds a step

  4. 4

    See the ARR behind the risk

    Coming soon

    Blu builds a step

About this recipe

When to use it

A deal's biggest early-warning sign is often invisible until it's too late: the champion changed role or stopped responding. This watches for exactly that and triggers re-engagement before the deal silently dies.

What it delivers

Detects when a deal's identified champion changes role, departs the company, or stops responding, and triggers a stakeholder re-engagement workflow before the signal turns into a stalled deal.

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

“Flags when a deal contact goes quiet using engagement recency, and triggers a rep re-engagement workflow before the deal stalls.”

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. 01Track the champion dailyCreate an AI-derived attribute 'champion_status' on the Deal object. Compute the deal's current champion status: ACTIVE (responding to outreach in last 21 days), QUIET (no response 21-45 days), GONE (bounced email OR explicit departure signal OR LinkedIn enrichment shows new company OR new title at same company), or UNCLEAR (deal has no identified champion: separate flag). Refreshed daily. The GONE detection combines: hard email bounces, opened-but-no-reply patterns, enrichment data refresh, and account-domain consistency checks.
    2. 02Find deals that lost theirsBuild a segment 'Champion-change deals' capturing open deals where champion_status transitioned to GONE in the last 7 days. Also includes deals where status is QUIET for 45+ days (effectively gone). Excludes deals already in closed-lost (handled separately). Use the result of "Track the champion daily".
    3. 03Get the rep movingCreate a workflow firing when champion_status transitions to GONE. Step sequence: (1) identify replacement-champion candidates from the account (similar role, peer, manager up: pulled from enrichment); (2) create an urgent task for the AE: 'Champion gone: re-engage stakeholders' with the candidate list and prior deal context; (3) post critical-tier Slack alert to the AE and their manager (this is a deal-saving moment); (4) flag the deal in CRM with champion-risk tag so forecast calls reflect reality; (5) IF account has any other active contact (engagement signal in last 30 days), prioritize that contact as warm-handoff. Don't auto-send email: rep must reach out personally. Use the result of "Track the champion daily", "Find deals that lost theirs".
    4. 04See the ARR behind the riskCompose a champion risk dashboard: count of open deals by champion_status, total ARR with GONE champions (the at-risk forecast), champion-departure rate trend, re-engagement success rate (deals that recovered after champion-change vs. died), and time-to-rep-action on champion-gone alerts. Surface deals where champion has been GONE 14+ days with no rep action (escalation pile). Use the result of "Track the champion daily", "Find deals that lost theirs", "Get the rep moving".

    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 /champion-change-detection 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