Finance asks what the platform team returns for what it costs. How do you show it without inflating the number?
Show platform ROI against a counterfactual cost: what product teams would spend doing the work themselves, measured from non-adopters. Add measured time saved, discounted because hours are capacity not cash, and consolidated licences. Report reliability separately and state the limits.
Answer
Short answer
Platform ROI is measured against a counterfactual. The question is not "what does the platform earn" but "what would the company spend, and lose, if product teams did this work themselves". You build the figure from three parts: the duplicated work the platform removes, measured time saved discounted to what is realistically reused, and consolidated tooling. You then report reliability and risk alongside it, and you say plainly what the number cannot capture.
Was this answer helpful?
Likely follow-ups
- Your honest figure comes out at 0.75. Finance proposes cutting the platform team in half. What do you put in front of them?
- How do you measure time saved without relying on a developer survey?
- The non-adopting teams say their own tooling is cheaper. How do you test that claim fairly?
- Which single metric would you report quarterly so finance can track the platform without a new business case each year?
Related questions
- Build or buy an internal developer platform: build the total-cost comparison.hardAlso on platform-engineering and business-case5 min
- Live case: you have thirty minutes to present a business case for migrating our monolith. Take us through the options, the sequence, the risks and how we would know it worked.hardAlso on business-case6 min
- The board asks why engineering has slowed down. What do you measure, and what do you refuse to measure?hardAlso on developer-productivity5 min
- How do you get a design system adopted by product teams moving at different speeds, and what do you do about the team that forked your component?hardAlso on platform-engineering5 min