Start small. Decide after.

No, and in most cases I would argue against it. The work takes what you already built, moves it onto infrastructure you own, and closes the gaps in it. Where part of the code really does need rewriting, that gets quoted separately so you can decide, rather than being folded quietly into a bill you already agreed to.

That is the point of the engagement. Your code, your GitHub repository, hosting, database, domain and secrets all end up in accounts created in your name, with you as the owner. I hold no key you cannot revoke in a minute without asking me first.

Yes. Those two are the most common by a distance, with Bolt and v0 close behind. Underneath the editor, these tools write fairly ordinary React and Node, which is exactly why moving your app across is realistic and a rewrite usually isn't.

Because it isn't the same job. A $600 migration copies your database from one host to another, which is a well-defined task and a fair price for it. This engagement also writes the access rules nobody ever wrote, rotates secrets that may already be in somebody else's hands, and spends real hours teaching you to run the result. If a straight database move is all you need, I'll say so on the call and point you at someone cheaper.

You might not need to, and I would rather you skipped it than resented it. If you are comfortable applying your own dependency updates, watching your own error rates, and being the person who gets up when something breaks at 2am, the engagement stands on its own without it. What the retainer buys is that I stay current on your codebase: security patches applied as they land rather than whenever you next look, monitoring that tells me before it tells your customers, and someone who does not need a week to remember how your app fits together. The founders who take it are usually the ones who do not want to be the only person alive who understands their own infrastructure. It starts after handover, and you can stop at the end of any month.

You'll know within the 72 hours the report takes, in plain language, ranked by what matters rather than by what sounds most alarming. What you do about it is your decision. Fixing it is quoted separately, so nothing arrives on an invoice you didn't agree to first.

We plan the cutover together and aim for no interruption at all. How close we get depends on your setup, mostly on the way your domain and database are configured, and I won't promise zero downtime before I have seen it. What I will do is tell you exactly what to expect before anything moves.

A senior engineer going through your app properly, with the report in your hands inside 72 hours. You get a written account of what you own and what is exposed, a recorded walkthrough of your own codebase, and a fixed quote if you want the work. It comes off the price of the engagement if you go ahead, and if there is nothing in there worth acting on you get the $750 back.

Pre-launch is the cheapest moment there will ever be to do this. No live users to migrate, and no incident to disclose if something was already wrong. Whether it is worth doing yet depends on how close you are to real customers, so ask me on the call and you'll get a straight answer either way.