Skip to main content

What Recurr does

Recurr migrates mobile subscription apps off Apple and Google in-app purchase rails onto direct web billing. The app stays the product surface; pricing, checkout, and the subscriber relationship move to web. Each migrated subscriber compounds margin permanently — the gap between your app-store fee (15–30%) and your direct web-billing cost (Recurr’s 3.5% platform fee plus standard Stripe processing). Migration also pulls forward roughly 9% of migrated annualised ARR (net of store fees) as a one-time cash-flow release, using a 45-day settlement timing assumption. The audit shows your specific recovery; see where the recovery comes from for the math.

Where to start

Run the 60-second audit

Get your specific year-one recovery, steady-state recovery, and cash-flow release on your numbers.

Read the Subscriber Migration Playbook

The opportunity, the deployment framework, what your team ships, and the worked example at $5M ARR.

What is store-to-web subscriber migration?

The category definition: how existing app-store subscribers move onto web billing without changing the app experience.

Who it's for

Subscription apps on iOS or Google Play, $1M+ ARR, with reachable subscribers.

How it works

Audit → Pilot → Migrate → Compound. Wave-by-wave, gated on retention and payback.

Model assumptions

The store-fee, web-fee, migration-rate, and settlement-timing assumptions behind the public audit.

What changes for your app

  • Pricing flexibility. Same-day price changes, regional offers, and trials - no app review.
  • Margin recovery. Apple’s 30%/15% and Google’s 15% off the top become Recurr’s 3.5% platform fee plus standard Stripe processing — a structural step-change in unit economics. See where the recovery comes from for the worked math.
  • Cash flow. Web billing shortens the settlement cycle - a one-time cash-flow release as the existing app-store base unwinds.
  • Direct subscriber rails. Pricing, checkout, subscriber communication, and payment recovery move onto infrastructure you control. Broader lifecycle modules are roadmap, not the migration promise.

What stays the same

  • The app remains the product surface.
  • Subscribers who don’t accept the migration offer stay on app-store billing — nothing changes for them — and are re-approached in later quarterly waves.
  • No SDK, no app release, no engineering build on your roadmap.
For app-specific modeling, start with the 60-second audit. For fit, timing, and pilot scope, book a Migration Review or email matt@recurr.dev directly.