When a DACH scaleup with external engineering capacity in India raises its next round or enters an acquisition process, the topic will come up. Investors and acquirers do not object to offshore engineering as such; many of their portfolio companies use it. What they look for is whether the arrangement creates hidden liabilities, weakens ownership of the core asset, or makes the company dependent on a single supplier it does not control. Founders who can answer those questions with documents rather than reassurance turn a potential discount into a non-issue. This briefing lists the questions that typically arise and the evidence that answers them.
The funding context
Diligence has become more thorough because capital has become more selective. EY's Startup-Barometer shows that German startups raised about EUR 8.4 billion in 2025, up 19 percent on 2024, but across only 716 financing rounds, the lowest number since 2019. Eighteen rounds exceeded EUR 100 million, together worth EUR 3.72 billion. Fewer, larger rounds mean each one is examined more closely, and engineering structure is part of that examination.
Investors also know the cost side. Destatis reports that an hour of work in Germany cost an average of EUR 45 in 2025, 29 percent above the EU average of EUR 34.90, and Bitkom's 2026 labour market study counts 79,000 missing IT specialists. External engineering capacity is therefore a rational answer that boards understand. What they test is whether it was implemented cleanly. The same Bitkom study shows how live the legal question is: 49 percent of companies call for reform of the status determination procedure for freelancers.
1. Who owns the code?
This is the first question in almost every technical due diligence, and the one most often answered badly. The chain of title must run without gaps from the individual engineer to your company.
- Engineer to vendor. Under the Indian Copyright Act 1957, Section 17, the employer is generally the first owner of works created by an employee in the course of employment under a contract of service. Freelancers or subcontractors used by the vendor are different: ownership must be transferred by written assignment, which Section 19 requires to be in writing.
- Vendor to you. Your contract must assign all rights in the work results to your company, or grant exclusive, unlimited, transferable usage rights in a form compatible with German copyright law (UrhG), including for software under §69a ff. UrhG.
- Pre-existing components. Vendor libraries, templates and open-source components need a clear licence position.
Evidence: the master agreement with its IP clause, confirmation that the vendor's engineers are employees or have signed assignments, and an open-source inventory.
2. Are there contingent labour law liabilities?
German investors know the risk patterns. If an external engagement is in substance Arbeitnehmerüberlassung under AÜG §1 without the required permit and labelling, §9 and §10 AÜG can create an employment relationship with the client. If individual freelancers are in substance employees, social security contributions may be owed retroactively under SGB IV §7, and withholding contributions can be a criminal offence under §266a StGB.
Evidence: the contract type (Werkvertrag under BGB §631 or Dienstvertrag under BGB §611), a description of how work is steered in practice, the Leistungsbeschreibung and acceptance records under BGB §640, and, for any individual contractors, Statusfeststellung results under SGB IV §7a where obtained.
3. How is data protected?
- Which personal data, if any, does the offshore team access?
- Is there a processing agreement under DSGVO Art. 28?
- Are transfers covered by Standardvertragsklauseln under DSGVO Art. 46 with a documented transfer impact assessment?
- What technical measures limit access: pseudonymised test data, role-based access, logging?
For companies in scope of Germany's NIS2 implementation law, in force since 6 December 2025, supply chain security is part of the risk management obligations, so the board will also ask how the vendor is assessed.
Evidence: the data processing agreement, the SCCs, the transfer impact assessment, an access matrix and the vendor's security policies.
4. How dependent are you on this vendor?
Boards worry about concentration. If a large share of engineering output comes from one external partner, a dispute, insolvency or key-person loss at the vendor becomes a company risk.
- Where is the source code hosted, and who controls the repository?
- Is architecture knowledge documented and held by internal staff as well?
- What notice period and handover obligations does the contract specify?
- Could another team take over within one quarter?
Evidence: repositories under your organisation's account, architecture documentation, the termination and transition clauses, and a short written transition plan.
5. Is the cost model sustainable?
Investors compare engineering cost to output. They want to see that external capacity is priced predictably and tied to deliverables, not open-ended hours. A fixed monthly fee with sprint-based acceptance is easier to model than variable time-and-material billing. They also check VAT treatment: services from a foreign provider to a German business are generally subject to reverse charge under §13b UStG, which should be reflected correctly in the accounts.
6. Are there export control issues?
For robotics, defence, dual-use and some industrial software, transmitting technology or software to a team outside the EU can itself be an export. Regulation (EU) 2021/821 covers dual-use items including technology transfer by electronic means, and national rules may add requirements. Investors in this space will ask whether a classification has been done.
Evidence: an export control classification of the relevant technology and, where needed, licences or a documented assessment that none are required.
7. What happens on exit?
Acquirers check whether contracts can be assigned or terminated on change of control, whether the vendor can claim rights in the product, and whether key knowledge would leave with the vendor.
How to present it
Put the answers in the data room before anyone asks. A two-page memo titled along the lines of external engineering: structure and controls, with links to the underlying documents, signals that the topic is managed. In board meetings, report external capacity with the same metrics as internal teams: delivered and accepted scope, open risks, and spend against plan. Surprises in due diligence cost more than the findings themselves.
A preparation checklist
| Area | Document | Status |
|---|---|---|
| IP | Master agreement with assignment clause, engineer status confirmation, OSS inventory | Ready / missing |
| Labour law | Contract type, steering description, acceptance records | Ready / missing |
| Data | Art. 28 agreement, SCCs, TIA, access matrix | Ready / missing |
| Dependency | Repository ownership, architecture docs, transition plan | Ready / missing |
| Finance | Fee model, VAT treatment | Ready / missing |
| Export control | Classification or assessment | Ready / missing / not applicable |
| Exit | Assignment and change-of-control clauses | Ready / missing |
Vendors should make this easy: every item above should map to a document they can provide on request. This briefing is general information, not legal or tax advice.
Boards are reassured by documents, not by vendor promises. niogod™ structures its engagements around a Werkvertrag or Dienstvertrag, sprint acceptance under BGB §640 and documented handover, so that each item on this checklist has a written answer (see security and compliance). If a round or a transaction is on next year's calendar, it is worth preparing that file well before the data room opens.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation