Custom software development in Germany: what it costs and what you get in 2026

If you are planning custom software development in Germany in 2026, you need three answers before you talk to any vendor: what it costs, what the price includes, and who should build it. A typical business application lands between 25,000 and 120,000 euros. This guide gives you the rate bands behind that range, the line items a serious quote carries, and a practical way to choose between an agency, a freelancer, and an international team like ours.

We build custom software for German clients every week, so this is the buying guide we hand to prospects before the first scoping call. It does not re-argue whether to build or buy. If that question is still open, read our custom software vs off-the-shelf guide first, then come back with a build decision in hand.

What counts as custom software development?

Custom software is software written for one client, as opposed to a package that many companies configure the same way. A customer portal that mirrors your pricing logic. An internal workflow tool that matches how your warehouse actually works. An integration layer that connects your ERP to a web shop without daily CSV uploads. A field service app with German language UI and offline views for technicians.

Three properties separate a real custom build from a configured package. First, you own the code and the data model, or your contract says exactly when each milestone becomes yours. Second, the scope follows your process instead of forcing your process into vendor fields. Third, the hosting, the interfaces, and the deletion routines are decisions you make, which is where the DSGVO work lives.

In Germany that third point carries weight. A custom build aimed at German users typically ships with German language UI and error messages, German date and tax formats, EU hosting, and a documented approach to personal data from day one. If a quote contains none of those lines, it is not a custom build for Germany. It is a generic build with German postage.

What does custom software development cost in Germany in 2026?

The honest answer is a range, because the same spec gets three different invoices depending on who builds it. In the proposals clients have shown us over the past two years, the bands look like this:

• German agencies: about 95-160 euros an hour. You get a German contract partner, German language everything, and people who can sit in your conference room.
• Senior freelancers: about 80-120 euros an hour. You get strong individual output and you supply the project management, QA, and DevOps around it.
• International teams like ours: 25-49 dollars an hour. You get senior engineering capacity with German side project leadership and QA sign-off on every release.

A typical business application, meaning a web app with user roles, several integrations, and German language UI, lands between 25,000 and 120,000 euros. The lower end is a tightly scoped first version with one or two integrations. The upper end is a multi role system with an ERP hookup, data migration, and a longer QA phase. Our app development cost guide for Germany walks through a worked 700 hour example at each rate so you can see where the spread comes from.

Three factors move a quote inside that range more than the feature list does. Integrations are the first. A documented REST API with a sandbox takes days. An old ERP with batch exports and manual reconciliation takes weeks. The second is DSGVO scope: processing agreements, deletion concept, and EU hosting setup are real hours, roughly 5 to 10 percent of a typical B2B build in our experience. The third is German language QA, meaning testers who notice when an umlaut breaks a PDF export or a tax format fails on an invoice.

Quotes also differ in what they leave out, which is why you should normalize them before comparing. Our guide to comparing software development quotes shows the method: same scope, same acceptance test, same warranty window, then compare. A quote that skips DSGVO, QA, and handover docs is not cheaper. It is shorter.

What is included in the price?

A serious custom quote in Germany has six parts. If any of them is missing, ask where it went before you sign.

Scoping and architecture. Expect a discovery phase that turns your process into user flows, a data model, and an integration list with effort attached. This is also where the hosting decision gets made. We default to EU regions, usually Hetzner or AWS eu-central-1 in Frankfurt, which takes most transfer and residency questions off the table early.

DSGVO compliant architecture. In a custom build this means data minimization in the data model, processing agreements with every sub-processor, a record of processing activities, and a working deletion concept. Products touching health or payment data need more, including a data protection impact assessment. This is budget scope, not legal decoration, and it belongs in the quote as hours.

Design and German language QA. German UI copy, German error messages, German formats, plus testers who run acceptance flows on staging against named test cases. Ask how many QA hours sit inside the quote and who signs the release. A build with zero QA hours is a build where you are the QA department.

Integrations and migration. Interfaces to ERP, CRM, payment, or identity providers, plus migration of existing data where needed. Each integration should name its API, its test environment, and its fallback behavior when the third party is down. Vague integration lines are where fixed prices go to die.

Acceptance and warranty. Each milestone needs pass criteria, a test window on staging, and a rule for silence. Warranty windows in agency contracts run thirty to ninety days from acceptance, covering defects against the agreed criteria. New requirements, third party breakage, and platform changes are not defects. That sentence belongs in the contract, not in a later argument.

Code you own and docs you can hand over. IP transfer tied to each accepted milestone, repository access with full history from day one, deployment docs, and a credentials inventory. Our contract checklist explains each clause in plain language, including which contract type you are signing and what it means for warranty. Our services page lists what we actually sign up for on each engagement shape.

Agency, freelancer, or international team: who should build it?

