Founder Playbook · Sub Club by RevenueCat
10 tactics from Dan Layfield
The Growth Formula: Churn, Retention Wins, & Smart Product Bets
Watch the full episode“projects in progress don't do anything for your business they only start to do something for your business when they go out the door so if you have big projects kind of like chunking them up into milestones so you ship things incrementally and start to slowly test assumptions goes a long way”
Projects In Progress Don't Move The Needle — Only Shipped Features Do
Dan's core product management insight after years scaling Codeacademy: the feeling of being busy — full project tracker, multiple things in parallel — is completely decoupled from business results. A backlog of in-progress work produces zero revenue until it ships. The remedy is aggressive milestone chunking so that something goes out the door continuously, test assumptions accumulate, and the team gets signal instead of just staying busy.
“the biggest wins we found were always like the third or fourth swing at something because you ship something you realize it doesn't work and if you move on immediately then unless you were completely off base it doesn't work”
Your Biggest Product Wins Come On The Third Or Fourth Attempt At The Same Problem
Dan's repeated experience at Codeacademy: the first and second attempt at any meaningful product problem rarely land. Engineers need time to learn the codebase area; designers need to internalize the nuances; the team needs to build intuition. The teams that win are the ones that stay focused on a problem long enough to take three or four shots — and look for 'signs of life' in test variants rather than declaring failure and moving on.
“if you take the number of users that you're acquiring per month and divide that by your month-to-month churn rate you get the ceiling of users that you can keep at that level...at 5,000 the number in which the inputs will equal the outputs”
The Growth Ceiling Formula: Divide Monthly New Users By Churn Rate To See Your Cap
Dan shares the formula most subscription founders don't know: max subscribers = new users per month / monthly churn rate. At 500 new users/month and 10% churn, you cap at 5,000 subscribers — period. Growing below that ceiling feels great and can mask the hard truth. The only ways to raise the ceiling are to reduce churn or increase acquisition. Without one of those, the business will plateau regardless of product investment.
“the best way of getting ahead of churn is not basing retention off of payments it's basing off of some sort of core action in the product...improving core activation and the core habit will always improve churn”
Track Core Habit Actions, Not Payments, To Predict And Prevent Churn Before It Happens
Payment status is a lagging churn indicator. A user can have a live subscription for months while behaviorally they've already churned — they've just forgotten to cancel. Dan's approach: define the core action that delivers value in your product (checking the weather, sending a Slack message, completing a lesson), and track whether users perform it on the expected cadence. When that habit breaks, churn is imminent. Intervening there is far more effective than any win-back campaign.
“the big three that I've seen work is pause like discount and kind of like connect with support...I've seen between like a 10 and 20% drop in churn depends a little bit on the use case but like it adds up to be material there's a reason all the giant companies do this”
Cancellation Flow: Pause, Discount, Connect With Support Cut Churn 10–20%
Dan has implemented cancellation-flow interventions at multiple companies and consistently sees a 10–20% reduction in churn. The three tactics in order of effectiveness: (1) pause — especially powerful for habit-based products where users get busy; (2) temporary discount — offer 50% off for 3 months before losing them; (3) connect with support — route negative-experience cancellers to a human. The caveat: these flows require custom payment processor logic that isn't cheap to build; prioritize based on how much your churn numbers will actually move.
“one of the highest ROI projects we ever did at Code Academy is we rewrote all of the checkout error copy...it literally took like two days...maybe that very conservatively lifted checkout page conversion like 1% but 100% of your new revenue goes through the checkout page so it's really like you lift the whole business's revenue 1%”
Rewriting Checkout Error Messages Lifted All Revenue 1% — A Two-Day Project
Dan's highest-ROI project at Codeacademy wasn't a new feature — it was rewriting payment error messages to actually explain the problem and tell users what to do next. Took two days. Because 100% of revenue flows through the checkout page, even a 1% lift propagates to the entire business. For subscription apps using web checkout especially, this is a high-leverage area that is routinely neglected in favor of flashier product work.
“your retention length will be really dictated by how long the user has the problem you're solving for...cell phone plans...I'll probably be with them 25 years because I have a daily need for their product...meditation apps where meditation is a thing you don't really need an app for you'll probably either like learn it or realize it's not for you relatively quickly”
Your Retention Ceiling Is Set By How Chronic The Problem You Solve Is
Dan frames churn not as a product problem but a use-case problem. Cell phone plans retain for decades because the need never goes away. Meditation apps churn quickly because the underlying need resolves — or dissolves. The highest-retention subscription products solve chronic, daily, irreplaceable problems. If your use case is episodic or short-term, you need massive acquisition volume or a retention mechanism (like a companion subscription or seasonal content) to counteract the structural ceiling.
“I know you know four of the five points that this growth hacker made on Twitter it's like that's not why the business is being successful those four things are completely irrelevant and aren't what's fundamentally driving the business it's this other thing that you can't even see”
Visible Tactics Rarely Explain Why Apps Grow — You're Copying The Noise, Not The Signal
Dan has seen the same pattern repeat: a growth account breaks down a successful app into five tactics, and four of them are completely wrong — he knows because he knows the founders. The real driver is invisible from the outside. Copying observable product choices (paywall design, ad creative, onboarding steps) from competitors imports their experiments without their context. Dan's alternative: understand the underlying theory of why something works, then derive your own implementation.
“your monetization systems as a whole are really just like a measure of how much of the value your product produces that you capture in money...if the product isn't increasing in value it's really tough to raise your prices”
Monetization Is Just Value Capture — Build More Product Value Before Optimizing The System
Dan's grounding framework for subscription monetization: pricing tiers, paywalls, and upsells are a system for capturing a percentage of the value the product creates. Once founders start making money, it's easy to make the monetization system the goal itself — optimizing captures rates on a fixed pie. But the bigger lever is always making the pie bigger. Product value is the prerequisite; monetization efficiency is the multiplier. Don't optimize the multiplier when the base number is stagnant.
“the complexity tax is real it's like the northstar of your development should be protecting like future velocity...geo-based pricing almost always works...but you have to then manage 10 price packages forever”
The Complexity Tax Is Real: Every Monetization Tactic You Add, You Own Forever
Dan watched Codeacademy introduce geo-based pricing — it worked, but every subsequent price change, ad copy refresh, or support doc now had to account for ten tiers instead of one. The complexity tax compounds: it slows every future decision. His rule: exhaust all simple, low-complexity improvements first. Save the tactics that require permanent infrastructure (regional pricing, pricing tiers, paywalls per persona) for later when the revenue they unlock genuinely justifies the velocity they cost.