# Shared Infrastructure's Value Case Depends on Who Else Benefits ## Claim A platform or shared-infrastructure investment's real value comes from how many teams beyond the requester can use it, so "who else benefits" belongs in the business case as a structural question, not an optional nicety. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds specifically for investments whose defining property is shared use — a platform, shared tooling, common infrastructure — not for single-team tools where one requester genuinely is the only beneficiary. - Doesn't claim every platform pitch needs to enumerate every future beneficiary precisely — only that a business case which never asks the question is systematically undervaluing exactly the thing that distinguishes a platform investment from a project investment. - The presenters scale their example small (a churn-reduction pitch); the same discipline applies at any size, from a two-engineer six-week build to an ecosystem-level optimizing-stage platform. ## Evidence CNCF's worked example: a churn-reduction pitch justified as a lightweight centralized platform, framed not as "I want to build a platform" but as solving a business goal that sales, customer success, and executives all care about, with the explicit "who else benefits" question naming every team that gains platform access as part of the value case — not as a side benefit mentioned after the fact. ## Links - [[3. Resources/Permanent Notes/A Contribution Pipeline Needs a Defined Next Step After Training]] — contrasts; that note is about a single pipeline's own continuity, this note is about a platform's value being defined by breadth of reuse rather than depth of one team's outcome - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — applies-in; funding requests for shared infrastructure should structurally include this question rather than defaulting to single-team ROI framing - [[3. Resources/MOCs/Open Source Governance MOC]] — applies-in; the same logic underlies why open-source infrastructure investment gets justified across an ecosystem, not one maintainer's workload - [[3. Resources/Permanent Notes/Support Collapses When the Benefits Are National and the Costs Are Local]] — because extends: that note makes the benefit side conditional on the beneficiary set; this makes the cost side conditional on the same thing. ## Tests / falsifiers - Compare approval rates for platform funding requests that explicitly name multiple downstream beneficiary teams against requests framed around the requesting team's needs alone, holding technical scope constant. - If a platform pitch that never mentions other beneficiaries gets funded and adopted broadly anyway, that would suggest the explicit "who else benefits" framing is a communication tactic rather than a necessary condition for the value actually existing. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/Turning Platform Engineering Work Into Business Value]] — Danielle Cook & Simon Foster, CNCF Ambassadors, CNCF/KubeCon talk