Skip to main content
Intempt
Coming soon

GTM health and revenue leakage

Answers where the go-to-market machine leaks over a trailing 90 days, by source and cohort rather than by rep, so you can move spend and fix process.

Authored by Intempt Technologies

Recipe curators

Agentic workflow

Coming soon

1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Build the RevOps board

    Coming soon

    Blu builds a step

About this recipe

When to use it

Trailing GTM health, funnel attribution, win-loss patterns, and NRR trends are usually pulled together manually before a leadership review. This builds the strategic RevOps / CRO view natively.

What it delivers

Tracks trailing GTM health, funnel attribution by source, win-loss patterns, and NRR trends for the RevOps / CRO strategic 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 where the go-to-market machine leaks over a trailing 90 days, by source and cohort rather than by rep, so you can move spend and fix process.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. 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.

    1. 01Build the RevOps boardCreate a Dash board (12-column composition canvas) titled "Revenue Operations". Persona: RevOps lead or CRO. Question answered: "Is the GTM machine healthy? Where's the leakage and where do we re-allocate?": strategic horizon (trailing 90 days + cohort views), aggregate granularity (segment/source/cohort, not per-rep), drives spend re-allocation and process changes. This dashboard is intentionally distinct from the Sales Pipeline Dashboard. RevOps is strategic and trend-oriented (is the funnel getting healthier?); Sales Pipeline is operational (which deals to work now). Zero card overlap between the two. Board-level configuration: - defaultDateRange: last_90_days - exclusionPeriod: incomplete_periods - visibility: project - boardFilters: none by default - boardBreakdowns: UTM source (lead source): pushed down so cards decompose by acquisition channel where applicable Layout: 4 rows. Row 1: Strategic KPIs (heightPx: 200, four metric cards at widthUnits: 3): - Card 1: Insights metric to source recipe: win-rate-trend, vizType: metric, titleOverride: "Trailing-90d Win Rate" - Card 2: Insights metric to source recipe: deal-velocity-by-stage, vizType: metric, titleOverride: "Median Sales Cycle (Closed Deals)" - Card 3: Funnel metric to source recipe: lead-to-mql-to-sql-funnel, vizType: metric, titleOverride: "MQL to Closed-Won Rate" - Card 4: Retention metric to source recipe: net-revenue-retention-by-cohort, vizType: metric, titleOverride: "Trailing 12-Month Blended NRR" Row 2: Funnel health (heightPx: 440, two cards at widthUnits: 6): - Card 1: Funnel to source recipe: lead-to-mql-to-sql-funnel, displayMode: chart, vizType: funnel_steps (the full qualification funnel) - Card 2: Funnel to source recipe: funnel-dropoff-attribution-by-source, displayMode: chart, vizType: funnel_steps (small-multiples by source) Row 3: Win-loss intelligence (heightPx: 400, full-width single card at widthUnits: 12): - Card 1: Insights to source recipe: win-loss-analysis, displayMode: chart, vizType: bar (won vs. lost by source, with stage-at-loss decomposition view) Row 4: Trend and revenue retention (heightPx: 440, two cards at widthUnits: 6): - Card 1: Insights to source recipe: win-rate-trend, displayMode: chart, vizType: line (trailing win-rate trend with rolling-90d smoothing) - Card 2: Retention to source recipe: net-revenue-retention-by-cohort, displayMode: chart (multi-line cohort NRR curves) Annotations: - This board is meant for monthly QBR review, not daily/weekly. The right cadence is reading it once per month, looking for inflection points. - Row 1 KPIs are 4 leading indicators: declining win rate, lengthening sales cycle, falling MQL to Won, or NRR dipping below 100% are all early-warning signs that warrant strategic intervention. - Row 3 (full-width win-loss) is the strategic centerpiece: the breakdown by source shows where to invest more vs. less; the breakdown by stage-at-loss shows whether losses come from qualification (top-funnel ICP issue) or closing (late-funnel competition/pricing issue). Taxonomy notes: - All source recipes use canonical events: Deal won, Deal lost, Deal stage changed, Lead stage changed, User created, Subscription started, Subscription updated, Subscription canceled. - net-revenue-retention-by-cohort depends on Subscription updated.changed_fields parsing for expansion/contraction split. - win-rate-trend (new in v5) is the single-metric tracking version of win-loss-analysis.

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /revenue-operations-dashboard in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Intempt TechnologiesDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Intempt TechnologiesPost 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 Intempt TechnologiesReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Intempt Technologies

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post 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 Product swap in a sceneReplaces the product in a shot you already have with a different one, keeping the scene, lighting and shadow the same.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe