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.

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 fee

From $10,000 USD, paid to reserve a pilot slot. The pilot fee scales with the size of the migration project. The fee is:
  • Credited against migration. When the pilot clears its gates and the engagement moves to full migration, the pilot fee is applied against the migration fee.
  • Refundable before kickoff. If internal alignment changes before the pilot starts, the reservation can be refunded or moved to a later window.
  • Committed at kickoff. Once kickoff starts, the fee pays for pilot work already underway. It is not a performance guarantee.
  • 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 fee covers

Once kicked off, the pilot covers:
  • Pilot wave design - cohort spec for 1-3 small waves, sized for statistical relevance against a matched IAP 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 typically runs over 2-3 weeks. 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.

​
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.

​
How to reserve

The reservation link comes after the Migration Review call. 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