Blog

Product2 min read

How much does an MVP cost (and why that's the wrong question)

Everyone wants the number. But the price of building the first version is the smallest part of the bill. What weighs is what happens after it goes live.

It is the question we hear most in a first conversation: “how much does it cost to build an MVP?”. It is fair. Whoever has an idea and a budget needs to know whether one fits in the other.

The problem is that the question measures the wrong part of the mountain.

The cost you see and the cost you don’t

Building the first version of a product has a visible cost: screens, business rules, payment integration, publishing. That is the number that goes into the proposal.

But there is another cost, which shows up in no proposal:

  • the server that has to stay up every month;
  • the library that gets a security fix and needs updating;
  • the backup that needs to exist — and work;
  • the small change the first customer asks for in week two;
  • the bug that only appears when the hundredth user does something nobody expected.

A cheap MVP that nobody maintains gets expensive very quickly. It doesn’t stop all at once: it grows fragile, until touching it becomes scary.

A better question

Instead of “how much does it cost to build?”, we prefer to start with another one: “what needs to be true for this idea to be tested with real people?”

That question cuts scope for the right reason. It isn’t about doing less to spend less, but about doing only what proves or disproves the hypothesis. Sometimes that is a full app. Sometimes it is a website with a form and an automation behind it. Sometimes it is a smart spreadsheet — and that’s fine.

The best MVP is the smallest product that answers your business’s most expensive question.

Building and maintaining in the same contract

That is why Kabran doesn’t separate the two. The same contract covers building and keeping it live: monitoring, backups, updates and the small everyday changes. You don’t get a file and a “good luck”. You get a working product, and we keep watching over it.

That changes the math. Instead of a big number at the start and surprises later, there is a predictable cost to keep the product standing and evolving.

So, how much?

It depends on what your idea needs to prove. And that is a conversation we like to have before any number: what you want to find out, who will use it, what happens if it works.

If it works, by the way, that is when the product most needs someone looking after it.

Written by Kabran