Skip to main content
After the Migration Review confirms a safe path, the pilot is the next commitment. The reservation is designed so the buyer signal is real while the pre-kickoff alignment risk is contained.

Pilot deposit

From $10,000 USD, paid to reserve a pilot slot. The pilot deposit scales with the size of the Migration Program. The deposit is:
  • Credited against migration. When the pilot clears its gates and the engagement moves to full migration, the deposit is applied against the migration fee.
  • Refundable before kickoff. If internal alignment changes before the pilot starts, the reservation can be refunded (minus payment processing) or moved to a later window.
  • A deposit, not a price for an experiment. It is a commitment device around a reserved implementation window, credited in full against the migration fee. Once kickoff starts, it is committed.
  • Paid by card or bank transfer. Whichever is easier for your finance team.
This shape is intentional: the reservation creates real commitment around a real implementation window. Recurr gets a credible signal that the engagement is serious; the customer gets a clean way to manage internal alignment before work starts.

What the pilot deposit covers

Once kicked off, the pilot covers:
  • Pilot wave design - cohort spec for 2-3 waves of 1,000-1,500 subscribers each, stratified across cohorts and sized for statistical relevance against a matched store-billing holdout
  • Email composition + send - Recurr writes and sends the migration emails for each pilot wave
  • Web checkout setup - branded checkout on your subdomain, theme matched to your brand
  • Stripe Connect onboarding - Connect account in your name, configured for application-fee flows
  • Entitlement integration - wiring into your RevenueCat, Adapty, or custom backend
  • Daily wave reporting - observability dashboard with the live cohort metrics
  • Kickoff pack - concise pilot scope, owners, access requirements, and wave-readiness checklist
The pilot runs over two weeks - 2-3 waves of 1,000-1,500 subscribers each, 2,000-4,500 in total. The deliverable at the end is decision-grade data: migration rate, holdout-relative churn, billing health metrics, and a recommendation on whether and how to proceed to full migration.

Implementation windows

Pilot capacity is deliberately limited while the framework is founder-led. Recurr only offers windows that can actually be serviced. The slot language is simple:
StatusMeaning
AvailableA near-term implementation window is open
HeldA window is temporarily held while the buyer reviews the Migration Analysis
ReservedThe pilot deposit is paid and the kickoff window is confirmed
If the next realistic window is too far out, that is surfaced before payment. The point of the reservation is to create commitment around a real kickoff window, not to park a prospect in limbo while app-store fees keep accruing.

What happens at the end of the pilot

Three outcomes:

Strong fit, scale up

Pilot clears the gates. Engagement moves to full migration; the pilot reservation is credited against the migration fee.

Adjust + iterate

Pilot data suggests the cohort spec needs adjustment before going broader. Additional pilot waves run; full migration follows once the gates clear.

Honest pass

Pilot data shows the migration is unlikely to land cleanly for this app. The engagement ends at the end of the pilot. No full migration fee is due.
The third outcome is rare but explicitly available. The framework’s job is to find out, not to push through. The pre-kickoff refund window is separate from this pilot outcome.

Performance fees during pilot

During the pilot, performance pricing accrues normally on the migrated cohort — subscribers who convert through pilot waves generate performance-fee balances per the standard mechanic, deducted at settlement across the 12 months that follow. If the pilot does not proceed to full Migration Program (mutual nogo decision): the unpaid performance-fee balance on the pilot cohort voids alongside the pilot’s commercial close-out. Recurr earns only on the months the pilot subscribers paid through; subsequent months void. This is parallel to the standard void-on-churn mechanic, applied at the program-decision level rather than the per-subscriber level. For the standard mechanic, see performance pricing →.

Full migration fee

Pilot and full migration run under one agreement, signed upfront - the pilot is phase one. Phase 2 proceeds on the floors agreed in that document, and you can cancel for any reason at the end of the pilot. The migration fee is not published as a fixed public price because the scope depends on app size, stack, cohort complexity, and operational support needs. For qualified apps, full migration is typically scoped below one month of current app-store fees. See pricing model → for the full fee structure.

How to reserve

The reservation link comes after the Migration Review call, inside your Migration room - the private hub where your whole team sees the deal. It’s not on the public site - the link is per-customer, generated after the call confirms strong fit and an implementation window is available. Run the audit -> Book the Migration Review -> reservation link arrives via email after the call. The Migration Analysis