A founder showed us their Bolt prototype recently. They apologized for the code quality before we even opened it. "I know it's messy — we'll need to start over."
We didn't start over. We treated the prototype as what it actually was: a spec.
The screens showed exactly what the product should do. The flows revealed how the founder thought about user journeys. The database schema — even the messy one — showed which relationships mattered. The copy on every button and error message reflected months of thinking about the problem.
That's not throwaway. That's the most detailed spec document most founders will ever produce. Typically, specifications are slide decks and bullet points. This was a working demo that real users had already clicked through.
We kept the UI almost entirely. Rebuilt the backend in Rails. Rewired the auth. Restructured the database. But we didn't redesign a single screen. The prototype told us everything we needed to know about what to build. Our job was figuring out how to build it for production.
If you've built something with AI tools: don't apologize for it. Walk us through it like you'd walk through a spec. Show us what it does, what you wish it did, and where it breaks. That's the best briefing we can get.
