How Much Should an MVP Cost?

It is the first question most founders ask, and the honest answer — "it depends" — sounds like an evasion. It is not. The cost of an MVP is almost entirely a function of scope, and scope is a choice you make, not a fact you discover. The useful conversation is not "what does an MVP cost" but "what is the smallest version that would teach us something real?"

As a rough frame: a tightly-scoped MVP — one core workflow, standard integrations, no exotic requirements — typically lands in the low tens of thousands. Add real complexity — multiple user types, custom integrations, compliance, novel technical problems — and it climbs from there. The number is driven less by how big the vision is and more by how much has to be true on day one.

The most expensive decision is usually invisible: scope creep disguised as reasonableness. Every "while we are at it" feature feels small in isolation and enormous in aggregate. The last 10% of scope routinely takes 40% of the time. A disciplined MVP is defined as much by what it refuses to include as by what it does.

There is also a cost to under-investing. An MVP built too cheaply — no analytics, no error monitoring, brittle infrastructure — cannot actually teach you anything, because you cannot see what is happening or trust what you shipped. The goal is not cheapest; it is the smallest complete version that produces real signal.

The best way to control cost is to validate before you build and to sequence ruthlessly: ship the one thing that tests your core hypothesis, learn, then decide what is next with real data instead of a spec written on day zero. That is not a way to spend less — it is a way to avoid spending on the wrong thing.