What separates an MVP from a market-ready product.
For founders in Adelaide and beyond: the difference between a prototype your team ships and a product your customers renew.
The MVP conversation has calcified into a caricature. Founders build the smallest possible thing, throw it at users, and hope. Most of what gets called an MVP is really a demo — enough to raise, not enough to renew.
There is nothing wrong with a demo, if you know that's what you have. The problem is that founders spend the year after the raise trying to convert a demo into a business, without ever going back and doing the product work that a real MVP would have forced them into.
The renewal test
A market-ready product is one a customer will renew after the honeymoon. That single test is more useful than any framework. It forces you to ask: after the novelty wears off, what problem does this still solve better than the alternative?
Apply the renewal test to your roadmap and it re-orders itself in about ten minutes. Every feature that only exists to close the first sale drops down the list. Every workflow that a real user has to survive on a Tuesday morning moves up. The founders who pass the renewal test almost never have the prettiest product — they have the one their customers cannot stop using.
The four things founders under-invest in
Every product that survives its second year invests in the same four things founders systematically under-fund at MVP: onboarding, support workflows, admin tooling, and telemetry. These are not glamorous. They are what turns a working prototype into a business.
Onboarding is what decides whether the first ten customers become the first hundred. Support workflows are what decide whether your team drowns at scale. Admin tooling is what decides whether the founder can go on holiday. Telemetry is what decides whether you know which features earn their keep and which are quiet drag on the codebase.
You do not need all four on day one. You need to know which one you're deferring, why, and what will break when you can no longer defer it. Founders who name the trade-off keep control of the roadmap. Founders who ignore it end up rebuilding the same product 18 months later, this time with paying customers watching.