Pipeline value snapshot
Shows the value of your open pipeline today by summing your deal events, broken out by stage.
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
Value open pipeline by stage
Coming soonBlu builds a step
About this recipe
When to use it
A big pipeline number can hide dangerous concentration in one or two deals. This decomposes current pipeline by stage, weights it into a real forecast, and flags concentration risk so a healthy-looking total doesn't hide a fragile one.
What it delivers
Snapshots current open pipeline value decomposed by stage, with a stage-weighted forecast and a concentration-risk flag when too much value sits in too few deals.
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 the value of your open pipeline today by summing your deal events, broken out by stage.”
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.
- 01Value open pipeline by stageCreate an Insights report called "Pipeline Value Snapshot". Series A: Event "Deal stage changed", scope: most-recent state per deal_id where new_stage is in open stages (not in closed_won, closed_lost, or equivalent terminal stages), aggregation: Sum of "amount", unit: $, label: "Open Pipeline Value" Series B: Same as A but with each deal's amount weighted by historical close-rate of its current stage (compute the historical win-rate per stage from trailing-180d closed deals, then multiply each open deal's amount by its current stage's win-rate), label: "Weighted Forecast" Series C: Computed: Series A grouped by new_stage / Series A total × 100, unit: %, label: "Pipeline Concentration by Stage" Time range: Current snapshot Compare: Previous snapshot 30 days ago (point-in-time pipeline shift) Breakdown for the chart view: By new_stage (current stage of each open deal) Chart type: Horizontal bar chart per stage with Series A as the bar value, Series B as a secondary mark/line, and the previous-snapshot value as a dotted overlay Annotations: - Add the pipeline-value-to-quota ratio if the workspace has a quota target configured (otherwise skip). - Flag if >40% of pipeline value is concentrated in late stages (proposal/negotiation): execution risk if any major deal slips. - Flag if >40% of pipeline value is concentrated in early stages (qualification/discovery): pipeline thin on near-term close-able deals. - Highlight the largest single deal in the pipeline (by Deal created.amount): single-deal concentration risk. - Add a 30-day delta callout: "Pipeline grew/shrank by $X (Y%) vs. 30 days ago. Net change driven primarily by [stage_X movement / new deals / closed deals]." Use case: the headline pipeline metric every sales VP and CRO looks at first thing each morning. Distinct from deal-velocity-by-stage (which is about how fast deals move): this is about how much money is currently in motion and where it sits. Taxonomy notes: - Deal stage changed carries amount, new_stage, previous_stage, deal_id, currency. - "Open" vs "Closed" stage classification depends on the project's lead/deal stage configuration. Standard convention: closed stages are those whose name matches /won|lost|closed/i. - Weighted forecast computation requires historical deal data; if trailing-180d closed-deal volume is insufficient (<50 deals), use a fallback weighting (early-stage 10%, mid 30%, late 70%) and flag the imprecision.
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 /pipeline-value-snapshot 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 