Mon – Sat: 9:00 AM – 7:00 PM IST
Mobile

What is an MVP in software?

The smallest build that answers a real question — and why most so-called MVPs answer none.

In short

A minimum viable product is the smallest version of a product that can test the assumption the business is betting on. It is not a cheap version of the full product and not a prototype. The distinguishing question is: what would we have to see for this to be worth continuing, and what is the least we can build to find out?

Why It Matters

Why this matters in practice

Most MVPs fail in one of two directions. Either they become a full product with the word minimum attached, taking a year and testing nothing; or they are so thin that nobody can use them and the result tells you nothing about whether people would. Both failures come from skipping the first question — which assumption is this testing?

Tests the riskiest assumption rather than building the easiest features
Reaches real users quickly enough for the answer to still matter
Scope is defined by the question, not by what seems reasonable
Produces a decision: continue, change direction, or stop
How It Works

How it works in practice

Name the assumption

What has to be true for this to work? Usually it is about demand or willingness to pay, not about whether the software can be built.

Define the success signal

What would you need to observe to continue? Decide before building, because afterwards the bar moves.

Cut to the core journey

One user type, one path through the product, end to end. Breadth is what makes an MVP late.

Build it properly

Minimal in scope, not in quality. A crashing MVP tests whether people tolerate crashes, not whether they want the product.

Measure and decide

Against the signal defined up front. An MVP that ships and is simply extended has skipped the decision it existed for.

Worked example

A worked example: the MVP that was not minimum

A business plans an MVP for a field service app. The initial list has 34 features. Everyone agrees to cut it down, and after two workshops it has 29 — because every feature has an advocate and no one wants to be the person who removed theirs.

A better cut asks a harder question: what single workflow, end to end, proves this is worth building? The answer is that a technician receives a job, completes it on site, captures a signature, and the office sees it as done. That is perhaps six features. Scheduling optimisation, parts ordering, customer notifications, reporting and the other twenty-three are all plausible and none of them tests the premise.

Built as six features, the app ships in weeks and immediately teaches things no workshop would have: technicians need the customer's phone number more than the job description, signatures fail in sunlight, and the office wants a photo rather than a tick. Two of those were not on the list of 34 at all. Built as 29 features, it ships in months and teaches the same things later, after the effort has been spent in the wrong places.

Key terms

The vocabulary, briefly

Term What it means
Minimum viable product The smallest build that delivers real value and produces real learning.
Scope creep Additions that turn an MVP into a full product before anything has been validated.
Validated learning Evidence from actual usage, as distinct from opinions gathered in a meeting.
Technical debt Shortcuts taken deliberately for speed. Acceptable when recorded; corrosive when forgotten.
Pivot Changing direction based on what the MVP revealed. The outcome an MVP exists to make affordable.
What Goes Wrong

Common mistakes worth avoiding

Scope defined by features, not by the question

Every stakeholder's must-have arrives, and the MVP becomes version one by another name.

No success criterion

Without one, any outcome can be read as encouraging, and the project continues by default.

Minimal quality instead of minimal scope

Users judge a broken product as a bad product, not as an early one.

Building for every user type at once

One segment, done well, answers the question. Three segments triples the work and blurs the result.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Features in MVP scope Smaller is usually better. A list that only grows during planning is a warning sign.
Time to first real user The clock that matters, because learning does not start until someone uses it.
Usage of each shipped feature The honest verdict on what was worth building. Routinely surprising.
Assumptions tested Whether the build is producing evidence or just producing software.
FAQ

Questions we are asked about this

Short enough that the answer still matters to the decision. If the market or the budget will have moved by delivery, the scope is too large regardless of the calendar.
A proof of concept tests whether something is technically possible, usually internally. An MVP tests whether real users want it, which means it has to reach them.
Small enough to ship in weeks rather than months, and complete enough that someone can do a real job with it end to end. The test is not feature count but whether a user can finish a workflow — half a workflow is not an MVP, it is a prototype, and it generates opinions rather than evidence. If the smallest end-to-end workflow still takes six months, the scope is probably a programme rather than a product.
No, and conflating the two is the most damaging misreading of the idea. An MVP has fewer features, not worse ones. What it ships should work properly, because users judge it on what it does rather than on what it leaves out. Deliberate technical shortcuts are legitimate where they are recorded and scheduled for repayment; shipping something broken teaches you that users dislike broken software, which you already knew.
They will, immediately, and that is useful data rather than a problem. The question to ask is what they are trying to achieve rather than which feature they named, because the stated request is usually one solution to an underlying need and often not the best one. Prioritise by how many users hit the same underlying problem and how much it costs them. Building every requested feature is how an MVP becomes an unfocused product.
When it has answered the question it was built to answer — whether people will use this, whether it saves the time you expected, whether they will pay. At that point you either invest with evidence, change direction, or stop. The failure mode is an MVP that quietly becomes the product without anyone ever reviewing what it proved, which means the shortcuts stay and the learning is never acted on.
Related

Where to read next

Flutter app development cost

Read more

What is Flutter?

Read more

Request a free proof of concept

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.