Paid user retention
See whether paying customers continue logging in, tracked month by month and compared by plan.
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 logo and revenue retention
Coming soonBlu builds a step
About this recipe
When to use it
You can lose lots of small accounts while revenue retention looks fine, or the reverse. This tracks logo and revenue retention as two separate lines every month, broken down by plan tier.
What it delivers
Tracks monthly paid retention with logo retention and revenue retention reported separately, plus a plan-tier comparison layered on top.
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
“See whether paying customers continue logging in, tracked month by month and compared by plan.”
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 logo and revenue retentionCreate a Retention report called "Paid User Monthly Retention". Anchor event: Subscription started where trial_end is null (paid signup, not trial) Return event: Session start (logo retention) AND Revenue completed (revenue retention): render as two views Cohort granularity: Monthly Time range: Last 6 months Breakdown: By Plan (from Subscription started.Plan) Compare: Previous period (prior 6 months of cohorts) Chart type: Retention curve plus cohort table with M1 through M6 columns Logo Retention view: - Cell value = % of cohort users who emitted at least one Session start in month N Revenue Retention view: - Cell value = Sum of Revenue completed.amount in month N from cohort users / Sum of Revenue completed.amount in month 0 from cohort users × 100, unit: % - This separates "do users stay?" from "do they pay the same or more?" Annotations: - Add benchmarks: 95% monthly logo retention is industry-good for self-serve SaaS; 85% is below par. - Flag any plan tier where M3 logo retention is below 80%. - Flag any cohort where revenue retention exceeded logo retention by 10+ percentage points (expansion offsetting churn: good). - Highlight the highest-retaining plan tier. Surface whether enterprise tiers retain materially better than starter tiers. Taxonomy notes: - Subscription started with trial_end=null marks paid (non-trial) starts. - Revenue completed has amount, customer_id, type: the canonical recurring revenue marker. - "any_active_event" as a return signal can be substituted with Session start (most reliable active marker).
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 /paid-user-retention 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 