Deals to work this week
Answers which open deals need attention now using weighted forecast and risk or engagement scores on active pipeline.
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
Build the pipeline board
Coming soonBlu builds a step
About this recipe
When to use it
Open pipeline reviews often miss multi-threading risk and engagement drop-off until a deal has already stalled. This surfaces both directly, alongside deal velocity. See AI sales machine reviews for how this compares to dedicated sales tech.
What it delivers
Tracks open pipeline, deal velocity, multi-threading risk, and account engagement on active deals for the AE / Sales Manager operational view.
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
“Answers which open deals need attention now using weighted forecast and risk or engagement scores on active pipeline.”
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.
- 01Build the pipeline boardCreate a Dash board (12-column composition canvas) titled "Sales Pipeline". Persona: Account Executive or Sales Manager. Question answered: "What deals do I work this week?": current-state operational view, this-quarter horizon, per-deal/per-rep granularity. This dashboard is intentionally distinct from the Revenue Operations Dashboard. Sales Pipeline is operational (deals to work now); Revenue Operations is strategic (GTM trends and health). Board-level configuration: - defaultDateRange: last_30_days (rolling, since open deals are point-in-time) - exclusionPeriod: none - visibility: project - boardFilters: none by default (each card scopes its own population per recipe definition) - boardBreakdowns: owner_id (rep): pushed down so each card decomposes by rep where applicable Layout: 4 rows. Row 1: Operational KPIs (heightPx: 200, four metric cards at widthUnits: 3): - Card 1: Insights metric to source recipe: pipeline-value-snapshot, vizType: metric, titleOverride: "Open Pipeline Value" - Card 2: Insights metric to source recipe: multi-threading-coverage-by-deal, vizType: metric, titleOverride: "Single-threaded Deals" - Card 3: Insights metric to source recipe: accounts-at-risk-count, vizType: metric, titleOverride: "Accounts at Risk" - Card 4: Insights metric to source recipe: deal-velocity-by-stage, vizType: metric, titleOverride: "Median Sales Cycle (days)" Row 2: Deal health (heightPx: 440, two cards at widthUnits: 6): - Card 1: Insights to source recipe: deal-velocity-by-stage, displayMode: chart, vizType: bar (horizontal bar per stage with median time-in-stage) - Card 2: Insights to source recipe: multi-threading-coverage-by-deal, displayMode: chart, vizType: stacked_bar (threading distribution per stage) Row 3: Account-level intelligence (heightPx: 400, full-width single card at widthUnits: 12): - Card 1: Insights to source recipe: account-engagement-score-trend, displayMode: table (top 30 accounts ranked by current engagement, with trend sparkline; sortable by week-over-week change) Row 4: Behavioral signals (heightPx: 400, two cards at widthUnits: 6): - Card 1: Funnel to source recipe: lead-customer-sales, displayMode: chart, vizType: funnel_steps (high-level pipeline progression) - Card 2: Insights to source recipe: pipeline-value-snapshot, displayMode: chart, vizType: bar (full pipeline-value-by-stage view from the recipe) Annotations: - Row 1's four KPIs are the daily-check numbers: what's in pipeline, what's at risk (single-threaded), what accounts need saving, and how fast we move. - Row 3 (the full-width account table) is the key actionable artifact: sorted by week-over-week engagement change, it surfaces both expansion candidates (rising) and churn-risk accounts (falling). Taxonomy notes: - All source recipes use canonical Intempt events: Deal stage changed, Deal won, Deal lost, Deal created, Meeting scheduled, Session start, Click on, Ticket created. - pipeline-value-snapshot includes weighted-forecast computation (each deal's amount × historical close-rate of its current stage).
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 /sales-pipeline-dashboard 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 