> ## Documentation Index
> Fetch the complete documentation index at: https://recurr.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How it works

> Audit → Pilot → Migrate → Compound. The Controlled Migration Framework, with the meetings and deliverables you'll see at each phase.

Engagement runs as a four-phase framework: **Audit → Pilot → Migrate → Compound**. Each phase has clear gates, defined deliverables, and a small number of customer touchpoints — meetings and artifacts you'll actually see.

The audit you ran on the website is Step 1. You're already on the track.

## Audit — Week 1

**What it does:** quantify fee exposure and recovery cases on your numbers, pressure-test fit, and produce a decision-grade scope for a safe pilot.

Two meetings, three deliverables, plus an optional stakeholder session:

|                           | What                                                                                  | When                                                           |
| ------------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
| Audit                     | 60-second self-serve calculator + emailed PDF                                         | Now                                                            |
| **Migration Review**      | 30-min founder-led call                                                               | Within \~1 week                                                |
| Migration Brief           | Quick-turn document summarizing the call                                              | Same evening as the Migration Review                           |
| **Migration Walkthrough** | 60-min demo-led call with your team to pressure-test scope                            | Booked at the Migration Review — your team joins via the Brief |
| Migration Analysis        | Decision document: cohort spec, gating thresholds, pilot scope, implementation window | Walked at the Walkthrough, delivered same evening              |
| Migration Agreement       | Pilot terms, MSA + DPA, reservation mechanics                                         | Signs before pilot kickoff                                     |
| Stakeholder Alignment     | Optional working session with finance + legal + tech                                  | Where buying committees need it                                |

**Output:** signed agreement + reserved pilot slot.

## Pilot — Weeks 2-3

**What it does:** validate the migration mechanics, the cohort spec, and the holdout-relative churn delta — against measurable data, not hope.

<Steps>
  <Step title="Pilot onboarding">
    Stripe Connect account live in your name; DNS CNAME pointed at branded checkout; entitlement integration wired into RevenueCat, Adapty, or your custom backend; first wave queued. \~2-4 hours of engineering time on your side.
  </Step>

  <Step title="Pilot waves run">
    2-3 waves of 1,000-1,500 subscribers each, stratified across cohorts, against matched store-billing holdouts. Recurr operates the campaign; your team reviews wave copy.
  </Step>

  <Step title="Weekly Results & Strategy Review">
    30-45 min, every wave week. The dashboard data + the next wave's recommendation. Your team signs off.
  </Step>

  <Step title="Pilot debrief — go / no-go">
    Decision point. If retention, payback, billing health, and support load clear pre-agreed gates → move to Migrate. If not → adjust cohort spec, run additional pilot waves, or close the engagement.
  </Step>
</Steps>

**Output:** decision-grade data on migration rate, holdout-relative churn, and a recommended scope for full migration.

## Migrate — Weeks 4-12

**What it does:** roll the migration across your subscriber base, wave-by-wave, gated on the prior wave's results.

<Steps>
  <Step title="Migration kickoff">
    Wave plan locked from pilot learnings. 10 weekly waves, each moving roughly 10% of the addressable base — every cohort starts in week one, stratified. Compressible to roughly four weeks on strong performance.
  </Step>

  <Step title="Wave-by-wave rollout">
    Waves ship weekly. Per-cohort volume ramps wherever benchmarks clear. Auto-pause if thresholds breach.
  </Step>

  <Step title="Weekly Results & Strategy Review">
    Same cadence as pilot. Your role: review, sign off, exception calls.
  </Step>

  <Step title="Migration debrief">
    Final wave closes. Migrated cohort sized, recovered margin booked, ongoing rail confirmed.
  </Step>
</Steps>

**Output:** scaled migration across proven cohorts. Recurring margin lift booked for as long as each migrated subscriber stays active.

## Compound — ongoing

**What it does:** layer new web acquisition onto the migrated base; let the book shift from store-rail dependence to web-rail compound year over year.

<Steps>
  <Step title="Compound strategy session">
    Working session after the migration closes. Where new web acquisition routes, which channels make sense at the recovered LTV, what the next 12 months of platform motions look like.
  </Step>

  <Step title="Ongoing platform motions — passive">
    New web acquisition continues at the lower fee structure. Win-backs, retention rail, branded billing communications — all run on the rails you now own. Retention safeguards continue measuring against the matched holdout.
  </Step>
</Steps>

**Output:** structural shift from store-rail dependence to web-rail compound. Each year more of the book renews on web fees instead of store fees.

## The three things that keep the framework safe

This is the same machinery on every wave, in every engagement:

* **Wave-based pilots with matched store-billing holdout.** Each wave runs alongside a control cohort kept on store billing. Churn impact is measurable, not assumed.
* **Multi-axis cohort selection.** Tenure, geo, engagement, renewal window, plan — the pilot samples across all five axes at once, and rollout volume ramps wherever each cohort's benchmarks clear.
* **Store-policy compliance.** Migration runs entirely outside the app: email + owned channels, branded web checkout, no in-app messaging or links. The app binary stays untouched.

For what each function on the buying committee owns through the engagement, see [for your role →](/for-your-role/founders).