November 19, 2026
What Is an MVP, and How Do You Launch a Digital Platform With Less Cost and Risk?
What a minimum viable product is, why start with one, how to decide what goes in, what to measure after launch, with a real example.

You have an idea for a digital platform: a marketplace for booking services, an app connecting two sides, or a system that solves a problem you know well in your sector. And you have two options.
Build the whole platform with everything you imagine, and launch it in a year. Or build the smallest version that proves the idea works, launch it in weeks, then build the rest based on what actually happens.
The second option is called an MVP. In most cases, it is the smarter one.
What is an MVP?
MVP stands for Minimum Viable Product: the smallest version of your product that is enough to test its most important assumption with real users.
The key word is “viable”. An MVP is not a poor or broken version of the product. It is a focused one: it does one essential thing, and does it well.
What an MVP is not
- Not a buggy beta. Users won’t give you a second chance if the first experience is bad.
- Not the full product at lower quality. It is a smaller product at good quality.
- Not just a presentation or a design. It is something people actually use.
Why start with an MVP?
- Lower upfront cost: you pay to build what you need now, not everything you might need one day.
- Lower risk: if your assumption is wrong, you find out after weeks, not after a year and a full budget.
- Learning from reality: real users use the product in ways you didn’t expect. That knowledge doesn’t come from meetings.
- Proof for investors and partners: a working platform, however small, is far more convincing than an idea on paper.
How to decide what goes into the MVP
This is the hardest part, because every feature feels “essential” when you think about it. These steps help:
- Identify the most important assumption. What must be true for the project to make sense at all? For example: “space owners are willing to list their spaces, and customers are willing to book them online”.
- Choose one main user. If your platform has two sides, which one must you convince first?
- Map only the core journey. The steps from the user arriving to getting value: search, choose, book, confirm. Everything outside that journey waits.
- Split features into three lists: essential now, useful later, and nice idea. The MVP is the first list only, and it is usually shorter than you expect.
- Ask: can this be done manually at first? Many features can be handled by hand behind the scenes in the first weeks, such as confirming bookings or matching requests, before they are worth automating.
A real example
On one project I worked on, the brief was a platform for booking spaces, connecting space owners with customers. The temptation to build everything was strong: reviews, messaging, advanced dashboards, reports.
But the first question was simpler: can someone find a suitable space and book it easily? So the work centred on that journey first, and the rest waited. You can read the details in the case study.
What to measure after launch
An MVP without measurement is just a small product. Before launch, decide what will tell you the idea works:
- How many people completed the core journey to the end?
- Where do those who don’t finish stop?
- Do users come back a second time?
- What do they ask for, or complain about, most?
The answers decide your next step: carry on and build the next feature, change direction, or stop before spending more.
Common mistakes
- An MVP that grows into a full product: “just one more feature” repeats until launch slips by months.
- Neglecting the experience because it’s “only an MVP”: small doesn’t excuse confusing. The core journey must be clear and easy. I explain why in What Is User Experience (UX)?
- Launching with no measurement plan: so you can’t tell whether it worked.
- A technical build that can’t grow: simple features don’t mean a throwaway build that has to be torn down completely later.
In short
An MVP is not just a way to save money; it is a way of thinking: start with the smallest thing that proves your idea is worth it, then let real users tell you what to build next.
If you have a platform idea and want to know what belongs in its first version, send me a short description using the form below. Defining MVP scope is one of the things I work on most with project owners.
Start a Project
Have a project in mind? Let's talk about what you need.
Whether you are defining a new digital product, improving an existing experience, building a website, or need support with a specific digital project, send me a brief overview and I'll suggest the best way forward.
A short brief is enough to start. I'll get back to you within two working days.
Direct
What happens next
- I read the brief and reply within two working days
- A 30-minute call to understand the situation
- A written proposal with scope and a fixed price