Web App Development Cost (2026): 3 Price Levels Explained

Web app development cost in 2026 usually lands between €10,000 and €40,000 for an internal tool, €25,000 to €90,000 for a customer-facing app with logins and payments, and from around €55,000 for a platform with several user types. Those are my rough estimates for work by an experienced European freelancer, excluding VAT. What moves you within a range is rarely the number of screens: it's integrations, permissions and how much has to work on day one.

I'm a freelance developer based in Denmark, so treat these figures as a starting point for a conversation rather than a quote. I'll also point out when building a custom web app is the wrong move.

The short answer

The estimates assume €90-150 an hour, a realistic band for experienced freelancers in Western and Northern Europe. Two apps in the same column can easily sit at opposite ends of the range.

A quick way to place your project: if only your team logs in, you're at level one. If your customers log in, you're at level two. If different groups trade with each other or pay a subscription, you're at level three.

For the wider picture, including websites, mobile apps and maintenance, see my complete guide to software development cost.

How a web app quote is calculated

Nearly every quote comes from the same sum: estimated hours times an hourly or day rate. A fixed price is that same estimate with a risk margin on top.

The rate depends heavily on who you hire and where they're based. The freelancermap survey of more than 5,000 IT freelancers in Germany, Austria and Switzerland puts the 2026 average at €103 an hour, and €91 for development roles. Danish rates sit higher: LønRadar's 2026 rate guide lists DKK 800-1,200 an hour for senior freelancers in Denmark, roughly €110-160. Agencies usually charge more, because their rate also covers project management, sales and office costs.

Offshore teams quote much lower rates, and that can work. Often, though, the savings move into your own time: writing detailed specs, coordinating across time zones and checking quality. A developer at €70 an hour who needs 450 hours costs more than one at €110 who needs 250. I go deeper on what's normal in my post on freelance developer rates in Denmark and Europe.

Hours are the bigger unknown. They should cover discovery, interface design, testing, server setup, handover and the fixes that follow launch, not just coding. When a quote leaves those out, they tend to come back later as change requests.

Three price levels, with examples

Internal tools: €10,000-40,000

Internal tools are used by your own staff. They usually replace a spreadsheet that has outgrown itself, a process run through email, or a legacy system nobody dares touch. Think shift planning, an order overview that pulls from several systems, or an admin panel your support team uses to look things up.

It's the cheapest level because you can accept more. Users can get a short walkthrough, the design can lean on a ready-made component library, and when something breaks, the person affected sits down the hall. The low end is a single-purpose tool with a handful of screens. The high end adds roles, reports and an integration or two, for example with your accounting system or CRM.

Customer-facing web apps: €25,000-90,000

Once customers log in, the bar rises. Strangers need to use the app without help, on their phones and in whatever browser they have. You need password resets, transactional emails that actually arrive, and a plan for what happens when something fails on a Friday night.

Typical examples are a customer portal with orders and invoices, booking with online payment, or a self-service tool that takes load off your support team. In the EU, personal data comes with GDPR obligations: a lawful basis for processing, data processing agreements with your vendors and sensible hosting choices. Users never see that work, but doing it properly takes time, and it's a large part of the gap between the first two levels.

Platforms: from €55,000

A platform serves several user types with different needs and permissions. That might be a marketplace with buyers and sellers, a SaaS product where each customer company has its own account, or a B2B portal where customers, staff and partners work on the same data.

Complexity grows faster than the feature list here. Every new user type needs its own screens, permissions and notifications, and everything has to be tested across roles. Subscriptions, trials, upgrades and cancellations take far more work than they seem to on a whiteboard. If you're planning a subscription product, my breakdown of SaaS development cost in Europe covers it in detail.

The range is open-ended because platforms rarely stop growing. Many start with a first release of 600-1,000 hours and expand as users arrive.

What moves the price most

Within each level, the same factors push the cost up or down. These are the ones I check first when I estimate a project.

