Speed got cheap. Judgement did not. The build is now the commoditised part. The planning, the product judgement and the commercial thinking about what is worth building are where the value and the risk have moved.
How long the build takes
It depends entirely on what it is.
| What you're building | Rough build time |
|---|---|
| Proof of concept | Around 3 days. |
| Simple, well-scoped MVP | 2 to 4 weeks. |
| Genuinely complex MVP | 8 to 16 weeks. |
In short: a proof of concept can be built in days, a well-scoped MVP in a few weeks, and a genuinely complex product in a few months. Planning comes first and sits outside these build times. It is where the judgement happens, and it is the part that decides whether any of the build time is well spent.
Where the cost really sits
The build is cheap. The wrong build is not.
A cheap, fast MVP of the wrong product is the most expensive thing you can build. Not because of what it cost to make, but because of the time, the market position and the credibility you spend finding out it was the wrong thing.
So the real cost of an MVP is not lines of code. It is the judgement, the planning and the commercial thinking that decide what is worth building in the first place. That is the part worth paying for, and the part that AI has made more valuable, not less.
The honest position
The cheapest option is almost never the cheapest in the end. Offshore day rates look lower on paper, but the cost of rework, communication overhead and production failures often erases the saving.
And if your MVP is genuinely simple, you may not need a studio at all. A competent freelancer or a no-code build may be the honest right answer, and we will tell you if that is the case rather than sell you a build you do not need. Anyone quoting a firm MVP price before understanding your problem is selling you the cheap part and hoping you do not notice the expensive part is missing.