Keep, improve or rebuild: what happens to your AI-built prototype
A prototype you built yourself is worth bringing. How Planning decides what to keep, what to improve and what to rebuild before customers rely on it.
Prototypes2 min read
AI tools let someone with no coding background put together a working demo in an afternoon. That is useful. A prototype you can click through says more about your idea than a document does, and it gives everyone something concrete to talk about.
A demo and a product that customers rely on are different jobs, though, and the gap between them is easy to underestimate.
What a prototype proves, and what it leaves open
It proves the idea can be shown. On its own it does not answer who all the users are, what each of them needs to get done, what happens when something goes wrong, or how you will run the product once real customers depend on it.
How Planning looks at it
Planning includes an assessment of anything you already have, including AI-built work. Each part lands in one of three groups.
- Keep: screens, flows, wording or code that already does the job.
- Improve: parts that are right in intent but need work before customers use them.
- Rebuild: parts that would cost more to repair than to redo, or that cannot carry the first release.
Nothing that still works is thrown away for the sake of starting fresh. The call is made against the first-version scope, not against a preference for our own code.
Bring what you built
A link, a screen recording or a few screenshots are enough for the call. No clean-up needed first.
Book an introductory call