Platform investments fail in the boardroom before they fail anywhere else — usually because the case was argued in infrastructure language, or padded with numbers nobody believes. This paper sets out an ROI model that survives a sceptical CFO, because every input is measurable and every claim is conservative.
The cost of doing nothing
The baseline is not zero. Without a platform, the organisation already pays: every team independently solving delivery, security and compliance; senior engineers absorbed by undifferentiated work; onboarding measured in months; incidents caused by drift between hand-built environments. The honest comparison is platform cost versus this distributed, invisible spend — not versus nothing.
A model a CFO will accept
- 1.Count the teams and the fraction of their capacity spent on undifferentiated platform work (measure it; do not assume an industry figure).
- 2.Price the duplication: that fraction × loaded engineer cost × team count.
- 3.Price the risk: incident hours, audit preparation weeks, delayed launches attributable to delivery friction.
- 4.Set against it: platform team cost, migration effort, and a credibility discount on every projected saving.
Leading versus lagging metrics
Lagging metrics (velocity, incident rate, audit cost) prove the case after a year. Leading metrics keep the initiative funded until then: time-to-first-deploy for a new service, percentage of deployments on paved roads, tickets per release, onboarding time. Publish them monthly — momentum visible early is what buys patience for the compounding returns.
The executive narrative
Do not sell tooling. Sell capacity and risk, in the form the measurements support: 'we return a measured share of engineering capacity to product work, and we make our delivery posture auditable by construction.' The platform is the mechanism; the deliverable is an organisation that ships faster with fewer surprises — and can prove it.
“If the business case needs optimistic numbers, it is not ready. The honest case is strong enough.”