Platform Funding
Central cost, showback, chargeback, and justifying a team that ships no customer feature.
6 to work through
-
intermediate
A platform group of 9 engineers costs roughly $2.2M a year fully loaded. Its business case says it saves 300 product engineers 25 minutes a day. Finance does not believe the saving. Roughly what is the defensible number, and what does it rule in or out?
3 min answer -
intermediate
A platform team is funded as a cost centre and is being asked to justify itself. What changes if it is funded as a product?
2 min answer -
advanced
A CIO asks why the internal platform still needs funding two years after it was "delivered". What do you say?
1 min answer -
advanced
A platform team is asked to justify its existence. What should it measure, and what happens when platforms are funded as cost centres?
2 min answer -
advanced
A platform team must justify continued investment when its value is indirect. What arguments and measures work?
2 min answer -
advanced
Finance proposes charging teams for platform consumption to drive cost awareness. What is your view?
2 min answer
3 terms in this topic
Platform as Product
Running an internal platform with a product manager, a roadmap, identified users and measured adoption, rather than as a project with an end date.
conceptPlatform Funding Model
How internal platform work is paid for, which determines what the platform optimises for and whether it survives a budget cycle.
practiceShowback
Reporting each team's share of platform and infrastructure cost without actually charging it, to change behaviour without creating a market.
Neighbouring topics
Platform Engineering
General material on internal platforms as products with users, adoption and lifecycles.
Internal Developer Platform
The assembled surface teams actually touch, and what belongs behind it.
Paved Road & Golden Path
A supported default route that is easier than the alternatives rather than mandatory.
Self-Service Provisioning
Teams getting infrastructure without a ticket, and the guardrails that make that safe.
Service Templates
Scaffolding new services with observability, CI and security already wired in.
Platform APIs
Treating the platform's own interfaces as contracts with consumers and compatibility rules.
Platform Tenancy
Isolating teams sharing a cluster, account or pipeline fleet, and where isolation must be hard.
Cluster Architecture
How many clusters, split by what, and the blast radius each split buys.
Service Mesh Operations
What a mesh genuinely solves, its failure modes, and the cost of running one.
Container Image Strategy
Base images, layer hygiene, rebuild cadence, and patching a fleet of images.
Developer Environments
Local, remote and ephemeral environments, and the fidelity each can honestly claim.
Inner Loop & Outer Loop
Where an engineer's time actually goes, and which loop a platform investment shortens.
Abstraction Level Choice
How much to hide, and the leak that turns a helpful abstraction into a trap.
Platform SLOs
Committing to reliability for internal consumers who cannot choose another provider.
Platform Adoption
Migrating existing teams onto a platform without a mandate, and reading the adoption curve.
Platform API Deprecation
Removing something dozens of internal teams depend on, on a timeline that holds.
Guardrails vs Gates
Preventing a class of mistake automatically versus stopping to ask a human.
Platform Telemetry
Instrumenting the platform itself: usage, friction, and where teams leave the paved road.
Platform Team Topologies
Stream-aligned, enabling, complicated-subsystem and platform teams, and their interactions.