How it works
Self-service first. Optional, quoted human help when you need it. Your project history comes with you either way.
1. Write a brief
Who uses the app, what they need to do, what is out of scope and how sensitive the data is. You set a spending limit up front.
2. Define your records
List the kinds of records the app manages and their fields. Each change creates a new specification revision.
3. Approve a plan
Each build task proposes a plan: the files it may change, the tools it may use, its migration risk and its maximum cost. Nothing paid runs until you approve that exact plan.
4. Watch it build
Work happens in an isolated workspace. You see real states — working, waiting for you, paused at a budget limit, failed — never a made-up percentage.
5. Review and accept
See the diff, the test results and a protected preview with synthetic data. Accept the exact revision or discard it. You can restore any checkpoint later.
6. Export or get help
Download a complete source archive at any time. If you want launch help, request an assessment on the same project; a person reviews it and quotes a scope.
Costs and limits
Every paid step reserves its maximum possible cost before it starts. If any limit — task, project, workspace or platform — cannot cover the next step, work pauses and an owner must deliberately raise the limit. Limits stop future work; they cannot undo costs a provider has already incurred, and late provider reports are reconciled before anything is charged.
What a source export is not
A source archive is not a backup of databases, uploaded files, sign-in accounts, DNS or third-party accounts. Moving those is a separate, explicit step.