Weekly business review
One scorecard with the six numbers to look at every Monday: new signups, new paying customers, churn, revenue, net new customers and engagement.
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
Build the Monday scorecard
Coming soonBlu builds a step
About this recipe
When to use it
Most teams rebuild their Monday exec summary by hand from six different reports every week. This composes the 6 numbers every founder actually asks for - new customers, churn, revenue, MRR/ARR, retention, top engagement - into one dashboard.
What it delivers
Composes a single dashboard covering the 6 KPIs a weekly business review typically needs: new customers, churn, revenue, MRR/ARR, retention, and top engagement.
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
“One scorecard with the six numbers to look at every Monday: new signups, new paying customers, churn, revenue, net new customers and engagement.”
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.
- 01Build the Monday scorecardCreate an Insights report called "Weekly Business Review Summary". This recipe is a multi-series KPI dashboard combining the headline numbers a founder or exec wants to see every Monday morning. Render as a multi-metric scorecard. Series A: Event "User created", aggregation: Count Unique Users, weekly, label: "New Signups" Series B: Event "Subscription started" where trial_end is null (paid signup) OR for ecommerce mode "Placed order" where this is the user's first order, aggregation: Count Unique Users, weekly, label: "New Paying Customers" Series C: Event "Subscription canceled" (saas) OR users whose Users.Last seen exceeds 90 days (ecommerce churn proxy), weekly, label: "Churned Customers" Series D: Event "Revenue completed" with type indicating recurring revenue (saas) OR Sum of Placed order.total_price (ecommerce), aggregation: Sum of amount or total_price, weekly, label: "Revenue" Series E: Computed: Net New Customers = Series B − Series C, label: "Net New Customers" Series F: Trailing 7-day DAU (count of unique users with Session start), label: "Engagement" Time granularity: Weekly Time range: Last 12 weeks Compare: Previous period (prior 12 weeks) AND year-over-year Chart type: Multi-card scorecard layout: each metric gets a card showing: current week value, week-over-week % change, year-over-year % change, 12-week trend sparkline Annotations on each card: - Highlight the current-week value vs. trailing 4-week average (trend indicator: accelerating / steady / decelerating). - Flag any metric that moved >15% week-over-week in either direction (exec-attention threshold). - Flag any metric trending wrong-direction for 4+ consecutive weeks (durable trend, not noise). - Add a quality-of-growth indicator: Net New Customers (E) growing while Churned Customers (C) is also growing = treadmill (high churn offset by acquisition); Net New growing while Churned is flat or shrinking = compounding growth (best-in-class). Use case: the WBR-fill report. Founders, execs, and operators run a weekly cadence on the same 5-6 numbers. This recipe makes that cadence one-click: automatically populated, automatically annotated, ready to present. Replaces the spreadsheet most teams maintain manually for this purpose. Taxonomy notes: - This recipe operates as an aggregator over multiple canonical events. For mode=saas, prioritize subscription/revenue events. For mode=ecommerce, prioritize order events. For mode=all, render both side-by-side. - The "churn" definition for ecommerce uses Users.Last seen as a proxy because there's no explicit churn event in DTC ecommerce: adjust the threshold (60/90/180 days) per business model.
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 /weekly-business-review-summary 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 