Ecommerce revenue overview
Answers how much you are making, which channels drive it, and whether the trend is holding.
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 revenue board
Coming soonBlu builds a step
About this recipe
When to use it
Revenue, AOV, channel, and category performance are usually spread across separate reports that never quite line up. This puts the founder-level revenue overview in one place.
What it delivers
Surfaces top-line revenue, AOV, channel performance, conversion, and category performance for the Founder / CMO revenue overview.
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 how much you are making, which channels drive it, and whether the trend is holding.”
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 revenue boardCreate a Dash board (12-column composition canvas) titled "E-commerce Revenue". Persona: Founder or CMO. Question answered: "How much money are we making, where is it coming from, and is the trend healthy?" Board-level configuration: - defaultDateRange: last_30_days - exclusionPeriod: incomplete_periods - visibility: project - boardFilters: none by default - boardBreakdowns: device_type: pushed down to applicable cards Layout: 4 rows. Row 1: Revenue KPIs (heightPx: 200, four metric cards at widthUnits: 3): - Card 1: Insights metric to source recipe: revenue-by-channel, vizType: metric, titleOverride: "Total Revenue (30d)" - Card 2: Insights metric to source recipe: average-order-value-trend, vizType: metric, titleOverride: "AOV" - Card 3: Insights metric to source recipe: cart-abandonment-rate, vizType: metric, titleOverride: "Cart Abandonment Rate" - Card 4: Insights metric to source recipe: product-category-performance, vizType: metric, titleOverride: "Top Category Revenue Share" Row 2: Revenue trends (heightPx: 400, two cards at widthUnits: 6): - Card 1: Insights to source recipe: revenue-by-channel, displayMode: chart, vizType: bar (horizontal, with YoY comparison) - Card 2: Insights to source recipe: average-order-value-trend, displayMode: chart, vizType: line (multi-line: AOV, units/order, price/unit decomposition) Row 3: Conversion behavior (heightPx: 400, two cards at widthUnits: 6): - Card 1: Funnel to source recipe: browse-purchase-funnel, displayMode: chart, vizType: funnel_steps (with device breakdown) - Card 2: Insights to source recipe: cart-abandonment-rate, displayMode: chart, vizType: line (trend with previous-period overlay) Row 4: Category and retention (heightPx: 440, two cards at widthUnits: 6): - Card 1: Insights to source recipe: product-category-performance, displayMode: chart, vizType: treemap - Card 2: Retention to source recipe: purchase-retention, displayMode: chart, vizType: retention_curve Annotations: - This is the canonical CMO/Founder weekly-check dashboard for ecommerce. Row 1 is the headline; Row 2 surfaces channel mix shifts; Row 3 surfaces conversion bottlenecks; Row 4 surfaces inventory/retention strategy. - The AOV decomposition in Row 2 Card 2 (units/order vs price/unit) is the diagnostic: AOV moving via price = merchandising/pricing impact; AOV moving via units = bundling/cross-sell impact. Taxonomy notes: - All source recipes use canonical events: Placed order, Cart created, View page, Checkout created.
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 /ecommerce-revenue-dashboard 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.
