Prototype vs MVP: Which Do You Need First?

Prototype and MVP are two of the most misused terms in product development. Getting the distinction right, and the order right, can save you months of time and tens of thousands of pounds.

Prototype and MVP are two of the most misused terms in product development. Founders use them interchangeably. Agencies use them to mean whatever suits the conversation. The confusion is so widespread that most people building their first digital product don't realise they've mixed them up until they've already spent money on the wrong thing.

Getting the distinction right, and getting the order right, can save you months of time and tens of thousands of pounds.

What is a prototype?

A prototype is a real, working version of your product built tightly around your core idea, designed to test whether your concept works before you commit to building the full thing.

The word "prototype" has been muddied by the design industry, where it's often used to describe clickable mockups in tools like Figma: screens that look like a product but don't function like one. That's not what we mean here, and it's not what you need.

A genuine prototype is functional. Users can sign up, interact with it, and use it to do the thing it's supposed to do. It's deliberately scoped (it doesn't have every feature the eventual product will have) but what it does have works properly. It's real enough to generate real feedback.

Think of it as the smallest real version of your product that tests your core assumption.

What is an MVP?

An MVP (minimum viable product) is the simplest version of your product that delivers enough value to real users to test whether there's genuine market demand, and to begin building a customer base.

The key difference from a prototype is intent and audience. A prototype tests an idea. An MVP tests a business. A prototype is something you put in front of carefully selected users to learn from. An MVP is something you launch (properly, to your actual target market) to see whether people will use it, retain it, and pay for it.

In the UK, a standard MVP typically costs between £30,000 and £70,000 and takes three to six months to build. A full product build costs significantly more. These are serious commitments, which is exactly why getting the sequence right matters so much.

The common mistake: skipping the prototype

The most expensive mistake founders make is going straight from idea to MVP (or worse, straight from idea to full product) without a prototype stage in between.

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%. Most of those founders built an MVP or a full product before they had genuine evidence that the core concept worked.

A prototype catches that problem early, cheaply, and quickly. The sequence should be: idea → prototype → learning → MVP → launch. Skipping the prototype doesn't save time. It front-loads the risk.

Prototyping adoption has tripled in recent years. The global prototyping market is projected to reach $63.9 billion by 2034, growing at 11.5% annually, reflecting how central testing before building has become to modern product development.

What a prototype tells you that an MVP can't

- Whether users understand what the product does immediately - Whether the core flow works the way you expected - Whether the problem you're solving is real enough that users engage genuinely - Whether you're building for the right people - Whether the concept needs to pivot before you invest in the full build

What an MVP tells you that a prototype can't

- Will people use this product consistently over time, not just once? - Will they pay for it, and how much? - Can you acquire customers at a cost that makes commercial sense? - Does the product retain users, or do they churn quickly? - Is there a sustainable business model here?

How much does each stage cost?

A Bluprint Prototype Sprint builds a real, fully functional digital product in five days from £750.

A standard MVP in the UK costs £30,000 to £70,000 and takes three to six months. A full product build costs significantly 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.

Spending £750 on a prototype before committing to an MVP isn't a delay. It's the decision that makes the MVP investment rational rather than speculative.

What happens if your prototype validates?

If you test your prototype and the signals are positive (users engage with it, they understand it immediately, they come back, they'd pay) you're ready to move to the next stage.

Historically that transition meant starting again with a new agency, a new brief, and a significant new budget, with all the risk that comes from handing over context to a team that wasn't part of the prototype process.

That's changed. A validated prototype gives any development team everything they need to build accurately and efficiently. The scope is defined by real user behaviour, not assumption. The brief is precise rather than speculative. And the risk that typically sits at the start of an MVP build has already been addressed.

Bluprint stays with you through that journey. Depending on what you need next, we can connect you with the right development partner, stay actively involved through the build, or support the complete journey from prototype to finished product.

The journey looks like this:

Prototype Sprint: from £750, five days. The core concept built and ready to test.

Partner Match: when you're ready to build, we connect you with the right developer. They receive a tested, validated brief and can hit the ground running.

Guided Build: for clients who want Bluprint actively involved through the development process, not just at the prototype stage.

Full Partnership: for products that have proven themselves and are ready to scale, with Bluprint supporting the complete journey.

The £750 prototype isn't a sunk cost you leave behind. It's the foundation everything that follows is built on.

A practical guide to deciding which you need right now

Have I tested this concept with real users using something real? If no, you need a prototype first.

Do I have genuine evidence that people will use and pay for this? If no, you need a prototype first.

Am I confident enough in the core concept to invest £30,000–£70,000 in building it out properly? If not, you need a prototype first.

Do I have a paying customer or signed commitment? If yes, you may be ready to go straight to MVP.

Is my prototype already validated and am I ready to build further? If yes, talk to us about the next step.

The bottom line

The prototype answers: does this concept work? The MVP answers: can this become a business?

You need the first answer before the second question is worth asking. An MVP built on a validated concept and one built on a hope cost the same to make. Only the first is worth the money.

The prototype is what makes the MVP worth building. Get that right and everything that follows is built on evidence rather than assumption.