Offshore vendors frequently sell dedicated developers or team extension: named engineers, billed monthly per person, working as part of your team. The model is popular in markets without a statute like the AÜG, and many contract templates are drafted for those markets. Signed unchanged by a German company, such a contract can describe Arbeitnehmerüberlassung in its own words, while leaving the buyer with the delivery risk, an incomplete rights chain and gaps in data protection. This checklist lists twelve clauses to read twice, why they matter under German law, and what to ask for instead.
Why these contracts are on more desks
The pressure to sign quickly is real. Bitkom counted 109,000 unfilled IT positions in Germany in 2025, with an average vacancy of 7.7 months, and even after the figure fell to 79,000 in 2026, 78 percent of companies still report a shortage. India's technology sector, which NASSCOM estimates employed about 5.95 million people at the end of FY26, is an obvious place to look, and dedicated developer offers are a frequent format in which that capacity is sold.
Enforcement has not relaxed either. 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. The Deutsche Rentenversicherung carried out 23,052 status determination procedures in 2024, and of 3,002 objections against status decisions dealt with that year, only 669 succeeded in full or in part. A contract that reads like labour leasing is hard to argue away later.
Instruction and integration
| Red flag | Why it matters | What to ask for |
|---|---|---|
| 1. The developer works under the client's direction or reports to the client's manager | Transfers the right to instruct, the core indicator of Überlassung under §1 Abs. 1 Satz 2 AÜG | Vendor retains the right to instruct its personnel, client communicates through a named vendor lead |
| 2. The client approves leave, working hours or replacements of named developers | Employer functions move to the client | Vendor guarantees capacity and qualification, staffs and schedules autonomously |
| 3. The developer is described as an extension of the client's team, using client email, hardware and internal tools without external marking | Visible integration into the client's organisation | External accounts clearly marked, vendor-managed devices where possible |
| 4. The vendor disclaims responsibility for output because the client manages the developer | The vendor sells time, the client carries delivery risk and the legal risk of directing people | A Werkvertrag with acceptance, or a Dienstvertrag with vendor-led steering, service levels and reporting |
Scope, billing and acceptance
| Red flag | Why it matters | What to ask for |
|---|---|---|
| 5. Billing per named person per hour, with timesheets approved by the client | Suggests provision of labour rather than a service or a result | Fixed fee per team or per deliverable, approval of results rather than hours |
| 6. No Leistungsbeschreibung, only roles and seniority | No basis for acceptance, defect claims or performance management at the vendor level | Sprint or milestone based Leistungsbeschreibung with acceptance criteria |
| 7. Unrestricted subcontracting without disclosure | Unknown individuals, gaps in the rights chain and in data protection documentation | Prior notice or consent, list of subcontractors, flow-down of IP and data protection obligations |
Rights and data
| Red flag | Why it matters | What to ask for |
|---|---|---|
| 8. Rights transfer only after payment of all invoices, without detail on scope | No rights to delivered code in a dispute, and under §31 Abs. 5 UrhG the scope may be narrower than expected | Exclusive Nutzungsrechte with enumerated types of use, passing per accepted and paid increment |
| 9. Assignment clause silent on duration, territory and lapse | Under Section 19 of the Indian Copyright Act, defaults of five years and Indian territory can apply, and unexercised assignments can lapse after one year | Express worldwide territory, full term of copyright, exclusion of lapse |
| 10. Data protection covered by a single confidentiality clause | Art. 28 DSGVO requires specific content, and access from India requires a transfer tool under Art. 44 ff. DSGVO | Separate AVV, SCCs in the correct module, documented transfer impact assessment |
Exit and enforcement
| Red flag | Why it matters | What to ask for |
|---|---|---|
| 11. Long minimum terms with high non-solicitation buyouts and no handover duties | Lock-in without a guaranteed transfer of knowledge | Reasonable notice periods, defined handover services, documentation duties |
| 12. Governing law and courts in the vendor's country only | Enforcement of German-law expectations becomes slow and costly | German law with a German place of jurisdiction, or arbitration at a neutral seat with a clear procedure |
How to read the result
No single clause decides the legal classification. Authorities and courts look at the overall picture and at how the contract is actually performed. Clauses 1 to 5 are the most sensitive for the AÜG question because they describe the operating model. If three or more of them are present, the contract is likely to describe Überlassung, and for a vendor operating from India that cannot be cured by a licence, because §3 Abs. 2 AÜG requires refusal for activity from establishments outside the EU and EEA. Clauses 6 to 12 are mainly commercial and data protection risks, but they determine what you actually own and control at the end.
Negotiation sequence
- Fix the operating model first. Agree who directs the engineers and how requirements flow. The rest of the contract follows from that.
- Replace headcount with scope. Convert role lists into a Leistungsbeschreibung, even if it is sprint based and evolves.
- Close the rights chain. Request the vendor's employment and subcontractor clauses on IP, not only the client-facing clause.
- Attach the data protection set. AVV, SCCs and TOMs as annexes, signed together with the main contract.
- Define the exit. Handover services, documentation and access revocation, priced in advance.
Questions for the first vendor call
- Who on your side directs the engineers day to day, and how do our requirements reach them?
- Are all engineers employed by you, or do you work with freelancers or subcontractors?
- Can you show the IP clauses in your employment contracts?
- Which tools, including AI assistants, will your engineers use with our code and data?
- What does handover look like if we end the engagement?
A note on language
Marketing terms such as dedicated team, staff augmentation or team extension are not legal categories. What matters is what the contract says about instructions, scope, acceptance and rights, and how your teams actually work with the engineers. A vendor that understands the German framework will usually welcome these questions.
This article is general information and does not constitute legal advice for your specific situation.
A contract that passes this checklist is usually one that was written for the German framework from the start. On that basis, niogod™ offers its pods under a Werkvertrag or Dienstvertrag with a sprint-based Leistungsbeschreibung and a German-speaking Projektleiter on the vendor side who directs the engineers. If you would like to hold an existing offer against this checklist, the contact page is a sensible place to begin that conversation.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation