Retention as Habit-Building Plus Expansion
Retain by baking high-frequency habits into the product, then convert steady usage into expansion revenue
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 3
- Confidence
- 90%
Qu splits retention into two steps: building a usage habit and driving expansion. Habits require the product to have high enough natural frequency and ideally collaboration built into the workflow — loops and emails reinforce but can't substitute. Once usage is steady, expansion follows three levers: upgrade to a higher tier, buy more seats, or consume more of an add-on. A recurring move is to reframe a retention problem as an adoption problem for a higher-frequency use case.
Origin
Drawn from Hila Qu's work as head of growth at Acorns (an intentionally low-frequency 'set it and forget it' investing app) and at GitLab, plus her advisory practice.
Core principles
- 01Fundamental retention comes from the product being high-frequency and part of the workflow, not from email loops
- 02Low-frequency products are structurally hard to retain and hard to re-engage
- 03Expansion is part of retention: steady usage is the platform for selling more
- 04The three expansion levers are higher tier, more seats, and more consumption
- 05A retention problem can often be reframed as an adoption problem for a stickier use case
How to run it
- 1
Build the habit into the product itself
Ensure the product has high enough natural frequency and, ideally, collaboration built into the workflow so users return every day or week. This is the fundamental driver of retention.
Pro tip You can reinforce habits with loops — email a user after an action to bring them back to repeat it — but the habit must live in the product first.
Watch out A once-per-month product is very hard to build into a habit and gives you few levers to drive engagement when users aren't in the product.
- 2
Reframe retention as adoption of a higher-frequency use case
If retention is weak because frequency is low, add higher-frequency use cases and drive their adoption instead of attacking retention head-on.
Pro tip At Acorns, driving adoption of the higher-frequency 'recurring investment' feature (which correlated strongly with retention) worked better than attacking retention directly; adding IRA and spending/debit accounts added structurally higher-frequency use cases.
- 3
Trigger expansion at the right moments
Once usage is habitual, use data to trigger the right conversation at the right moment to the right person across three expansion levers: upgrade tier, add seats, or consume more.
Pro tip Expansion reuses activation and conversion tactics — it's getting people to the aha of a new feature, using it, and converting on it.
In the wild
Acorns began as a passive investing app — buy ETFs, add money, don't check for 10 years. Sound investing philosophy, but as head of growth Qu couldn't drive engagement or even tell whether users were retained because success required no return visits. She found via data that the 'recurring investment' feature correlated highly with retention and ran experiments to drive its setup, then added higher-frequency use cases (IRA retirement accounts, a spending/debit account).
→ Recurring-investment adoption rose quickly and successfully; higher-frequency accounts (an IRA carries tax consequences that make leaving hard) structurally improved retention by turning it into an adoption problem.
Common mistakes
Relying on email loops to create retention
Loops and lifecycle emails only reinforce a habit that already exists in the product. If the product isn't high-frequency or embedded in the workflow, no amount of email substitutes for that fundamental driver.
Attacking a retention problem head-on when frequency is the real issue
When users churn because the product is inherently low-frequency, direct retention tactics have little leverage. The higher-leverage move is to add and drive adoption of higher-frequency use cases.
Is it for you?
Best for
Growth leaders at PLG products with steady acquisition but weak or low-frequency retention
Not ideal for
Teams that haven't yet fixed activation or conversion — retention is the later, messier stage
From the transcript
“I call retention the messy middle”
“your product need to have a high enough frequency. Like if you're using this once per month, it's not likely you can build this into…”
“When I was asked to work on retention... The biggest leverage for me is actually activation”
“there three buckets of product product led extension. The first one is up upgrade to a higher tier. The second one is a buying more…”
“Once you have a retirement account IRA, there's tax consequences... So you flip the question into again a adoption activation problem”
From the episode
The ultimate guide to adding a PLG motion
Hila Qu (Reforge, GitLab)