DACH engineering leaders who need external capacity usually choose between three models: staff augmentation, where individual engineers join the client's team; managed delivery teams or pods, where a vendor-led unit delivers a continuing stream of outcomes; and project outsourcing, where a vendor delivers a defined scope for a defined price. The models are often discussed as if price were the main difference. It is not. The real difference is who steers the work, who carries the risk of the result, and how the arrangement is treated under German labour and contract law. Choosing well starts with those questions.
The market context
The choice of model matters more because external capacity has become a standard part of German engineering organisations. In Bitkom's 2026 IT labour market study, 18 percent of companies say they rely more on external IT specialists, while 79,000 IT positions remain unfilled. The same study shows how sensitive the legal side is: 49 percent of companies call for reform of the status determination procedure for freelancers under SGB IV §7a.
Cost pressure pushes in the same direction. Destatis reports an average labour cost of EUR 45 per hour in Germany in 2025, 29 percent above the EU average of EUR 34.90. The work itself is changing as well: Bitkom's 2026 AI survey finds that 57 percent of German companies with at least 20 employees now use AI, up from 20 percent in 2024. That raises demand for specialised, well-governed engineering rather than generic headcount.
The three models in one table
| Dimension | Staff augmentation | Managed pod | Project outsourcing |
|---|---|---|---|
| Who directs daily work | Client managers | Vendor lead, against client-defined outcomes | Vendor project manager |
| Unit of commitment | Hours or days of a person | Sprint outcomes with acceptance criteria | Complete scope at a fixed or capped price |
| Scope flexibility | High | Medium to high, renegotiated per sprint | Low, changes via formal change requests |
| Result risk | Client | Vendor, per accepted sprint deliverable | Vendor, per project |
| Typical German contract type | Often Arbeitnehmerüberlassung under AÜG, or Dienstvertrag if structured carefully | Werkvertrag (BGB §631) or Dienstvertrag (BGB §611) with vendor-side steering | Werkvertrag (BGB §631) with Abnahme (BGB §640) |
| Client management effort | High | Moderate, concentrated in product ownership | Low during delivery, high in specification |
| Knowledge retention | In the client's team, if documented | Shared, documented as part of deliverables | With the vendor unless handover is contracted |
Staff augmentation: maximum control, maximum legal attention
Staff augmentation gives you engineers who work inside your process, take tickets from your backlog and report to your engineering manager. It is the most flexible model and the closest to having employees. That closeness is also its legal exposure. Under AÜG §1, temporary agency work exists where workers are integrated into the client's work organisation and subject to its instructions. If that describes the practice, the vendor needs a permit from the Bundesagentur für Arbeit, the assignment must be labelled and specified as Arbeitnehmerüberlassung in the contract, and the AÜG's rules on maximum duration and equal treatment apply. If the permit or labelling is missing, §9 and §10 AÜG can lead to an employment relationship with the client by operation of law.
With a foreign vendor delivering remotely, the permit question becomes complicated quickly. Staff augmentation is therefore best used with domestic, licensed providers, or with external specialists engaged under a carefully structured Dienstvertrag where the client does not issue work instructions.
Project outsourcing: clear risk transfer, rigid scope
Fixed-scope outsourcing transfers the result risk to the vendor. The contract defines the work, the price and the acceptance criteria; the vendor delivers; you accept or reject under BGB §640. This works well for bounded problems with stable requirements, such as a migration with a known target state or a defined integration.
Its weakness is change. Product requirements in a scaleup change monthly. Every change becomes a change request, every change request a negotiation, and vendors price uncertainty into fixed bids. If the scope cannot be described completely at the start, a fixed-price project is likely to become a dispute or an expensive series of amendments.
Managed pods: outcome commitment with sprint-level flexibility
A managed pod sits between the two. The vendor provides a stable team with its own lead and quality function. The client defines outcomes per sprint, with a Leistungsbeschreibung and acceptance criteria. The vendor decides how to achieve them and directs its own engineers. Scope can shift between sprints without renegotiating the whole contract, and the result risk sits with the vendor for each accepted increment.
The model depends on discipline on both sides. The client needs a product owner who can write acceptance criteria and make decisions. The vendor needs a lead who can translate between the client's domain and the engineering team and who actually holds authority over the engineers. Without those two roles, a pod drifts into staff augmentation with a different invoice.
A five-question decision framework
- Can you describe the outcome? If you can write acceptance criteria for the next four to eight weeks, a pod or project works. If you only know the direction, staff augmentation or internal work fits better.
- How stable is the scope? Stable for the full duration points to project outsourcing. Stable per sprint points to a pod.
- Who should steer engineers day to day? If your managers must, you are in staff augmentation territory and need the corresponding legal structure.
- How long will you need the capacity? Under three months favours project or specialist engagement. Six months and longer favours a stable pod.
- Where should knowledge live? If it must end up in your team, contract documentation and handover explicitly, whatever the model.
Mixing models deliberately
Many companies combine models. A typical pattern: a fixed-scope project for a clearly bounded migration, a managed pod for the continuing product workstream, and one or two licensed contractors through a domestic provider for short specialist peaks. The combination works if each engagement has its own contract type, its own steering logic and a named owner on your side. It fails when the boundaries blur and the same engineers move between models without the paperwork following.
Common failure patterns
- Signing a Werkvertrag and then managing the engineers like employees. The contract label does not decide; the practice does.
- Using fixed-price outsourcing for exploratory product work, then fighting over change requests.
- Running a pod without a client-side product owner, so the vendor guesses priorities.
- Choosing staff augmentation from a foreign vendor without checking the AÜG position.
Whichever model you choose, decide it on control and risk first and price second. This article is general information, not legal advice.
For teams that want continuity without placing individual engineers under their own direction, the managed pod sits between the other two models. niogod™ works in that model, with a German-speaking Projektleiter on the vendor side, a Werkvertrag or Dienstvertrag led structure and sprint-based Abnahme (see the deployment protocol). If you are choosing a model for next year, it helps to test each option against the five questions above.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation