Eighteen percent of the names listed in a standard engineering capabilities deck-those glossy PDFs that look like high-end real estate brochures-will never actually touch a single line of your code. This is not a clerical error or a rounding mistake; it is a structural necessity of the traditional services business model.
The “Ghost Percent” – Inventory that exists on slides but never in your codebase.
The “bench” was once marketed as a warehouse of ready-to-work genius, an insurance policy against the terrifying reality of an empty calendar. For decades, the size of that warehouse was the only metric that mattered (a metric often measured in floor-space square footage and headcount totals). If a firm had five hundred engineers, it was assumed they could solve five hundred engineers’ worth of problems simultaneously.
Scale was the moat. But as the complexity of software shifted from “can we build it?” to “how specifically do we maintain it?”, that moat began to look more like a stagnant pond.
Slide Fourteen and the Collaborative Stare
The capabilities deck in front of Ingrid, a director of digital with a persistent crick in her neck from reviewing three such decks today, is open to slide fourteen. It features a map of the globe dotted with pins, a headcount figure that looks like a high-score in a video
