Product-Led Retention

A written retention definition, honest cohort curves, the behaviours that predict who stays, review rhythms for churn and dormancy, and fixes for the moments users quietly leave.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Product-Led Retention, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

204

Starter tasks

🧩 Product Management

Product-Led Retention

Finding the product behaviours that keep users coming back, building habit-forming loops and fixing the moments where users quietly leave.

  1. Written definition of a retained user
  2. Natural usage interval for your product
  3. First cohort retention table
  4. Retention curve shape diagnosis
  5. Churn, dormancy and involuntary loss definitions
  6. Retention baseline by plan, segment and channel
  7. Behaviours that separate kept users from lost ones
  8. Retention target with guardrail metrics
  9. Map of moments where users quietly leave
  10. Weekly retention signal check
  11. Monthly cohort review meeting
  12. Churned user exit interviews
  13. Cancellation reason survey and tagging
  14. At-risk account watchlist from usage decline
  15. Failed payment recovery and card update prompts
  16. Win-back programme for lapsed users
  17. Release retention guardrail check
  18. Retention bets backlog
  19. Quarterly retention review with leadership
  20. Reading cohort tables and retention curves
  21. Habit formation models and their ethical limits
  22. Measuring retention effects with long holdouts
  23. Churn, lifetime value and payback maths
  24. Net revenue retention and expansion maths
  25. Interviewing people who left
  26. Correlation traps in retention analysis
  27. Cancellation flow that respects the user
  28. Pause and downgrade options decision
  29. Welcome-back experience after an absence
  30. Value recap showing what users achieved
  31. Fixing the biggest exit point
  32. Stored value audit of what users would lose
  33. Multi-user accounts as a retention lever
  34. Retention share of the roadmap
  35. Dark pattern audit of retention tactics
  36. Data export and clean offboarding
  37. Retention sprint week
  38. Post-mortem on a lost key account
  39. Annual renewal season readiness
  40. Retention data pack for investors
  41. Churn watch around a price change
  42. Retention evidence before product-market fit
  43. Spreadsheet retention for a team without an analyst
  44. First 60 days on a product with a leaking cohort
  45. Retention for low-frequency and seasonal products
  46. B2B retention when the buyer is not the user
  47. Usage depth histogram and power user curve
  48. Predictive churn score, tested honestly
  49. Survival analysis of time to churn
  50. Cohort-based lifetime value model

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Written definition of a retained user

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Teams argue about whether retention is improving because each person means something different by an active user: logged in, opened the app, or did the thing the product exists for.

First tasks

  • List the three actions a user takes when they are getting real value
  • Write a one-sentence retained user definition for each candidate
  • Check with engineering that the chosen action is tracked reliably
  • Publish the definition on the team's metrics page
  • Revisit the definition after a year of product changes @recurring(yearly)

Natural usage interval for your product

Payroll tools used twice a month will look like a disaster on a daily active user chart, and a messaging app will look healthy on a monthly one. Working out how often a satisfied user genuinely needs the product sets the window every retention measure should use: daily, weekly, monthly or per cycle. Get this wrong and the team will chase the wrong problem.

First tasks

  • Pull a list of users who have been active for at least six months
  • Chart the days between their consecutive core actions
  • Pick the window that covers most of their return gaps
  • Update the retention dashboards to use that window

First cohort retention table

An overall active user count can grow for years while every new cohort leaks faster than the last, because fresh sign-ups hide the loss. A cohort table, one row per sign-up month and one column per period since, shows whether newer users stay better or worse than older ones. It is the single chart most retention decisions start from.

First tasks

  • Create a cohort log from the metrics log template
  • Write the query that groups users by sign-up month
  • Fill the table for periods 1, 2, 3, 6 and 12 where data exists
  • Write two observations about how newer cohorts compare with older ones

Make it yours.

Install Product-Led Retention, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.