Skip to content

Guide

What is an MVP in software development?

What a minimum viable product is, what it is not, and how to decide what goes into the first version of your software.

Muhammad BilalFounderPublished 3 min read

"MVP" is one of the most used terms in software and one of the most misunderstood. Some people use it to mean a rough prototype; others mean a full first version with every feature. Neither is quite right, and the difference affects what you build, how long it takes and what it costs.

What "minimum viable product" means

A minimum viable product is the smallest version of a product that real users can use, built to test your riskiest assumption. It is a learning tool as much as a product.

The two words carry equal weight:

  • Minimum is about scope. It does the fewest things needed to test the idea.
  • Viable is about quality. What it does, it does properly. People can rely on it, pay for it if that is the plan, and their data is safe.

The term was popularised by Eric Ries in The Lean Startup, which describes building the smallest thing that lets a team start learning from real customers, then improving it in short cycles.

What an MVP is not

  • Not a prototype or clickable mock-up. A prototype shows what something could look like. An MVP is used for real, with real data. Prototypes are useful earlier, for testing a design, but they do not tell you whether people will actually use or pay for the product.
  • Not version 1.0 with everything in it. If the first release includes every feature on the wish list, it is not minimum, and it will take much longer to learn anything.
  • Not an excuse for poor quality. Broken payments, lost data or weak security are not "MVP shortcuts". They destroy the trust you need from early users. Cut features, not quality.

Types of MVP

There is more than one way to build a minimum viable product:

Concierge and "Wizard of Oz" MVPs

The user sees a simple interface, but a person does some of the work behind the scenes. For example, customers request a quote through a form, and your team prepares it by hand. This tests demand and the shape of the service before you automate anything.

Single-feature product

The product does one job very well. Many successful products started this way and added features only after the first one was clearly wanted.

Landing page with a waiting list

A page that describes the product and collects sign-ups. It is quick and cheap, but it only tests interest. People signing up is not the same as people using or paying, so treat it as a first signal, not proof.

How to decide what goes in

  1. Start from the question. Write down the single most important thing you need to learn. For example: "Will clinic receptionists use online booking instead of the phone?"
  2. List every feature you have in mind. Do not filter yet.
  3. Find the journey that answers the question. Keep only the features that journey needs. Everything else goes on a "later" list.
  4. Look for manual shortcuts. If something can be done by hand for the first few weeks, it can wait.

Our MVP scope planner helps with steps 2 to 4: it sorts features into must-have, should-have and later, and warns you when the must-have list is growing too long.

After launch

What to measure

In the first weeks, watch behaviour rather than opinions:

  • How many people who are invited actually start
  • How many complete the core journey
  • How many return without being reminded
  • Whether anyone pays, or commits to paying

Talk to users as well. Numbers tell you what is happening; conversations tell you why.

Iterate, pivot or stop

After a few weeks of real use you will usually be in one of three positions:

  • Iterate: the core idea works, and the feedback tells you what to improve next.
  • Pivot: people use it, but not the way you expected, or a different group needs it more. Change direction based on what you saw.
  • Stop: the evidence says the problem is not painful enough. Stopping early is a success: you saved the money a full build would have cost.

In short

An MVP is the smallest real, reliable product that answers your most important question about the market. Decide the question first, keep the scope tight, keep the quality high, and plan how you will measure the result before you launch.

  • MVP
  • Planning

Try it yourself

Planning your MVP?

Tell us about the idea and the people it is for. We will help you find the right first version.

Keep reading