How much does an MVP cost in 2026? Market ranges, cost drivers and hidden costs

The cost of an MVP ranges from €25 a month for an AI app builder to six-figure agency budgets. Most agencies in the DACH region (Germany, Austria, Switzerland) quote €15,000 to €50,000. This guide puts the costs of an AI app builder, a freelancer, an agency and your own team side by side, with sources and dates. We have deliberately left our own prices out: you will find them on our MVP development page.

First, a definition: in 2009, Eric Ries described the MVP as the version of a new product that lets a team collect the maximum amount of validated learning about customers with the least effort. The same post contains a sentence that reframes the cost question: "MVP, despite the name, is not about creating minimal products." With an MVP, you buy an answer, not a finished product.

Hence the first rule of MVP costs: what an MVP should cost depends on the question it is meant to answer. A waitlist tests interest; a subscription with real payments tests willingness to pay. The agency TJ Labs prices a landing page with a waitlist at €3,000 to €8,000 and a web app MVP at €20,000 to €50,000.

One question up front can sometimes save the entire budget: are you building an MVP at all? If you want to find out whether customers will use and pay for a new product, you are building an MVP. If you want to digitize an established internal process, you need custom software, which follows different economics.

If you are still unsure what form your product should take, our comparison of website, web app or portal will help.

About the data: on October 10, 2026, we reviewed the German-language Brave Search results for "was kostet ein MVP" (what does an MVP cost), "MVP Kosten" (MVP costs) and "MVP entwickeln lassen Kosten" (cost of having an MVP built). None of the guides compares all four routes with sources and dates. Running costs usually appear as a lump sum, with no provider and no date.

First, an overview: we compare four routes to an MVP, and each one bills differently. We leave out nearshore teams (developers in nearby countries); according to easy.bi, their rates run from €40 to €80 per hour. The table summarizes the figures as of October 10, 2026; the sources follow in the text.

Here we look at MVPs that run in the browser. If your MVP is purely a mobile app in the Google ecosystem, Firebase is usually the simpler starting point; our comparison Supabase or Firebase explains why.

AI app builders such as Lovable and Bolt generate a working application from text prompts. Lovable costs €25 a month on the Pro plan with 100 credits and €50 on the Business plan, both including VAT as listed for Germany. Credits cover building, chat, hosting, the backend and the AI features of the finished app; 50 additional credits cost $15 on the Pro plan.

Bolt bills in tokens, which are units of AI usage: the Pro plan starts at $25 a month for 10 million tokens. Lovable states in its documentation that the chat pricing model applies only until October 31, 2026, and that the included cloud and AI allowances are provisional. So check the prices on the day you decide.

On ownership, Lovable is clear: "You own your code," its FAQ says, with one caveat: "subject to any third-party rights in the underlying AI models." Success, however, raises the bill: according to Lovable, apps that reach significant traffic or size may incur costs beyond the included allowance.

For an investor demo, a builder is the cheapest route. It reaches its limit when real customer data and payments come in: from then on, the data model, permissions and operations matter more than build speed. In a later migration, the interface is rarely the expensive part; the data model is, as our article on migrating from Firebase to Supabase shows.

For freelance developers, there is a reliable figure: freelancermap's Freelancer-Kompass 2026 reports a median of €90 per hour for software and web development and €95 across all IT disciplines. It is based on four surveys of 5,412 platform users and anonymized data from more than 340,000 users in the DACH region. At the median, 100 hours cost €9,000.

What a single freelancer rarely provides: project management, a second person for code review and cover during vacations. For an MVP, that need not be a drawback, as long as someone on the founding team can manage the technical work.

Agencies publish ranges, and most of them fall between €15,000 and €50,000. Two of them, proreactware from Ingolstadt and business.digital, cite exactly this range for a typical MVP. For a web app with a backend and login, proreactware estimates €25,000 to €50,000. Groenewold IT puts a web app with two to three core features at €15,000 to €40,000 net; easy.bi and bytefront give the same range for a simple MVP.

