In Germany, "external workers in the team" triggers a specific mental image: Zeitarbeit, the temp-work model of industrial staffing, licensed agencies, equal-pay clocks, workers leased by the shift. That image is so strong that IT buyers regularly apply its assumptions, low-skill, interchangeable, legally always Arbeitnehmerüberlassung, to staff augmentation, a model that shares almost none of them. The confusion is not cosmetic. It leads companies to reject augmentation for prestige reasons, to force service contracts into leasing constructions they don't need, or, more dangerously, to run engagements under the wrong legal frame entirely. One clarification up front: this article explains the models and is not legal advice; the legal classification of any specific arrangement needs qualified counsel.
Why the Zeitarbeit association misleads IT buyers
Zeitarbeit earned its associations in industrial and logistics staffing: high-volume, interchangeable roles, margins on hourly wage differences, workers dispatched by the shift. Those associations travel badly into IT. An augmented senior engineer is not interchangeable capacity, is often more senior than the internal team members, and is engaged for expertise rather than for headcount by the hour. Buyers who carry the temp-work frame make predictable mistakes: they expect rock-bottom rates and are shocked by specialist pricing, they treat the external as a fungible resource and skip integration, and they assume every external engagement legally requires an AÜG license, which pushes them toward leasing constructions even where a service contract is the appropriate form. The vocabulary problem is real: both models get marketed under "Personaldienstleistung", and some providers offer both without clearly distinguishing them.
The three structural differences
- Skill level and role logic: classic Zeitarbeit concentrates in standardized roles where workers are substitutable; augmentation exists precisely because the skill is scarce and not substitutable, the engagement is built around a specific person's verified capability.
- Engagement logic: Zeitarbeit fills a seat, the client directs the worker's daily tasks exactly like an employee's, and the value is presence. Augmentation fills a capability gap, the external contributes expertise toward outcomes inside the team's process, and the value is what gets built and what the team learns.
- Legal frame: Zeitarbeit is by definition Arbeitnehmerüberlassung under the AÜG, license requirement, equal-pay rules after nine months, maximum leasing duration, works-council information rights. Augmentation is typically structured as a contract for services, where the client does not hold employee-style direction rights and the AÜG regime does not apply, if and only if the practice matches the paper.
The comparison at a glance
| Zeitarbeit (AÜG leasing) | Staff augmentation (service contract) | |
|---|---|---|
| Typical skill profile | Standardized, substitutable roles | Scarce specialist skills, person-specific |
| Legal construction | Arbeitnehmerüberlassung under the AÜG | Contract for services (Dienst-/Werkvertrag logic) |
| Who directs daily work | The client, like an employer | The external works self-directed toward agreed outcomes |
| License requirement | Yes, AÜG license (Erlaubnis) for the agency | No AÜG license needed, because no leasing occurs |
| Equal pay / max duration rules | Yes, statutory (equal pay after 9 months, duration caps) | Not applicable, commercial terms are freely agreed |
| Pricing logic | Hourly wage plus agency markup | Day rate or engagement price for expertise |
| Core risk | Cost and duration limits, image within teams | Misclassification if lived like leasing (verdeckte Überlassung) |
When classic AÜG-based leasing is actually the right answer in IT
It would be dishonest to frame leasing as the outdated model and augmentation as the modern one in every case. The models answer different needs, and sometimes the leasing answer is the correct and compliant one.
- You genuinely need directive control: the person must work fixed shifts in your service desk rota, follow your daily task assignment, and be steered like an employee, that is the factual pattern of leasing, and contracting it as anything else creates risk rather than removing it.
- The engagement is long, integrated and headcount-like, but a permanent hire is blocked: a compliant AÜG construction with a licensed provider is the legally clean way to run exactly that pattern, within the duration limits.
- Your works council and procurement processes are built around AÜG: in some organizations the leasing route is the fast, established path, and fighting it costs more than using it.
- The role is standardized enough that substitutability is a feature: first-level support, rollout squads, managed operations shifts, here the temp-work economics genuinely fit.
How to choose the frame, and keep it honest
The practical test is direction and integration, decided before contracting, not after. If you need to control when and how the person works day by day, plan for a leasing construction with a licensed provider and accept its rules. If you need scarce expertise contributing to outcomes, contract a genuine service arrangement and then actually operate it that way: outcome-based steering, execution autonomy, no employee-only mechanisms, documentation that matches. The worst position is the middle: a service contract on paper with employee-style direction in practice, that is the hidden-leasing pattern that creates retroactive risk for both sides. When the intended operating reality is unclear, that ambiguity itself is the finding: resolve it, with qualified legal advice for your specific case, before the external starts, not when an auditor asks.
