Skip to main content
Intempt
Coming soon

Subscription revenue health

Review subscription revenue compounding or erosion using the subscription page's fixed NRR curve and MRR movement waterfall.

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 subscription board

    Coming soon

    Blu builds a step

About this recipe

When to use it

MRR movement, churn cohorts, and payment recovery are usually assembled by hand before a board meeting. This builds the monthly board-review view natively.

What it delivers

Tracks MRR movement, churn cohorts, payment recovery, and NRR for the monthly board-review subscription metrics 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

“Review subscription revenue compounding or erosion using the subscription page's fixed NRR curve and MRR movement waterfall.”

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 subscription boardCreate a Dash board (12-column composition canvas) titled "Subscription Health". Persona: Finance Lead, RevOps Lead, or CRO running monthly subscription-business review. Question answered: "Is the subscription engine compounding or eroding? Where is the leakage?" Distinct from SaaS Growth Command Center (founder daily/weekly view, mixed engagement + revenue) and Customer Success Dashboard (account-level operational save plays). Subscription Health is monthly board-review cadence, focused exclusively on subscription/revenue mechanics. Board-level configuration: - defaultDateRange: last_90_days - exclusionPeriod: incomplete_periods - visibility: project - boardFilters: none by default - boardBreakdowns: Plan (pushed down where applicable) Layout: 4 rows. Row 1: Subscription health KPIs (heightPx: 200, four metric cards at widthUnits: 3): - Card 1: Insights metric to source recipe: mrr-trend, vizType: metric, titleOverride: "MRR (Current)" - Card 2: Insights metric to source recipe: mrr-movement-decomposition, vizType: metric, titleOverride: "Net New MRR (Last Month)" - Card 3: Retention metric to source recipe: net-revenue-retention-by-cohort, vizType: metric, titleOverride: "Trailing-12mo NRR" - Card 4: Insights metric to source recipe: monthly-logo-retention-trend, vizType: metric, titleOverride: "Logo Retention (Annualized)" Row 2: MRR movement waterfall (heightPx: 480, full-width single card at widthUnits: 12): - Card 1: Insights to source recipe: mrr-movement-decomposition, displayMode: chart, vizType: stacked_column (the canonical MRR waterfall: New, Expansion, Reactivation, Contraction, Churn, Net New per month). The strategic centerpiece of this dashboard. Row 3: Retention dynamics (heightPx: 440, two cards at widthUnits: 6): - Card 1: Retention to source recipe: net-revenue-retention-by-cohort, displayMode: chart, vizType: line (cohort NRR curves: answers "are recent cohorts compounding revenue or eroding?") - Card 2: Retention to source recipe: paid-user-retention, displayMode: table (cohort retention grid for logo retention vs revenue retention side-by-side) Row 4: Revenue leakage and recovery (heightPx: 440, two cards at widthUnits: 6): - Card 1: Funnel to source recipe: payment-failure-recovery-funnel, displayMode: chart, vizType: funnel_steps (dunning recovery: surfaces revenue at risk and the recovery rate) - Card 2: Insights to source recipe: expansion-revenue-trend, displayMode: chart, vizType: stacked_bar (upgrade vs. seat-expansion mix: quality of expansion revenue) Annotations: - This dashboard is meant for monthly review (e.g., the day before board meeting), not daily/weekly. The right cadence is reading it once per month and looking for inflection points. - Row 1 KPIs are the four numbers a CFO reports to the board. NRR ≥ 100% indicates the installed base is growing despite churn; NRR ≥ 110% is top-quartile; <90% indicates revenue erosion. - Row 2 (MRR movement waterfall, full-width) is the single most important view in subscription analytics. Reading it: green stacks (New + Expansion + Reactivation) should consistently outweigh red stacks (Contraction + Churn). Months where it doesn't are the moments to investigate. - Row 4 surfaces the operational levers: dunning recovery rate of 70% is healthy; expansion revenue ≥30% of new MRR is healthy; both can be operationally improved without changing the product. Taxonomy notes: - mrr-movement-decomposition and net-revenue-retention-by-cohort both depend on Subscription updated.changed_fields parsing for expansion/contraction split: see those recipes' notes. - All other source recipes use canonical events: Subscription started, Subscription canceled, Subscription updated, subscription_resumed, Invoice paid, Invoice payment failed, Revenue completed. - monthly-logo-retention-trend annualizes the monthly retention rate; surface the annual implication directly (e.g., "95% monthly = 54% annual retention").

    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 /subscription-health-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