7 Min. Read

68 percent of IT organizations plan a vendor consolidation in 2026. The majority aims for 20 percent fewer suppliers. The reality: Most programs take 30 to 36 months, achieve a 18 percent reduction, and only realize the savings in the third year. The costly mistake is not the target number, but underestimating the integration gap between old and new systems.

The 68 Percent Figure: What the Market is Doing Right Now

This figure comes from a Gatekeeper survey on vendor consolidation for 2026: 68 percent of the tech leaders surveyed state they will actively reduce their vendor portfolios within the next twelve months. The average target is to have 20 percent fewer suppliers-well below the half-yearly cost-cutting demands of many CFOs, but within a range that teams can handle operationally.

The drivers are three familiar factors: cost, risk, complexity. Cost, because SaaS stacks ballooned during the pandemic. Risk, because every vendor relationship opens up its own security, compliance, and data privacy exposure. Complexity, because nobody can fully oversee 120 to 200 suppliers in a mid-sized company anymore. The idea that “less is better” is intuitively correct. The implementation is not.

Gartner sharpens the forward-looking view: By 2027, 70 percent of all organizations will consolidate their cloud-native application vendors to a maximum of three strategic providers. This is a radical figure that marks the difference between tactical rationalization and strategic architectural decision-making. Anyone currently working with five cloud platforms, four observability stacks, and three identity providers will not reach this target in one year.

The Three Typical Consolidation Waves

Observing consolidation programs in DACH (Germany, Austria, Switzerland) companies reveals three recurring waves-each with its own target scale, timeframe, and pitfalls.

The first wave is security tooling. Gartner reported in 2022 that 75 percent of organizations were aiming for security vendor consolidation, primarily because CISOs were juggling between five and twelve overlapping tools for endpoint, network, identity, and SIEM. This wave has largely been implemented by 2024 and 2025-any company still relying on 20 security vendors today has missed the market trend. Typical outcome: reduction to a single XDR platform plus two to three specialized add-ons.

The second wave is SaaS tooling beyond security. Slack, Teams, Notion, Asana, Jira, Confluence, Monday, Airtable-collaboration and productivity tools are the most visible targets. Here, savings are often lower than hoped, because user resistance and workflow dependencies are greater than in the security context. According to Gartner, the mid-market has reduced its SaaS portfolio by an average of 18 percent over the last two years-mostly quietly through expiring licenses, not via active migration.

The third wave is platform consolidation in the cloud stack. This is where the major levers for the coming years lie: multi-cloud architectures are deliberately reduced, observability stacks unified, API management centralized. This is the wave addressed by Gartner’s 70 percent forecast. It is technically demanding, politically sensitive within organizations, and has the longest timelines-rarely under 24 months, often 36 or more.

Why 20 Percent is the Realistic Target

In consolidation projects, CFOs often demand a reduction of 30 to 40 percent in vendor numbers. Experience from real-world programs shows that 20 percent is the robust upper limit if the consolidation is to proceed without operational disruptions. David Weisong, CIO of Energy Solutions, spent three years reducing his software catalog from 120 to 105 applications-a 12.5 percent cut. During the same period, his company scaled from two locations with 120 employees to over 500 employees across six sites. Without the consolidation effort, the catalog would likely have grown to 180 applications.

Sources: Gatekeeper Vendor Consolidation Report 2026, Gartner SaaS Management 2025, CIO.com Case Analysis

Why is achieving more rarely possible? Four interconnected reasons. First: At least 30 percent of vendors are so deeply embedded in operational processes that replacing them would constitute a separate migration project. Second: Another 15 percent are critical for compliance and are on vendor lists that have been painstakingly approved internally. Third: Change management resistance from users consumes time that is missing from Excel-based planning. Fourth: New contracts with strategic partners often have minimum purchase commitments that can eat up savings in the first twelve months.

The realistic roadmap for a 20 percent cut looks like this: Quarter 1 categorization and prioritization, Quarters 2 and 3 replacement of the simple cases, Quarters 4 to 6 the complex migrations, Quarters 7 and 8 stabilization. To arrive at the goal within 18 months, you must work with three to four parallel workstreams from day one-and that requires capacity which is not readily available in most IT organizations.

The underestimated share: Integration and migration costs