There are three sensible answers and they suit different projects.

A German agency fits when procurement needs a domestic contract partner, when people must be on site several days a week, or when a tender or certification regime only a German firm holds applies. You pay the 95-160 euro band for presence, process, and liability under German law. For safety critical systems, public sector tenders, and board level comfort purchases, that premium is money well spent.

A senior freelancer fits a small, well specified build with a technical owner on your side. A customer portal with one integration and a clear design is a classic freelance project at 80-120 euros an hour. The condition is real: someone on your side must own scope decisions weekly, test against edge cases, and run deployments. One freelancer getting sick becomes your new launch date, so keep the scope small enough that this risk is acceptable.

An international team like ours fits the middle that agencies overprice and freelancers cannot cover alone: a business application with several integrations, a deadline, and German standard communication. The engineering hours run in the 25-49 dollar band while German side project leadership owns scope, QA sign-off, and accountability. The trade-off is plain. We run on calls, shared boards, written decisions, and async updates rather than conference rooms. Clients who need a room full of people every Tuesday should hire the German agency with a clear conscience.

If you are unsure which shape fits, a short software consulting engagement before the build contract answers it cheaply. One scoping workshop usually shows whether the project is a freelance build, an agency build, or a team build, and it produces the scope document every vendor needs to quote against.

How does the DSGVO shape a custom build?

Whenever your software processes personal data of people in the EU, the GDPR applies, and a custom build gives you the controls a package never does. You choose where the data lives, what the data model stores, how long each record survives, and who processes it on your behalf.

In practice that means four decisions land in the architecture phase. Hosting region and sub-processor list come first, with EU regions as the default for German buyers. Data minimization comes second: every personal field needs a reason, because each field you store is a field you must protect and eventually delete. Deletion routines come third, meaning retention periods per record type plus a tested way to erase a user completely. Processing agreements with every sub-processor come fourth, and they must exist before launch, not after.

The contract side mirrors the technical side. Custom software built to order is generally treated as a Werkvertrag under Section 631 of the German Civil Code, which means a result is owed, and the default limitation period for defect claims runs two years unless the contract shortens it. Most agency contracts do shorten it to the customary thirty to ninety days. Hours billed under staff augmentation, by contrast, are usually a Dienstvertrag, where effort is owed and acceptance works differently. On IP, the Germany specific point from our checklist applies here too: usage rights transfer per milestone is the clause to insist on. Read the full reasoning in our contract checklist before you countersign anything.

One practical note from the projects we run. DSGVO work goes fastest when it starts in week one. Bolting a deletion concept onto a finished data model costs multiples of designing it in. Put the data protection decisions in the discovery document and the rest of the build inherits them for free.

How long does a custom project take?

A tightly scoped MVP takes roughly six weeks to three months from signed scope to staging. That covers one user role, one or two integrations, and a short QA phase. A business application with several integrations, data migration, and German language QA takes six months or more. Public sector timelines and certification gates add further months that no vendor can compress.

The biggest variable is rarely engineering speed. It is how fast the client decides. Projects with a named product owner who attends a weekly scope call and answers within days ship on time. Projects where five stakeholders must agree on every screen ship late at any hourly rate. Bitkom counted 149,000 unfilled IT positions in Germany, which is one reason internal decision capacity is scarcer than engineering capacity on most builds we see.

A realistic milestone plan looks like this. Weeks one and two: discovery, data model, integration inventory, hosting decision. Weeks three to ten: build in weekly releases to staging with QA sign-off per milestone. Final two weeks: acceptance testing against named criteria, migration, launch, and handover docs. Anything with an ERP integration or a data migration adds a second build block of similar length. Ask every vendor to map their quote onto a plan shaped like this one. The vendor who cannot is not ready.

How to start without an 80-page spec

You do not need a perfect specification. You need a tight first scope and a vendor who counts flows with you instead of billing you for ambiguity.

Start with one process, not the whole company. Name the users, the ten most important flows, the one integration that must work on day one, and the report or export the business cannot live without. That fits on two pages and it is enough for a serious vendor to estimate. Everything else goes on a phase two list that the contract explicitly excludes.

Then run one scoping workshop before the build contract. A good workshop produces the data model sketch, the integration list with test environments, the acceptance criteria per milestone, and the DSGVO decisions from the previous section. That document is what turns three vendor quotes into comparable numbers under our quote comparison method. Without it you are comparing moods.

Finally, sign a first milestone you can accept in four to six weeks. Fixed scope, named test cases, IP transfer on acceptance, warranty window stated. If the first milestone ships well, extend. If it does not, you have paid for one milestone and you own it. That is the whole method.

If you have a scope sketch, send it. We will count the flows with you, tell you which line items your project actually carries, and quote it in writing: talk to us.