How Much Does a Custom Web App Cost in Germany?

The cost of a custom web app is driven by what happens behind the screens, not by how many screens there are. Who logs in, what data is stored, which other systems the app talks to and whether money changes hands: those four questions explain most of the difference between a modest quote and a large one.

That is also why quotes for "an app" can differ wildly, whether they come from a Berlin studio or an offshore team. Once you know the cost drivers in your own idea, you can shrink the first version, compare quotes on the same scope and budget for the costs that continue after launch.

What makes a web app different from a website

A web app is an application that runs in the browser, with no app-store download. Apps built with web technologies can run on phones, tablets and desktops from a single codebase, and can even be installed like a native app if you want that. For many business ideas, you do not need separate iOS and Android apps.

A website informs; a web app does work. As soon as people sign in, enter data and come back to it later, there is logic to plan, build, test and secure. Adding a contact form or an embedded booking widget does not turn a website into a web app. If you are unsure which one you need, start with Website or Web App.

The cost drivers at a glance

Go through the table row by row and note which column fits your idea. The more rows land on the right, the bigger the project.

An integration usually runs through an API (application programming interface): an agreed way for two programs to exchange data, such as your app and your calendar or payment provider.

Why these drivers multiply the effort

Every role is a small application of its own

Customers see only their own records, staff see everything, admins can also delete. Each role needs its own views, rules and tests. Broken access control, meaning users can see or change data that is not meant for them, is number one in the current OWASP Top 10 (2025), the reference list of the most critical web application security risks. Getting this right takes time, and it is not optional.

Integrations are the most underestimated line item

Connecting to another service means reading its documentation, setting up test accounts, handling failures (what happens when the service does not respond?) and keeping up when the provider changes something. Two-way sync is far more work than a simple export.

If personal data flows to a service provider, such as a hosting, email or AI provider, the GDPR generally requires a data processing agreement with them (Art. 28). In Germany you will hear it called an AVV. Setting these up is part of the work.

Payments are more than a pay button

The payment provider handles the transaction itself. Your app still has to know what happens when a payment is cancelled, fails or is refunded, and who issues the invoice. Subscriptions and credit notes add another layer.

The admin area is easy to forget

Someone has to create, correct, block and export records. A plain admin area is manageable. Reports and dashboards are features in their own right.

Comparing local and offshore quotes

Founders in Germany often hold one quote from a local studio and one from a team abroad with a much lower day rate. A lower rate is only a saving if both quotes cover the same scope and the same responsibilities. Before comparing totals, check:

• Does each quote list the same roles, screens, integrations and admin functions?
• Who signs the data processing agreements, and where will the data be hosted?
• Is the interface delivered in German if your customers or staff are German-speaking?
• Who handles security updates and bug fixes after launch, and at what cost?
• Are hosting accounts, code and domain in your name, or the provider's?
• Are prices net or gross? German business quotes are usually net, plus VAT.

A cheaper build that leaves these open can end up costing more. A local provider is not automatically better either; the point is to compare like with like.

Hypothetical example: the same idea at two sizes

Running costs: what continues after launch

The one-time build price is not the whole bill. Plan for these from day one:

• Hosting and database: monthly costs that can grow with usage.
• Third-party services: email delivery, payment providers (usually a fee per transaction), maps, or AI APIs that often bill by usage.
• Maintenance and security updates: Germany's Federal Office for Information Security (BSI) names vulnerability and patch management as a key measure for web applications and recommends checking the components in use regularly for security holes.
• Backups: for personal data, the GDPR requires among other things the ability to restore access promptly after an incident (Art. 32). That needs tested backups.
• Further development: new features after launch are separate work.

Buy before you build

The cheapest web app is the one you do not have to commission. Appointment booking, invoicing, newsletters, simple forms and project boards are all solved by mature software on a monthly plan. If such a tool covers your core workflow, it is almost always the better choice.

Custom development makes more sense when your process is unusual and off-the-shelf software only fits with workarounds, when you are stitching several tools and spreadsheets together by hand, or when the app is part of what you sell to customers. The overgrown spreadsheet is a classic case; see Replacing a spreadsheet with a web app.

How you can influence the price

• One core job first: decide what version one must do to be useful. Web App MVP features shows how to cut a wish list down.
• Write it down: a clear brief prevents misunderstandings and change requests. Use the web app brief template.
• Fewer roles at launch: client accounts can often wait for version two.
• Manual before automatic: a weekly CSV export your office uploads to the accounting tool is much cheaper than a live integration.
• Design system over bespoke design: saves design and review rounds.
• A fixed quote: insist on a written scope before work starts.

Where Ichii's entry price fits, and where it does not

Ichii builds small, clearly defined web apps from €1,999 net, one-time; the final price depends on the agreed functions and is set in a fixed quote before the project starts. That entry point fits projects like Version A above. It does not mean every SaaS product, AI tool, portal or booking platform costs that: work involving ERP integration, many integrations or complex role models is outside that scope. Hosting, third-party services and technical maintenance from €29 per month (scope agreed individually) are charged separately.

Your next step

Place your idea in the table above. If most rows land in "Small", write a few sentences on who uses the app, the core workflow and the data it stores, and send us a web app enquiry. If many rows land on the far right, look first at established industry software or at a provider that specialises in large integration projects.