Integrations are the factor most often underestimated. In a meeting it sounds like one line: "it should pull orders from our ERP" (the central business system many companies run on). In practice the effort depends on whether that system has a decent API, whether there's a test environment, and who at the vendor answers questions. Ask for each integration to be priced as a separate line item.

Compliance deserves an early look too. If your app serves consumers, for example as an online shop or a ticketing platform, it may fall under the European Accessibility Act, which applies to products and services placed on the market after 28 June 2025. Service businesses with fewer than 10 employees and under €2 million in turnover are exempt. This isn't legal advice, so check with an adviser if you're unsure.

What it costs after launch

Running a web app costs money every month. Hosting, a domain, transactional email, backups and monitoring typically add up to somewhere between a few dozen and a few hundred euros a month for a modest app, depending on traffic and requirements. Hosting inside the EU can make GDPR simpler, and it's rarely the expensive line.

Then there's maintenance: security patches, framework and dependency upgrades, and the small fixes that appear once real users arrive. A common rule of thumb is to set aside 15-20% of the build cost per year for maintenance and small improvements. Treat that as a rough guide, since it depends heavily on how much you keep developing. My guide to annual web app maintenance cost breaks down what goes into it.

When you shouldn't build a custom web app

I build web apps for a living, but custom isn't always the right answer. Here are three situations where I'd usually advise against it:

• An off-the-shelf tool covers most of the need. If a SaaS product solves 80% of your problem for a monthly fee, it's almost always cheaper than building, even over several years. Adapt your process to the tool before you adapt a tool to your process.
• The need hasn't been tested. If you don't know whether customers will use it, start smaller with a no-code tool like Airtable or a lean first version. My post on realistic MVP development cost covers that route.
• Nobody on your side has time. A web app needs a steady flow of decisions from you. Without a dedicated contact person, the project gets slower and more expensive, no matter who builds it.

A custom build tends to pay off when the process is part of what makes your business different, or when workarounds in standard tools cost your team hours every week.

How to get a quote you can budget against

1. Describe the problem, not the solution. Who will use the app, what do they do today, and what does that cost you? That's easier to price accurately than a list of 40 features.
2. Prioritize ruthlessly. Split your wishes into "must be in the first release" and "can wait." It's the fastest way to move down the range.
3. Start with a discovery phase. For larger builds, I recommend a short, paid, fixed-price discovery phase that pins down scope, integrations and risks before any building starts. The final quote then becomes an informed estimate rather than a guess.
4. Ask for pricing per phase. A fixed price for the first release plus a clear agreement on what follows is easier to manage than one big number.
5. Check what's left out. Testing, hosting, handover and maintenance should be listed somewhere in the quote, even if the answer is "not included."

That's how I work: you deal directly with me as the developer, you own the code from day one, and you get a reply within one business day. You can see what a project looks like on my page about custom web app and platform development.

Frequently asked questions

Can I get a web app built for under €10,000?+

Yes, if the scope is very narrow, such as a simple internal tool with one purpose and no integrations. At that budget you rarely get customer logins, payments or a bespoke design. If money is tight, an off-the-shelf tool or a no-code setup is often a better place to start, and you can build something custom once the need is proven.

Does AI make web app development cheaper in 2026?+

Somewhat, but less than the hype suggests. AI coding tools speed up boilerplate and prototypes, and you should see some of that saving in a quote. The big cost items are still discovery, integrations, security, testing and responsibility for the app once it's live. If someone offers a full customer-facing app for a fraction of these ranges, ask who fixes the bugs afterwards.

Why do quotes for the same web app vary so much?+

Mostly because each vendor is pricing a different reading of your brief. One assumes a bare first version, another includes design, testing and hosting setup, and a third adds a margin for unclear requirements. Rates also differ by country and business model. Compare quotes line by line, and ask each vendor what they assumed you didn't need.

Who owns the code when a freelancer builds my web app?+

Whoever the contract says, so make sure it says you. In many European countries, copyright in code written by a contractor stays with the contractor unless the agreement transfers it, unlike code written by employees. Ask for a clause that assigns the rights to you, and keep the code in a repository you control from day one. This isn't legal advice, so have a lawyer review larger contracts.