How much of the budget
actually builds?
The engineering budget is already approved. The productive capacity ratio measures what share of it creates new capability versus is consumed by maintenance, integration, and structural overhead — the complexity tax. Record it each quarter and the trend becomes the instrument.
Capital Efficiency · The Complexity Tax · The CFO Case
Open the toolNot a cost metric.
A capital-efficiency one.
Cost reduction implies the engineering budget should shrink. Capital efficiency asks whether the same approved budget is producing a return. That distinction is the whole argument. When a third of engineering capacity is consumed by structural complexity rather than forward capability, an infrastructure investment is not a cost — it is the recovery of value from spend already committed.
The CFO already approved the budget. The question is whether the budget is still building.
The productive capacity ratio is the share of engineering capacity left for new capability once the complexity tax is removed. One number, recorded each quarter, that turns an architectural case into a capital case.
Four inputs,
once a quarter.
The capital allocation
The confirmed split from your quarterly capital session — foundational platform, product delivery, innovation. It sums to 100%; it is the budget you agreed to.
The overhead consumed
The actual share of capacity absorbed by technical-debt servicing, integration overhead, and structural complexity — regardless of which bucket funded it. This is the complexity tax, and it is the only input that moves the ratio.
The foundational protection
Whether the foundational bucket confirmed at the start of the quarter actually held — or was eroded under delivery pressure. The record that reveals whether capital discipline is real or nominal.
The driver and the context
What drove the overhead this quarter, and the notes that explain the direction of travel. Enough context that the number is legible a year later.
One ratio, five bands,
and a CFO argument.
The ratio is 100% minus the overhead consumed — the capacity left for new capability. It lands in a band, and the tool drafts the capital-efficiency statement you can take to the CFO. Recorded each quarter, the readings form the trend that is the real signal.
60–100%
Strong to healthy. The system is generating new capability efficiently. Protect the foundational bucket and watch the trend direction.
50–60%
Warning. Nearly half of engineering capacity is absorbed by overhead. Identify the driver and prepare the capital case.
Below 50%
Serious to critical. Structural degradation is consuming delivery capacity. A capital decision is required — make the CFO argument.
Record it each quarter, alongside the capital-allocation session — when the confirmed buckets are fresh and the quarter's actual overhead is known. One reading per quarter is enough; the value is in the sequence.
Bring the trend to the board and the CFO when the ratio slips into Warning or below, or when foundational erosion appears alongside AI initiatives blocked by platform state — the point at which the complexity tax stops being an engineering concern and becomes a capital one.
The budget is approved.
Prove what it builds.
One ratio, recorded each quarter, that turns the complexity tax into a capital-efficiency case — measured, not asserted.
Open the tool