CTOs often present external engineering capacity to the CFO as a rate: so many euros per day or per month. The CFO compares that rate with the salary of an employee, sees a higher number, and asks why the company should pay more. The discussion is lost before it starts, because it is framed as a cost comparison when it is an investment decision. This guide sets out how to build the case in the terms a CFO uses: cash out, value in, timing, risk and accounting treatment. It ends with a one-page memo structure.
The macro numbers a CFO will recognise
CFOs respond to figures they can verify, and four are useful as context for any capacity case. IW Köln estimated that the skilled-labour shortage cost the German economy about EUR 49 billion in lost output in 2024, about 1.1 percent of production potential, rising to an estimated EUR 74 billion by 2027. Bitkom's 2025 survey found that 85 percent of companies report a shortage of IT specialists. Demand is not slowing: Bitkom reported in September 2025 that 36 percent of German companies with at least 20 employees now use AI, up from 20 percent a year earlier, and the federal government's Hightech Agenda Deutschland, presented in 2025, aims for 10 percent of economic output to be AI-based by 2030. These numbers do not prove your case, but they show the CFO that the hiring constraint is structural rather than a failing of your recruiting team.
Principle 1: Compare total cost, not rates
A permanent hire's salary excludes employer social contributions, recruiting fees, equipment, benefits, ramp-up and absence. In our separate analysis of a German senior hire, an illustrative gross salary of EUR 80,000 resulted in a first-year cost of about EUR 143,600 and a steady-state cost of about EUR 518 per productive day. Present every option on that basis. A CFO who sees a full cost model is far more likely to trust the comparison than one who sees a rate next to a salary.
Principle 2: Price the alternative honestly
The relevant alternative to external capacity is rarely an employee who starts tomorrow. Bitkom's 2025 survey reports that filling an IT role in Germany takes 7.7 months on average. The realistic alternative is therefore usually a vacancy for several months, followed by a ramp-up. Put the cost of that path into the model, including the cost of delayed roadmap items.
Principle 3: Express value as cost of delay
Finance teams understand cash flows. Translate engineering output into the cash effect of delivering earlier or later: revenue from a product module, a contract renewal that depends on a feature, savings from an internal automation, or a regulatory deadline that blocks a market. The question becomes: what is it worth to have this result N months earlier?
Illustrative calculation
The following is an illustrative calculation with hypothetical figures, not market prices or the price of any specific provider.
- An external team costs EUR 20,000 per month and is engaged for six months: total EUR 120,000.
- It enables a product module to go live four months earlier than the hiring path would allow.
- The module is expected to generate EUR 40,000 gross margin per month once live.
Within the planning horizon, the earlier launch yields four additional months of margin: EUR 160,000. Net benefit: EUR 40,000. Return on the external spend: about 33 percent.
Principle 4: Show the sensitivity
A CFO will challenge the assumptions. Do it first. Show how the result changes when the key inputs vary.
| Monthly margin of module | Benefit of 4 months earlier | Net result after EUR 120,000 cost |
|---|---|---|
| EUR 20,000 | EUR 80,000 | minus EUR 40,000 |
| EUR 30,000 | EUR 120,000 | EUR 0 (break-even) |
| EUR 40,000 | EUR 160,000 | EUR 40,000 |
| EUR 60,000 | EUR 240,000 | EUR 120,000 |
The break-even line is the most useful number in the table. It tells the CFO what has to be true for the decision to pay off, which is a much easier discussion than defending a single point estimate. Add a second sensitivity on time saved: if the module goes live only two months earlier, the case may not hold.
Principle 5: Value the flexibility
Permanent hires are long-term commitments. In Germany, once the probationary period ends, protection against dismissal applies in many companies, and statutory notice periods under BGB §622 lengthen with tenure. External capacity under a service contract can usually be reduced at contractual notice. For a product line with uncertain prospects, that flexibility has real value. Describe it qualitatively if you cannot quantify it: the downside if the product line is stopped is limited to the notice period.
Principle 6: Address the accounting treatment
CFOs will ask how the spend appears in the financial statements. Under the German Commercial Code, a company may choose to capitalise self-created intangible assets of fixed assets (§248 Abs. 2 HGB), with development costs, but not research costs, as the basis (§255 Abs. 2a HGB). In the tax balance sheet, self-created intangible assets may not be capitalised (§5 Abs. 2 EStG). Under IFRS, IAS 38 requires capitalisation of development costs once specific criteria are met. How externally commissioned development is treated depends on the contract design and on who bears the development risk. Involve your auditor early; the answer affects EBITDA and therefore how the case looks to investors.
Principle 7: Name the risks and their mitigation
- Delivery risk: mitigated by sprint-based acceptance (Abnahme under BGB §640) and the right to reduce or exit.
- Legal risk: mitigated by a contract model that keeps direction of the engineers with the provider, avoiding Arbeitnehmerüberlassung under §1 Abs. 1 Satz 2 AÜG.
- Data and IP risk: mitigated by a DSGVO Art. 28 agreement, standard contractual clauses and exclusive rights of use in all results.
- Knowledge risk: mitigated by documentation as a deliverable and code in your own repositories.
The one-page memo
- Decision requested: amount, duration, notice period.
- Problem: the roadmap item at risk and why internal capacity cannot deliver it in time.
- Options compared: wait and hire, external capacity, descoping. Full cost and timing for each.
- Value: cost of delay for the affected items, with sources for each assumption.
- Sensitivity: break-even values for margin and time saved.
- Risks and mitigation: delivery, legal, data, knowledge.
- Accounting: expected treatment, confirmed with the auditor.
- Review point: the date and the metric on which the engagement will be continued, scaled or stopped.
Providers that work with a fixed monthly fee make the cost side of this memo simple. The value side is yours to build, and it is the part that wins the CFO's approval.
This guide is general information, not legal, tax or accounting advice.
The cost line in that memo is easiest to defend when it is a single, fixed figure with a defined review point. niogod™ structures its engagements that way: a three-person pod at a fixed monthly fee, sprint-based acceptance under BGB §640 and a contractual notice period, so the downside your CFO is underwriting is visible from the start. If a capacity case is due for your next planning cycle, that is a good moment to compare notes.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation