What is an MVP? Examples, scope and common mistakes

Hephaestus Technology7 min read

What is an MVP? A minimum viable product is the smallest version of a new product that lets a team learn the most about real customers for the least effort. Eric Ries, who popularised the term, defined it in 2009 as the version of a new product "which allows a team to collect the maximum amount of validated learning about customers with the least effort." It is an experiment with a question attached, not a cheap first release.

Key takeaways

  • An MVP is defined by what it helps you learn, not by how few features it has.
  • Many good MVPs are not software at all: a landing page, a manual service or a two-page site can test the key assumption.
  • Scope an MVP around one riskiest assumption and one measurable success signal.
  • The DSDM MoSCoW method suggests keeping Must Have work to typically no more than 60% of effort, leaving room for contingency.
  • Enterprise Ireland's Pre-Seed Start Fund ideally looks for an MVP or live beta, though it is described as not essential.

What does MVP mean in plain English?

An MVP is the cheapest credible thing you can put in front of real customers to test whether your most important assumption is true. "Minimum" means you leave out everything that does not help answer that question. "Viable" means it must be real enough that customers behave as they would with a finished product, for example by signing up, using it on real work or paying.

Steve Blank, whose customer development work shaped the lean startup movement, puts it bluntly: "a minimum viable product (MVP) is not always a smaller/cheaper version of your final product." The question comes first; the form of the MVP follows from it.

How does an MVP work?

An MVP works as a loop: state a hypothesis, build the smallest test, measure what customers actually do, and decide what to change. A typical sequence looks like this:

  1. Write the hypothesis. "Finance teams at firms with 50 to 250 staff will pay monthly to automate supplier statement reconciliation."
  2. Choose the success signal. For example, five of 20 trial companies use it weekly for a month and two convert to paid.
  3. Build only what the test needs. Everything else goes on a "not now" list.
  4. Run the test with real users, not friends or colleagues.
  5. Decide: persevere, change one element (the segment, the problem or the offer) or stop.

The aim is validated learning: evidence from customer behaviour rather than opinions.

What are some real MVP examples?

The best-documented examples are tiny compared with the products that followed. Two worth knowing:

  • Buffer's two-page site. Founder Joel Gascoigne described in 2011 how he launched a two-page MVP explaining the product and collecting emails, then added a pricing page in between to see whether people would click through to paid plans. Only after people kept clicking did he build the product, in about seven weeks of evenings and weekends, and he had his first paying customer within four days of launch.
  • Blank's drone startup (a cautionary one). In Steve Blank's account, a team building agricultural drones defined the wrong MVP. The real question was whether farmers cared about the data, which could have been tested by renting a plane and processing the images by hand before building any hardware.

Common MVP formats, from cheapest to most involved:

MVP type What it is Best for testing
Landing page or smoke test A page describing the offer, with sign-up or pre-order Demand and messaging
Concierge MVP You deliver the outcome manually to a few customers Whether the outcome is valuable
"Wizard of Oz" MVP Looks automated to the user, but people do the work behind the scenes User experience before automation
No-code app Built on a platform such as Bubble or Glide Workflow and retention
Single-feature product Custom code, one core job done well Technical feasibility plus usage

If you are unsure which of these you need, our guide to prototype vs MVP vs pilot explains how they differ.

How should you scope an MVP?

Scope an MVP backwards from the one assumption it must test, then cut until it hurts. A useful tool is MoSCoW prioritisation from the DSDM agile framework, which sorts requirements into Must Have, Should Have, Could Have and Won't Have this time. The Agile Business Consortium's guidance describes Must Haves as the "Minimum Usable SubseT" and recommends typically no more than 60% Must Have effort, with around 20% Could Have effort held as contingency.

A practical scoping test for each feature: "If we removed this, could we still learn whether the hypothesis is true?" If yes, it moves down a category. When you are ready to brief developers, our guide to writing an MVP scope document developers can quote on turns this into a template.

How much does an MVP cost?

It depends far more on the type of MVP than on the idea. A landing page or concierge test can cost little beyond founder time. A no-code build adds platform fees: Bubble's published plans start at $0 on the free tier and $32 a month for Starter, billed annually, before any build time. Custom software is usually the most expensive route, because cost scales with features, integrations, platforms (web, iOS, Android) and the people needed. Our breakdown of MVP cost in Europe covers the drivers in detail.

What are the most common MVP mistakes?

The most common mistake is treating the MVP as version 1.0 and building for months before anyone uses it. In CB Insights' review of 111 startup post-mortems, building something without a market need was cited in 35% of cases, and a flawed product in 8%. Other frequent mistakes:

  • No hypothesis or success metric. Without one, every result looks like progress.
  • Too many features. Each extra feature delays learning and blurs what caused the result.
  • Testing with the wrong people. Friends, investors and colleagues are not your customers.
  • Skipping the "viable" part. A product so rough that nobody can use it on real work tells you nothing about demand.
  • Ignoring basics such as data protection. If your MVP collects personal data from EU users, GDPR applies from day one, however small the product.

Do Irish funders expect an MVP?

Often, yes, though not always as a hard rule. Enterprise Ireland's Pre-Seed Start Fund offers €50k or €100k investment plus 10 mentoring sessions, and a Donegal County Council notice on the fund says that "ideally the start-up would have a Minimal Viable Product (MVP) or be live in Beta," alongside a validated customer proposition. Having an MVP with real usage data makes the conversation with any early-stage investor more concrete.

Frequently asked questions

What is the difference between an MVP and a prototype?

A prototype tests whether something can be built or how it should look and work, usually with a small group in a controlled setting. An MVP is put in front of real customers to test whether they will use or pay for it. Many teams build a prototype first and an MVP second.

Does an MVP have to be software?

No. A landing page, a manually delivered service or a simple spreadsheet-based workflow can all be MVPs if they test the key assumption with real customers. Software is only needed when the assumption depends on the software itself.

How long should it take to build an MVP?

There is no standard duration, because it depends on the type of MVP. A landing page can go live in days; Buffer's founder built his first product in about seven weeks of evenings and weekends. If your plan stretches over many months, the scope is probably too large.

When is an MVP finished?

An MVP is finished when it has answered the question it was built to test, either by meeting or missing the success signal you set in advance. At that point you persevere, change one element or stop.

Can an MVP be used to raise funding?

Yes, especially when it produces real usage or revenue data. Enterprise Ireland's Pre-Seed Start Fund ideally looks for an MVP or live beta, although this is described as not essential.

If you want help deciding what your MVP should test, book a free 30-minute call.

Cover photo by Thirdman on Pexels.

Hephaestus Technology

We help founders and businesses validate, build and launch products across software, AI and hardware, from offices in Ho Chi Minh City, Dublin and Delaware. See how we work.

Tell us what
you're building.

A free 30-minute call. You'll get an honest view of the idea, the risks we see and what we'd do first, whether or not we end up working together.