How much does an MVP cost – and how do you keep the start lean?

Having an MVP developed: what belongs in the minimum

An MVP is the smallest version of your product that delivers real value to a clearly defined target group and shows you whether the idea holds up. It is not a half-finished product and not a throwaway prototype, but a deliberately reduced, working application. Its core can usually be put in one sentence: who solves which problem with which workflow?

For the costs this means: the price does not result from your entire vision, but from the part you need to test now. Anyone who tries to squeeze in every wish function is no longer building an MVP but a full version with all its risks. So first define which assumption the project has to prove – for example that customers book an appointment online or upload data themselves – and build exactly that.

MVP, prototype or clickable mock-up: what is the difference?

A clickable prototype shows the interface and workflows without real functions behind it. It is the cheapest way to talk through ideas with prospects, and it is suited to clearing up misunderstandings early or to showing the idea to investors and partners. It answers whether people understand the concept, but not whether they will actually use the product in daily life.

An MVP, by contrast, really runs: users create accounts, store data and trigger the core workflow. That requires a database, logic and hosting, so the costs are higher. Often the combination makes sense: first a prototype for alignment, then an MVP for the real-world test. This way, budget flows into development only once the direction is right.

What makes an MVP more expensive – and what does not belong in it yet

Cost drivers usually come from well-meant additions. An admin area with many settings, several languages, different payment methods, elaborate notifications or a connection to every conceivable third-party system are rarely needed for the first test. Much can initially be handled by hand, such as writing invoices manually or processing requests by email, until it is clear that automation is worthwhile.

Still, plan the foundation properly: login, data security, data protection and a technical structure that allows extensions. Fixing these later is more expensive than building them right from the start. The decisive question is: do I need this function to test my core assumption? If not, it goes on the list for the second version.

• Belongs in the minimum: core workflow, login, data storage, data protection
• Can wait: admin area with many settings, additional languages
• Can wait: several payment methods, vouchers, loyalty programs
• Can wait: connections to third-party systems that can run by hand at first
• Can wait: elaborate animations and special design

Web, iOS or Android: which platform for the start?

The choice of platform strongly influences the budget. A web app runs in every browser, is quick to update and needs no approval from app stores. For many MVPs it is the most economical entry, especially as it can be placed on a smartphone home screen like an app. Native apps for iOS and Android add effort through device functions, tests on different devices and the publishing process.

A dedicated app is worthwhile at the MVP stage mainly if you absolutely need device functions such as the camera, background location or push notifications, or if your target group searches exclusively in the app store. A middle path is to develop with a technology that shares part of the code between web and mobile apps. We advise you on the platform before the budget is set.

From idea to test: how an MVP project runs

An MVP project begins with a clarification conversation: problem, target group, assumption and success criterion. Then we jointly define the scope and prioritize the functions. Design follows, a clickable prototype if needed, and development in short stages, after each of which you see a working interim version. This way you recognize early whether the direction is right and can adjust without blowing the budget.

Launching with real users involves a small circle of pilot users, simple measurement of usage and a fixed date for the evaluation. The decision comes out of that: expand, adjust or deliberately stop. A stop is also a valuable result, because it prevents costly misinvestment in a full version. This turns assumptions into a reliable basis for decisions.

Budget after the MVP: further development, operation and rights

Besides development, expect operating costs for hosting, domain, backups and maintenance. Also plan a budget for the next version, because an MVP delivers insights that call for adjustments. Anyone who puts all the money into the first version has no room afterwards to react to the feedback.

Clarify in advance, by contract, who owns the source code, design and access credentials and who may develop the application further later. For orientation: the Starter package from €2,500 suits a very compact MVP with a clear core workflow, the Professional package from €8,000 suits an MVP with a database, roles and integrations, and Enterprise is intended for extensive platforms. For a clearly defined scope we preferably offer a fixed price.