All articles

How much does it cost to build a web app?

A web app can cost fifteen thousand euros or half a million — and the difference is rarely the pretty screens. What actually sets the price, and how to keep it sane.

"Web app" covers an enormous range, which is why the price does too. A booking form and a full operational platform are both web applications, and they are separated by a factor of thirty in cost. Before you can budget for one, it helps to know what you are actually paying for — because it is almost never the part you are looking at.

The screens are the cheap part

The most common budgeting mistake is to price a web app by its screens. The interface — the buttons, forms, and pages you can see — is real work, but it is rarely where the cost lives. The cost lives underneath: the logic that decides what happens when a user acts, the data model that has to stay correct as the business grows, the permissions that decide who can see and do what, and the handling of everything that goes wrong. A screen that looks simple can sit on top of a week of rules; a screen that looks busy can be a day of work. You are paying for behaviour, not pixels.

What drives a web app's price

A handful of factors move a web app's cost more than anything else. User roles and permissions: an app where everyone sees the same thing is far cheaper than one where an admin, a manager, and a customer each get a different, controlled view. Integrations: connecting to payment, email, a CRM, or an existing back-office system is where estimates quietly balloon. Real-time and scale: if the app must update live, handle many concurrent users, or process significant data, the architecture — and the price — steps up. State and workflow: anything with an approval chain, a multi-step process, or records that move through statuses is more expensive than it looks. And the invisible essentials — security, testing, monitoring, and the ability to deploy safely — are what separate an app that survives real use from a demo that breaks in week two.

Rough ranges to plan around

As an illustrative guide, not a quote: a simple, well-scoped web app — a focused tool, a few roles, one or two integrations — commonly lands in the low-to-mid tens of thousands of euros. A serious business web application — real workflows, several integrations, proper roles, the reliability a company can run on — typically runs from the mid tens of thousands into the low hundreds. A large, scaled platform goes up from there. The spread within each band is wide, and it is driven mostly by how much genuine complexity hides behind the feature list and how high the bar for reliability is.

The costs that arrive after launch

A web app is not a purchase; it is a living thing that needs hosting, monitoring, security updates, and changes as your business changes. A realistic budget accounts for this from the start rather than being surprised by it — ongoing running and maintenance is a normal, ongoing line, not a failure of the build. Teams that ignore it end up with software that slowly rots because no one owns keeping it healthy, which is far more expensive than tending it would have been.

How to keep the price sane

The discipline that saves the most money is ruthless prioritisation of the first version. Decide the one job the app must do to be worth having, build exactly that to a high standard, ship it, and let real usage tell you what to build next. Resist the urge to launch with everything; a web app that does one thing genuinely well beats one that does ten things half-way, and it costs a fraction to get to something real that people actually use. From there, every euro you spend is informed by evidence rather than guesswork — which is the cheapest way to build anything.

Scoping a web app?

Tell us what you want it to do. We'll help you separate the version worth building first from the wish list — and put a real number on it.

Book a free discovery call