> ## 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. # For founders > What migration looks like from the seat that owns the decision: ROI, risk, time-to-decide, and what happens during the engagement. If you're the founder or CEO, your job during a migration is decision-grade input + sign-off — not running the operation. Here's the shape from your seat. ## What you decide 60 seconds, no commitment. Output: dollar magnitude on your specific numbers. [Run it →](https://recurr.dev/audit) 30 minutes, founder-led, free. Output: clear go/no-go on a safe pilot path for your app. [Book it →](https://recurr.dev/apply) From \$10K, credited against migration, refundable before kickoff if internal alignment changes. The first real commitment. During migration, each wave's results inform whether the next ships. \~1 hour per week of your attention. ## What you don't decide * Cohort spec at the operational level (Recurr proposes; you approve) * Email copy (Recurr writes; you can review or trust the framework) * Wave timing within agreed parameters * Integration mechanics (Recurr handles; your CTO's involvement is light) ## What you should keep an eye on * **Migration rate** — how much of the eligible base is moving onto web rails * **Holdout-relative churn delta** — is migration costing you retention? * **Cash-flow release landing** — when does the cash-flow release hit your account? * **Recurring margin lift** — does the post-migration P\&L look like the audit projected? The dashboard surfaces all four in real time. You're not chasing reports. ## What changes for you over time * **Through pilot:** active engagement, weekly review, decision-grade attention * **Through full migration:** lighter — gating decisions are largely procedural once the framework's working * **Post-migration:** mostly invisible. Recurring margin shows up in your P\&L; new web subscribers route through the lower fee structure automatically. ## When this is wrong for you If you're not the kind of founder who likes wave-by-wave detail and quick decisions, migration may feel slower than you expect. The framework's safety is in the gating; gating means decisions, and decisions need a decision-maker. If you'd rather hand it off and check back in 12 weeks, that's not how a migration goes. If that's a dealbreaker, the Migration Review is the right place to surface it. The framework can tilt toward less-frequent gating in exchange for tighter cohort scoping, but it can't run blind.