Skip to main content
Recurr moves your subscribers to web billing through four controlled stages. Each one is proven before the next begins, so the program earns its way to scale. The stages describe how migration reaches your whole eligible book. They do not describe migration ending — the eligible book refills as new store cohorts mature, and the waves keep reaching them.

​
Audit

Size the opportunity first. The audit models the recovery and the cohorts on your own numbers, before any commitment — you see what a move is worth before you make one. See where the recovery comes from.

​
Pilot

Prove the motion on a bounded slice. A contained cohort validates the real migration: subscribers act on the message, checkout converts cleanly, app access continues, support load stays manageable, and churn holds inside the agreed guardrails. The pilot is deliberately small, so the proof is real before anything scales.

​
Migrate

Expand cohort by cohort as the signals hold, until the waves have reached your whole eligible book. Each cohort is earned by evidence — subscriber movement, billing health, and support signal — and the rollout stays reversible at the cohort level. Migration changes the billing rail for paying subscribers, so it moves at the pace the signals justify. This is where the migration fee activates; see Program Go-live.

​
Compound

Grow the connected web book. Migrated subscribers run on Oikos, and Kairos chooses the next motion for each one — the right offer, message, and timing — so the book keeps compounding long after the move. See Kairos. Compound is not an end state. Your eligible book refills as new store cohorts mature, and migration keeps reaching them at the same 5% — see ascension. The four stages describe how the program earns its way to scale, not a program that closes out.