The consolidation case is always strong on paper. One vendor instead of six. One contract, one support relationship, one integration model, one set of credentials. A volume discount, and a procurement team that stops managing five renewals.
All of that is true. It is also the entire case, which is worth noticing.
What the discount is buying
A suite discount is a payment for future pricing power. That is not a cynical reading — it is the business model. The vendor is buying share of your estate now in exchange for a position where your cost of leaving exceeds the cost of accepting whatever the next renewal contains.
The measure of that position is not what you pay. It is how many separate systems would have to be replaced simultaneously to change vendor. When the answer is one, you have a supplier. When it is six, you have a dependency, and every renewal from then on is a negotiation you enter without an alternative.
Sophisticated buyers price this. Most do not, because the exit cost is speculative and the discount is on the current page.
The three costs that arrive later
The weakest module sets your floor.
No suite is uniformly good. Every one has two or three strong products and several acquired or under-invested ones. Consolidating means adopting the weak modules alongside the strong, and the teams stuck with the weak ones will work around them — with spreadsheets, shadow tools, manual process. You have not removed those systems. You have made them invisible, which is worse, because they are now outside every control you have.
Your roadmap becomes their roadmap.
With six vendors you have six roadmaps, and one falling behind is survivable. With one, your capability in every consolidated area advances at that vendor’s pace. If they are slow to a genuine shift in the market, you are slow, and no partial response is available to you.
The integration advantage decays.
The strongest argument for a suite is that the modules work together. That is usually true at purchase and degrades afterwards, because suites are assembled by acquisition and integration between acquired products is frequently shallower than demonstrated. Within a few years you are often maintaining integrations between products from the same vendor — all the cost of best-of-breed integration, none of the choice.
When consolidation is right
This is not an argument for best-of-breed, which has its own well-documented failure: an estate nobody can operate, integrated by a team that has since left.
| Consolidate when | Because |
|---|---|
| The capability is genuinely commoditized | If every product does the job adequately, differentiation is not worth the integration cost. |
| Your constraint is operating capacity, not capability | A team that cannot run six tools well will get more from one run properly, whatever the feature comparison says. |
| The shared data model is the point | Where value comes from data moving across modules — core finance, HR, ERP — the integration argument is real rather than marketing. |
| You can still name your exit | If you can describe how you would leave and roughly what it costs, you have kept the position. If you cannot, you have not consolidated. You have committed. |
Write the exit cost next to the savings
The failure is rarely the decision itself. It is that the decision is made once, on year-one economics, and never revisited — while the position it creates compounds annually.
Two disciplines make consolidation safe. Consolidate where capability is commoditized and keep choice where it differentiates you, which demands an honest view of which is which and is the harder half. And write the exit cost into the business case at signature, next to the savings. Not because you plan to leave, but because a number nobody wrote down is a number nobody will defend at the renewal where it finally matters.
If your team cannot describe what leaving would involve, the discount was not a discount. It was a deposit.
This is an argued position on sourcing strategy. It names no vendors and makes no claims about specific products or contracts.
Related Reading
- SaaS Management & Optimization
- IT Asset Management (ITAM)
- Procurement & Source-to-Pay
- Technical debt was never about bad code. That is the whole point of the metaphor.
- Knight Capital lost $460 million in 45 minutes because of code it stopped using in 2003
- Amdahl’s Law was written to argue against parallel computing. Now it is used to plan it.
- Vendor Consolidation Strategy: Reducing Complexity Without Sacrificing Capability
- Third-Party Risk Management: A Framework for Vendor Security Assessment
Independent. No sponsorships. Unsubscribe anytime.