How much does a web app cost? Prices, cost drivers and running costs
Demian A. Venzke6 min read
"How much does a web app cost?" is about as precise as "How much does a house cost?". The answer ranges from a four-figure sum to an amount that would actually buy you a house. You still need to plan. So here are benchmarks, the main cost drivers and a few levers that save money without cutting the wrong corners.
The short answer
For a custom-built web app, current market overviews list roughly these agency ranges for the German-speaking market (business.digital, 2026, German):
| Project | Examples | Typical agency price |
|---|---|---|
| Simple | Booking with admin, internal tool, customer portal with login | from €20,000 |
| Medium | User accounts, roles, payments, emails, reporting | €40,000 to €100,000 |
| Complex | Marketplace, multiple tenants, AI features, many integrations | from €100,000 |
These are prices with a traditional project setup. How it can cost less without hurting quality comes further down.
What really drives the price
It isn't the number of pages that drives cost, it's the number of decisions the system makes for you. The main drivers:
User roles and permissions
An app where everyone sees the same thing is far simpler than one with customers, staff and admins. Every role brings its own views, permissions and edge cases. Two roles often mean more than twice the effort of one, because every transition between them has to be tested.
Payments
One-off payments are quick to add today. Subscriptions with upgrades, cancellations, invoices and taxes in several countries are a project of their own. I use established providers like Stripe or Paddle instead of building this myself. That saves weeks and risk.
Integrations
Every connection to an existing system, whether CRM, ERP or accounting, is a small project with its own documentation, its own errors and its own tests. In company projects, integrations are often the biggest source of uncertainty. That's why they need to be assessed before a fixed price is agreed.
Design ambition
A clean, understandable interface built on proven patterns isn't a cost driver, it's the standard. It gets expensive with elaborate animations, custom illustrations or a full design system.
Web or native
A web app runs in the browser on every device. Native apps for iOS and Android add store approvals, two platforms and separate updates. For a first product, a web app is almost always enough.
Privacy and security
Personal data, health data or payment data increase the review effort. That's no reason to save money, it's a reason to get it right from the start. Which gaps are especially common is covered in Security flaws in AI-generated code.
Fixed price or hourly rate?
Freelancers in the German-speaking market charge around €104 per hour on average (Freelancer-Kompass 2025, German), agencies usually more. Both models have their place:
- Hourly rate: flexible while the scope is still changing a lot. But the risk sits with you: every loop, every open question and every detour ends up on your invoice.
- Fixed price: predictable, because the scope is fixed beforehand. If the provider misjudges it, they carry the risk. The precondition is a clearly defined scope.
I work exclusively with fixed prices or a fixed monthly scope. It forces both sides to decide clearly what gets built before anything starts. And that is exactly what saves the most money.
Running costs after launch
Many budgets end at launch. The app keeps running though, and that costs money:
- Hosting: a server in Germany starts at a few euros a month. Managed platforms cost more but take work off your hands.
- Database and storage: many providers have free entry tiers, then billing follows usage.
- Email delivery, analytics, payment providers: usually small monthly amounts or fees per transaction.
- Maintenance: updates, security patches, small adjustments. Set aside a fixed budget instead of leaving it to chance.
For a small product, pure operating costs are often in the range of a few dozen to a few hundred euros a month. The bigger item is further development, once real users give real feedback.
How to save without cutting the wrong corners
- Test before you build. A clickable prototype for a few thousand euros answers many questions before the first line of code exists.
- One core flow first. Start with the one path that shows the value. Everything else comes when users ask for it.
- Standards over custom builds. For login, payments and email there are proven building blocks. Custom work only pays off where it sets you apart from competitors.
- Less coordination, more decisions. The most expensive time in projects is waiting for approvals. One accountable person who is allowed to decide saves more than any discount.
- Use AI, but with judgement. AI tools write a large share of code today. Without experienced review, though, that turns into costly security gaps and products nobody understands.
What you get with Framepass
The packages build on each other, so you only invest as much as the next decision requires:
| Package | Duration | Price | Result |
|---|---|---|---|
| Sprint | about 1 week | €3,500 | Concept, scope, clickable prototype |
| Pilot | about 3 to 4 weeks | from €9,500 | Your MVP: one working core flow, live |
| Product | ongoing | from €6,500 per month | Further development without an in-house product team |
What exactly is included is on the homepage.
Frequently asked questions
How much does a simple web app cost?
At agencies, a simple custom web app usually starts at around €20,000. With a clear scope and a fixed price, a first working core flow is possible for considerably less, at Framepass from €9,500.
How much does a web app cost per month?
For small products, pure operating costs for hosting, database and services are often a few dozen to a few hundred euros a month. On top of that comes a budget for maintenance and further development.
Is a fixed price realistic in software development?
Yes, if the scope is clearly defined before the start. Additional requests are then agreed before implementation instead of being billed afterwards.
Is a web app cheaper than a native app?
Usually, yes. A web app runs in the browser on every device. Native apps need two platforms, store approvals and separate updates.
Conclusion
A web app costs as much as the decisions it has to make. If you reduce the scope to the core, use standards and work with a fixed price, you get to a working product for far less than with an open-ended hourly budget, and you stay in control of the spend.