Deal velocity by stage
Shows how long deals sit in each sales stage and which stage is the bottleneck, with won deals set against lost ones.
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
Time deals in each stage
Coming soonBlu builds a step
About this recipe
When to use it
Sales cycle length is a symptom. This shows the disease: median time in every single stage, with the bottleneck stage flagged, and a side-by-side of how fast won deals move versus lost ones.
What it delivers
Measures median time spent in each deal stage, flags the stage with the longest dwell time as the bottleneck, and compares stage velocity between won and lost 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 how long deals sit in each sales stage and which stage is the bottleneck, with won deals set against lost ones.”
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.
- 01Time deals in each stageCreate an Insights report called "Deal Velocity by Stage". Series A: Event "Deal stage changed", aggregation: Average of "time_in_previous_stage": computed by Lovable as the time delta between consecutive Deal stage changed events for the same deal_id (or between Deal created and the first Deal stage changed for the entry-into-first-stage case) Series B: Same as A but using Median instead of Average (less sensitive to outlier slow deals) Series C: 75th-percentile time-in-stage (the "long tail" of slow deals) Breakdown: By "previous_stage" property on Deal stage changed Time range: Last 90 days of stage transitions Compare: Previous period (prior 90 days) Chart type: Horizontal bar chart per stage with median (Series B) as the bar, p75 (Series C) as a whisker, and average (Series A) as a marker Also include a parallel comparison view: - For deals that ultimately reached Deal won (won deals): median time-in-stage per stage - For deals that ultimately reached Deal lost (lost deals): median time-in-stage per stage - The delta surfaces which stages distinguish winners from losers (won deals are typically faster through middle stages; lost deals stall in qualification or proposal) Annotations: - Flag the stage with the longest median time-in-stage (the primary bottleneck). - Flag any stage where median velocity worsened by >30% vs. previous period (deteriorating sales process). - Highlight stages where won-deal velocity is materially faster than lost-deal velocity (>2× faster): these are the stages where decisive movement predicts close. - Surface the total median sales-cycle length (sum of stage medians) and the trend. Use case: knowing which stage is your bottleneck is the foundation of every sales-process improvement. Most CRMs report stage-conversion rate but not stage-velocity; this is the missing half. Taxonomy notes: - Deal stage changed has previous_stage and new_stage relations, plus deal_id. - "Time in stage" is computed by Lovable from successive Deal stage changed events on the same deal_id. - Deal won and Deal lost are canonical terminal states; deal_closed_won and deal_closed_lost may also fire depending on integration.
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 /deal-velocity-by-stage 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 