Multi threading coverage
Shows distinct stakeholders engaged per open deal from deal and contact data.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Count contacts on each deal
Coming soonBlu builds a step
About this recipe
When to use it
A deal with one engaged stakeholder is fragile - if that person leaves or goes quiet, the deal dies with them. Gartner's own research ties single-threaded deals to materially lower close rates. This counts real distinct stakeholders per deal so the fragile ones surface before they stall.
What it delivers
Counts the number of distinct stakeholders engaged per deal, flagging single-threaded deals that carry materially higher risk per established sales research.
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
“Shows distinct stakeholders engaged per open deal from deal and contact data.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- 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.
- 01Count contacts on each dealCreate an Insights report called "Multi-Threading Coverage by Deal". Series A: Event "Deal stage changed", scope: per active deal_id, aggregation: Count Unique users from the user_ids property (the distinct stakeholders attached to the deal across all stage events) Series B: Same per-deal computation but counting only Meeting scheduled events linked to the deal (via deal_ids relation): distinct users who actually attended a meeting Series C: Computed: Series A bucketed into "Single-threaded (1 contact)" / "Lightly threaded (2-3)" / "Multi-threaded (4-6)" / "Deeply threaded (7+)" Breakdown: By deal stage (open deals only, group by current stage from Deal stage changed.new_stage) Time range: All open deals + last 90 days of closed deals Chart type: Stacked bar chart: bar per stage, segments showing the threading-bucket distribution Also include a parallel "win-rate by threading level" view: - For closed deals (Deal won + Deal lost) in the last 12 months, compute win rate by threading bucket - Surface: single-threaded deals win X%, multi-threaded deals win Y%, with the gap quantified Annotations: - Flag any open deals (especially in late-stage proposal/negotiation) that are still single-threaded: these are at acute risk and need multi-threading action by the AE. - Add the Gartner benchmark: B2B deals with 5+ engaged stakeholders close at 1.8× the rate of single-threaded deals. - Highlight the share of pipeline value (sum of deal amount) currently sitting in single-threaded deals: this is the dollar amount at risk. - Flag any deals where threading shrank vs. prior period (a stakeholder went silent: investigate champion-departure risk). Use case: the standard B2B sales hygiene report. AEs are notoriously single-threaded; this report makes the risk visible and quantifies it in dollars. Top-performing sales orgs make this their #1 weekly review. Taxonomy notes: - Deal stage changed.user_ids is a relation (multi-value) carrying associated users. - Meeting scheduled.user_ids and Meeting scheduled.deal_ids together let us count meeting-attended stakeholders per deal. - Deal "current threading count" is computed across all events linked to the deal_id (Deal stage changed, Meeting scheduled, Call completed, Email sent).
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /multi-threading-coverage-by-deal in Blu once this recipe is live there.
- 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 