Stop Trying to Make Your MVP Perfect

Most of the founders we work with don’t have a building problem. They have a stopping problem. They know what they want to build, they can picture the finished thing in detail, and that picture is exactly the problem. The version in their head is polished, complete, ready to impress everyone. And that is the version they want to launch.

It is an understandable instinct, especially for founders who don’t come from a tech background. You only get one first impression, the thinking goes, so the first release has to be the full vision. Every feature a competitor has, plus the ones that set you apart. Smooth, finished, no rough edges.

That instinct is what quietly burns through early budgets and drags launch dates months to the right.

What an MVP actually is

The term gets thrown around loosely, so it is worth being precise. A minimum viable product, an idea popularised by Eric Ries in The Lean Startup, is not a smaller, cheaper version of the finished product. It is the smallest thing you can put in front of real customers to learn whether the idea holds up. The point is not the product. The point is the learning.

“Minimum” and “viable” are doing equal work in that phrase. Viable means it has to genuinely solve the problem for someone, not be a hollow demo. Minimum means nothing beyond what is needed to test that. The hard part, and the part founders resist, is that “minimum” almost always means leaving out features you are certain you need.

The maths is uncomfortable

Until real customers use your product, every feature you build is a guess. A well-researched guess, perhaps, but a guess. And the evidence on guesses is not kind. One oft-cited study from the Standish Group found that 64% of the software features they looked at were rarely or never used. Most of what gets built turns out to be weight, not value.

So when you insist on launching with the full feature set, you are spending real money, in AUD, hard-coding your guesses before a single customer has told you which ones are right. You spend more than you had to. You launch later, which means you start learning later. And the product is now more tangled and more expensive to change, right at the stage when you will most need to change it.

A tighter loop, not lower standards

The alternative is not sloppier work. It is a shorter cycle. Build a little, put it in front of customers, watch what they actually do, and let that decide what you build next. Eric Ries calls it build, measure, learn. The Agile world has its own language for the same idea, along with a fair amount of ceremony layered on top that you can usually ignore. Strip away the jargon and the workshops and what matters is simple: short cycles, real feedback, and a willingness to change direction based on what you see rather than what you assumed.

We are not Agile purists, and we are wary of anyone selling Agile as a religion. Stand-ups and sprint boards don’t make a product good. Listening to customers and acting on what they tell you does. The framework earns its keep only to the degree it keeps you close to reality.

Getting to a real MVP is mostly cutting

In practice, finding your MVP is an exercise in subtraction. Take the full vision and ask, honestly, of each feature: does the idea fail without this on day one? Most features don’t survive that question. The ones that do are your MVP. The rest go on a list for later, when you have evidence they are worth the money.

And some of what you cut doesn’t need to be built at all, at least not yet. We often find that a feature a founder was ready to pay to develop can be handled by hand in the early days, with a person quietly doing the work behind the scenes. Done on purpose, that is not a shortcut or an embarrassment. It is frequently a better early experience, a white-glove touch while the numbers are still small, and it shows you exactly what the eventual software needs to do before you spend a cent building it.

Sometimes the most honest version of this advice is harder still: the idea isn’t ready to build yet, and the right next step is a conversation, not a quote. We have told founders exactly that. It tends to be cheaper than what they walked in expecting, and it is always more honest.

If you are weighing this up

If you are sitting on an idea and trying to work out how much of it to build first, that is a conversation worth having. Speak to us about your MVP strategy. We can help you build it, or simply be an adviser.