The Real Cost of Infrastructure and Vendor Sprawl

No mid-market business sets out to run forty vendors. It happens one contract at a time: a department buys a tool to solve a specific problem, a project needs a specialist platform, an acquisition brings its own stack along with it. Three years later, nobody can produce a full list of what the business is actually paying for, and the finance team is reconciling invoices from suppliers that operations barely remembers signing up.

This is vendor sprawl, and it's one of the most expensive things a scaling business can have happen to it without ever making a single bad individual decision.

Why sprawl is invisible until it's counted

Sprawl is invisible because every contract that created it looked reasonable in isolation. A £400-a-month tool is easy to approve and easy to forget. It's only when someone lines up every subscription, every hosting account and every support contract against each other that the pattern becomes visible: overlapping tools doing the same job for three different departments, contracts that auto-renewed past the point anyone was using them, and infrastructure spend spread across enough providers that no single relationship is big enough to negotiate seriously on.

The direct cost is the easiest part to quantify. A genuine infrastructure and vendor audit at this size of business typically finds a meaningful chunk of recoverable spend sitting in duplicate or unused licensing, work Boardman has seen repeatedly across mid-market engagements even before any renegotiation happens.

The cost nobody puts on a spreadsheet

The direct spend is only part of the picture. Sprawl has a second, larger cost that rarely appears on any single invoice: coordination overhead. Every additional vendor adds another support contact, another escalation path, another set of credentials, another renewal date to track. During normal operation this is an irritation. During an incident, it's the difference between a contained problem and a chaotic one, because nobody can say with confidence which vendor owns which part of the failure.

Sprawl also taxes decision-making speed. A business with five core platforms can move quickly when it needs to change something, because there are only five relationships and five contracts to consider. A business with forty platforms has to check for hidden dependencies before touching almost anything, which means IT becomes structurally slower at exactly the moments the business most needs speed, during a growth push, an acquisition, or a market shift.

Where sprawl actually comes from

Three patterns show up again and again in mid-market businesses:

Departmental procurement. When individual teams can buy software without a central view, sprawl is a near-certain outcome, not a risk. Marketing, sales and operations each solving their own problem independently is rational at the team level and expensive at the company level.

Acquisition residue. Every acquisition brings its own IT estate. Without a deliberate integration plan, the acquired company's tools simply sit alongside the parent company's tools indefinitely, doubling costs for capability the business already had.

Fear of migration. Once a system is embedded, however marginal its value, the perceived cost and risk of moving off it usually exceeds the visible cost of just continuing to pay for it. This is how genuinely redundant systems survive for years past their useful life.

What it actually takes to fix

Fixing sprawl is not primarily a negotiation exercise, although renegotiating consolidated contracts from a position of real leverage is part of it. It starts with an honest, complete inventory: every vendor, every contract, every renewal date, mapped against what each one is actually used for and by whom. Most mid-market businesses have never had this document exist in one place before.

From there, the real decisions are about which systems can be consolidated without disrupting the business, which contracts are worth renegotiating now versus at natural renewal, and which relationships need to be exited altogether rather than managed. None of this requires heroics. It requires someone with the authority and the time to own the full picture, rather than each department continuing to manage its own slice of it.

The businesses that get real value out of this exercise treat it as an ongoing discipline, not a one-off clean-up. Sprawl regrows quietly the moment nobody is watching for it, which is exactly how it built up the first time.