Feature adoption by plan
Shows feature adoption across plan tiers using a breakdown of active users.
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
Map feature use to plan tier
Coming soonBlu builds a step
About this recipe
When to use it
Feature usage that's flat across your whole base is a myth - Enterprise and Starter use your product completely differently. This breaks adoption down by plan tier so you can see which features drive which tier's value.
What it delivers
Tracks feature adoption rate by plan tier over time, surfacing which features have strong affinity with which tiers instead of reporting one blended adoption number.
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 feature adoption across plan tiers using a breakdown of active users.”
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.
- 01Map feature use to plan tierCreate an Insights report called "Feature Adoption by Plan". Series A: Event "Click on" filtered by target_id (a stable identifier representing a feature surface: e.g. /feature/<feature-slug>), aggregation: Count Unique Users Series B: Computed: Series A / total active users in the same plan tier × 100, unit: %, label: "Adoption Rate" Breakdown: By target_id (the feature) on the X axis, secondary breakdown by Plan (resolved from the user's most-recent Subscription started.Plan) on the Y axis Time range: Last 30 days Compare: Previous period (prior 30 days) Chart type: Heatmap (target_id / feature on Y axis, plan tier on X axis), cell value = adoption rate %, color intensity scaled Also include a parallel view: per-feature adoption-rate trend over the last 12 weeks, broken down by plan tier: to show whether adoption is accelerating, flat, or declining per feature. Annotations: - Flag features with high adoption in higher tiers but low adoption in lower tiers (candidates to promote down-tier OR signs of plan-feature mismatch). - Flag features with declining adoption in any tier (deprecation candidate or UX issue). - Highlight features used by >40% of paying users: these are the load-bearing features whose performance and reliability matter most. - Highlight features where higher-tier users adopt at >2× the rate of lower-tier users (the best upgrade-pitch features). Taxonomy notes: - Click on carries target_id, target_text, target_class, target_tag, hierarchy, path. The product team identifies features by stable target_id values. - "feature_name" is not a canonical property; target_id (or target_text for human labels) is the canonical handle. - Plan lives on Subscription started; this requires joining to the user's active subscription.
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 /feature-adoption-by-plan 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.