Beyond that range, prices fan out in both directions. BlueBranch, based in Fürth, advertises a starting price of around €8,000 for a lean scope. TJ Labs estimates €50,000 to €100,000 for complex MVPs such as marketplaces, while easy.bi and bytefront cap their top tier at €250,000. According to TJ Labs, hourly rates in Berlin run from €95 to €145; decivo puts them at €80 to €140 for experienced developers.

A caveat: these are vendor statements, not market statistics, and hardly any page cites a source. Do the math: published agency rates range from €80 (easy.bi) to €200 (proreactware) per hour, a factor of 2.5. The range of €15,000 to €50,000 spans a factor of 3.3. So the hourly rate explains much of the spread; the rest comes down to scope, meaning what the price includes.

An in-house team has no project price, only salaries. The Entgeltatlas (pay atlas) of the German Federal Employment Agency reports a median of €6,301 gross per month for expert-level occupations in software development. Over a year, that comes to €75,612 for one position, before employer social security contributions, office space and equipment.

The German Federal Statistical Office measures what an hour of work costs the employer: in the information and communication sector, it averaged €58.50 per hour worked in 2025, including gross pay and non-wage costs. Then there is time: according to the German digital industry association Bitkom, filling an open IT position takes 7.7 months on average.

For an MVP, this is the slowest route: by the time the position is filled, any of the other three routes would long since have delivered numbers. A single hire is not a team either: nobody covers for them during vacation or illness. That is why we advise against hiring permanent staff too early.

The right route is the cheapest one that still answers your question.

Before we get to technology: the length of the feature list is the first price driver. In 2019, Pendo analyzed usage data from its customers' software products. On average, 80% of features are rarely or never used, and 12% generate 80% of daily usage. The analysis covered 615 customer accounts with more than one year of usage data.

For your MVP, this means: every feature you cut is one you neither build nor maintain. For what remains, five variables move the price. They differ in cost and, above all, in how expensive they are to add later.

An integration connects your MVP to another system, for example the ERP system where a company manages orders, inventory and invoices. The price hinges on one distinction: reading and displaying data is manageable. Writing data back requires error handling, automatic retries and coordination with the other system's vendor.

So the rule for an MVP is: connect read-only first. Add write access only once the measurement phase, meaning the first weeks with real users, proves the need. We take the same approach when connecting customer portals to ERP and SSO: the first version displays data, and write operations come later.

A role defines what someone is allowed to do in the system. Two roles, such as customer and administrator, are a simple branch in the code. A tenant, by contrast, is a customer company whose data must be kept strictly separate from that of other companies. If you sell your MVP to businesses, this separation belongs in the data model from the start.

Separation gets expensive when every part of the application has to enforce it on its own. It is cheaper to enforce it directly in the database with Row Level Security (RLS): the database returns to each company only its own rows. Our article on Row Level Security in Supabase shows how this works without an extra layer in the code.

Payments cost you twice: once in the build and again on every transaction. For the integration, vendors quote €3,000 to €6,000 (proreactware) or around €4,000 (business.digital). For ongoing fees, Stripe's German pricing lists 1.5% plus €0.25 per payment for standard EEA cards, 2.8% plus €0.25 for premium cards and €0.35 for SEPA Direct Debit.

Subscriptions through Stripe Billing cost an additional 0.7% of billed volume, with no setup or monthly fees. For example, a €49 monthly subscription paid by standard card incurs about €1.33 in fees, or 2.7%. By direct debit, it is about €0.69. Our tech stack overview describes the role Stripe plays in our projects.

Enterprise customers want their employees to sign in with their existing company account: single sign-on, or SSO. The backend platform Supabase offers SSO via SAML 2.0 starting with the Pro plan, with 50 SSO users per month included and $0.015 for each additional one. WorkOS, by contrast, bills per connection, meaning per customer company: $125 a month per connection for up to 15 connections, tiered down to $65 per connection for 51 to 100.

For comparison: ten customer companies with 500 SSO users in total cost $6.75 a month at Supabase on top of the Pro plan, versus $1,250 at WorkOS. The alternative to Supabase's built-in login (Supabase Auth) is Keycloak, an open-source server for authentication and permissions. It has no license fee, but running it costs money, as our article What does Keycloak really cost? shows. Is Supabase Auth enough? explains when you need it.

