When the generator stops and reality starts
Different tools, remarkably similar endings. Something is generated quickly, it demos beautifully, and then it meets a second user.
What tends to go first, in order
- Sign-in. Accounts that look separate but share one pot of data underneath.
- Saving. Information written in two formats, or written twice, or not written at all when two people act at once.
- Edges. Anything a demo never does: an empty list, a name with an apostrophe in it, two people saving at once, a dropped connection halfway through.
- Deployment. It runs on the machine it was made on, and nowhere else, reliably.
This is not a failure of nerve on your part. Generated code is written to satisfy the next prompt, not to be lived in for three years. Nobody asked the tool what happens when 400 people arrive at once, so nobody got an answer.
What we keep, and what we build underneath
We keep the product thinking, the screens, the flow, and the decisions you have already made about what this thing is. That is genuinely valuable and we do not throw it away.
Underneath it we build a data design that holds up, real accounts and permissions, error handling for the ugly cases, a deployment that is repeatable, and a record of how it all fits together so you are never again dependent on one person's memory.
Where it ends: in your hands, with nothing withheld and nothing rented back to you afterwards. What every rescue includes sets out the paperwork.