Consolidating software in mid-market companies: what actually works

Software consolidation has a bad reputation in a lot of companies: a rushed annual project squeezed in before the budget renewal, cutting a handful of visible tools without ever addressing the underlying problem. Companies that get lasting results approach consolidation differently — as an ongoing discipline rather than a one-time exercise.

Gartner's three-lever framework

Gartner structures software cost optimization around three distinct levers: efficiency (streamlining existing processes and tools), consolidation (reducing redundancy across vendors and infrastructure), and renegotiation (securing better terms with the vendors you keep). Treating all three as one single exercise — "cutting costs" — is the most common mistake: each one calls for a different method.

Start with visibility, not with cutting

Forrester points out that companies typically accumulate unused SaaS subscriptions, over-licensed enterprise agreements, functionally overlapping tools, and purchases made directly on cloud marketplaces outside the normal procurement process. Without a complete, current view of what actually exists, a consolidation project amounts to deciding what to cut without knowing what's actually in use — the risk of breaking real usage is just as high as the risk of leaving waste in place.

Redundancy doesn't always show up at the tool level

Two pieces of software with different names and categories can cover 70% of the same functional need. The most expensive redundancy isn't always the obvious one — a reporting tool paid for by finance and another paid for by operations can overlap almost entirely without anyone ever noticing, simply because the two purchases were made by different teams at different times.

Moving from a one-time exercise to continuous tracking

Forrester notes a clear shift in how mature companies approach the issue: license optimization is moving from a periodic exercise, triggered by an audit or a renewal, to a continuous operating model — ongoing tracking of actual consumption rather than a once-a-year check. A mid-market company that only revisits its software contracts at renewal time structurally misses the windows where a correction is still possible.

What consolidation shouldn't turn into

Locking every new software purchase behind heavy IT approval slows teams down without guaranteeing they'll stop finding workarounds. The realistic goal isn't zero redundancy — it's redundancy that's visible and justified, rather than redundancy that accumulated by accident and gets discovered months too late.