All case studies

Where reduction worked

Codat

Took roughly 400 deployable units down to 160

A single Azure certificate change had to be fixed in hundreds of services, so the team merged services and re-architected nothing.

Removed: roughly 400 deployable units, taken down to around 160 — merged services, no re-architecting, no database consolidation in phase one.

Outcome: features that used to need a coordinated march across three or four repositories now land in a single pull request.

Codat’s engineering team took “roughly 400 deployable units down to around 160” after a single Azure certificate change had to be fixed in hundreds of places. Their reason was maintenance rather than performance: “Every certificate rotation became hundreds. A long tail of services that no one had touched in months still had to be patched, observed, and kept alive.” Phase one merged services and nothing else — no re-architecting, no database consolidation — and features that used to need a coordinated march across three or four repositories now land in a single pull request. Blast radius includes the work you repeat every time someone else changes a platform.

Source: Codat Engineering, Shrinking the estate: consolidating to go faster (4 August 2026)