What Is an MVP, and Why Do So Many Big Companies Start With One?

TL;DR: An MVP is the smallest version of a product a company can launch to test whether real people want it, before committing serious time and money to building it properly. If you're looking at a young company as a potential investment, spotting that it's still at MVP stage tells you a lot about how early — and how risky — that business really is.

Every big company you can name today started somewhere much smaller and much rougher than the version you use now. The trick almost all of them share is that they didn't try to build the finished, polished product on day one. They built the smallest possible version that could prove the idea worked, put it in front of real users, and only then decided whether it was worth building further.

Turning that first rough idea into a working product is itself a specialised job. Startups that get this stage right usually bring in a team that specialises in MVP development rather than trying to build a full platform alone from scratch — it keeps the first version small, fast to ship, and genuinely testable instead of half-finished in every direction at once.

What "MVP" actually means

MVP stands for minimum viable product. Pull the phrase apart and it tells you exactly what it's describing: the minimum version (as little as possible), that's still viable (good enough to actually use and judge), of a product (a real thing people can try, not just an idea on paper).

It's easy to assume "minimum" means "bad" or "unfinished," but that misses the point. An MVP is deliberately small, not accidentally broken. Every feature that isn't strictly needed to test the core idea gets cut, on purpose, so the team can find out fast whether the idea is worth pursuing at all.

This is different from a prototype. A prototype is usually a rough mock-up used internally, or shown to a small group, mainly to check that an idea can work — it's rarely handed to real customers to use day to day. An MVP goes further: it's released to actual users, who use it for real, which is the only way to get an honest answer about demand rather than a guess.

Why companies deliberately launch something unfinished

It sounds risky to show the world something half-built, so why do it on purpose? Because the alternative is usually worse.

• It's far cheaper to test than to guess. Spending months of research trying to predict whether people will want a product is expensive and often wrong. Spending a few weeks building a stripped-down version and watching what real users actually do with it is usually cheaper and more accurate.
• Real behaviour beats opinions. People are notoriously bad at predicting their own future behaviour in surveys. What someone says they'd do and what they actually do when a product is sitting in front of them are often two very different things.
• It protects against the biggest startup risk: building the wrong thing. Most young companies don't fail because they built their product badly — they fail because they spent years building something nobody needed. An MVP is designed to catch that mistake early, while it's still cheap to change course.

For anyone evaluating a young company, this matters directly. An MVP stage isn't a red flag by itself — it's completely normal — but it does mean the business is still answering the most basic question of all: does this idea actually work? That's a very different kind of risk from a company that has already proven demand and is now scaling a working product.

Three famous MVPs you've probably used

These stories are widely documented and often retold in business and product circles — they're useful here purely as illustrations of the concept, not investment tips about any specific company or its shares.

Dropbox

Before building the full file-syncing product, Dropbox's founder famously put together a simple explainer video showing how the service would work, rather than the service itself. Thousands of people signed up to a waitlist after watching it, which was all the proof the team needed that demand existed before writing most of the underlying engineering.

Zappos

The online shoe retailer Zappos started with an MVP so simple it barely looked like a business at all: the founder photographed shoes in local stores, listed them on a basic website, and only bought the pair from the shop once a customer actually ordered it online. There was no warehouse, no inventory and no logistics system — just a fast way to test whether people would buy shoes without trying them on first.

Airbnb

Airbnb's earliest version wasn't a platform at all. Its founders rented out air mattresses on the floor of their own apartment to a handful of guests during a conference, as a way to test whether strangers would actually pay to stay in someone else's home. That tiny, almost accidental experiment became the starting proof behind what later grew into a global platform.

How to spot "MVP stage" in company news

You don't need insider information to notice when a company is still at MVP stage — the language in press releases and news coverage usually gives it away. Keep an eye out for phrases like:

• "Beta" — an early, still-being-tested version, usually offered to a limited group of users first.
• "Pilot" — a small-scale trial run, often with one customer, region or partner, before any wider rollout.
• "Early access" — a product that's live but deliberately limited to a small group while the company keeps refining it.
• "Limited rollout" — available in only one market, city or user group for now, with wider release still to come.
• "Waitlist" — the product isn't fully available yet; the company is gauging and managing demand before scaling up.

There's a useful general rule here: a company that's already listed on a stock exchange has almost always moved well past the MVP stage — public markets expect a proven, operating business, not an early idea test. A young, newly founded startup described in the news as "launching its MVP," on the other hand, is explicitly telling you it's still at the very beginning of that journey. For a formal definition straight from a widely used source, Investopedia's entry on minimum viable product is worth a read if you want the textbook version.

What this means if you're tracking a company in the Challenge

If you spot a company in the news that's described as testing, piloting or launching an MVP, that's not a signal to rush out and buy or sell anything — this isn't investment advice, and MVP stage alone tells you nothing about whether a specific move is a good idea. What it does tell you is something about risk and stage: an MVP-stage business is, by definition, still working out whether its core idea even has demand, which usually means more uncertainty and more potential for sharp swings than a company with years of proven operating history.

That connects directly to an idea covered in our guide to what volatility actually is: younger, less-proven businesses tend to see bigger price swings precisely because there's less established evidence to anchor expectations around. Recognising "this company is still at MVP stage" is one more piece of context you can fold into how you think about risk across your virtual £100,000 portfolio in the Student Investor Challenge — alongside everything else you already track about a company before deciding how much weight to give it.

Frequently asked questions

Is an MVP the same as a beta version?

They're closely related but not identical. An MVP is usually the very first working version released to real users to test whether an idea is worth building further. A beta often comes slightly later, once the basic idea has already been validated, and is used to iron out bugs and gather feedback before a wider public launch.

Do all big companies start with an MVP?

Not every company uses the term, but the underlying pattern — testing a small, unfinished version before investing heavily — shows up again and again in well-known launch stories. Some companies skip it because they have huge existing resources or are entering an already-proven market, but for most new ideas, an MVP-style test is the cheapest way to avoid building something nobody wants.

Why would a company show investors an unfinished product?

Because an MVP still answers the most important question: does anyone actually want this? Early evidence of real demand, even from a rough version, can matter more to investors than a polished product with no proven interest behind it. It also shows the team can build and test quickly, which is itself a useful signal.

Is "MVP" the same in software as in other industries?

The core idea — test the smallest version of something before committing fully — applies well beyond software, but the term is used most often in tech and startups. A restaurant testing a single pop-up stall before opening a full premises, or a brand trial-running one product before a full range, is working on the same principle even if nobody calls it an MVP.

Once you start noticing MVP-stage language in company news, it's hard to unsee it — and it gives you a sharper lens for judging how early, and how risky, a business genuinely is before you form a view on it.