Most Series A and B engineering budgets in the DACH region are headcount plans: a list of roles, a start month for each, and a salary. The plan is approved, the money is reserved, and twelve months later the roadmap is behind while the personnel budget is underspent. The cause is structural. A headcount plan describes intended hires, not delivered capacity. This guide sets out a capacity-based budgeting method that makes hiring lag and ramp-up visible, and shows how a flexible capacity layer can close the gap without breaking the budget logic.
The 2026 budget context
Funding has returned, but more selectively. The EY Startup-Barometer reports that German startups raised about EUR 8.4 billion in 2025, 19 percent more than in 2024, while the number of rounds fell 5 percent to 716, the fourth annual decline in a row. Fewer, larger rounds mean boards expect the money to turn into delivered roadmap quickly. At the same time, the cost base is rising: Destatis reported nominal wage growth of 4.2 percent in 2025, and StepStone's Gehaltsreport 2025 puts the median gross salary for IT professionals in Germany above EUR 58,000. Hiring remains slow, with Bitkom counting about 109,000 unfilled IT positions in 2025. A budget that assumes hires arrive on time and at last year's salary is optimistic on two counts.
Step 1: Express the roadmap in engineer-months
Start from what must be delivered, not from who must be hired. For each roadmap item the engineering leads estimate effort in engineer-months, with a confidence range. Add a fixed share for maintenance, incidents, security and technical debt; for a product already in production this is rarely small. The sum is the capacity requirement for the budget period.
Step 2: Model realistic capacity supply
Current team capacity is the number of engineers multiplied by months, adjusted for vacancy, holidays, sickness and internal overhead. New hires add capacity only after two delays:
- Time to fill. Bitkom's 2025 survey of German companies reports an average of 7.7 months to fill an IT position.
- Ramp-up. A new engineer typically needs some months before reaching full output. Use your own historical data; in the illustration below we assume three months at 50 percent.
Illustrative calculation
The following is an illustrative calculation for a hypothetical scaleup with 20 engineers that plans to grow to 35 within the fiscal year.
| Scenario | Assumption | Engineer-months delivered |
|---|---|---|
| Existing team | 20 engineers, 12 months | 240 |
| Plan: new hires | 15 hires productive from month 4 (9 months each) | 135 |
| Plan total | 375 | |
| Realistic: new hires | Requisitions opened in month 1, filled after about 8 months, starting in month 9; 3 months at 50% then 1 month at full output: 2.5 each | 37.5 |
| Realistic total | 277.5 |
In this example the company delivers about 74 percent of the capacity the plan assumed. The personnel budget for the fifteen new roles is largely unspent, and the roadmap slips by roughly a quarter. Both effects come from the same cause. Your actual numbers will differ, but the direction of the effect is consistent whenever time to fill is long.
The budget effect in the example
Continue the illustration with a loaded monthly cost of EUR 8,887 per engineer, the steady-state figure from our separate analysis of a German senior hire (gross salary, employer contributions, equipment and benefits). The plan reserves 135 engineer-months for new hires, about EUR 1.2 million. Realistically the fifteen hires are employed for four months each, 60 months in total, which costs about EUR 533,000. Roughly EUR 667,000 of the approved budget is therefore not spent on new hires in that year. That amount is the natural funding source for flexible capacity during the gap, and the board has in effect already approved it.
Step 3: Separate core and flexible capacity
The gap between requirement and realistic supply should be addressed explicitly, not hoped away. A useful structure is two layers:
- Core capacity: permanent employees who own architecture, product knowledge and long-term code ownership. Budgeted as personnel cost.
- Flexible capacity: freelancers, managed delivery teams or project vendors that cover the time until hires are productive, absorb peaks, and deliver well-defined work packages. Budgeted as external services, with notice periods that allow it to shrink.
The share of flexible capacity is a management decision. Companies with high regulatory or IP sensitivity usually keep it lower. Companies with long hiring lag and fixed launch dates usually need more of it in the first year.
Step 4: Build the budget lines
| Budget line | How to calculate |
|---|---|
| Existing team | Loaded annual cost per engineer multiplied by headcount, including employer contributions and benefits |
| New hires | Loaded monthly cost multiplied by realistic months employed, not planned months |
| Recruiting | Agency fees or internal recruiting cost per hire, multiplied by planned hires |
| Flexible capacity | Monthly fee multiplied by months needed to close the capacity gap |
| Tooling and infrastructure | Per-engineer cost for licences, cloud and devices, for both layers where relevant |
| Contingency | A buffer for attrition and replacement hiring |
Because new hires are budgeted for realistic months, the money released from the unrealistic plan funds the flexible layer. In many cases the total budget remains close to the original headcount plan while delivered capacity is much closer to the requirement.
Step 5: Re-forecast quarterly
Every quarter, compare three numbers: capacity required, capacity delivered, and money spent. If hires arrive faster than expected, reduce the flexible layer at the next notice date. If they arrive slower, extend it. This is the reason notice periods for flexible capacity matter as much as their price.
What to show the board
Investors and boards respond better to a capacity plan than to a headcount plan, because it links money to roadmap delivery. A one-page view should show:
- Capacity requirement by quarter, derived from the roadmap.
- Realistic core capacity, with hiring lag and ramp-up applied.
- Flexible capacity planned to close the gap, with exit dates.
- Total cost by quarter, split into personnel and external services.
- Key risks: hiring slippage, attrition, scope growth.
Common pitfalls
- Budgeting new hires from their planned start date, which hides the capacity gap.
- Treating flexible capacity as a failure of hiring rather than as a planned layer.
- Choosing flexible capacity on rate alone, without considering the management time it consumes from the core team.
- Contracting flexible capacity with long minimum terms, which removes the flexibility.
Managed pods, freelancers and project vendors are all options for the flexible layer. The method above works regardless of which option you choose; the point is to budget the capacity you will actually have.
The flexible layer works best when it can be sized up or down at each re-forecast without renegotiation. niogod™ offers it as a three-person pod at a fixed monthly fee, priced around the cost of one German engineering hire, with a German-speaking Projektleiter as the single point of contact for your engineering lead. If your next budget round is approaching, it is worth modelling that line before the board meeting rather than after.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation