A CIO asks why the internal platform still needs funding two years after it was "delivered". What do you say?

What the interviewer is testing

Whether you can explain the difference between a project and a product to a budget holder.

The answer

A platform was never a thing to be delivered — it is a service other teams depend on continuously.

The question contains the assumption that causes platforms to fail: funded as a project, built, team disbanded, and within two years the capability has decayed into an unowned legacy dependency that everything relies on and nobody maintains. That outcome is more expensive than continued funding, and it arrives quietly.

Concretely, ongoing funding buys:

Currency. The cloud provider deprecates services, base images need patching, runtimes reach end of life, security requirements change. Standing still is not an option.

Support. Teams depending on it need help, and without it they route around the platform and the consolidation is lost.

Roadmap. New requirements arrive as the estate evolves. A platform frozen at its launch scope becomes an obstacle within a year.

Migration and deprecation, so change is absorbed centrally rather than by every consuming team independently.

The evidence to bring

Adoption — proportion of eligible workloads, and the trend.

Consuming teams' outcomes — lead time and change failure rate before and after adoption. This is the strongest evidence available and it directly answers what the platform is for.

Avoided cost — what the estate would spend if each team solved these problems independently.

Currency and risk — what would be unpatched or unsupported without it.

What a strong answer adds

Proposing the funding model that works: central funding with a mandate to serve, measured on adoption and on consuming teams' delivery metrics — and showback so teams see what they consume without being cross-charged, which delivers cost awareness without the avoidance incentive that chargeback creates.

Common weak answers

Arguing from engineering necessity. Accepting project funding and hoping for renewal.