Plan tier mix shift
Shows how revenue is spread across plans over time and whether revenue mix is drifting up market or down market.
Authored by Intempt Technologies
Recipe curators
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Compare revenue and customer mix
Coming soonBlu builds a step
About this recipe
When to use it
A shift in your customer base's plan mix happens gradually and is easy to miss month to month. This tracks % of revenue and % of customers per plan over time, so up-market or down-market drift becomes obvious.
What it delivers
Tracks the percentage of revenue and percentage of customers attributable to each plan tier over time, surfacing directional drift toward higher or lower tiers.
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 how revenue is spread across plans over time and whether revenue mix is drifting up market or down market.”
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.
- 01Compare revenue and customer mixCreate an Insights report called "Plan-Tier Mix Shift". Series A: Event "Revenue completed" filtered to recurring revenue type (or Invoice paid as fallback), aggregation: Sum of "amount", unit: $ Series B: Count of users with an active subscription at month-end (active = has Subscription started with status in active states, no subsequent Subscription canceled or subscription_expired before the month-end) Series C: Computed: Series A by plan / total Series A × 100, unit: %, label: "% of Revenue by Plan" Series D: Computed: Series B by plan / total Series B × 100, unit: %, label: "% of Customers by Plan" Time granularity: Monthly Breakdown: By Plan (resolved from each user's most-recent active Subscription started.Plan) Time range: Last 12 months Compare: Year-over-year Chart type: Two stacked area charts side-by-side: Series C (revenue mix) and Series D (customer mix) Annotations: - For each plan, label start-of-period and end-of-period share with the change in percentage points. - Flag any plan whose share of revenue shifted by >5 percentage points YoY. - Highlight any divergence between revenue mix and customer mix (e.g., higher tier growing as % of revenue but flat as % of customers = ARPA going up = pricing/positioning working). - Flag the opposite divergence (customer mix shifting up-market but revenue mix flat = discounting eroding the up-market thesis). This is one of the most consequential questions for SaaS pricing/positioning teams. Taxonomy notes: - Plan is on Subscription started. Active subscription status is determined by absence of a later Subscription canceled / subscription_expired for the same subscription_id.
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 /plan-tier-mix-shift 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.
