A web development engagement gone wrong almost always traces back to gaps in the contract — IP rights unclear, scope undefined, acceptance criteria missing, AVV not signed, exit terms vague. German contract law has specific shape that US-style “let’s just sign a one-pager” doesn’t address. For a German GmbH commissioning web work in 2026, the contract is the cheapest insurance you’ll ever buy.
This guide walks through what a web development contract for a German GmbH actually needs to cover in 2026: the Werkvertrag vs Dienstvertrag distinction, IP transfer, AVV/DPA, GoBD-compliant billing, change control, exit clauses, and the German-specific contract patterns that protect a GmbH from common dispute scenarios.
This guide is informational and not legal advice. For specific contracts, engage a German Anwalt (Rechtsanwalt für IT-Recht or Vertragsrecht).
What’s the difference between Werkvertrag and Dienstvertrag?
The single most important German contract distinction for web work.
Werkvertrag (contract for a work / deliverable)
Vendor owes a defined result. Payment is contingent on delivering the agreed deliverable. Acceptance (“Abnahme”) triggers warranty period and final payment.
Used for: fixed-price builds with defined deliverables — most web development projects.
Dienstvertrag (service contract)
Vendor owes effort (time and skill), not a specific result. Payment is for hours worked, not for outcomes.
Used for: consulting, advisory engagements, time-and-materials work.
Why it matters
- Acceptance: Werkvertrag requires explicit acceptance; Dienstvertrag doesn’t.
- Warranty: Werkvertrag has a 2-year warranty period for defects (§ 634a BGB). Dienstvertrag doesn’t.
- Termination: Different rules. Dienstvertrag often easier to terminate.
- Liability: Werkvertrag has stricter liability for defects.
Most web builds are Werkverträge. Ongoing maintenance retainers are typically Dienstverträge. Confusion between the two creates disputes.
What are the essential clauses in a German web development contract?
Twelve clauses that should appear in every German GmbH web development contract:
1. Vertragsparteien (parties)
Legal name, address, Handelsregister number, USt-ID for both parties. Vertretungsberechtigte Person clearly named.
2. Vertragsgegenstand (scope)
Detailed scope description — what’s being built, what’s NOT being built, deliverables list, milestones. Vague scope = future disputes.
3. Leistungsbeschreibung (specification)
Technical specifications, design files referenced, integrations defined, performance targets stated.
4. Vergütung (compensation)
Total fee, payment milestones, USt rate, payment terms (typically net 14 or net 30), late payment interest (§ 288 BGB allows base rate + 9% for B2B).
5. Termine (timeline)
Milestones with dates. Consequences of delay (typically: warning + new deadline, not automatic penalty unless explicitly agreed).
6. Mitwirkungspflichten (client cooperation)
Client’s responsibilities (provide content, give feedback within X days, sign off on milestones). Without this, vendor can be blamed for delays caused by client inaction.
7. Abnahme (acceptance)
Process for accepting deliverables. Acceptance criteria, who signs off, how long client has to test. Critical for Werkvertrag.
8. Änderungen (change control)
How scope changes are handled. Written change request, cost/timeline impact, signed by both parties.
9. Urheberrecht (IP and copyright)
This is the big one. German law distinguishes between:
- Urheberrecht (moral rights) — non-transferable; remains with the developer.
- Nutzungsrechte (usage rights) — what the GmbH actually gets.
The web development contract Germany agreement must grant: exclusive, perpetual, transferable, sublicensable, worldwide usage rights for all purposes. Without these explicit rights, the GmbH can’t even modify the code without the developer’s permission. Many “we own the code” assumptions are wrong under
10. Vertraulichkeit (confidentiality)
NDA / Verschwiegenheit clause covering business information, customer data, unreleased products.
11. Datenschutz und AVV (data protection)
If the vendor processes personal data, you need a separate AVV (Auftragsverarbeitungsvertrag) per GDPR Article 28. Reference the AVV in the main contract as an addendum.
12. Haftung (liability)
Liability limit (typically capped at total contract value, with exceptions for intent and gross negligence). Force majeure clause.
What does GDPR/DSGVO add to a web development contract?
Two essentials:
Auftragsverarbeitungsvertrag (AVV)
If the vendor processes personal data on your behalf — e.g., they touch your customer database during development, they host the staging server, they access user accounts — you need an AVV per Article 28 GDPR.
Standard AVV terms cover: scope of processing, sub-processor list, technical/organizational measures (TOMs), audit rights, breach notification timelines (typically 24–72 hours), data deletion at engagement end.
Sub-processor disclosure
Vendor must list all sub-processors (their hosting provider, monitoring tools, etc.) and notify the GmbH of changes.
See our GDPR compliance guide for broader DSGVO context.
What’s the IP clause Germany-specific gotcha?
Two German-law specifics often missed:
Urheberrecht doesn’t transfer
In Germany, the moral right (Urheberrecht) of the actual person who wrote the code stays with that person. Cannot be assigned to a company in advance.
What the GmbH gets is Nutzungsrechte (usage rights) — the right to use, modify, distribute, sublicense the code. The contract must explicitly grant: ausschließliche, zeitlich und räumlich unbeschränkte, übertragbare, unterlizenzierbare Nutzungsrechte für alle bekannten und unbekannten Nutzungsarten.
Without “alle bekannten und unbekannten Nutzungsarten,” you may not be allowed to use the code in ways unforeseen at signing (a new media channel that emerges later, for instance).
Custom illustrations, photography, type, music
Same applies to design assets. The contract must explicitly grant broad usage rights or include separate license terms for each asset.
For broader hiring frameworks see our 15 red flags when hiring a web developer guide.
Three additional clauses for freelance engagements:
Scheinselbständigkeit clause
The contract should explicitly state the freelancer is independent, has other clients, uses their own equipment, has freedom in execution. Mitigates “false self-employment” reclassification risk by the Deutsche Rentenversicherung.
For broader Scheinselbständigkeit risk mitigation see our hire React developer guide (covers the topic in detail).
Eigene Werkzeuge (own equipment)
Freelancer uses their own laptop, accounts, tools — not employer-provided. Important for Scheinselbständigkeit defense.
Mehrere Auftraggeber (multiple clients)
Freelancer has other clients, not exclusively this one. Again, Scheinselbständigkeit defense.
What about source code escrow?
For larger projects with long-term operational dependency, source code escrow makes sense:
- Third party (escrow agent) holds source code
- Released to GmbH on defined trigger events (vendor bankruptcy, abandonment, dispute)
- Costs €500–€2,500/year for typical setups
Not necessary for most small projects. Worth considering for any project where the vendor is critical infrastructure.
What does exit / handover require?
Often forgotten until the relationship ends badly. The contract should specify:
- All source code in the GmbH’s Git repository (continuous push, not one-time handover)
- All credentials, licenses, accounts transferred to the GmbH
- Plugin/theme licenses purchased under the GmbH’s name
- Documentation of architecture, deployment, operations
- Data export and deletion at engagement end
- A defined exit period (typically 30 days hypercare post-handover)
How does German payment law shape contracts?
Three German-specific payment considerations:
GoBD-compliant invoices
Sequential invoice numbers, full company addresses, VAT breakdown, USt-ID for B2B, reverse-charge for EU B2B. Vendor’s invoices must be GoBD-compliant or your Steuerberater will reject them.
Net 14 / Net 30 payment terms
German B2B norm. Define explicitly. Late-payment interest defaults to base rate + 9% for B2B (§ 288 BGB).
Skonto
Some German vendors offer a small discount (1–3%) for payment within 7–14 days. Define in contract if applicable.
Four patterns:
Using a US-style one-page agreement
A 1-page contract works in the US sometimes. In Germany it creates dispute risk on every project above €5,000.
Skipping the AVV
GDPR-required for any vendor processing personal data. Without it, the GmbH bears liability for vendor data breaches.
Vague IP clauses
“Customer owns the code” — under German law, this is meaningless without explicit Nutzungsrechte language.
No defined acceptance process
“It looks good” is not Abnahme. Define acceptance criteria, who signs, how long the client has to test.
When should you engage a German lawyer for contracts?
For first-time engagements with new vendors, definitely. For subsequent projects with the same vendor, you can usually rely on a template you’ve vetted.
For broader agency choice context see our how to choose a web development agency guide and 15 red flags when hiring guide.
Frequently Asked Questions About Web Development Contracts in Germany
Werkvertrag for fixed-price builds with deliverables; Dienstvertrag for maintenance and consulting.
8–20 pages for €10,000–€50,000; 4–8 pages below; 15–30+ pages above €50,000.
Yes for German GmbH + German vendor; English with German governing law works for international vendors.
German law, jurisdiction at the GmbH’s seat city; Frankfurt am Main as a neutral default for international.
Yes for vendor-critical infrastructure; skip for small/medium replaceable-vendor projects.
€2,000–€6,000 for a solid one-time template; €250–€500/hour for revisions.
Both need explicit broad Nutzungsrechte language — illustrations, photo, type, code are separate Urheberrecht works.
As a contract addendum or standalone signed document, cross-referenced from the main contract.
Need help structuring a contract?
This guide is informational. For specific contracts engage a German IT-Rechtsanwalt. If you’d like a 30-minute conversation about contract structure, common clauses, and what to negotiate, book a meeting or send details via our contact page.