Duolingo
Users try once and never come back
Add a streak counter
People hate losing things more than they like gaining them. A streak counter turns that into a reason to come back every day.
Intermediate
2-3 weeks to build, 1-2 months to measure
Retention growth experiments
Keep users coming back. Learn from Duolingo, Spotify, Amazon and more.
49playbooks
Intermediate17
Beginner26
Advanced6
All retention playbooks
Common SaaS pattern
Users sign up and never come back
Send a 7-day onboarding email sequence
Guide new users through their first week with daily emails that teach one thing and prompt one action.
Beginner
3-5 days to write and set up, 2 weeks to measure
Common SaaS pattern
Users cancel without giving you a chance to keep them
Add a cancellation flow that solves their problem
Instead of a one-click cancel, ask why they're leaving and offer a targeted solution. Save 10-20% of cancellations.
Beginner
3-5 days to implement, 2-4 weeks to measure
Duolingo gamification case study
Users don't feel progression or accomplishment
Add achievement badges and levels
Visualize progress with badges and levels. Every completed action becomes a mini-celebration.
Intermediate
3-4 weeks
Common product pattern
Users complete experiments but don't learn from them systematically
Add a "learnings" capture step after every experiment
After each experiment, prompt users to capture what they learned. Over time, this builds a knowledge base that makes the product indispensable.
Beginner
3-5 days to implement, 4-8 weeks to build meaningful knowledge bases
Persistent feedback buttons generate 5x more feedback than help center links
Your product has no way for users to give quick feedback
Add a one-click feedback button on every page
A persistent feedback button lets users report issues or share ideas in 10 seconds.
Beginner
1-2 hours to implement
Common pattern
You don't know why users churn — they just disappear
Add a one-question churn survey
When users cancel or go inactive, ask ONE question: "What's the main reason you're leaving?" The data transforms your retention strategy.
Beginner
1-2 hours to implement, insights within 2-4 weeks
Strava, Duolingo, GitHub
Users don't realize they're making progress toward their goals
Add a progress dashboard showing trends over time
Show users their growth over time. A line going up is the best retention tool ever invented.
Intermediate
3-7 days to implement, 2-4 weeks to measure engagement impact
Linear, Canny
Your product has no way for users to express what they want to see built
Add a "vote for next feature" poll in-app
A simple monthly poll asking "What should we build next?" gives users voice and investment in the product's future.
Beginner
1-2 hours to implement poll, monthly ongoing
Duolingo gamification, 80% organic growth
Users have no accountability to keep using
Add friend challenges
Let users challenge friends to goals. Social accountability is stronger than willpower.
Intermediate
3-4 weeks
Figma, Notion
Users churn because they feel alone using your product
Add lightweight social features — activity feeds, comments, or reactions
Simple social features like reactions, comments, or activity feeds make users feel part of something. Social products retain better.
Intermediate
1-2 weeks to implement basic social, 4 weeks to measure retention impact
Slack, Mailchimp
Your product works fine but users don't feel emotionally connected
Add personality and delight to micro-interactions
Small moments of delight - animations, witty copy, easter eggs - create emotional connection that prevents churn.
Beginner
2-5 days to add delight moments, ongoing
Duolingo, GitHub, Snapchat
Users use your product sporadically with no rhythm
Add streak tracking to encourage consistent usage
Show users their usage streak and celebrate consistency. Nobody wants to break a 14-day streak.
Beginner
3-5 days to implement, 2-4 weeks to see streak formation
Common pattern
Users have no reason to stay beyond the tool itself
Build a community around your product
Users who join your community churn 40% less because they've built relationships, not just workflows.
Intermediate
1-2 weeks to set up, 2-3 months to build critical mass
Common SaaS pattern
You don't know which users are about to churn until it's too late
Build a customer health score and intervene early
Score users based on usage patterns. When their score drops, reach out before they churn.
Advanced
2-4 weeks to build scoring system, 1-2 months to validate
Figma Community
You're creating all the content yourself and it doesn't scale
Build a user-generated content flywheel
Let users create and share things inside your product. Their content attracts new users, who create more content. A flywheel that spins faster over time.
Advanced
2-3 months to launch, 6+ months for flywheel effect
Amazon Prime
Users cancel because there's only one reason to stay
Bundle more value into the subscription
Add things to your subscription so canceling means losing multiple things they use.
Advanced
3-6 months
Strava
Users hit goals but nothing happens
Celebrate milestones with shareable badges
Turn personal achievements into shareable social moments. Users who share milestones retain 2x better because they've publicly committed to your product.
Beginner
1-2 weeks to implement basic version
Strava
Users don't feel like they're making progress
Celebrate user milestones with badges
Mark users' achievements with badges and celebrations. Progress feels invisible without recognition, and recognition creates commitment.
Beginner
2-4 weeks
Common B2B pattern
Power users don't have a way to give you feedback or influence the roadmap
Create a customer advisory board of your top 10 users
Your top 10 users become invested stakeholders who never churn and advocate publicly for your product.
Beginner
1 week to set up and invite, quarterly ongoing
Based on Nir Eyal's Hook Model
Users use your product once but don't form a habit
Create a daily reason to come back
Design a feature that gives users a different, valuable reason to check in daily. Variable rewards create stronger habits than predictable ones.
Advanced
2-4 weeks to design and implement, 4-6 weeks to measure habit formation
Canny, Linear
Users request features in emails and support tickets that get lost
Create a public feature request board
Let users submit and vote on feature requests. Users who feel heard stay longer, and you build what actually matters.
Beginner
1-2 hours to set up, ongoing to maintain
Pattern from Nir Eyal's Hooked model
Users complete the core workflow once and never return
Create a reason to check back daily or weekly
Your product delivers value once. Add something that creates a recurring reason to visit: new data, recommendations, or updates.
Intermediate
1-2 weeks to implement, 4-6 weeks to measure habit change
Common retention pattern
Users don't know about features you shipped months ago
Drip-announce features users haven't tried
Instead of one big announcement, drip-feed feature announcements to individual users based on what they haven't used yet.
Intermediate
1-2 weeks to build the system, ongoing to add new features
Intercom
Users only use one feature and never discover the rest
Drip-reveal features over time
Don't show everything at once. Reveal features gradually based on usage. Users who discover more features stay longer.
Intermediate
3-4 weeks
Dribbble
There's no switching cost — users leave easily
Let users build a public profile
When users invest in a public profile—portfolio, stats, reputation—leaving means losing their identity. That's a switching cost no competitor can overcome.
Advanced
4-8 weeks to build, 3-6 months to see retention impact
Spotify Wrapped
Users drift away and forget you exist
Make a shareable year-in-review
Turn user data into a personalized story they'll want to share. Free marketing that also makes them feel understood.
Advanced
4-6 weeks to build first version
Superhuman
High-value trial users don't activate fully
Offer a free 15-minute onboarding call
For users who match your ideal customer profile, offer a free 15-minute setup call. Human touch converts better than any drip email.
Intermediate
1 day to set up, immediate results per call
ProfitWell/Paddle churn research
Users cancel when a pause would save them
Offer a pause option instead
Many cancellations are temporary. Offer a pause and they'll come back instead of churning forever.
Beginner
1-2 weeks
Duolingo streak mechanics, 14% retention boost
Users lose streaks and quit in frustration
Offer streak freezes as a safety net
One missed day ends a 100-day streak? That's rage-quit territory. Offer protection and monetize it.
Beginner
1-2 weeks
Spotify, Netflix, LinkedIn
Every user sees the same dashboard regardless of how they use your product
Personalize the dashboard based on each user's behavior
Show users the data and actions most relevant to them. A personalized dashboard feels like a product built just for them.
Intermediate
1-3 weeks to implement, 2-4 weeks to measure
Intercom, Superhuman
Users hit problems and leave instead of contacting support
Reach out proactively when users seem stuck
Monitor for users who seem stuck (repeated errors, long sessions on one page, abandoned actions) and reach out before they give up.
Intermediate
1-2 weeks to set up triggers, immediate impact on saves
Figma, VS Code
Users go through the same onboarding twice when they start a new project
Remember user preferences across projects and contexts
Your product should learn from how each user works and apply those preferences automatically.
Intermediate
3-7 days to implement preference memory, ongoing to add more
Intercom, Slack
New features get shipped but adoption is low
Run an in-app feature launch campaign
Don't just ship features — launch them in-app with announcements, tutorials, and incentives to try.
Beginner
1-2 days per feature launch campaign
Common SaaS pattern
You don't have a way to win back users who cancelled months ago
Run a quarterly win-back campaign with a compelling offer
Users who cancelled 3-6 months ago are your warmest cold leads. A personal email with a relevant update can reactivate 5-10%.
Beginner
2-3 hours to write and send, results within 1-2 weeks
Spotify Wrapped, GitHub Skyline
Your product has seasonal usage patterns with predictable dips
Run a seasonal campaign during your slow period
If usage dips predictably (holidays, summer, end of quarter), run a campaign specifically designed to maintain engagement during that period.
Beginner
2-3 days to design campaign, runs for 2-4 weeks
Grammarly
Former users are gone and you've given up on them
Run a win-back campaign for dormant users
Users who left aren't gone forever. A well-timed "we miss you" campaign with the right incentive brings a surprising number back.
Beginner
1-2 weeks to set up, results within 2-4 weeks
Slack, Dropbox
Your sales team chases users who aren't ready to buy
Score users by product usage to find sales-ready leads
Track which free users are most active and reaching feature limits. These are your best upgrade candidates.
Intermediate
1-2 weeks to build scoring, ongoing outreach
Common SaaS pattern
Users leave after free trial without trying your best features
Send a "features you missed" email before trial ends
Before the trial ends, show users which Pro features they haven't tried yet. Many will extend or convert after discovering something new.
Beginner
3-5 hours to build, results within first trial cohort
Common SaaS retention pattern
Users don't realize how much value they've gotten from your product
Send a monthly value summary showing their ROI
At the end of each month, show users exactly what they achieved. Users who see their ROI don't churn.
Intermediate
3-5 days to build template, monthly automation
Common pattern
You ship improvements but nobody notices
Send a monthly "what we shipped" email to all users
A monthly email highlighting 3-5 things you shipped keeps users informed and shows the product is alive and improving.
Beginner
1-2 hours per month, ongoing
Common retention pattern
Users set up features and then forget about them
Send a periodic reminder of unused features with results
If a user set up a feature but hasn't checked it in 2 weeks, send them a summary of what they're missing.
Beginner
3-5 days to build email templates, ongoing automated sending
Quora
Users forget you exist between sessions
Send a personalized weekly digest
A weekly digest email with personalized content gives users a reason to come back. It's a habit trigger delivered to their inbox.
Beginner
2-3 weeks to build first version
Grammarly, Strava, GitHub
Users forget about your product between sessions
Send a weekly email with their personal stats
A weekly email showing users their own data and progress. Keeps your product top of mind and gives a reason to return.
Beginner
3-5 days to build template and automation, immediate retention impact
Common retention pattern
Users go quiet after the first week
Send a "we miss you" email with their data
Don't send generic "come back" emails. Show users what they're missing by including their actual data and progress.
Beginner
3-5 days to build email sequence, 2-4 weeks to measure
Grammarly
Users forget you exist between sessions
Send weekly personal stats
A personalized stats email gives users a reason to come back. Not a newsletter—their own data, delivered every week.
Intermediate
2-3 weeks to build, results visible within a month
Slack, LinkedIn
Users come back after a week and don't know what changed
Show a "since you've been away" summary on return
When users return after 3+ days, show a quick summary of what happened while they were gone.
Intermediate
3-5 days to implement, 2 weeks to measure impact
Linear, Notion, Figma
Users don't know you ship new features every week
Show a "What's new" feed inside the app
A small notification badge on a "What's new" button keeps users aware of improvements without sending more emails.
Beginner
1-2 days to implement, ongoing to maintain
Common SaaS pattern
Users don't know other customers like them use your product
Show in-app social proof: "500 founders use this"
Show usage stats, active user counts, and peer activity inside the product. Users who feel part of a crowd stay longer.
Beginner
1-2 hours to implement, ongoing automatic updates
Frequently asked questions
What is retention rate?
Retention rate measures how many users continue using your product over time. Common metrics include Day 1, Day 7, Day 30 retention (% of users who return), and cohort retention curves.
Why is retention important for growth?
Retention is the foundation of sustainable growth. High retention means your acquisition efforts compound. A 5% improvement in retention can increase profits 25-95%. Leaky buckets can't be filled.
How do I improve retention?
Focus on habit formation (streaks, reminders), increasing switching costs (data, integrations), and delivering ongoing value. Understand why users leave through exit surveys and cohort analysis.
Ready to run your first experiment?
Sign up free and get experiment suggestions matched to your goals.