Skip to main content
Intempt
Coming soon

SaaS growth command center

Shows whether you are growing and whether growth is healthy on one dashboard: weekly actives, MRR, trial conversion, activation, retention and feature adoption.

Authored by Sid Chaudhary

Founder & CEO at Intempt

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

    Coming soon

    Blu builds a step

About this recipe

When to use it

WAU, MRR, trial conversion, retention, activation, and feature adoption each tell part of the growth story, and checking them separately misses how they interact. This puts them all on one founder-level canvas.

What it delivers

Combines WAU, MRR, trial conversion, retention, activation, and feature adoption into a single founder-level SaaS growth canvas.

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 whether you are growing and whether growth is healthy on one dashboard: weekly actives, MRR, trial conversion, activation, retention and feature adoption.”

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 growth boardCreate a Dash board (12-column composition canvas) titled "SaaS Growth Command Center". Persona: SaaS founder or GM. Question answered: "Are we growing, and is the growth healthy?" Board-level configuration: - defaultDateRange: last_30_days - exclusionPeriod: incomplete_periods - visibility: project - boardFilters: none by default (allow user to add plan_tier filter at runtime) - boardBreakdowns: none Layout: 4 rows × variable cards per row. All cards isLinked: true (live-mirror the source recipe). Widths sum to 12 per row. Row 1: Headline KPIs (heightPx: 200, four metric cards at widthUnits: 3 each): - Card 1: Insights metric card to source recipe: weekly-active-users-trend, displayMode: chart, vizType: metric, titleOverride: "Weekly Active Users" - Card 2: Insights metric card to source recipe: mrr-trend, displayMode: chart, vizType: metric, titleOverride: "MRR" - Card 3: Insights metric card to source recipe: trial-to-paid-conversion-rate, displayMode: chart, vizType: metric, titleOverride: "Trial to Paid" - Card 4: Insights metric card to source recipe: stickiness-ratios-dau-wau-mau, displayMode: chart, vizType: metric, titleOverride: "Stickiness (DAU/MAU)" Row 2: Growth trends (heightPx: 400, two cards at widthUnits: 6 each): - Card 1: Insights trend to source recipe: mrr-trend, displayMode: chart, vizType: stacked_area - Card 2: Funnel to source recipe: signup-activation-funnel, displayMode: chart, vizType: funnel_steps Row 3: Activation depth (heightPx: 400, two cards at widthUnits: 6 each): - Card 1: Insights to source recipe: feature-adoption-by-plan, displayMode: chart, vizType: bar - Card 2: Insights to source recipe: stickiness-ratios-dau-wau-mau, displayMode: chart, vizType: line (full trend, not just metric) Row 4: Retention and behavior (heightPx: 440, two cards at widthUnits: 6 each): - Card 1: Retention to source recipe: user-retention-weekly, displayMode: table (cohort grid) - Card 2: Path to source recipe: first-session-paths-after-signup, displayMode: chart, vizType: sankey-style path Annotations: - The four KPIs in Row 1 should be reviewed alongside the stickiness ratio (Row 1 Card 4): high WAU/MRR with falling stickiness is a leading indicator of churn. - All cards respect the board-level date range; users can override per-card if needed. Taxonomy notes: - All 7 source recipes are taxonomy-grounded against Intempt V2.1. - Cards reference recipe slugs by id; when isLinked: true the card is a live mirror of the source recipe's configuration. - KPI cards use the metric vizType applied to the source chart-recipe: Lovable renders the recipe's headline metric as a single number.

    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 /saas-growth-command-center 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

    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

    More recipes by Sid Chaudhary

    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 Return rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    Got a play worth sharing?

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

    Submit a recipe