RevenueCat has always been where app developers go to handle subscriptions. In this interview, Perttu Lähteenlahti talks about how that tooling is shifting as AI gets pulled into more of the workflow.
One example is the paywall editor. What used to be a drag-and-drop tool is turning into something much closer to generation: give it a design system, a screenshot, or the shape of the app, and it can build the paywall for you. That is a very practical change, as paywalls are one of those jobs teams have to ship, tune, and revisit constantly, and they are usually more tedious than anyone wants to admit.
That same pattern shows up elsewhere in the product. Perttu talks about RevenueCat’s MCP work, platform-specific skills, and a broader push to make AI useful on top of the subscription data teams already have. The direction is pretty clear: ask better questions inside the dashboard, get experiment ideas back, understand how the app is performing, and move faster without turning every decision into a manual analysis task.
The interview also gets into what is coming next. Multi-page paywalls, fuller onboarding flows, more support for ads, deeper monetization data, bigger moves around virtual currencies, and more emphasis on React Native Web all point in the same direction of RevenueCat treating AI as a valuable part of how monetization tooling itself works.
There is also a useful product lesson underneath all of this: RevenueCat moves toward whatever developers are already using, whether that is React Native, Flutter, Unity, Kotlin Multiplatform, or something newer. The AI layer follows the same logic, so if developers are already building with agents and assistants, the monetization stack has to meet them there.
