What is a minimum viable product (MVP)?

MVP: definition and origins

Minimum viable product roughly means “the smallest product that can survive on the market.” The term became known mainly through Eric Ries and his book “The Lean Startup.” The basic idea: instead of spending months building a perfect product behind closed doors, you bring a lean version to market early.

An MVP is not a half-finished prototype. It is small but functional and solves a specific problem for a clearly defined target group so well that users actually use it—and ideally pay for it.

How an MVP is created

At its core is the “build–measure–learn” cycle. First, the most important assumption is formulated, for example: “Skilled trades businesses would hand out appointments online if it worked without a phone call.” The MVP contains only the features needed to test this assumption.

Anything that isn't essential to the core question goes on a list for later stages. This discipline is the hardest part—and the most important.

• Describe the problem and target group precisely
• Define the core feature and postpone everything else
• Define metrics, e.g., sign-ups or repeat usage
• Build, launch, and gather user feedback
• Based on the results, develop further, adjust, or discard

Benefits and limitations of an MVP

An MVP reduces risk: you find out early whether your product is accepted and only then invest in expanding it. Real usage data replaces assumptions, and the first customers can generate revenue while the product grows.

The danger lies in misguided frugality. If the MVP is so bare-bones that it offers no real value, the results are not very meaningful. And if the code is written sloppily under time pressure, technical debt builds up and slows down later expansion.

• Faster time to market
• Investment decisions based on real data
• Early feedback from active or paying users
• Still plan for a clean technical foundation

Real-world example: testing a platform idea

A company wants to build a marketplace platform for skilled trades services. Instead of developing reviews, chat, payment processing, and an app right away, it starts with a web application: submit a request, receive quotes, award the job. Only when this core feature catches on do further stages follow.

Web applications and progressive web apps are particularly well suited for an MVP because they can be built quickly and are easy to adapt. Nano Concepts helps sharpen the feature set and develops the MVP on a foundation that can grow with it later.