The choice between fixed price, time and material and sprint-based pricing is usually framed as a question of who carries cost overruns. In Germany it is also a legal question, because the pricing model interacts with the contract type (Werkvertrag under BGB §631 or Dienstvertrag under BGB §611) and with the boundary to Arbeitnehmerüberlassung under the AÜG. A model that looks commercially convenient can create legal exposure, and a model that looks legally safe can be commercially unworkable for evolving software. This analysis compares the three models and gives a framework for choosing between them.
Fixed price
Under a fixed price, the vendor delivers a defined result for an agreed amount. In German law this typically maps to a Werkvertrag: the vendor owes a result (Werk), the client accepts it through Abnahme (BGB §640), and payment follows acceptance. Statutory rights for defects (BGB §634) apply.
Where it works: well-specified, bounded work such as a migration with known scope, an interface implementation against a documented API, or a component with clear acceptance tests.
Where it fails: product development with evolving requirements. Vendors price uncertainty into the bid as a risk premium. When requirements change, which in product work they do, change requests become the main commercial instrument and the relationship turns adversarial. Large fixed-price software projects are also prone to disputes about whether the delivered work matches the specification.
Time and material
Under time and material (T&M), the client pays for effort at agreed rates. Legally this typically maps to a Dienstvertrag: the vendor owes diligent work, not a specific result. The client carries the cost risk of slow progress.
Where it works: exploratory work, research spikes, consulting, operational support where the scope is a service rather than an artefact.
Where it creates risk: T&M is the model most often used for staff augmentation, where engineers join the client's team and take daily instructions from the client's managers. If the engineers are integrated into the client's work organisation and subject to its instructions, the arrangement can qualify as Arbeitnehmerüberlassung under §1 Abs. 1 Satz 2 AÜG. Without the required permission, §9 AÜG can render the contracts void and §10 AÜG can deem an employment relationship between the engineers and the client. The rate format does not cause this, but T&M without a defined service scope makes it far more likely in practice.
Sprint-based pricing
Sprint-based pricing sits between the two. The client pays a fixed fee per sprint or per month for a stable team. Before each sprint, both parties agree a scope in a Leistungsbeschreibung with acceptance criteria. At the end of the sprint, the client reviews and accepts the results. Depending on how it is drafted, this can be structured as a series of small Werkverträge, or as a Dienstvertrag with clearly defined service increments.
Why it suits product engineering: it keeps the cost predictable for the client, keeps scope flexible from sprint to sprint, and keeps delivery responsibility and the right to direct the engineers with the vendor. The client's influence runs through the sprint scope and acceptance, not through individual instructions to engineers.
What it requires: a client-side product owner who can write sprint goals and acceptance criteria, and a vendor-side lead who translates them into work and directs the team.
Comparison
| Criterion | Fixed price | Time and material | Sprint-based |
|---|---|---|---|
| Typical German contract type | Werkvertrag | Dienstvertrag | Werkvertrag series or Dienstvertrag with defined increments |
| Who carries overrun risk | Vendor (priced in as premium) | Client | Shared: fixed fee, flexible scope |
| Budget predictability | High until changes | Low | High |
| Scope flexibility | Low, via change requests | High | High at sprint boundaries |
| AÜG proximity in practice | Low | High if run as staff augmentation | Low if direction stays with vendor |
| Client effort | High upfront specification | High ongoing direction | Moderate, per sprint |
Why the choice weighs more in 2026
Market conditions sharpen the differences between the models. Destatis reported that nominal wages in Germany rose 4.2 percent in 2025 against consumer price inflation of 2.2 percent, and rate cards for time and material work tend to follow wage costs. Bitkom expected German IT services revenue to grow 3.1 percent to EUR 52.6 billion in 2025, while software revenue grew 9.5 percent to EUR 52.7 billion, which suggests that spending is shifting toward software and product work, the kind of work least suited to rigid fixed prices. Capacity is also still scarce: Bitkom's 2025 survey counts about 109,000 unfilled IT positions and an average of 7.7 months to fill one. Under those conditions, T&M contracts with annual rate escalation and fixed-price contracts with expensive change requests both shift more cost to the client than they did a few years ago.
What each model means for the budget
For finance teams the models also differ in how they behave in planning. A fixed price is a single commitment, but change requests make the final figure uncertain until delivery. T&M produces a monthly run rate that is easy to forecast only if team size is stable and timesheets are controlled; the cost of the output remains open. A sprint-based fee produces a fixed monthly run rate with a known team, which makes it behave like a personnel cost line in the budget, while the scope remains steerable. For a CFO that combination, predictable cost with adjustable content, is often the decisive argument.
A decision framework
- Can you specify the full result today, with acceptance tests? Use fixed price under a Werkvertrag.
- Is the work exploratory or advisory, with no defined artefact? Use T&M under a Dienstvertrag, with a written description of the service and with the vendor directing its staff.
- Is it ongoing product development with evolving requirements? Use sprint-based pricing with a sprint-level Leistungsbeschreibung and Abnahme.
- Do you actually want engineers to work as part of your team under your managers? Then you are looking for Arbeitnehmerüberlassung. Use a provider with the required AÜG permission and accept the associated rules, or hire directly.
Clause patterns for sprint-based contracts
- A framework agreement defining team composition, monthly fee, sprint length and notice.
- A sprint scope document template: goals, user stories, acceptance criteria, out-of-scope items.
- An acceptance clause: review window, criteria for acceptance, handling of defects found in review.
- A communication clause: the client's product owner communicates with the vendor's lead; instructions to individual engineers are excluded.
- A capacity clause: what happens when a sprint scope proves larger than the team can deliver, and how carry-over is handled.
None of the three models is inherently right. The practical rule is to match the model to how specifiable the work is, and to make sure the way the team is actually run matches what the contract says. Authorities assess the arrangement as it is lived, not only as it is written.
This analysis is general information, not legal or tax advice.
For ongoing product engineering, the sprint-based model is the one niogod™ was built around: a fixed monthly fee for a three-person pod, a Leistungsbeschreibung with acceptance criteria per sprint, and a German-speaking Projektleiter who directs the team, so instructions never run from your managers to individual engineers. If you are reviewing an existing T&M arrangement, that is a useful benchmark to hold it against.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation