Skip to main content
Intempt
Coming soon

Single threaded deal alert

Finds late stage deals where only one person on the buyer's side is engaged and gives the rep three other names to bring in.

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

    Count who is actually engaged

    Coming soon

    Blu builds a step

  2. 2

    Find the risky ones

    Coming soon

    Blu builds a step

  3. 3

    Give the rep three names

    Coming soon

    Blu builds a step

  4. 4

    See what threading is worth

    Coming soon

    Blu builds a step

About this recipe

When to use it

Deals with only one engaged contact lose three times more often, usually because nobody notices until the champion disappears. This surfaces the risk with a recommended contact list attached.

What it delivers

Detects deals where only one contact from the buyer side is engaged, and surfaces them with a multi-threading task plus a recommended list of additional contacts to bring in.

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

“Finds late stage deals where only one person on the buyer's side is engaged and gives the rep three other names to bring in.”

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. 01Count who is actually engagedCreate an AI-derived attribute 'threading_depth' on the Deal object. Count distinct buyer-side contacts who have (a) attended a meeting on this deal, OR (b) replied to an email on this deal, OR (c) been explicitly added as a deal contact. Output: integer count. Flag as 'single-threaded' if count = 1 and deal is in Demo / Proposal / Closing stage (early-stage single-threading is normal; late-stage is a red flag).
    2. 02Find the risky onesBuild a segment 'Single-threaded deals - mid+ stage' capturing open deals where threading_depth = 1 AND stage is Demo, Proposal, or Closing. Excludes deals < 14 days old (haven't had time for multi-threading naturally) and deals flagged as exec-buyer (1-person decision is genuine in some buyer profiles, e.g. founder-led SMB). Use the result of "Count who is actually engaged".
    3. 03Give the rep three namesCreate a workflow firing daily for deals newly-flagged as single-threaded. Step sequence: (1) recompute threading_depth (fresh); (2) for genuine single-threaded mid-stage deals, fetch suggested additional contacts from account enrichment (peer roles, manager up, related team members), prioritized by likely-buying-influence; (3) create a task for the rep labeled 'Multi-thread this deal: 3 suggested contacts' with the contact list pre-attached; (4) Slack DM to the rep with deal context. If lone champion is the decision-maker (CEO of a small co, etc.), suppress: that's not single-threading risk. Use the result of "Count who is actually engaged", "Find the risky ones".
    4. 04See what threading is worthCompose a threading health dashboard: % of mid+stage deals that are multi-threaded (target: 70%+; below 50% is a coaching gap), distribution of threading depth by stage, single-threaded-deal win rate vs. multi-threaded win rate (the proof-of-value chart), rep leaderboard on threading depth, and aged single-threaded deals (>30 days single-threaded = high-loss-risk pile). Use the result of "Count who is actually engaged", "Find the risky ones", "Give the rep three names".

    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 /single-threaded-deal-alert 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