In Switzerland, a serious MVP built by a senior independent typically lands in the tens of thousands of CHF. The budget splits into four blocks — framing, functional core, reliable foundations, operations — and framing is the one most often skipped.
The wrong reflex
Ask for an MVP price and you will get a number before anyone has discussed the problem. That is the sign you are being sold development days, not a product.
What the cost actually consists of
An MVP is not "a smaller version of the full product". It is the smallest thing that lets you learn whether the business hypothesis holds. The budget therefore has four blocks:
- Framing: deciding what is NOT in the MVP. This is the highest-value block and the one most often reduced to nothing.
- The functional core: the journey without which the user can learn nothing. Usually much smaller than expected.
- Non-negotiable foundations: authentication if needed, protected data, reliable deployment, a base for measuring.
- What nobody sees: operations, support, fixes during the first real weeks.
What bloats it unnecessarily
- Anticipatory architecture: microservices, queues and "just in case" abstractions. A typical Swiss MVP runs fine on a single modular foundation.
- Hidden scope: payment integrations, notifications, a full back office — each of these choices often doubles the surface.
- Decorative screens: anything that serves neither the first impression nor the learning journey.
An honest range
In Switzerland, a serious MVP built by a senior independent typically lands in the tens of thousands of CHF — not thousands, not hundreds of thousands. Below that, something is sacrificed — usually framing or reliability. Above it, you are probably building a disguised V2.
The question to ask before any estimate
What do I want to have learned in three months?
If the answer is "have a product", the MVP has already drifted from a decision tool to a showcase object.