The €220k a month nobody was counting

The client did not ask for an audit. The delivery data asked for it. We had been an embedded partner for over three years; releases went out on schedule, the board saw steady activity, and nobody was alarmed. That is precisely what made it dangerous.

Activity is the best disguise a leak can wear

When delivery is visibly broken, someone owns the problem. When delivery is busy, nobody does. Here, tickets closed and burndowns burned down, but when we asked one question per backlog item, "which business capability does this serve?", more than 90% of user stories had no answer. The work was real. Its value was unaccounted.

Priced against the commercial roadmap, the unaccounted work and the outcomes it displaced added up to roughly €220,000 a month of visible leakage, with exposure up to €315,000, plus a cost of poor quality running to $400,000 a year.

Velocity tells you the engine is turning. It does not tell you the car is pointed anywhere.

What actually changed

Not headcount. The delivery system was rebuilt around traceability: Ideas → Opportunities → Business Capabilities → Features → User Stories → Sprints → Releases, enforced as a gate, not a guideline. Three metrics replaced activity reporting: First-Time Yield, System Availability, and Work in Progress.

• Every backlog item now traces to a capability, a roadmap priority, and a commercial outcome.
• Investment decisions moved to before the work, not after the release.
• Leadership reporting switched from "what we did" to "what it was worth."

If your dashboards are green and your roadmap still feels like a wish list, the leak is probably not in the code. It is in the connection between the code and the business. That connection is buildable, and it is worth building before it costs you a fifth of a million a month.