RecurrRun the audit
Recurr Research · Written for the chief executive

A control decision, not a billing project

The question is whether the stores keep owning the billing relationship for most of your subscriber base, or whether that relationship moves onto a rail the business controls. Everything else is implementation.

On a representative $5M store-billed book
$1.1M

A year to the stores — roughly $21K a week, funded or not.

12 wks

Two weeks to a pilot result, ten to a migrated book. Four on the ramp.

8.2%

Of the entire base would have to cancel because of the campaign to erase year one.

Run these on your own book

Figures scale with the book: store fees track billings at your blended rate. Gated rollout pauses at 1–2% measured attrition.

What you would actually be deciding

Whether to own the railPricing, lifecycle motions and the subscriber relationship stop being store-mediated. That is the durable change; the fee saving is the visible one.
Whether to test firstA two-week pilot on a slice of your own base, against a matched holdout, returns a measured migration rate and a churn delta. The decision to scale comes after that, not before it.
Who owns it internallyMigration is not product, not growth, not platform — which is why in-house attempts stall. Someone has to own the decisions even when the operating work is bought.
Build or buyCapability is not the question. An in-house build is quarters before the first wave, and the delay is paid in store fees either way.

What is not on the table

No app release

The path runs outside the app, under Apple 3.1.3(b) and Google Play policy. No SDK, no binary change, no roadmap slot.

No forced march

Every wave is gated on measured attrition. Subscribers who decline stay on store billing, untouched.

No lock-in

The Stripe account, the subscriber records and the surfaces are yours from the first wave. Stop, and billing continues without us.

No dormant wake-ups

Dormant and at-risk cohorts are excluded from outreach by design. Migration targets the engaged book.

One thing the model cannot settle: how many subscribers accept. Every figure above assumes a migration rate, and the pilot exists to replace that assumption with yours before anything scales.

See the size of it on your book

Sixty seconds and two inputs. What the stores take today, and what comes back — on your numbers rather than a representative book.

Run your numbers
Where this comes from

This is a one-page reading of the full method, written for your seat. The whole argument — the fee decomposition, the cash-flow release, the cohort framework, the guardrails and the commercial model — is published in the store-to-web subscriber migration playbook. Twenty-nine minutes, no gate.

2026 edition · Every figure computes from the same model the audit runs on your numbers. The worked example is a representative book: $5M store-billed ARR, 22% blended store fee, 50/50 plan mix at $10/mo and $100/yr. Web figures carry the payment rails only and do not net Stripe Tax.