MVP or prototype: the difference that decides your budget#
27 October 2026 · updated: 27 October 2026
What an MVP wants to be#
A minimum viable product is a product: cut down, but on the market. It has real users, real data, operational responsibility — and it must not break anything when people use it. An MVP is not a stage on the way to software; it is software that carries responsibility from day one: security, privacy, support, operation. That is why a sensible MVP project doesn't start with code but with questions: who pays for what? What happens to the data? Who is liable when something goes wrong?
What a prototype wants to be#
A prototype has a narrower assignment: to make a claim testable. Does the process run the way we understood it? Can your staff work with it? Does the flow function with real data? A prototype carries no market responsibility yet — it has to demonstrate, not be operated. That is exactly why it can be built in four concentrated weeks: the scope is one core process, not a product with everything around it.
Where the costs diverge#
| Prototype | MVP | |
|---|---|---|
| Goal | make one claim testable | survive on the market |
| Scope | one core process | everything the market demands |
| Operation | test environment, real sample data | production, support, security |
| Typical duration with me | 4 weeks (€4,800) | from a production project per scope |
| Risk of being wrong | stop after week 2, ~€2,400 | the whole budget is in the market |
The sentence behind the table: an MVP without a prior prototype moves the learning behind the biggest expense. If the core assumption is wrong — the process doesn't work that way, the users don't adopt it — you only find out after everything has been built. With a prototype, the same insight costs a fraction and arrives four weeks earlier.
When you can go straight to the MVP#
There are cases where a prototype would be wasted time: when the assumptions are already tested (from a previous project, from a client process that ran in the old system) and all that remains is clean implementation. Then you start from a scoping workshop directly into production development — fixed scope, fixed price, without the prototype detour.
How I offer it#
The clickable prototype (€1,200, one week) clarifies what should be built. The prototype sprint (€4,800, four weeks) tests whether the process runs. Only afterwards — with the insights collected — does the word MVP make sense. That is why "MVP" is only a secondary term with me: the primary ones are prototype, fixed scope, fixed price.
Soft CTA: you don't know which side your project is on? Free 20-minute intro call — there, "MVP or prototype" becomes a concrete recommendation with a price.