MVP

An MVP (Minimum Viable Product) is the simplest version of a product that you can build and release to test whether your idea works in the real world. It includes just enough features to be useful to early adopters, and — crucially — to start generating feedback that guides what you build next.

The key word is "viable." An MVP isn't a broken or half-finished product. It's a focused product that does one thing well enough for real people to use it and tell you what they think.

Why build an MVP?

The biggest risk in building a product is spending months (and tens of thousands of pounds) creating something nobody wants. An MVP dramatically reduces this risk by:

• Testing demand early: Find out if people will actually use (and pay for) your product before you've built the full version.
• Learning fast: Real user feedback tells you what features matter most, what's confusing, and what's missing.
• Conserving resources: Build only what you need to learn, then invest more once you have evidence of demand.
• Attracting investors: A working MVP with early traction is far more convincing than a slide deck.

What an MVP looks like

An MVP varies depending on your product, but common examples include:

• A web app with 3-4 core features instead of 20.
• A landing page with a sign-up form to gauge interest before building anything.
• A manual process that simulates what the software will eventually do automatically.
• A simple mobile app that covers one core use case.

Common MVP mistakes

• Too many features: Trying to include everything in version 1 defeats the purpose. Cut ruthlessly.
• Too polished: An MVP should look professional but doesn't need pixel-perfect design. Focus on functionality.
• No feedback mechanism: If you launch an MVP without a way to collect and act on user feedback, you've missed the point.
• Never moving past MVP: The MVP is a starting point, not the destination. Plan for iteration based on what you learn.

The companies that succeed are typically the ones that launch something small, learn from real users, and iterate quickly — rather than spending years building the "perfect" product in isolation.