Skip to main content

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.

Cohorts aren’t picked at random. Each wave targets a slice of the eligible base defined on five axes, each tested individually during the pilot so migration cohorts can sequence based on what cleared.

​
The five axes

Tenure

How long the subscriber has been continuously paying. 12+ months on a renewal cycle behaves very differently from a 3-month new subscriber. Long-tenure cohorts often migrate at higher rates.

Geo

Primary markets vs secondary. Compliance and reachability vary by region; payment-method support varies (e.g., SEPA, Brazilian Pix). Sequencing by geo lets you start where the path is clearest.

Engagement

Quintiles of in-app activity. High-engagement subscribers are typically easier migrations (they care about the app); low-engagement subscribers carry more churn risk on any touchpoint.

Renewal window

Time until next renewal. Subscribers near a renewal cycle tend to be more receptive — the renewal is on their mind. Longer-window subscribers can wait, and waiting compounds the recovery.

Plan

Annual vs monthly, premium vs basic, trial vs paid. Annual cohorts have different conversion mechanics than monthly (card-save vs early-charge); premium tier subscribers often have higher migration intent.

​
How the axes get used

Pilot waves test each axis individually:
  • Pilot wave 1: annual + 12+ month tenure + top-engagement quintile + primary geo
  • Pilot wave 2: monthly + 3+ month active + top engagement + primary geo
  • Pilot wave 3: annual + 12+ month tenure + mid-engagement quintiles 3–4 + primary geo
Each pilot’s result tells you something different — wave 2 isolates plan-mix sensitivity (vs wave 1’s annual baseline), wave 3 isolates engagement-tier sensitivity (vs wave 1’s top-engagement baseline). Migration waves then sequence by what cleared, with the strongest cohorts first. A typical engagement runs 5–7 migration waves at up to 10% of the eligible base each, with the cohort spec tightening or widening based on what the prior waves showed.

​
Why five and not more

There are more axes you could split on (signup source, device tier, language, billing currency, etc.). Five is the count where:
  • The combinatorics stay tractable. Five binary axes gives 32 cells; more axes explode the cohort space and starve any individual cell of statistical power.
  • The axes are independently meaningful. Tenure, geo, engagement, renewal window, and plan all carry distinct migration-rate signal. Adding a sixth typically correlates with one already on the list.
  • The reporting fits on one screen. A wave summary that’s one screen tall keeps the gating decision fast; a wave summary that scrolls is a slower decision.
If your app has a meaningful axis we haven’t named (e.g., a critical signup-source split), it gets folded in during the Migration Review. Operational safeguards →