Procurement teams at larger companies ask for evidence such as a SOC 2 audit report or an ISO 27001 certification. At Supabase, both are available only from the Team plan at $599 a month. Your MVP will usually not be certified itself. You can, however, prepare the documents procurement wants to see from the start.

If you plan an AI feature, the EU AI Act comes into play: according to the European Commission, the transparency obligations under Art. 50 have applied since August 2026. One example: telling people that they are interacting with an AI. The high-risk rules take effect only on December 2, 2027 (Annex III) and August 2, 2028 (Annex I). For an MVP, this usually means: plan for labeling and document how you classified your system.

A lot can wait, such as writing back into other systems. Tenant separation, however, belongs in the data model from day one.

A quote usually describes what will be built and rarely what operations will need afterward. In the cost guides we reviewed, hardly any of the following four items appears as a verifiable deliverable, even though you need all four from the first real user on. So ask for them in every quote; the full list of twelve items and eleven questions for vetting a quote is in our article on custom software development costs.

A test environment, often called staging, is a second instance of your MVP where you check changes before customers see them. Without one, your customers do the testing. Technically, it is cheap: Supabase charges $0.01344 per hour for a preview branch (its branching feature), so a full month of continuous operation at 730 hours costs $9.81. The effort lies in setting it up, not in running it.

A backup that has never been restored is just a hope. The German Federal Office for Information Security (BSI) makes restore testing a basic requirement in module CON.3: it "MUST be tested regularly" whether backed-up data "can be restored correctly and within a reasonable time" (our translation). Depending on the risk, Art. 32 GDPR also calls for the ability to restore data promptly after an incident and regular tests of how effective security measures are.

The Supabase Pro plan includes daily backups with seven days of retention. If you want finer-grained restore points, you can add point-in-time recovery, which restores to any given moment: according to the Supabase documentation, it costs $100 a month for a seven-day recovery window and requires at least the Small compute tier. The real cost item, though, is the test: restore, time it, record the result and repeat regularly.

Software ages even if you add no new features. One example is the JavaScript runtime Node.js: version 20 has received no updates since April 30, 2026, and version 22 will receive them until April 30, 2027. For production, the project recommends only long-term support (LTS) versions. If you launch your MVP on Node.js 22 today, plan the upgrade within the first year of operation.

Node.js 24 receives updates until April 30, 2028, and Node.js 26 is scheduled to become an LTS version on October 28, 2026. Then there are the dependencies: third-party libraries that receive their own security updates. Updates are therefore not an extra but a fixed operating cost.

As soon as your MVP processes personal data, you need a data processing agreement (DPA) with every service provider that processes it on your behalf. Art. 28 GDPR requires this contract to set out, among other things, the subject matter, duration, nature and purpose of the processing. This applies to hosting, email delivery and the agency or freelancer who handles operations.

The technical and organizational measures (TOMs) under Art. 32 describe how you protect the data. For you, they are an obligation; for your enterprise customers, they are a standard procurement question. Our article on a trust center for your SaaS product, a public page with your security evidence, covers which other documents procurement wants to see.

If these items are missing from the quote, you pay for them anyway: later, as a change request or after an incident.

Launch ends the build, not the bill. From then on, the bill arrives every month, and it has three parts: cloud services, fees and hours. The table shows list prices for an example setup with Supabase as the backend, as of October 10, 2026. Our introduction to Supabase explains what Supabase is.

For an MVP with few users, that comes to $45 a month: Supabase Pro and Vercel Pro, with email and error monitoring on free tiers. With a second developer seat, Resend Pro and Sentry Team, it is $111, or $114 with Sentry billed monthly. Two free tiers are only good during the build: Supabase Free pauses projects after a week of inactivity, and Vercel's pricing page limits Hobby to "personal, non-commercial use."

Fees depend on revenue (see Payments above). The third part is hours: updates, monitoring and small fixes. Rules of thumb that put this at 10 to 30% of development costs per year are common, mostly without evidence. Calculate in hours instead: in our experience, two to five hours a month are realistic for a web application of this size.

At the freelancer median of €90 per hour, that is €180 to €450 a month. Agencies charge their own hourly rates.

Operations are a line item of their own, not a percentage of development.

