Ask five founders what “MVP” means and you’ll usually get five versions of the same answer: the smallest version of the product we can launch with. That definition has quietly taken over, and it’s not what the term was supposed to mean.
The MVP that isn’t
A “minimum viable product” built this way is still a product. It has a login flow, a settings page, an onboarding sequence, a support email, just fewer features than the eventual v2. It takes weeks or months to build, because a smaller product is still a whole product. And when it launches to lukewarm numbers, the temptation is to conclude the idea was wrong, when what actually happened is the build was expensive and the test was slow.
What an MVP is meant to test
The original point of “minimum viable” was never about shipping a smaller thing. It was about testing the riskiest assumption in the idea as cheaply and quickly as possible. Sometimes that genuinely does need a working product. Often it doesn’t. It needs:
- A clickable prototype that lets a real user attempt the actual task, even if nothing behind it is real.
- A landing page and a genuine call to action, to see if anyone with the problem actually wants the solution.
- A concierge version: doing the “product’s” job manually for a handful of real users, to learn what actually matters before automating any of it.
Each of these can answer the real question (does this solve a real problem for a real person) in days, not months, and for a fraction of the cost of a build.
The question that actually matters
Before writing a single feature list, it’s worth asking: what is the one thing we’re not sure is true, and what’s the cheapest way to find out? Usually that’s not “will people use a full product with these ten features”. It’s something much narrower: will this specific person do this specific thing, given this specific nudge.
Answer that first. Build the smaller-but-still-a-whole-product version only once you know it’s worth building at all.
Not sure whether your idea needs a full build or a fast prototype to test it properly? Get in touch and we’ll give you a straight answer.
← Back to all insights