When a German company engages an external software team, it chooses between three legal models: the Werkvertrag (§631 BGB), the Dienstvertrag (§611 BGB) and Arbeitnehmerüberlassung under the AÜG. The choice is not cosmetic. It determines who carries the risk of the result, who may instruct the engineers, when payment falls due and which regulatory regime applies. For a team delivering from India, the realistic options are narrower than many buyers assume: a Werkvertrag or a vendor-steered Dienstvertrag. And either one only holds if daily practice matches the document.
The market context
The choice of contract model has become a volume question. Bitkom counted 109,000 unfilled IT positions in Germany in 2025, with an average vacancy of 7.7 months, and although the figure fell to 79,000 in 2026, 78 percent of companies still report a shortage of IT specialists. India's technology workforce, which NASSCOM estimates at about 5.95 million people at the end of FY26, is an obvious pool for DACH companies looking to close that gap.
Labour leasing itself is a large, regulated market. The Bundesagentur für Arbeit recorded around 622,000 temporary agency workers in 39,000 lending businesses on 30 June 2025. Enforcement is active as well: German customs reported that the Finanzkontrolle Schwarzarbeit checked 25,800 employers in 2025 and put the damage caused by undeclared work across all sectors at about EUR 675 million. Choosing the right model is therefore less about paperwork than about where your engagement stands if someone takes a closer look.
The three models in one view
| Criterion | Werkvertrag (§631 BGB) | Dienstvertrag (§611 BGB) | Arbeitnehmerüberlassung (AÜG) |
|---|---|---|---|
| What is owed | A defined result | Diligent performance of an activity | Provision of workers who work under the client's direction |
| Who directs the engineers | Vendor | Vendor | Client (Entleiher) |
| Acceptance and payment | Abnahme under §640 BGB, remuneration due on Abnahme (§641 BGB) | No Abnahme, payment for the service period | No Abnahme, payment per hour or month |
| Defect rights | Nacherfüllung, Minderung, Rücktritt, damages (§634 BGB) | No warranty for a result, liability for breach of duty | Not applicable in this form |
| Regulatory duties | None specific | None specific | Licence of the Verleiher (§1 Abs. 1 Satz 1 AÜG), labelling and naming duties (§1 Abs. 1 Satz 5 and 6 AÜG), maximum 18 months per worker (§1 Abs. 1b AÜG) |
| Typical fit | Defined scope, testable outcome | Ongoing capacity on an evolving backlog, vendor-led | Client wants to manage individuals directly |
Why the label does not decide
German law looks at how a contract is actually lived. §611a Abs. 1 Satz 6 BGB states this explicitly for the employment relationship: if the actual performance shows an employment relationship, the designation in the contract is irrelevant. The same reasoning is applied at the boundary between a Werk- or Dienstvertrag and Arbeitnehmerüberlassung. §1 Abs. 1 Satz 2 AÜG describes Überlassung as a situation in which workers are integrated into the client's work organisation and subject to the client's instructions.
A contract titled Werkvertrag in which the client's product owner assigns tasks to named engineers, sets their working hours and evaluates their individual performance is, in substance, likely to be treated as Überlassung. The practical question is therefore not which template to sign, but which model your organisation can actually operate for 12 or 24 months without drifting.
A note on the AÜG for India-based vendors
Arbeitnehmerüberlassung is not a neutral third option for vendors operating from India. Under §3 Abs. 2 AÜG, the licence must be refused if the activity is to be carried out from establishments outside the EU or the EEA. An Indian company supplying its own engineers from Bangalore can therefore not obtain an AÜG licence for that activity.
If the arrangement is in substance Überlassung and the AÜG applies, the buyer is working with an unlicensed supplier, with the consequences of §9 and §10 AÜG, including a possible fictitious employment relationship with the client. Whether the AÜG reaches purely remote work performed abroad depends on the domestic link (Inlandsbezug). The Bundesagentur für Arbeit has reassessed this question in its Fachliche Weisungen, courts are not bound by those Weisungen, and there is no settled higher court case law. Visits of engineers to Germany can strengthen the domestic link. Building a contract structure on the assumption that this question will always be answered in your favour is not prudent.
Decision framework
- Can you describe the outcome? If you can specify deliverables with acceptance criteria per sprint or milestone (a feature set, a migration, a test suite, an integration), a Werkvertrag fits. Abnahme becomes the contractual control point.
- Is the scope evolving, but can the vendor steer? If you need sustained capacity on a changing backlog, a Dienstvertrag can fit, provided the vendor's own lead translates your requirements into tasks and directs the team.
- Do you want to direct individuals day to day? Then you are describing Überlassung. Use a licensed Verleiher with EU or EEA operations, hire directly, or redesign the operating model so the vendor directs its people.
- Test the operating model, not only the document. Who writes tickets, who assigns them, who approves leave, who gives feedback to individuals. Each answer should point to the vendor.
- Document the interface. Name one or two vendor-side contact persons through whom requirements, change requests and acceptance flow.
Werkvertrag and Dienstvertrag: practical trade-offs
Werkvertrag
The Werkvertrag gives the buyer the strongest commercial protection. Payment is linked to Abnahme, and defects trigger statutory rights. The cost is specification effort. Without a Leistungsbeschreibung precise enough to test against, Abnahme becomes contested and the result orientation erodes into a time-and-material relationship in disguise. For agile delivery, a sprint-based structure with partial acceptance per increment is the usual solution. §641 Abs. 1 Satz 2 BGB provides that where the work is to be accepted in parts and the remuneration for each part is determined, remuneration for each part falls due on its acceptance.
Dienstvertrag
The Dienstvertrag is more flexible for discovery-heavy work, research prototypes and platform maintenance. The vendor owes diligent work, not a result. That shifts quality risk to the buyer, so service levels, reporting duties, staffing commitments and termination rights carry more weight. The boundary to Überlassung is identical to the Werkvertrag: the vendor must remain the party that organises and instructs its engineers.
Clauses that support the chosen model
- A statement that the vendor alone holds the right to instruct its personnel, and that the client communicates requirements through named vendor contacts.
- A Leistungsbeschreibung by sprint or milestone, with acceptance criteria (Werkvertrag) or service descriptions and reporting duties (Dienstvertrag).
- The vendor's right to select and replace team members without client approval of individuals, combined with a duty to maintain the agreed qualification level.
- No client control over working time, leave or disciplinary matters of individual engineers.
- A change request procedure that runs through the vendor's lead, not through direct tasking of engineers.
- Rules for on-site visits in Germany that keep them occasional, purpose-bound and vendor-organised.
How a pod model maps to this boundary
A pod model maps to this boundary when the vendor provides its own client-facing lead. A German-speaking Projektleiter acts as the single interface to the client, translates requirements into the team's work and directs the engineers, under a Werkvertrag or Dienstvertrag with a sprint-based Leistungsbeschreibung and Abnahme. The client steers the result, and the vendor steers the people.
This article is general information and does not constitute legal advice for your specific situation.
A contract model is only as robust as the operating model behind it. niogod™ was built around this boundary: a three-person pod led by a German-speaking Projektleiter, delivered under a Werkvertrag or Dienstvertrag with a sprint-based Leistungsbeschreibung and Abnahme, as described on the pod page. If external engineering is on your roadmap for next year, choosing the model before choosing the vendor is a conversation worth having early.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation