Expansion revenue trend
Shows month over month MRR change per subscription from Subscription updated change events, comparing each subscription's amount before and after the update.
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
Split upgrades from seat growth
Coming soonBlu builds a step
About this recipe
When to use it
Total MRR growth mixes new business with expansion into one number. This isolates expansion revenue specifically, derived from real subscription change events, so you can see whether growth is durable expansion or one-time new-logo sugar.
What it delivers
Derives expansion revenue directly from subscription_updated change events and tracks it as its own trend line, separate from new-business MRR, surfacing the real quality of MRR growth.
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 month over month MRR change per subscription from Subscription updated change events, comparing each subscription's amount before and after the update.”
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.
- 01Split upgrades from seat growthCreate an Insights report called "Expansion Revenue Trend". Series A: Event "Subscription updated" where changed_fields indicates a plan upgrade (parsed from the changed_fields text property: e.g. contains "plan_id" or "plan_items" with a higher-priced target), aggregation: Sum of the resulting subscription amount delta Computation: for each Subscription updated event, compare new amount vs. prior amount on the same subscription_id. Positive delta with plan change = upgrade. Sum positive deltas, unit: $, label: "Upgrade Revenue". Series B: Event "Subscription updated" where changed_fields indicates seat/quantity increase (e.g. plan_items quantity went up), aggregation: Sum of positive amount delta, unit: $, label: "Seat / Quantity Expansion Revenue" Series C: Computed: (A + B) / new_mrr_in_period × 100, unit: %, label: "Expansion as % of New MRR" where new_mrr = sum of Subscription started.amount in the period Time granularity: Monthly Breakdown: By Plan: show which starting plan tiers produce the most expansion Time range: Last 12 months Compare: Year-over-year Chart type: Stacked bar for A and B with Series C as a line on a secondary axis Annotations: - Add benchmarks: expansion as % of new MRR ≥ 30% is healthy; ≥ 50% is best-in-class. - Flag any month where total expansion revenue declined MoM by more than 15% (expansion engine stalling). - Highlight whether upgrade-driven expansion or seat-driven expansion dominates, and whether the mix is shifting. Taxonomy notes: - The canonical taxonomy has Subscription updated with a changed_fields text property and a plan_items property (flattenable to price_id, quantity, product). It does NOT have separate subscription_upgraded / subscription_downgraded events. - Computing upgrade vs downgrade requires comparing new vs prior subscription state: operationally this means: when Subscription updated fires, look up the prior Subscription started.amount and compute the delta. Positive delta = expansion, negative = contraction. - "subscription_payment" is not a canonical event. Use Revenue completed or Invoice paid for actual revenue capture.
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 /expansion-revenue-trend 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 