YC Root AccessRevenueCat: Powering Subscriptions for the App Economy
CHAPTERS
RevenueCat’s core mission: make in-app purchases painless and boost app revenue
Jacob explains RevenueCat as subscription/in-app purchase infrastructure that helps developers monetize without getting bogged down in payments plumbing. The product promise is straightforward: easier implementation, fewer headaches, and better outcomes for app businesses.
Why in-app subscriptions were such a mess: rebuilding payments over and over
Jacob and Miguel describe firsthand pain from building subscription systems at a previous mobile app company. A huge share of engineering time went into monetization work that wasn’t differentiating, including dealing with multiple app stores and changing requirements.
The cross-platform gap Apple/Google didn’t solve (and why that left developers stuck)
They argue Apple and Google lacked incentives to make a unified, cross-platform solution that gave developers a single view of their subscription business. RevenueCat positions itself as the neutral layer that standardizes and unifies data and workflows across platforms.
From internal solution to startup: generalizing the “RevenueCat way”
They had solved the problem for one app, but the company was born from the insight that the same solution should be generalized for tens of thousands of apps. Their lived experience created credibility in early customer conversations and helped them set a de facto standard for how developers think about subscriptions.
Choosing to start: timing, founder motivation, and committing to the leap
Jacob and Miguel discuss why they left jobs to start the company: personal founder ambition, love of “zero to one,” mutual respect, and a timing window. Jacob set a personal deadline (around turning 30) to finally start a company after years of discussing the idea.
YC and early go-to-market: “do whatever it takes” to get the first customers
Jacob details scrappy early customer acquisition: reaching out as an iOS developer, offering to fix code issues in exchange for SDK adoption and a revenue share. During YC, warm intros and YC brand credibility accelerated adoption and created compounding social proof.
Finding product-market fit: organic pull, breaking servers, and overwhelming demand
They describe PMF as the moment growth happens without heroic founder selling—and when infrastructure starts failing under load. Customer demand outpaced their bandwidth, and a PMF survey returned extremely high scores, reinforcing the signal that they’d hit a strong fit.
Selling to developers without “sales”: technical pull, long-tail leverage, and word of mouth
Their advice: don’t do traditional enterprise-style sales motions for developer tools. Instead, make adoption easy, answer technical questions well, and let developers pull the product in—while treating indie/long-tail developers as a powerful distribution engine.
Scaling the organization: staying close to customers at 100+ people
As the team grows past 100, they emphasize intentional customer proximity: founders staying reachable, building customer-heavy information feeds, attending developer conferences, and encouraging everyone internally to talk to customers without bureaucracy.
Operating discipline and transparency: consistent metrics and investor updates
Jacob explains the habit of sending consistent investor updates and keeping metrics stable over years. They treat it as a discipline mechanism that forces honesty, aligns a distributed team, and creates a shared “ground truth” for decision-making.
Building a remote-first company (pre-COVID): hiring advantages and operating systems
RevenueCat became remote-first largely out of necessity due to Bay Area hiring competition, then formalized the approach by borrowing from GitLab-style practices. They highlight benefits in talent access and coverage, plus the need for strong systems, documentation, and a clear compensation philosophy.
Competition and platform risk: thriving alongside Apple/Google/Stripe
They acknowledge platform dependency and the risk of incumbents, but argue scale and relationships create some protection. The broader takeaway: most modern businesses rely on major platforms, so founders should focus on building indispensable value rather than worrying about every ‘what if.’
Co-founder dynamics over time: trust, mutual respect, and investing in the relationship
Jacob and Miguel describe the co-founder relationship as unlike friendship, marriage, or coworking—yet containing elements of all. Their guidance centers on mutual respect, assuming good intent during disagreements, and making time to strengthen the relationship, especially in remote settings.
Market shifts and the Epic vs. Apple fallout: alternative payments and real-world impact
They cover how the Epic legal battles led to a U.S. ruling limiting Apple’s ability to block alternative payments links. RevenueCat observed the impact as modestly positive but smaller than many predicted, suggesting app store economics are closer to “market optimal” than expected.
Founder advice and long-game mindset: ignore noisy advice, don’t quit, build the company you want
Their closing advice blends pragmatism and resilience: expect hardship, talk to customers constantly, and trust yourself over external advice. Jacob emphasizes building a culture you enjoy, focusing on month-to-month progress, and treating perseverance as a decisive competitive advantage.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome