Skip to main content

Cost and Scope

MVP (Minimum Viable Product)

An MVP is the smallest version of a product real users will choose over what they do now. See examples, how it differs from a prototype, and what to ask.

Definition

An MVP, or minimum viable product, is the smallest version of a product that a real user would choose to use instead of whatever they do today, built so you can learn whether the rest is worth building.

Both halves matter. A small thing nobody can use teaches you nothing. A usable thing that answers no open question is phase one of a plan that was already decided, and calling it an MVP adds nothing.

The term was coined by Frank Robinson in 2001 and spread through Eric Ries’s book The Lean Startup in 2011. In software development it now gets used loosely for any first release, which is why the definition is worth pinning down before anyone quotes for one.

MVP, Prototype and Proof of Concept

These three get swapped for each other in proposals, and they are bought for different reasons.

A proof of concept answers a technical question: can this API give us the data we need, can this model read our documents accurately enough. It is usually never seen by a customer.

A prototype answers a design question. It shows how the thing would look and flow, often as clickable screens with nothing real behind them, and it is built to be thrown away.

An MVP is the first version of the real product. Real users log in, real data goes through it, and the code is meant to be kept and extended. That is why an MVP needs proper foundations even though it is small, and why it costs more than a prototype of the same screens. An app built quickly with AI tools can look like an MVP and still be a prototype underneath, and having a developer read the code is how you find out which one you have.

Deciding which of the three you are paying for, before work starts, avoids the worst conversation in software: finding out after launch that the version everyone likes has to be rebuilt before it can grow.

Examples

The textbook examples are consumer start-ups. Before building file sync, Dropbox published a short video of the product working to see whether people would sign up for it. Zappos began with its founder photographing shoes in local shops and buying them at full price when an order came in, to test whether people would buy shoes online at all. Neither was a software product yet. Both answered the one question that decided whether to build one.

For a business commissioning software, the shape is more ordinary. Picture an accountancy practice that wants a client portal with document upload, e-signatures, invoicing, messaging and a tax-deadline calendar. A sensible MVP might be the upload and a status page for each client’s return, done properly, in front of twenty clients. The question it answers is whether clients will use a portal instead of email. If they won’t, the other four features were never going to save the project.

The Failure Mode To Watch

The common failure is an MVP that is every feature at twenty percent, where it should be twenty percent of the features at full quality.

Budget is usually the cause. When a budget doesn’t cover what was described, “MVP” becomes the polite word for cutting it, and budget cuts take depth out of every feature. Cuts made for learning remove whole features and keep the survivors complete. The second shape is better, and you often have to ask for it.

A product with eleven half-working areas can’t tell you anything, because when users don’t adopt it you can’t separate a weak idea from thin execution. A useful test for any proposed scope: would you put each item in front of a paying customer as it stands? Anything that fails should be cut rather than shrunk.

What To Ask Before You Build One

  • What question does this version answer? If the answer is “it gets us started”, the thinking hasn’t been done.
  • Which features are complete and which are partial? Push for fewer, finished ones.
  • Who is the first real user, and when do they get it?
  • What result would make us stop or change direction? Agreeing this in advance stops the MVP drifting into version one of the original plan.

Our guide on how to scope an MVP walks through cutting a feature list down step by step. If you are still deciding whether to start small at all, MVP vs full build sets out what each path costs and where each goes wrong.

We build first versions of business software as part of our custom software development work, on foundations built to be extended. What moves the cost of a first version is covered on MVP development pricing. Other terms are in the glossary.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.