Win rate trend
Tracks win rate month by month with a 90 day rolling line, so you can see the direction without the noise of a single month.
Authored by Intempt Technologies
Recipe curators
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Track win rate over time
Coming soonBlu builds a step
About this recipe
When to use it
Sometimes you don't need the full win-loss breakdown, just the trend line: is your win rate going up or down. This tracks that single number over time as a lightweight GTM health check.
What it delivers
Tracks win rate as a single trend line over time, giving a lightweight ongoing read on GTM health without the full breakdown overhead of a win-loss analysis.
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
“Tracks win rate month by month with a 90 day rolling line, so you can see the direction without the noise of a single month.”
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.
- 01Track win rate over timeCreate an Insights report called "Win Rate Trend". Series A: Event "Deal won", aggregation: Count Series B: Event "Deal lost", aggregation: Count Series C: Computed: Series A / (Series A + Series B) × 100, unit: %, label: "Win Rate" Series D: Trailing 90-day rolling win rate (smoother for trend reading), label: "Win Rate (90-day rolling)" Time granularity: Monthly (cohort by close month) Time range: Last 18 months (so two trailing-12-month windows can be compared) Breakdown: By Users.UTM source (lead source attribution via the deal's primary_user_id): top 5 sources, optional secondary line per source Compare: Year-over-year (same month previous year, dotted overlay) Chart type: Line chart with Series C (monthly) and Series D (rolling) as primary lines, plus optional per-source overlay lines Annotations: - Add benchmark lines: median B2B SaaS win rate is 18: 22% (Gartner); top-quartile is 30%+; below 15% indicates either lead-quality or ICP issues. - Flag any month where Series C dropped >5 percentage points vs. the trailing-3-month average (acute decline: investigate that month's sales activity, comp changes, market events). - Flag if Series D (90-day rolling) has been declining for 3+ consecutive periods (durable downward trend, not noise). - Surface the trailing-12-month win rate vs. the prior 12 months as a single before/after callout: the headline number for board reporting. - Highlight any source whose per-source win rate diverges materially (>10pts) from the blended average: outlier channels deserve investigation. Use case: the win-rate trend that goes on the RevOps dashboard's headline KPI strip. Distinct from win-loss-analysis (which is a bar chart with breakdowns by source/reason); this is the single metric over time. Taxonomy notes: - Deal won and Deal lost are canonical events. Both carry amount, primary_user_id, owner_id, close_date, currency. - For workspaces using deal_closed_won / deal_closed_lost (alternative integration naming), substitute those. - Source attribution requires resolving primary_user_id to Users.UTM source.
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 /win-rate-trend 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.
