German buyers assessing offshore or nearshore delivery are usually not optimising for the lowest rate. They are optimising for a partner who will not create a compliance problem, will document what they build to a standard that survives audit, and will work inside a governance structure that includes stakeholders most offshore vendors have never had to accommodate. Rate matters, but it is rarely what the decision turns on.
01DSGVO is a design constraint, not a contract clause
Most vendors treat data protection as paperwork: sign the Auftragsverarbeitungsvertrag, list the sub-processors, move on. That satisfies the contract and not the obligation. The obligations that bite are architectural - data minimisation, purpose limitation, and the ability to actually delete a subject's data across every store including backups, logs and analytics.
The practical test is deletion. Ask a prospective partner how they would implement a deletion request in the system they are proposing to build. A partner who has done this describes the propagation problem - derived tables, search indexes, caches, event logs, backup retention - and how they bound it. A partner who says 'we delete the row' has not built for it.
02Nearshore and offshore solve different problems
Nearshore delivery within the EU removes the transfer question entirely and keeps working hours aligned, at a rate premium over offshore. Offshore delivery costs materially less and introduces both a transfer question and a timezone gap that has to be actively managed.
The cost comparison that matters is not the hourly rate, it is the rate multiplied by the hours actually spent on your work plus the coordination overhead. A team six hours away with a well-run handover produces more usable output per euro than a team two hours away with no delivery discipline, and the reverse is equally true.
| Model | Transfer question | Overlap hours | Typical rate index |
|---|---|---|---|
| In-house (DE) | None | Full | 100 |
| Nearshore (EU) | None | 6-8 | 50-65 |
| Nearshore (non-EU Europe) | Safeguards required | 6-8 | 40-50 |
| Offshore (India) | Safeguards required | 3-5 with effort | 25-35 |
03The works council is a stakeholder, not an obstacle
Where a Betriebsrat exists, decisions that affect how employees work - including tooling that could monitor performance - require consultation. Offshore vendors routinely discover this after proposing something that touches it, and the resulting delay gets attributed to bureaucracy rather than to a foreseeable governance step.
The practical implication for delivery is narrow but real: anything that logs individual user activity, tracks productivity, or changes established workflows needs to be raised early. Building it first and seeking agreement later is how features get shipped and then switched off.
04Documentation expectations are higher than most vendors assume
German engineering culture treats documentation as part of the deliverable rather than as an artefact produced if time permits. An architecture decision record explaining why an approach was chosen and what was rejected carries real weight, and its absence reads as unseriousness rather than as pragmatism.
This is worth budgeting for honestly. It is not overhead imposed for its own sake - it is what makes the system maintainable by someone who was not in the room, which is precisely the risk a buyer is trying to manage when the build happens elsewhere.
- Architecture decision records for anything structural, including rejected options
- Runbooks written to be executed by someone who did not build the system
- A data map: what personal data exists, where it sits, what the retention is
- Handover documentation treated as a milestone deliverable with acceptance criteria
Topics
Lena Voss
Lead Architect · SyncTrix
Writes about the engineering decisions behind production systems - architecture, delivery and the trade-offs that only show up at scale.
Building something like this?
SyncTrix engineers AI, SaaS, platform and cloud systems for enterprises and high-growth teams. Tell us what you're shipping and we'll scope it with you.