How to build a minimum viable product (MVP)

What an MVP is, how to decide what goes in it, and how to launch, measure and learn without overspending on version one.

By the UK Technology Hub teamPublished 4 minute read

The short answer

An MVP is the simplest version of a product that lets real users solve their core problem, so you can learn whether the idea works before investing heavily. Define one clear problem and audience, list the features, keep only those essential to solving that problem, build them well, launch to a small group and measure what they actually do.

Many new products fail not because they're badly built, but because they solve a problem people don't care enough about, or solve it in a way they don't want. A minimum viable product, or MVP, is designed to find that out quickly and cheaply.

What an MVP is, and isn't

An MVP is minimum because it includes only what's needed to test the core idea. It's viable because it genuinely works and delivers value. It's not a buggy prototype or a half-finished product, and it's not the full vision with everything included.

A good MVP does one important job well for a specific group of people.

Step 1: Define the problem

Write down, in a sentence or two:

  • Who has the problem.
  • What the problem is.
  • How they deal with it today.
  • Why current solutions fall short.

Talk to potential users before building anything. Ask about their current process, frustrations and what they've tried. Listen for problems they already spend time or money on.

Step 2: Define success

Decide what would prove the idea is worth pursuing. Examples:

  • A certain number of businesses use it weekly after a month.
  • A percentage of trial users convert to paid plans.
  • Users complete the core task faster than with their old method.

Clear measures stop you moving the goalposts after launch.

Step 3: List and cut features

List every feature you can imagine. Then sort them:

  1. Must have: without it, the core problem isn't solved.
  2. Should have: improves the experience but can wait.
  3. Could have: nice ideas for later.
  4. Won't have now: explicitly out of scope.

Be ruthless. Features like advanced reporting, multiple user roles, integrations and settings pages are often not needed in version one. Every extra feature adds cost and delays learning.

Step 4: Prototype and test

Before writing code, create a clickable prototype of the main screens and test it with five or more potential users. Watch them try to complete the core task. You'll spot confusing steps and missing information early, when changes cost almost nothing.

Step 5: Choose the right format

Decide whether the MVP should be a web app, mobile app or progressive web app. Web apps are often fastest and cheapest to launch and update. Our guide to web apps, mobile apps and PWAs explains the trade-offs. For some ideas, no-code tools can work for the very first test; see our guide to no-code versus custom development.

Step 6: Build it properly

"Minimum" refers to scope, not quality. The features you include should be reliable, secure and pleasant to use. Users judge an idea by their experience of it, and a buggy MVP can make a good idea look bad.

Build with growth in mind. A sensible architecture means you can add features later without starting again. Use proven services for payments, authentication and email rather than building them from scratch.

Step 7: Launch to early users

Start with a small group: people you interviewed, a waiting list or a pilot customer. Support them closely, ask for feedback and watch how they use the product. Early users are often forgiving if they see you respond quickly.

Step 8: Measure and learn

Combine numbers with conversations:

  • Analytics: sign-ups, activation, task completion and return visits.
  • Feedback: interviews, support questions and surveys.

Then decide: keep improving, change direction or stop. All three are valid outcomes. Learning that an idea doesn't work after a modest MVP is far better than discovering it after a large build.

Common MVP mistakes

  • Building for everyone instead of a specific audience.
  • Adding features because competitors have them.
  • Spending months perfecting before showing anyone.
  • Launching without a way to measure success.
  • Ignoring what users do in favour of what they say.

Budgeting

A focused MVP costs a fraction of a full product, but still needs proper design, development and testing. Our guide to app development costs explains the main factors.

How we help start-ups

Our app development service includes discovery workshops that help define the problem, prioritise features and produce a clickable prototype before build. We then build the MVP as a web app or mobile app, designed so it can grow if the idea takes off.

Frequently asked questions

How long does it take to build an MVP?

Often a few months for a focused product, depending on features and complexity. Tight scoping is the best way to shorten it.

Should an MVP be free for users?

Not necessarily. Charging early, even a small amount, can be the strongest test of whether people value the product.

What happens after the MVP?

You use what you learned to decide on the next features, improve the product, or change direction if the evidence points elsewhere.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

All web & mobile apps guides