How much does it cost to build an app, web app or MVP?

Choose what you are building and what the first release needs. The estimator shows a practical price range, delivery time, and the choices that affect both.

  • Transparent ranges
  • No personal data
  • Runs in your browser
Build the estimate
Choose the productA feature, web app, mobile app, or both.
Add what it needsAccounts, payments, integrations, maps, AI, or data.
Check the resultSee the cost, timing, and assumptions.

Build an initial estimate.

Choose the starting point and what the first release really needs.

What are you starting with?

The base includes one complete flow. Add only what it needs.

How defined is the first release?
What is needed beyond the core flow? Optional

Complex subscriptions, advanced AI, offline use, and legacy migrations need review first.

Four common project shapes.

Compare the likely cost and delivery time.

01

A feature or integration in existing software

EUR 3,000–8,0001–6 weeks

One defined outcome such as payments, a private area, an API, an internal panel, or a flow to finish.

Assumption: The project runs, access is available, and the change stays within one area.
02

A lean web MVP

EUR 10,000–25,0006–14 weeks

A usable web application with one main journey, the required backend, and deployment.

Assumption: One primary user, few integrations, and secondary features left for later.
03

A mobile MVP

EUR 15,000–35,0008–18 weeks

A first iOS and Android app with a backend, device testing, and a distributable build.

Assumption: The mobile flow is defined, without a full web app or large back office.
04

A web and mobile product

EUR 25,000–55,000+14–30+ weeks

The same journey works across web, iOS, and Android with shared backend and product logic.

Assumption: Release the core journey first, then add the remaining surfaces.

What moves the price.

These four areas have the biggest effect on cost and timing.

01

The main journey

Who uses it, what they complete, and what data the product needs to retain.

02

The starting point

Working code and deployment reduce uncertainty; missing tests or access add it.

03

Accounts and services

Permissions, recovery, payments, maps, email, and APIs add real states and failure cases.

04

Platforms and release

Web, mobile, stores, monitoring, and support change both build and release work.

What the estimate covers.

The range assumes one agreed release. Third-party fees and work added later are separate.

Included in the work

  • agreed frontend, backend, and integrations
  • testing and release preparation for the selected journeys
  • code, access, and handover notes

Separate costs

  • VAT and third-party subscriptions or usage
  • branding, content, and marketing
  • ongoing maintenance or features added later

Common questions.

Can an app or MVP be built for less?

Yes, by reducing the first release: one journey, one platform, fewer roles, and fewer integrations. A static prototype costs less, but it is not a working product.

What changes when code already exists?

Existing code can save time or add uncertainty. I check setup, the relevant code, tests, access, and deployment before pricing the change.

Does MVP mean an unfinished product?

No. The main journey must work from start to finish. Secondary features wait; reliability and data ownership do not.

Have a project in mind?

Send the estimate and anything that already exists. I will reply with the next practical step.