Calculator
Engineering capacity lost each year
€0
Contribution margin deferred
€0
Total addressable impact
€0
A conservative floor — partner onboarding and long-term maintenance are not included.
Calculated in your browser. Nothing you enter is sent anywhere.
Where the numbers come from
The calculator uses two of the four cost buckets from our Capital Efficiency Framework:
- Engineering rework and coordination: engineers × loaded cost × share of API work × share of that work lost to avoidable friction.
- Delayed time to market: the monthly contribution margin of a capability × the months it is delayed by serial handoffs, missing contracts and late interface redesigns.
The defaults are the framework’s illustrative example: 40 engineers at €120,000, 45% of time on API work, 10% of it lost to friction, and one capability worth €250,000 a month delayed by one month — €216,000 plus €250,000.
Two further buckets — partner and integration onboarding, and maintenance and technical debt — come on top and are left out to keep the estimate conservative. For scale: in Stripe’s Developer Coefficient study, developers spend 13.5 hours of a 41.1-hour week on technical debt.
Three questions worth asking internally
- Capacity: what share of our engineering payroll goes into reconciling, translating and repairing interface decisions that were already made somewhere else?
- Margin: how much contribution margin waits while front-end, mobile and partner teams wait for back-end code before contracts are final?
- Redundancy: how many duplicate components and endpoints are we paying for because nobody could find a contract they trusted?
