Skip to main content
Back to Glossary (M)
Glossary · M

MVP (Minimum Viable Product).

A minimum viable product (MVP) is the smallest working version of a product that already delivers complete value to real users and therefore produces meaningful feedback. It is not a cheap half-product but the fastest honest test of whether an idea actually gets used in everyday work.

Illustration of "MVP (Minimum Viable Product)": Comparison: MVP vs Later MVPCore featureLoginPaymentAnalyticsApplive in 6 weeksWinnerLaterAnalyticsiOS appIntegrationsMultilingualafter feedback→

MVP (Minimum Viable Product) — Explained in Detail

The term comes from the lean startup movement and is routinely misused. An MVP is not a stripped-down version of the desired product with something missing everywhere; it is a complete solution for one single, narrowly cut use case. The question is not 'what can we leave out?' but 'which one workflow has to work end to end for someone to open the tool voluntarily a second time?'. Everything that does not carry that workflow — roles, reporting, multilingualism, design polish — is deliberately deferred. That discipline separates an MVP from an unfinished product nobody takes seriously.

An MVP is a measuring instrument, not a milestone. Before it is built, you define which observation supports the idea and which refutes it: how many of the invited people complete the workflow, how many come back after a week, how often the old way gets chosen anyway. Without that definition set in advance, every result is interpreted favourably in hindsight. Who tests also matters: colleagues and friends are polite, affected or paying users are honest. An MVP only ever demonstrated internally produces applause instead of insight.

A practical example: a service business wants to replace a quoting process that currently runs on Excel and email. The MVP is not 'a CRM' but exactly one workflow — capture the enquiry, generate the quote from text blocks, send it as a PDF, set the status to won or lost. No permissions system, no accounting interface, no reporting. Three employees work with nothing else for four weeks. If all three stay with it voluntarily and stop opening Excel, expansion is justified. If the opposite happens, a few weeks were spent rather than half a year.

With us, a prototype or MVP for validating an idea starts at CHF 10,000; a fully built product sits well above that. The figure is deliberately meant as a boundary: anyone spending a multiple of it on the first answer to 'does anyone actually want this?' is usually buying features rather than insight. And not every idea needs bespoke software. If the workflow can be covered by an existing standard product, a spreadsheet or a deliberately manual process, that is the faster and cheaper test. Custom development pays off where no standard tool fits the workflow cleanly.

MVP, prototype and clickable mock-up compared

Stage
What it proves
Clickable mock-up
Shows screens, stores nothing. Proves only whether a workflow is understood.
Prototype
Usable, partly with real data. Exposes misunderstandings in workflow and interface before the domain logic is built.
MVP
One workflow complete and live, with real users. Proves whether the idea is actually used in daily work.
Full product
Roles, edge cases, interfaces, operations and support. Built only once the MVP holds up.

An MVP in practice: one enquiry, one push, one confirmation

How small an MVP may be is shown by the restaurant Han Kitchen in Zurich-Oerlikon. The one workflow that has to work end to end: a guest books through the website, the restaurant receives the reservation instantly as a push notification on the phone and confirms the guest with one tap via WhatsApp, from its own account and at no cost per message. The admin app runs as a web app on the home screen, without an app store. Nothing more is needed for the workflow to be used in daily work from day one.

The way of thinking carries over to any MVP: first build the one workflow the value depends on, so that it is genuinely used in daily work. Everything else, such as reports, additional roles or interfaces to till and accounting systems, comes only once usage shows it is needed. That is the core of an MVP: observe first, then expand.

If you want to test an idea of your own this way, you will find process, scope and limits under MVP development from CHF 10,000. How an MVP differs from a website and a native app is explained on web app development.

Frequently Asked Questions About MVP (Minimum Viable Product)

A prototype shows an idea; an MVP gets used. The prototype is usually clickable but not functional end to end, and it serves the conversation about workflow and interface. The MVP runs on real data in everyday work and therefore delivers observed behaviour rather than opinions. In practice one follows the other: a prototype for a few days, then the MVP once the direction is right.

As a rule of thumb, anything that needs more than roughly three months to reach real use is no longer an MVP. The timeframe follows from how narrowly the use case is cut, not from the size of the team. If it takes longer, too much was usually packed into the first version. The fix is to narrow the workflow further rather than to buy in additional capacity.

No. Established SMEs benefit particularly, because they know their processes precisely and have test users in-house. Only the purpose differs: a startup checks whether a market exists, while an SME checks whether a custom build genuinely improves an existing process compared with the tool already in use today. The test itself is the same — is it used voluntarily?

Ready for Your Project?

Apply this knowledge to your website — DLM Digital will help you.