Skip to main content
Intempt
Coming soon

Competitor signal response

Uses AI attribute scores from first-party events to spot competitive intent and trigger a personalized email plus a CSM follow-up task.

Authored by Sid Chaudhary

Founder & CEO at Intempt

Agentic workflow

Coming soon

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

  1. 1

    Spot competitor interest

    Coming soon

    Blu builds a step

  2. 2

    Group by what they intend

    Coming soon

    Blu builds a step

  3. 3

    Write a reply per intent

    Coming soon

    Blu builds a step

  4. 4

    Show what they are missing

    Coming soon

    Blu builds a step

  5. 5

    Respond within four hours

    Coming soon

    Blu builds a step

  6. 6

    See which rivals you lose to

    Coming soon

    Blu builds a step

About this recipe

When to use it

Visiting a comparison page or mentioning a competitor in a support chat is a clear signal, and it's gone if nobody acts on it fast. This fires competitive content and an AE/CSM task the moment it happens.

What it delivers

Detects behavioral signals like a visited competitor comparison page, a mentioned competitor in a support conversation, or a clicked competitor-keyword email, and fires personalized competitive content plus an AE/CSM task with intel and differentiators.

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

“Uses AI attribute scores from first-party events to spot competitive intent and trigger a personalized email plus a CSM follow-up task.”

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. 01Spot competitor interestCreate an AI-derived attribute 'recent_competitor_signal' on the User/Account object. Detects: (a) visited /vs/[competitor] comparison pages, (b) clicked competitor-named links in marketing emails, (c) mentioned competitor in support conversations or AI agent chats, (d) downloaded a competitor-comparison resource, (e) appeared on a competitor's review site as a reviewer (if data permits). Output: structured object with competitor_name, signal_type, signal_strength, recency, and inferred_intent (evaluation / dissatisfaction / curious-comparison / leaving). Stays active for 30 days after last competitor signal.
    2. 02Group by what they intendBuild a segment 'Active competitor signal' capturing users/accounts with recent_competitor_signal in the last 14 days where signal_strength is medium or high. Partitioned by inferred_intent so the journey branches accordingly. Excludes brand-new prospects (different motion, for prospects, competitive intel goes into the AE's sales process). This segment is specifically EXISTING CUSTOMERS or LATE-STAGE prospects where competitor signal is a save/competitive-defend moment. Use the result of "Spot competitor interest".
    3. 03Write a reply per intentThis step builds a designed marketing email (HTML). Generate competitive content variants per inferred_intent. Evaluation intent (existing customer comparing (concerning but not yet leaving): 'Helpful comparison: [Product] vs [Competitor] from your team's perspective') honest comparison + specific advantages relevant to their use case. Dissatisfaction intent (existing customer with friction signals + competitor signal (leaving risk): 'Want to talk? [CSM name] would like to understand what's not working') direct outreach offer, no defensive product pitch. Curious-comparison intent (neutral exploration): 'Most teams who compare us to [Competitor] choose [Product] for [specific differentiator]: here's why' + customer case study. Leaving intent (strong signals + cancel-page visit + competitor signal): exec-sponsor outreach offering executive-business-review meeting + retention discussion. Send-from: matched CSM or AE for high-signal cases; marketing@ for low-signal exploration. Use the result of "Spot competitor interest", "Group by what they intend".
    4. 04Show what they are missingConfigure a recommendation surface 'Capabilities you're not using yet' that activates when a user has a competitor signal. Pulls: differentiator features of [Product] that the user/account hasn't tried but their cohort uses for high-value outcomes. The surface answers the implicit question 'why stay?' with concrete unused capability: much more convincing than feature-comparison docs. Renders in-app for 30 days. Use the result of "Spot competitor interest", "Group by what they intend".
    5. 05Respond within four hoursBuild a journey wired to competitor-signal segment, branched by inferred_intent. Touch 1 (within 4 hours of signal: speed matters): intent-matched email. Touch 2 (Day 0 of touch 1): differentiator-recommendation surface activates in-app for 30 days. Touch 3 (Day 2, for high-signal-strength accounts): CSM/AE task with full competitor intel attached (competitor name, signal type, inferred intent, suggested talking points, customer's current usage profile). Touch 4 (Day 7, if account is still showing competitive intent + hasn't engaged with CSM): executive-sponsor outreach offer for high-ARR accounts. Exit on: explicit positive renewal/retention signal (saved), churned (loss: feed into win-loss analysis), or 30-day timeout with no further competitor signal (signal cooled). Use the result of "Spot competitor interest", "Group by what they intend", "Write a reply per intent", "Show what they are missing".
    6. 06See which rivals you lose toCompose a competitive defense dashboard: competitor signal volume per competitor (which competitors are hottest in your current customer base: strategic competitive intel for leadership), per-competitor save rate (which competitors you actually save customers from vs. lose to), inferred-intent distribution (evaluation vs. leaving: leading indicator of churn from competitive pressure), and ARR-weighted at-risk pile from competitor signals. Feeds the product-marketing competitive-positioning function with real data, not assumptions. Use the result of "Spot competitor interest", "Group by what they intend", "Write a reply per intent", "Show what they are missing", "Respond within four hours".

    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 /competitor-mention-detected-response 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.

    More recipes by Sid Chaudhary

    Got a play worth sharing?

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

    Submit a recipe