Your SaaS Stack Has a Leak: The Vendor Rationalization Guide
Most organizations are paying for software they don't use, software that duplicates other software, and software nobody can quite explain. Here's how to find the leak.
The Problem With Software That's Easy to Buy
The SaaS model changed how organizations buy software, and not entirely for the better. When procurement was hard, a capital expenditure, a formal evaluation, a lengthy IT review, there was a natural filter. Only serious requirements made it through.
Now anyone with a corporate card can spin up a subscription. That's genuinely useful for moving quickly. It's also how you end up with forty-seven SaaS tools, three project management platforms, two contract management systems, and a marketing automation tool that nobody uses because the one the sales team preferred was also purchased and they never integrated.
The average mid-market organization spends meaningfully more on software than its finance team knows, because spend is fragmented across departments, cost codes, and credit cards. The spend that is tracked is often treated as fixed, renewal reminders come in, they get approved by the person who approved the original purchase, and the cycle continues.
What a Rationalization Actually Involves
First, you need a complete picture. Pull all SaaS subscriptions, from IT-managed systems, department budgets, and anything on corporate cards. Include contracts with renewal dates and actual cost, not just the headline subscription fee (add-ons, professional services, and extra seats add up).
Then look at usage. Most SaaS platforms will give you utilization data, active users, feature adoption, login frequency. When you run this analysis, the pattern is consistent: somewhere between 20% and 40% of licenses are either unused or barely used. People got access, never onboarded properly, and the license kept renewing.
Cross-reference for overlap. You'll find tools doing similar things. It's rarely malicious, different teams bought what made sense for them, or a merger brought in a second instance of something you already had. But the overlap is real and it costs real money.
The Conversations You Need to Have
Rationalization runs into resistance because people attach to their tools. The team that fights hardest to keep a platform that costs £8,000 a year is usually the team that's built workflows around it and fears the disruption of changing. That's a legitimate concern, not obstruction.
The conversation that works is one that's honest about total cost and honest about what's being replaced. "We're going to retire this and move to the platform the rest of the organization uses, and here's how we'll make that transition manageable" lands better than "we're cutting software to save money."
Where there's genuine functional need, the tool does something that nothing else in the stack does, the users are genuinely dependent on it, and the cost is proportionate, keep it. Rationalization isn't about reaching a target number of tools. It's about making sure every tool earns its place.
What the Savings Look Like
A well-run rationalization of a 200-person organization's SaaS stack typically finds 15% to 30% cost reduction without removing anything that's actually being used. On a stack that's reached seven figures, that's meaningful.
The less obvious return is operational. Fewer tools means fewer integrations to manage, fewer security surface areas, and less of your IT team's time spent on vendor management. It also means data is less fragmented, which matters every time someone tries to build a report that should take twenty minutes and takes three days because the relevant information lives in four systems that don't talk to each other.