For this calculation, we use a market example rather than a quote of our own. Drawing on its project experience, the business.digital magazine puts an MVP at around €28,000 net and itemizes it: concept €3,000; design €4,000; core feature with user accounts and admin area €14,000; payment integration €4,000; testing, hosting setup and go-live €3,000. It is the only itemized example we found in the German search results, and it stops at go-live.

We extend it by twelve months of operations, based on three assumptions. First, the MVP runs commercially, meaning on Supabase Pro and Vercel Pro. Second, the subscription costs €49 a month and is paid by card via Stripe Billing. Third, support takes two to five hours a month, valued at the freelancer median of €90.

Result: the build and the first year of operations cost €30,160 to €33,400 plus $657.73 for services and the test environment, excluding taxes and payment fees. The build is the largest item, but support and services keep running long after the final project invoice.

More important than the total is what happens after the measurement phase. CB Insights analyzed 431 venture-backed startups that have shut down since 2023; for 385 of them, the reason could be identified. The most common one, in 70% of cases, was running out of capital. The median company had raised $11 million beforehand.

CB Insights itself puts the 70% in context: running out of capital is almost always the end point, not the cause. Behind it lie a lack of product-market fit, meaning too little demand for the product (43%), bad timing (29%) and unsustainable unit economics (19%). Cases could have more than one reason.

For your MVP, this means: hold back part of the budget. An MVP that eats the whole budget answers its question but leaves you no money to act on the answer.

First, the legal background in Germany: under a contract for work (Section 631 BGB, German Civil Code), the vendor owes the promised result; under a contract for services (Section 611 BGB), only the agreed services. In the first case, the vendor bears the risk that the software does not get finished. In the second, you do. Our guide to custom software development costs covers what applies at acceptance.

An MVP adds a twist: no vendor can contractually owe you product-market fit. A contract for work ensures that the first version works as described, not that customers want it. That is why a fixed price suits the first version with a fixed scope. For everything you learn from the metrics after launch, time and materials with a budget cap is the better fit.

A fixed price requires a clear scope. That scope comes from a short, paid concept phase, often called "discovery." The Austrian vendor Wavect, for example, charges €3,500 for two to three weeks, credits the full amount if you then commission the project and offers a fixed price under a contract for work.

This matches our experience from more than 150 completed projects: a fixed price for a small, tightly scoped first phase, then time and materials with a budget cap and approval every two weeks. Our fixed-price MVP follows the same pattern.

A fixed price buys you predictability in the build, not certainty that the market will play along.

Public funding can make an MVP cheaper, but only in the right order. In Germany, the federal funding database is a neutral starting point, covering programs from the federal government, the states and the EU. We do not list individual programs here, because programs, deadlines and budgets change constantly.

The key rule comes from the administrative regulations that accompany German budget codes. In the German state of Brandenburg, grants may "only be approved for projects that have not yet started." The start of a project is "generally the conclusion of a supply or service contract attributable to its execution" (our translation).

In the application, you also declare that you will not start before the grant decision without the approving authority's consent. If you sign the development contract before approval, you put the funding at risk. Other budget codes contain comparable rules.

The approving authority can grant exceptions in individual cases, and the responsible ministry can do so for entire funding areas. Some programs therefore allow you to start once your application has been received, though without any guarantee of approval. The program's guidelines set out what applies. When in doubt, schedule the project start after approval: a funding application is work in itself, and approval takes time.

Also check each program's purpose: some fund only internal projects and do not fit a product you want to sell to external customers. One principle from our roadmap for adopting AI in your company applies to an MVP as well.

Funding should never be the reason for a project.

Before you request quotes, answer three questions in writing. One page is enough, and it is what makes the quotes comparable.

Also write down which result will make you stop. A stop criterion set in advance protects you from one of the most expensive MVP mistakes: continuing to build even though the numbers say otherwise. Stopping after the measurement phase is then not a failure but a result.

Our packages and price ranges are public on our MVP development page; we quote the fixed price after a short concept check.

If you would rather have me look at your project directly, book an intro call with me: 30 minutes, no obligation. I will map your MVP to one of the four routes and tell you which items are still missing. If an AI app builder is enough for your question, I will tell you that too.