The most expensive aspect of vendor consolidation never appears on the savings slides: integration and migration costs. When a company reduces from three video conferencing tools to one, the license savings are quickly calculated. The costs for migrating meeting rooms, calendar integrations, third-party recording solutions, and user training rarely appear in the original business case. Yet they typically account for 40 to 70 percent of the first-year savings.

A particularly tricky area is identity and authorization data. Every vendor switch means that users, roles, groups, and access rights must be rebuilt in the new system. Those who don’t automate this lose weeks in manual work-and risk breaking audit trails, which in regulated industries directly leads to compliance problems. Therefore, the consolidation roadmap must always include an identity and data migration track.

“Be an efficiency expert or an operational expert, not simply a cost cutter.”
– Scott Klein, CIO TVG-Medulla (CIO.com, 2026)

The quote marks the core shift CIOs must make in consolidation programs: Those who frame the exercise purely as a cost hunt achieve the reduction-but leave behind an IT organization that is operationally less capable. Those who frame it as an efficiency and operational excellence program take longer, achieve less reduction, but leave behind an architecture that will carry them for the next three years. The CFO discussion is always the same-and it is decided not by slides, but by peer validation and board context.

The Counterargument: When Consolidation is the Wrong Answer

Not every vendor diversity is a bad thing. There are three scenarios where aggressive consolidation destroys more than it saves. The first: innovative niche vendors whose tools improve one critical workflow better than any platform solution. Replacing a bug tracker with highly specialized compliance functionality with a module from an enterprise suite often sacrifices precisely the feature that justified the original purchase.

The second scenario: critical dependency on a single hyperscaler. Concentrating your entire cloud infrastructure on one provider to reduce vendor costs creates a cluster risk that is often underestimated in governance documents. The DORA regulation in the financial sector already forces the industry to actively manage concentration risks and maintain exit strategies. For other regulated sectors, this is only a matter of time.

The third scenario: redundancy as a business model decision. Two payment providers, two CDN providers, two DNS services are not inefficiency, but active resilience management. To avoid accidentally consolidating this away, these exceptions must be explicitly incorporated into the consolidation logic-otherwise, the first unnoticed outage jeopardizes the entire savings effort.

Decision Framework: Three Questions Before Starting

Before launching a consolidation initiative, three questions should be answered. They are deliberately phrased to be uncomfortable and cannot be glossed over with standard consulting answers.

First Question: What is the real business case-cost, risk, or architecture? The three goals are not additive. A cost-focused program optimizes for quarterly savings and consumes architectural decisions. A risk-focused program optimizes for compliance and vendor governance, not for savings. An architecture-focused program needs three years and only delivers savings in the third year. If you don’t clarify which of the three goals dominates at kickoff, you’ll build a program that achieves none.

Second Question: What capacity does your own organization have for migration work? Every vendor replacement ties up project management, integration, data migration, user training, and stabilization. If the program runs without dedicated resources and expects existing teams to handle it “on the side,” the realistic throughput rate is two to three vendor replacements per quarter. Anyone aiming to shut down 30 vendors in twelve months needs eight to ten parallel streams and a dedicated migration team as a prerequisite, not an option.

Third Question: What is the fallback plan if a strategic partner fails, raises prices, or is acquired? Consolidation inherently creates dependency. Anyone who consciously accepts this dependency must consider exit strategies and contingency paths. This is not paranoia, but part of the responsibility that is reassigned with every vendor reduction. Especially in regulated industries, exit management is now a subject of audit scrutiny.

Conclusion

Vendor consolidation is not merely an economic exercise. It is an architectural decision cycle with financial side effects. Those who launch it as a pure cost-cutting hunt will deliver savings twelve months later that are consumed by integration costs, user resistance, and silent workarounds. Those who set it up as an operational excellence program accept a 20 percent reduction instead of 40 percent-but gain an architecture that will hold up for the next three years and won’t need to be reopened during the next wave of M&A or CFO demands.

The figure CIOs should show their CFOs is not the cumulative savings after year one, but the total cost of ownership difference after year three-including migration costs, integration testing, and stabilization reserves. Opening up this calculation elevates the conversation to the level it deserves. Then, they can discuss the question that truly matters: what operational flexibility the company wants to afford in the future, and what dependencies it will accept to achieve it.

Frequently Asked Questions

Source cover image: Pexels / Kuan Liao