Cost is the argument that finally gets governance taken seriously, and it is the one technical people are worst at making. Engineers argue quality; the budget responds to money.
The damage from sprawl accumulates quietly and gets attributed to other things: “integration complexity,” “developer onboarding time,” “maintenance burden.” Trace those back and you find the same root causes. Four teams built four customer APIs because nobody could discover the first one. Every new integration takes three weeks because each API is idiosyncratic and each needs its own learning curve. A breaking change ships without warning and six downstream teams spend a sprint recovering. Services nobody calls stay funded because nobody can prove they are unused. And the security exposure of APIs the security team does not know exist is a cost you pay all at once.
None of this appears on a line item called “API sprawl,” which is exactly why it persists.
The counter-move is to make it visible. Count the duplicate APIs. Time the integrations. Count breaking changes and the engineer-days they consumed. Show the legacy surface explicitly. Once the number exists, the governance conversation stops being an aspiration about best practice and becomes a straightforward comparison of two costs — and governance wins that comparison nearly every time.
