Skip to main content
Onboarding prepares the customer, Recurr, and the subscriber experience. Kickoff is the point where everything is confirmed ready and the first pilot cohort is contacted.

​
Onboarding steps

1

Confirm the operating team

Name the executive owner, finance owner, technical contact, support contact, and day-to-day migration owner.
2

Confirm the payment rail

Stripe is the default rail. Existing Stripe setup is reviewed, or a new Stripe path is prepared. Paddle can be scoped where merchant-of-record coverage is required.
3

Confirm access continuity

Recurr maps how migrated subscribers will continue receiving app access through RevenueCat, Adapty, Stripe, Paddle, Firebase, or your custom backend.
4

Prepare subscriber surfaces

Email, checkout, billing, help, and cancellation guidance are prepared in your brand.
5

Lock pilot cohorts

Recurr and the customer confirm the first cohorts, comparison context, and gating thresholds.

​
Customer involvement

The customer approves the decisions. Recurr runs the workflow. Typical customer work is concentrated around access to systems, technical review, brand and content approvals, support policy review, and the stakeholder approvals already captured in the Migration Hub. After signing, the operating work is tracked in the Migration Dashboard.

​
Kickoff readiness

The first pilot cohort should not be the first time the program discovers a missing owner, a broken access path, or an unclear support rule. Before kickoff, confirm:
  • Owners named across executive, finance, technical, support, and day-to-day migration
  • Pilot scope, fee, and Oikos first-year treatment understood, and the fee reconciliation path agreed
  • First cohorts approved, eligibility and tenure/churn logic reviewed, and exclusions confirmed for hard-to-reach or unsafe cohorts
  • Messaging, cadence, and offer framing approved
  • Sender identity, DNS authentication, and Apple private-relay registration ready
  • Branded checkout, billing, and help surfaces ready, with TLS and routing tested per surface
  • Payment rail ready for live transactions, and the access continuity path tested
  • Analytics and subscriber signals mapped, and the support diagnosis path confirmed
  • Conflicting lifecycle, paywall, recovery, or winback campaigns paused or made state-aware
  • Refund, dispute, and overlap handling agreed, and cohort gate thresholds agreed

​
Kickoff

The pilot cohort launches only when the agreed owners can answer:
  • Who is being contacted?
  • What path will they see?
  • How will access continue?
  • What happens if they need help?
  • What signals decide whether the next cohort scales, pauses, or adjusts?