Founder Playbook · Sub Club by RevenueCat
12 tactics from Patrick Falzon
Why Most Apps Hit a Revenue Ceiling (and How to Plan for It) — Patrick Falzon, The App Shop
Watch the full episode“Maybe not the answer everyone's going to want to hear here: I tend to think most apps will hit that ceiling and it's actually very hard to break through it. The way we thought about it is more of accepting that as a constraint for the mobile business and then how do you architect around it.”
Most apps will hit a $10-30M revenue ceiling — plan around it rather than hoping to be the exception
Falzon explains the mechanics behind the ceiling: organic App Store search is a finite pool you eventually max out; paid UA hits a ceiling when your CAC approaches your LTV cap. Most mobile LTVs sit under $100, which limits how much you can profitably spend on any channel. The constraint is structural, not a failure of execution. Falzon's advice: accept it as a given and either build a portfolio of several $30M apps, or find an organic breakout channel that the ceiling math does not apply to.
“A common thread I see at least is that apps that break out — like a Duolingo, even a Spotify — are inherently mobile-first products that for a large part of their life had very big free user bases. If you're doing a hard paywall, accept that you are probably capping this at $10-20-30M of Revenue.”
Apps that break through the ceiling almost always have a massive free user base driving organic distribution
Falzon observes that the breakout exceptions to the $10-30M ceiling built massive free communities before monetizing seriously. The free base became their distribution, their brand, and their referral engine. Hard-paywall apps that convert everyone immediately rarely build that community and therefore cap out on organic growth. For founders who want to build past the ceiling, a substantial free experience is not just generosity — it is a prerequisite for the network effect that breaks the ceiling.
“A big market is great only if you can take a substantial share of that market. If it is so competitive that you can't actually garner market share, it's not actually valuable to you. There's a little bit of a Goldilocks approach — markets that are big enough to create enduring products but where you could still be a relative big fish in a smaller pond.”
Market size is only half the story — competition determines whether you can actually capture any of it
Falzon describes the two-dimensional market assessment framework applied at Mosaic when evaluating acquisitions: market size alone is insufficient. VPNs were avoided because every dollar of user acquisition competed against players spending aggressively. Personal finance was avoided because banks with 10x higher LTVs would always outbid a standalone budgeting app for the same acquisition keywords. The lesson: find markets large enough to build a real business but not so contested that you must outspend incumbents just to exist.
“All of your features should fit into one of those two buckets — are we trying to increase ARPU or are we trying to increase retention? I'm not sure what the other rationale for releasing a new feature is if you're not going to increase ARPU or retention.”
Every feature should do one of two things: increase ARPU or increase retention — nothing else justifies the build
Falzon's feature-classification rule from Mosaic's product operating model: before a feature is approved, classify it as either an ARPU driver (upsell opportunity, new paid tier, consumable) or a retention driver (reduces churn, deepens habit). The two categories require different marketing strategies, different success metrics, and different positioning to the user base. Features that do not clearly belong to either bucket tend to be features the team thought were cool rather than features users needed — and they disappear unused.
“LTV is particularly hard in the early days. What I advise people to do is think more about your range of possible outcomes. You're getting a directional estimate at best — so run a range of scenarios and assign some probabilities to them, come up with your best estimate, start making decisions, and go back and check it every month or two.”
LTV is a terrible metric to buy against — use capped time-horizon cash flow predictions instead
Falzon argues 'lifetime' value is literally incalculable — cohorts from six years ago still renewing mean there is no finite lifetime to average. The practical alternative: cap LTV at a specific time horizon (2-3 years is common), separate payback period as a distinct metric, and run scenario analyses with probability weights rather than claiming a single LTV number. Early-stage companies need tight payback periods because they lack cash; mature companies can extend payback windows and buy against longer-horizon projections. The wrong approach is picking a single LTV number and treating it as fact.
“If you have a 5% buffer on retention before this price test winner is no longer a winner, maybe don't roll that one out. If retention can go down by 50% and that thing's still a winner — close your eyes and roll it out. Sensitize it to say: if retention comes in 10% worse, does it change my answer?”
Price increases hurt annual retention more than monthly — sensitize tests before rolling out
Falzon describes a recurring mistake at Mosaic: price tests run against monthly subscribers produced misleading signals about annual subscriber impact. Monthly retention data arrived quickly; annual renewal data took 12+ months. Teams would roll out a price increase that looked like a winner on monthly data, then a year later discover annual churn spiked and the test was actually a loss. The fix: before rolling out any price test, model the range of retention impacts and check whether the outcome is still positive under the pessimistic scenario.
“Over 50% of installs come through search and go to one of the top three rankings on search. It is really critical that if you're going to launch a product you understand what relevant keywords for your product — what is your ability to rank on those keywords? If the first three results are hundred-million-dollar companies with massive budgets, that's probably a concern.”
ASO is over 50% of installs and the incumbent at position one is nearly impossible to displace in 2024
Falzon draws on data from Mosaic's portfolio to establish that App Store search is the single largest install channel for most apps, but positions 1-3 capture the vast majority of that traffic. The incumbent advantage in established categories is severe: apps like Lose It have held top rankings for a decade-plus. An app entering the calorie-counting category in 2024 cannot rely on ASO; it must identify an alternative acquisition lever (TikTok organic, SEO, paid) or find a keyword niche the incumbents have left uncontested.
“All designers have a pretty unique and personal theme — the things they like to lean into. If you keep using the same designer what you find is you get in this trap of incremental improvements where you're changing 5% or 10% of a thing. Sometimes it's actually better to bring in a new designer and say go wild with it.”
Rotate creative designers across products — the same designer produces incremental variations, not breakthroughs
Falzon identifies a structural problem in paid UA creative teams: designer style becomes a fixed constraint, and iterations within that style produce only marginal performance gains. Mosaic's solution was rotating designers across apps every two months, forcing wholesale creative exploration rather than incremental polish. For smaller teams without that option, the lesson is equivalent: periodically commission a completely fresh creative approach from someone with no history on the brand.
“We started publishing reports and working with reporters to help them report on the issue — here's how many spam calls Americans are getting every month, here's how it's growing. When you accumulate multiple Wall Street Journal articles that reference you and Financial Times articles — that starts building a brand and organic halo.”
Proprietary data plus press relationships beat direct ads — Robokiller built organic brand through spam-call reports
Falzon describes RoboKiller's content and PR strategy: the app had the largest dataset on US spam calls and texts, and Mosaic created a recurring monthly spam-call report that journalists and regulators (FCC, FTC) found genuinely valuable. The Wall Street Journal and Financial Times cited these reports repeatedly; cable news segments featured the data. No single press mention drove meaningful downloads — but the accumulated brand signal reduced CAC across all other channels and built credibility that converted skeptical users.
“My general bias in the mobile space is towards slimmer products and being okay having multiple products that serve adjacent use cases. Having a product that has eight different features on a smartphone app — it's very hard to get users to understand all of those features and effectively switch between them.”
Slim products on mobile beat feature-rich ones — two apps with three features each outperforms one app with eight
Falzon applies a lean-product principle rooted in mobile UX constraints: small screens, limited attention, and one-tap navigation make feature-dense apps cognitively costly. Mosaic consistently favored spinning out adjacent functionality into separate apps rather than cramming it into existing ones. This enabled better user segmentation — different personas could self-select the right product — and better monetization through separate subscriptions. The counter-intuitive outcome: more apps, each doing fewer things well, generated more total revenue and better retention.
“We tried to have one or two max for every product. If you have like seven then you're creating noise and the actual signal is getting lost. Think about like the one or two key things — for RoboKiller it was actually less about what was the user doing, it was more about are they actually getting spam calls and are we blocking calls on their behalf.”
Track one or two core engagement metrics per app — seven metrics create noise that buries the signal
Falzon explains that the right engagement metric is not always a user action — for RoboKiller, the product value was delivered passively so the metric was passive too: are calls being blocked, and were any legitimate calls blocked by mistake. The second question (false positives) was the leading churn indicator: when RoboKiller incorrectly blocked a real call, that user churned at high rates. Identifying the one or two metrics that actually predict revenue retention is harder than picking common vanity metrics, but far more predictive.
“Build towards that goal — don't just assume it's going to happen. Be thoughtful around who is a potential buyer, what can I do to make this more interesting to that buyer? The cleaner and more professionalized your setup is, the easier it's going to be to find a buyer.”
Build toward an exit from day one — know your buyer categories and what makes you attractive to each
Falzon outlines the three exit categories for subscription apps: app roll-up portfolios (most willing, most price-disciplined), private equity (prefer a portfolio over a single app, want visible profitability), and strategic acquirers (rare, value free users and brand over financials). Each buyer type values different things. The practical advice: choose your buyer category early and then build the metrics that make you attractive to that type, rather than optimizing generically and hoping.