What Is an MVP? (Minimum Viable Product, Explained)

MVP is one of the most used and least understood terms in product development. Getting it wrong, or getting the order wrong, costs time and money most founders can't afford to waste.

If you've spent any time around startups, digital agencies, or corporate innovation teams, you've heard the term MVP. Minimum Viable Product. It's become one of those phrases that gets used so freely it's started to lose meaning, applied to everything from a rough sketch to a fully launched product, often by people who aren't entirely sure what it means themselves.

That vagueness is expensive. Building an MVP when you need a prototype wastes money. Stopping at a prototype when you need an MVP leaves opportunity on the table. And commissioning a full product build when either would have done the job is the mistake that costs organisations tens of thousands of pounds and months of time they didn't need to spend.

What MVP means in business

In business, MVP means the smallest version of a product you can put in front of real customers to find out whether they will use it and, usually, whether they will pay for it.

That is a commercial question rather than a technical one. An MVP is not a milestone in a build plan. It is the point where an assumption about the market stops being an opinion held in a meeting and starts being something you have evidence for.

The term gets used loosely, though, and in most business conversations it means one of three quite different things:

The real definition: a minimal but genuinely working product, released in order to learn something
A budget signal: "do the cheap version", which is not the same thing at all
A cut-down scope: the full product with features removed, which is the most common use and the most expensive one

(Outside software, MVP also stands for Most Valuable Player. In any product or technology context it means Minimum Viable Product.)

The precise definition, and where it came from, is next.

What MVP actually means

MVP stands for Minimum Viable Product. The term was popularised by Eric Ries in The Lean Startup, where he defined it as "that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort."

An MVP is not a rough product. It's not a half-finished one. It's a deliberately minimal but genuinely functional product that delivers real value to real users, and is designed specifically to generate learning about whether there's a sustainable business or use case behind it.

The minimum part means you build only what's essential to deliver that core value. The viable part means it actually works: properly, reliably, in a way that users can genuinely engage with. Both words matter equally.

What an MVP is not

An MVP is not a prototype: a prototype tests whether a concept works. An MVP tests whether a business works. They serve different purposes at different stages and at significantly different costs.

An MVP is not a bad version of your product: the minimum in MVP refers to features, not quality. An MVP should be excellent at the one or two things it does.

An MVP is not the final product: an MVP is the beginning of a learning process, not the end of a build process.

Why MVPs matter, and what happens when you skip them

The common thread in failed products is rarely bad code. CB Insights looked at 431 venture-backed companies that shut down from 2023 onwards and could pin down why 385 of them failed. Poor product-market fit accounted for 43%, and two thirds of those never found a market at all. The thing got built before anyone checked whether people wanted it.

The commercial case is equally clear. Without an MVP showing real traction, raising money takes four to five times longer. Investors don't fund ideas: they fund evidence. An MVP is the most credible evidence you can produce.

And the cost of getting it wrong is significant. Validating before building prevents more than 50% of wasted development spend. Teams that spend at least 20% of their MVP budget on pre-development validation are three times more likely to build a successful product.

Who needs an MVP?

Founders and early-stage startups: you have an idea, you've done some early validation, and you're ready to test whether there's genuine market demand before raising money or committing to a full build.

Product teams at growing companies: when an established business wants to add a new product line or enter a new market, MVP thinking applies just as much as it does at startup stage.

Corporate innovation teams: large organisations increasingly use MVP methodology for internal innovation. A department that wants to digitise a process or build an internal tool doesn't need to commission a full enterprise build to find out whether the idea works.

Operations and department leads: the operations manager who knows there's a better way to run a process, the department head with a digital idea they can't get IT to prioritise. For this audience, a prototype is often all they need to get approval for the MVP build.

When do you need an MVP versus a prototype?

The honest answer is that most people need a prototype before they need an MVP. The prototype validates the concept. The MVP validates the business. You need the first answer before the second question is worth the investment.

If you haven't yet tested your core concept with real users using something real, you need a prototype first.

If you have tested the concept, the signals are positive, and you're ready to launch properly to your target market, you're ready for an MVP.

The key question to ask yourself is: what am I trying to prove, and to whom?

- If you're trying to prove the concept works: prototype. - If you're trying to prove the business works: MVP. - If you're trying to prove to your organisation that the investment is justified: often a prototype is enough to get the budget approved for the MVP.

How much does an MVP cost in the UK?

A standard MVP in the UK typically costs between £30,000 and £70,000 for a properly built product with multiple features, platform support, and third-party integrations. Simpler MVPs with tighter scope can come in below that, but the £8,000-£15,000 figures you'll see quoted elsewhere typically describe prototypes, not MVPs.

Complex or enterprise-level MVPs, with real-time data, AI features, or regulatory compliance requirements, regularly cost £70,000 to £200,000 or more.

HM Treasury tells its own departments to assume software projects cost more than the first estimate. Its Green Book guidance on optimism bias sets the upper adjustment for developing software and systems at 200% on capital cost and 54% on duration, and tells appraisers to start at that upper bound rather than work up to it. The guidance adds that a higher adjustment may be needed earlier still, which is the point at which least is known about what the thing has to do.

This is why the step before the MVP matters so much commercially.

The step before the MVP, and why it used to be skipped

Getting proper validation before committing to an MVP build used to be expensive and slow. A formal discovery phase with an agency could cost thousands and take weeks before any build work started. Most founders either skipped it and paid the price later, or couldn't afford to do it properly.

That's changed. A working prototype that tests your core concept with real users can now be built in five days, and the learning it produces is categorically more useful than any amount of market research or specification writing.

Building something real before you commit to an MVP means the MVP you build is grounded in evidence rather than assumption. The scope is defined by what users actually responded to, not what you thought they would. The brief you give developers is precise rather than speculative. And the investment you make in the MVP has already been de-risked.

Bluprint's Prototype Sprint builds a real, fully functional digital product in five days from £750: the validation stage that de-risks the MVP investment before you make it. When your prototype validates and you're ready to build further, Bluprint can connect you with the right development partner through our Partner Match service, a developer who receives a tested, validated brief rather than a speculative one, and can hit the ground running from day one.

The bottom line

An MVP is not a prototype. It's not a rough product. It's the beginning of a learning process: a deliberately minimal but genuinely functional product launched to your real target market to test whether there's a sustainable business behind your idea.

Most people who think they need an MVP actually need a prototype first. And most people who've built a prototype that's validated their concept are ready to build an MVP, with a development partner who has everything they need to build it properly from day one.

Building something nobody wanted is the failure a prototype can actually prevent. It is how you find out before the real money gets spent.