Local AI: Governance Before Hardware Purchase
Benedikt Langer
10 min readFour developments over two weeks show that locally operated AI goes far beyond the tech stack. ...
Read Article
12 min read
7 Min. Read Time
68 percent of IT organizations plan vendor consolidation by 2026, aiming for a 20 percent reduction in providers. However, the reality is that most programs require 30 to 36 months to achieve an 18 percent reduction, with savings realized in the third year. The costly mistake is not the target number but underestimating the integration gap between old and new systems.
Key Takeaways
- 68 percent of tech leaders plan vendor consolidation by 2026, aiming for a 20 percent reduction in vendors, alongside a two-digit percentage cost reduction.
- Gartner predicts that by 2027, about 70 percent of organizations will consolidate their cloud-native application vendors to a maximum of three strategic providers.
- Mid-market companies have already reduced their SaaS portfolios by an average of 18 percent over the past two years, primarily through non-renewal of expiring licenses rather than active migration.
- The underestimated cost component is not the new license but the integration and migration overhead: data, identities, workflows, and audit trails need to be translated into the target stack.
- Consolidation is not just a cost-cutting exercise. The key question is which dependencies a company consciously accepts and where a secondary provider is needed as an operational fallback.
The 68-Percent Figure: What the Market Is Currently Doing
The figure comes from a gatekeeper survey on vendor consolidation for 2026: 68 percent of the surveyed tech leaders plan to actively reduce their vendor portfolios in the next twelve months. The average target is a 20 percent reduction in vendors, well below the half-yearly cost reduction demands of many CFOs but within a range that teams can operationally manage.
Drivers are three known factors: cost due to the pandemic-expanded SaaS stacks, risk because each vendor relationship opens up a separate security, compliance, and data protection area, and complexity because 120 to 200 vendors in a mid-sized company are no longer manageable. The idea that “less is more” is intuitively correct, but the implementation is not.
Gartner sharpens the focus forward: 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 number that marks the difference between tactical rationalization and strategic architectural decision-making. Anyone working with five cloud platforms, four observability stacks, and three identity providers today will not achieve this target in a year.
Definition
Vendor Consolidation is the deliberate reduction of active suppliers by combining overlapping functions with a strategic partner. It differs from Vendor Rationalization, where only redundant or underutilized contracts are terminated without changing the architecture. Rationalization is tidying up, while consolidation is a restructuring.
The Three Typical Consolidation Waves
Those observing consolidation programs in DACH companies notice three recurring waves – each with its own target size, time horizon, and obstacles.
The first wave is Security Tooling. Gartner reported in 2022 that 75 percent of organizations are aiming for security vendor consolidation, primarily because CISOs juggle between five and twelve overlapping tools for endpoint, network, identity, and SIEM. This wave was largely implemented by 2024 and 2025 – anyone still sitting on 20 security vendors has missed the market movement. Typical outcome: Reduction to an XDR platform plus two to three specialized additions.
The second wave is SaaS Tooling beyond Security. Slack, Teams, Notion, Asana, Jira, Confluence, Monday, Airtable – collaboration and productivity are the most visible targets. Here, the savings are often lower than expected due to user resistance and workflow dependencies being greater than in the security context. According to Gartner, mid-market companies have reduced their SaaS portfolios by an average of 18 percent over the last two years – mostly quietly through expiring licenses, not through active migration.
The third wave is Platform Consolidation in the Cloud Stack. This is where the big levers of the coming years lie: Multi-cloud architectures are being consciously reduced, observability stacks are being unified, and API management is being centralized. This is the wave that addresses Gartner’s 70 percent forecast. It is technically challenging, politically sensitive, and has the longest timeframes – rarely under 24 months, often 36 or more.
Why 20 Percent is the Realistic Goal
CFOs often demand 30 to 40 percent fewer vendors in consolidation projects. Experience from real programs shows that 20 percent is the feasible upper limit if the consolidation is to run without operational cuts. David Weisong, CIO of Energy Solutions, has reduced his software catalog from 120 to 105 applications over three years – a 12.5 percent reduction. During this time, his company scaled from two sites with 120 employees to over 500 employees across six sites. Without the consolidation, the catalog would likely have grown to 180.
68 %
Tech Leaders with Consolidation Plan 2026
20 %
Typical Vendor Reduction Target
18 %
Mid-Market SaaS Reduction in Two Years
Sources: Gatekeeper Vendor Consolidation Report 2026, Gartner SaaS Management 2025, CIO.com Case Analysis
Why is more rarely possible? Four reasons intertwine. First, at least 30 percent of vendors are so deeply embedded in operational processes that replacing them would require a separate migration project. Second, another 15 percent are compliance-critical and are listed on internal lists that were painstakingly approved. Third, change management resistance among users costs time that is not accounted for in Excel plans. Fourth, new contracts with strategic partners have minimum commitments that often eat into the savings in the first 12 months.
The realistic roadmap for a 20 percent cut looks like this: Quarter 1 for categorization and prioritization, Quarters 2 and 3 for the simple cases, Quarters 4 to 6 for complex migrations, and Quarters 7 and 8 for stabilization. Anyone aiming to achieve this in 18 months must start with three to four parallel workstreams – and that requires capacity that is not readily available in most IT organizations.
The Underrated Component: Integration and Migration Costs
The most expensive aspect of vendor consolidation is rarely highlighted on cost-saving slides: integration and migration costs. When a company consolidates from three video conferencing tools to one, the licensing cost savings are quickly calculated. However, the expenses associated with migrating meeting rooms, calendar integrations, third-party recording solutions, and user training often go unaccounted for in the initial business case. These costs typically make up 40 to 70 percent of the first year’s savings.
A particularly sensitive area is identity and authorization data. Each vendor switch means that users, roles, groups, and access rights must be rebuilt in the new system. If this process is not automated, it can result in weeks of manual work and risks breaking audit trails, which can directly lead to compliance issues in regulated industries. Therefore, the consolidation roadmap must always include an identity and data migration plan.
“Be an efficiency expert or an operational expert, not simply a cost cutter.”
– Scott Klein, CIO TVG-Medulla (CIO.com, 2026)
This quote highlights the core shift that CIOs must make in consolidation programs: those who approach the exercise as a pure cost-cutting measure will achieve the reduction, but will leave an IT organization that is less operationally capable. Conversely, those who approach it as an efficiency and operational excellence program will take longer, achieve less reduction, but will leave an architecture that will bear fruit in the next three years. The CFO discussion is always the same – and it will not be decided by slides, but by peer validation and board context.
The Counterargument: When Consolidation is the Wrong Answer
Not every vendor diversity is bad. There are three configurations where aggressive consolidation can do more harm than good. The first: innovative niche providers whose tools improve a critical workflow better than any platform solution. Replacing a bug tracker with specialized compliance functions from an enterprise suite module often results in losing the very feature that made the tool worth purchasing.
The second configuration: critical dependency on a single hyperscaler. Concentrating the 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 mandates active management of concentration risks and the retention of exit strategies. For other regulated sectors, this is only a matter of time.
The third configuration: redundancy as a business model decision. Two payment providers, two CDN providers, two DNS services are not inefficiency, but active resilience management. If these are not consolidated by mistake, they must be explicitly incorporated into the consolidation logic – otherwise, the first unnoticed failure can negate all the savings.
Decision Matrix: Three Questions Before You Begin
Before a consolidation initiative is launched, three questions must be answered. They are intentionally uncomfortable and cannot be dismissed with standard consulting answers.
First Question: What is the true business case – costs, risk, or architecture? These three goals are not additive. A cost program optimizes for quarterly savings and devours architectural decisions. A risk program optimizes for compliance and vendor governance, not for savings. An architecture program requires three years and delivers savings only in the third year. If the kickoff does not clarify which of the three goals dominates, a program is built that achieves none.
Second Question: What is the capacity of your organization for migration work? Each vendor transition ties up project management, integration, data migration, user training, and stabilization. If the program runs without dedicated resources and the existing teams are expected to do it “on the side,” the realistic throughput rate is two to three vendor transitions per quarter. If you want to switch off 30 vendors in 12 months, you need eight to ten parallel streams and a migration team as a prerequisite, not an option.
Third Question: What is the fallback plan if a strategic partner fails, prices rise, or is acquired? Consolidation inherently creates dependencies. If you consciously enter into these dependencies, you must also consider exit strategies and contingency plans. This is not paranoia but part of the responsibility that comes with every vendor reduction. In regulated industries, exit management is now a subject of scrutiny.
Conclusion
Vendor consolidation is not just an economic exercise. It is an architectural decision cycle with financial side effects. If you start it as a pure cost-cutting exercise, you will deliver a saving after 12 months that will be eaten up by integration costs, user resistance, and hidden workarounds. If you approach it as an operational excellence program, you accept a 20 percent reduction instead of 40 percent – but gain an architecture that will last for the next three years and not be torn apart by the next M&A wave or CFO’s demands.
The number that 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 tests, and stabilization reserves. Those who calculate this can elevate the conversation to where it belongs. And then they can discuss the question that truly matters: What operational flexibility does the company want to achieve in the future and what dependencies does it accept for that?
Frequently Asked Questions
How long does a typical vendor consolidation take?
Programs under 18 months typically achieve only rationalization, not true architecture consolidation. For a strategic reduction of 20% of the vendor count, 24 to 36 months is realistic. The duration depends less on the number of vendors than on the depth of integration. Isolated SaaS tools can be replaced in a few weeks, while deeply integrated platform services require a migration project per vendor.
At what point does an external vendor management team become cost-effective?
An external vendor management team with one to two full-time employees becomes cost-effective at an active portfolio of 80 to 100 vendors. Below this threshold, a partial function within procurement or IT sourcing is sufficient. External consulting helps during the initial assessment phase but should not take over operational management, as this risks knowledge leaving the company.
How can you prevent retired tools from returning via shadow IT?
Three levers are most effective. First, a functional replacement solution that truly covers the workflows of the old tools, not just formally replaces them. Second, clear procurement rules with sanctions for bypassing, coupled with SSO enforcement and expense controls. Third, regular SaaS discovery scans that automatically identify new shadow tools. Without the first lever, the other two are merely symptomatic treatments.
What role does negotiation position play with strategic partners?
Each consolidation increases dependence on remaining partners and shifts negotiation power, often to the disadvantage of the customer. Countermeasures include multi-year price guarantees, exit clauses with defined cost caps, and contractually fixed service levels with penalties. Those who complete consolidation without implementing these clauses will pay back the promised savings in the second round of negotiations.
How do you communicate realistic timelines to CFO and board?
Three tools are effective. First, a total cost of ownership calculation over three years that explicitly shows migration and integration costs. Second, a quarterly progress report structure with clear milestones that makes progress visible without turning every slip into a drama. Third, peer benchmarking that shows typical timelines and throughput rates of other companies, which relieves the discussion from the question of whether the team is working too slowly.
What distinguishes a 2026 consolidation from programs of the past years?
Two things. First, the cloud-native wave has more than doubled the number of providers in the last five years. Many companies have built SaaS stacks during the pandemic that were never planned. Second, regulatory requirements like DORA, NIS2, and the EU Data Act are forcing companies to actively document their vendor landscape. The 2026 consolidation is therefore not just a cost program but also compliance-driven, changing priorities and tolerance for interim stages.
Editor’s Reading Tips
More from the MBF Media Network
- → Data-Act Implementation Act for IoT Manufacturers (MyBusinessFuture)
- → Valkey 9 vs. Redis 8: Cloud Cache Comparison (cloudmagazin)
- → Cyber Resilience Act 24-Hour Reporting Requirement (SecurityToday)
Image Source: Pexels / Kuan Liao