Twice in the last fortnight I’ve met non-technical founders who had been building for more than a year without a single real user touching the product. That isn’t unusual. I’ve had north of 15 of these conversations this year alone.
When I ask why nobody has seen it yet, the answer is usually some version of “it’s not ready”. The worry is that early users will see how thin it is and lose interest.
They won’t want it anyway #
That worry is almost always misplaced. The people you show an early prototype to are almost certainly not going to want it in its current form, however long you polish it. That’s fine, because getting them to want it was never the point. You’re showing it to them to find out what you should be building.
So treat the prototype as a question you put to real users. Watch what they try first and where they get stuck, and listen for what they ask for that you never thought to build. Their answers turn your guesses into decisions.
Every day without an answer adds a guess #
Every decision before launch is a guess, and each day without feedback stacks more guesses on top of the early ones. After a year, a wrong call from the second month has ten months of work sitting on top of it.
The two founders I met show what that costs. One is rebuilding the core of a profitable product, and no new feature has reached a customer since the rebuild started. The other is pre-revenue, paying a low-firepower outsourced team and watching the bill grow while the opportunity gradually passes by.
I gave both the same advice: get something small in front of real users this month, then let what they do tell you what to build next.
Ask small #
Before an MVP, the question can be a prototype with no backend at all, where you do the “automation” by hand behind the scenes. A prototype with a working backend is now almost as fast to build, so that’s an option too. For a rebuild, it means shipping one slice behind a feature flag instead of switching everything over on one big launch day.
If your engineers can’t ship something that small in under a month, you have a different problem, and for most startups in 2026 it’s one that shouldn’t exist.
If you haven’t started building yet, the step before all of this is in Before you start your MVP.