Skip to content
DT Nova

Web app development cost: what a web application costs to build and run

Web app development cost is set by what the application has to do and for whom: how many user roles and workflows it supports, what data it holds, which systems it connects to, and how strict its security, privacy and accessibility requirements are. An internal tool for one team and a customer-facing product used by many organisations can differ several times over in work, even if both look like a few screens in a browser. This guide explains the cost drivers, the running costs after launch, the costs people forget, and how to compare quotes on the same basis.

It does not quote our own prices. It explains how a web app budget is built, so any quote you receive, from us or from anyone else, makes sense. For what we build, see web app development; for software budgets in general, see our guide to custom software development cost, and for mobile apps, the guide to app development cost.

The short version

  1. The first version: discovery, design, building, testing, data migration and launch. People's time is almost all of it.
  2. Running costs: hosting, databases, storage, email and third-party services, growing with users and data.
  3. Maintenance: security updates, dependency upgrades, monitoring and fixes, every year.
  4. Change: new features as users show what they need.

Three common shapes of web app

ShapeTypical scopeWhat sets the cost
Internal toolOne team, a few workflows, login through the company identity providerWorkflows, integrations with existing systems, permissions
Customer-facing appCustomers log in to order, book, track or manage somethingSelf-service flows, security, accessibility, support load
SaaS productMany organisations share one system, each with its own users and dataTenant separation, billing and subscriptions, admin tools, scale

People's time is most of the bill

A web app is built from hours: understanding the workflow, designing screens, writing and testing code, and preparing it to run safely. What an hour costs follows where the team works. Eurostat's release of 31 March 2026 puts average hourly labour costs across the whole economy in 2025 at €34.9 in the EU and €38.2 in the euro area, from €12.0 in Bulgaria to €56.8 in Luxembourg (read on 12 November 2026). These are whole-economy figures, not software rates, but they explain why the same scope is quoted very differently in different countries. Compare totals for the same scope, not hourly rates.

What drives web app development cost

DriverWhy it adds workHow to keep it in check
Roles and permissionsEach role sees different data and actions, and every rule must be testedDefine who may see and do what before design starts
WorkflowsEach workflow has states, rules, notifications and edge casesBuild the workflow that carries the value first
IntegrationsERP, CRM, payments, identity and other systems each have their own interface and limitsCheck the other system's interface before quoting
Multi-tenancySeparating customers' data in one system touches every query and screenDecide early whether the app serves one organisation or many
Payments and billingSubscriptions, invoices, taxes and refunds add logic and testingUse a payment provider's billing features where they fit
Offline and mobile useOffline data and installable app features need extra design and testingA responsive web app first; add offline only where used
Security and privacyLogin, access control, logging and data protection by design are built in, not addedCollect only the data the workflow needs
AccessibilityForms, tables and dashboards are where accessibility usually failsTest against WCAG 2.2 from the first release

Requirements that belong in the scope

Some requirements take little effort to plan and a lot to retrofit. The GDPR requires data protection by design and by default (Regulation (EU) 2016/679, Article 25) and security appropriate to the risk (Article 32), which affects the data model, access control and logging from the first day. WCAG 2.2 has been a W3C Recommendation since 5 October 2023 (current version 12 December 2024) and is the standard most buyers now test web apps against. For security testing, the OWASP Web Security Testing Guide, version 4.2 at the time of reading, describes what a thorough test of a web application covers (all read on 12 November 2026). Ask each supplier how these are handled in their quote.

Buy, configure or build

A custom web app is not always the right answer, and a good supplier will say so. If a ready-made product or a low-code tool covers the workflow, the subscription is usually the better deal at first. A custom web app pays off when the workflow is what sets you apart, when the team works around a product in spreadsheets, when per-user fees grow faster than the business, or when you need data and code under your own control. Compare five years for the same users and scope: subscription fees, add-ons and workarounds against the build, hosting and maintenance.

The hidden costs of a web app

  • Third-party services. Maps, identity, email, file processing and AI models priced per user or request can outgrow hosting.
  • Data migration. Moving data from spreadsheets or an old system takes cleaning and checking.
  • Admin tools. Someone has to manage users, fix data and answer support questions; those screens need building too.
  • Dependency upgrades. Frameworks and libraries release security fixes all the time.
  • Support. Customer-facing apps bring questions, and the answers cost staff time.
  • Exit. Code, data and hosting outside your company's name make every future change dearer.

Pricing models and who carries the risk

ModelHow it worksWho carries the risk
Fixed priceAn agreed price for a written scopeThe supplier carries estimation risk; the buyer carries the risk of a wrong scope
Time and materialsHours billed as worked, against an estimateThe buyer carries overrun risk; most flexible
Phased fixed priceThe first version at a fixed price, later phases priced one at a timeShared: each commitment is small and based on real use
Dedicated teamA team billed monthly for continuous developmentThe buyer carries the risk of low output; fits long-running products

How to compare web app quotes

  • Is it a fixed price for a written scope, or an hourly estimate?
  • Which roles, workflows and screens are included, by name?
  • Which integrations are included, and what is assumed about the other systems?
  • How are security, privacy and accessibility tested, and against which standards?
  • Does it include hosting set-up, backups, monitoring and a launch period?
  • What does maintenance cover each year, and what counts as new work?
  • Which third-party services are assumed, and who pays for them?
  • Are the source code, database and hosting accounts in your company's name?

Ways to spend less without cutting quality

  • One workflow first. Launch the part that carries the value, then add the rest based on use.
  • Web before native. A responsive web app often covers what separate apps would.
  • Buy the commodity parts. Identity, payments, email and file storage are solved problems.
  • Fewer roles. Every role you do not add is a set of permissions you do not test.
  • Own the code. Code in your own repository keeps every future change open to competition.

Related reading: client portal cost, API integration cost and software maintenance cost. All our services are on the services page, and every guide is in the guides library.

Questions people ask

How much does it cost to build a web app?

It depends on the number of user roles and workflows, the data it holds, the systems it connects to and how strict the security, privacy and accessibility requirements are. An internal tool for one team with a few screens is a different project from a customer-facing product with payments, subscriptions and several organisations sharing one system. Any figure given before that scope is written down is a guess.

Is a web app cheaper than a mobile app?

Often, because one web app runs in every browser on desktop and mobile, with one codebase and no app store review. A mobile app is the better choice when the product needs offline use, deep device features or a place on the home screen that a progressive web app cannot give. Compare both for the same features.

What does a web app cost to run each month?

Hosting and databases, file storage, email and other services, monitoring and backups, which grow with users and data; plus maintenance, security updates and support. Third-party services with per-user or per-request pricing, such as maps, identity or AI models, can become the largest running cost.

What is a progressive web app, and does it cost more?

A progressive web app is a web app that can be installed to the home screen, work partly offline and send notifications in supported browsers. It adds some design and testing work over a plain web app, and is often far less work than separate native apps.

Who owns the code of a custom web app?

That depends on the contract. With us, the source code, database and hosting accounts are in your company's name from the start, so you can change supplier without rebuilding. Check this clause in every quote.

Sources

Your web app scope checklist

Write one line for each before you request quotes. The answers make quotes comparable.

  • The problem the app solves, and for whom, in one sentence.
  • Internal tool, customer-facing app or SaaS product.
  • Each user role and roughly how many people.
  • The workflows in the first version, step by step.
  • The systems it must connect to, and how they expose data.
  • The data it holds, and which of it is personal data.
  • Payments or subscriptions, if any.
  • Devices and offline needs.
  • Accessibility and security standards to test against.
  • Ownership: code, database and hosting in your company's name.