Feature discovery for paid users
Shows paying customers the features they have never opened, one at a time, picked for the way they actually use the product.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon5 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Find features they never use
Coming soonBlu builds a step
- 2
Pick who is worth nudging
Coming soonBlu builds a step
- 3
Write the nudge
Coming soonBlu builds a step
- 4
One feature every two weeks
Coming soonBlu builds a step
- 5
See what the nudges actually change
Coming soonBlu builds a step
About this recipe
When to use it
A paid user who never touches half the product is more likely to leave, and nobody flags it until the renewal call. This nudges toward one relevant feature at a time before that becomes a problem.
What it delivers
For paid users who haven't touched key features after 30+ days, fires a feature-discovery nudge journey - one feature at a time, contextually relevant to their use case.
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 paying customers the features they have never opened, one at a time, picked for the way they actually use the product.”
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.
- 01Find features they never useCreate an AI-derived attribute 'untouched_features' on the User object. Computed weekly. For each user, compare features-touched in last 90 days against the catalog of features available on their plan, and surface the top 3 high-value features they haven't used. Prioritize features by: (a) historical correlation with retention among similar users, (b) features the user's use case (inferred from segment / industry / role) suggests they should benefit from. Excludes features that the user's plan doesn't include. Output: ranked list of 3 untouched features with the recommended order.
- 02Pick who is worth nudgingBuild a segment 'Feature discovery audience' capturing paid users where subscription is at least 30 days old AND untouched_features list is non-empty AND the user has had at least 2 sessions in the last 14 days (active enough to benefit from a feature nudge). Excludes users in initial onboarding (different motion) and users who already received a feature-discovery nudge in the last 30 days. Use the result of "Find features they never use".
- 03Write the nudgeGenerate per-feature discovery email templates (one template that pulls the top untouched feature per recipient). Subject: '[First name], you haven't tried [feature] yet': specific feature, specific benefit. Body: brief value statement of the feature ('Users who use [feature] save an average of [time/effort metric]'), a short use-case description that matches the user's segment, a screenshot or short GIF showing the feature in action, and a deep-link CTA into the app at the right place. Tone: helpful nudge, not 'we noticed you're not getting your money's worth' (which feels accusatory). Use the result of "Find features they never use", "Pick who is worth nudging".
- 04One feature every two weeksBuild a 3-touch journey triggered weekly for users in the feature-discovery segment. Each touch surfaces a DIFFERENT untouched feature from the user's list (not the same feature 3 times). Touch 1: top feature, Day 0. Touch 2: second feature, Day 14. Touch 3: third feature, Day 28. Skip a touch if the user actually started using that feature between touches (they got the message: don't pester). Exit on: user adopts all 3 features (success), user opens cancel-flow (handoff to pre-cancellation-save), or 60-day completion. Use the result of "Find features they never use", "Pick who is worth nudging", "Write the nudge".
- 05See what the nudges actually changeCompose a feature adoption dashboard: feature-discovery email volume by feature (which features need the most nudge: could signal weak in-app discoverability), feature-adoption rate after nudge (% of recipients who use the feature within 14 days of receiving the nudge: typical: 8-15%), retention lift from adoption (compare 90-day retention of users who adopted post-nudge vs. control), and untouched-feature distribution (which features are most-commonly never-touched: informs product team where the discoverability gaps are). Use the result of "Find features they never use", "Pick who is worth nudging", "Write the nudge", "One feature every two weeks".
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-discovery-for-paid-users 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 