The gap between consolidation intent and consolidation spending
A Futurum survey of 830 IT decision-makers conducted in May 2026 found 41 percent planning to reduce or consolidate their application count, with nearly two-thirds favoring a mostly-platform procurement strategy over point solutions going forward. That is a clear statement of intent from a large sample of the people who actually control enterprise software budgets, and on its own it would suggest a meaningful shift toward fewer, broader platforms.
But Futurum's follow-up spending research from October 2026 found little corresponding movement toward major software suites, and the firm's Enterprise Apps Net Score, a measure of positive spending intentions, fell from 16.4 in October 2024 to 9.6 two years later. The major suites' share of positive spending intentions barely changed over that same period, while smaller and departmental products faced the most replacement pressure, meaning consolidation intent is landing on niche tools first, not on the enterprise suites it is usually assumed to favor.
Why intent is not converting into suite spending
Futurum VP of research Keith Kirkpatrick puts the gap directly: "Consolidation is happening, but most of it is not flowing to platform suites." He adds a second, more pointed observation that explains the timing mismatch: "Buyers are planning consolidation faster than they are funding it." That distinction matters for any CIO benchmarking their own consolidation roadmap against peer organizations, since a peer's stated intent is a weaker signal than their actual budget commitment.
A 2025 BCG study, partially funded by SAP, adds a further wrinkle: companies that favor best-of-breed applications over suites were actually more likely to anticipate vendor consolidation than companies already running suites, suggesting the consolidation conversation is happening loudest precisely among organizations least structurally positioned to execute it quickly. Among organizations actively pursuing consolidation, replacements split almost evenly between broader suites and other specialized products, with only a smaller group considering AI-based alternatives as the replacement path.
What actual consolidation looks like at HPE
Hewlett Packard Enterprise CIO Rom Kosla offers the clearest executed example in this research. When Kosla arrived in 2023, the company's IT environment was handling roughly two million support tickets a year for about 60,000 employees, a volume that pointed directly at an underlying system sprawl problem rather than a staffing problem. His response was to consolidate more than 20 separate ERP systems onto a single SAP instance running on private cloud, a multi-year architectural commitment rather than a procurement-level vendor swap.
Kosla's explicit target is an 85 percent reduction in that support ticket volume, a specific, measurable outcome rather than a vaguer goal like fewer vendor contracts or lower license spend. That specificity is itself the lesson: a consolidation program defined by a ticket-volume or outcome target is verifiable in a way that a program defined only by a reduced application count is not, since application count can shrink without any corresponding improvement in how the business actually operates.
Why Ricoh Europe is consolidating without picking a single suite
Ricoh Europe CIO Nick Pearson is pursuing common back-office systems through the company's One Ricoh initiative, a clear consolidation effort by any definition, while deliberately keeping a dual-ERP strategy that retains Oracle alongside other platforms rather than standardizing on one. Pearson frames the choice directly: "We want to offer choice," a stance that treats vendor flexibility itself as a strategic asset worth preserving even inside an otherwise consolidating architecture.
Pearson's approach is a useful counterexample to the assumption that consolidation success means arriving at a single vendor. A separate example in the same research describes a ServiceNow customer that increased spending on that platform specifically while simultaneously reducing reliance on Jira, consolidating around capability rather than around a single company's full product catalog, a pattern that shows up repeatedly among the organizations actually executing rather than merely planning.
The four questions to ask before calling your own consolidation a success
This research frames application count, vendor count, and operating cost as three different metrics that can tell three different stories about the same consolidation program, and warns that AI-based replacements in particular can shift costs rather than eliminate them, since someone still has to run, secure, and maintain whatever replaces the old system. Finishing a technical consolidation does not by itself guarantee a business benefit, which more often requires continued operational work well after the last legacy system is decommissioned.
Before reporting your own consolidation program as complete, apply the four questions this research proposes: what specifically the organization wanted to achieve, what an honest portfolio assessment actually revealed, which changes genuinely made sense given that assessment, and what measurably improved afterward. A CIO who can answer the fourth question with Kosla's kind of specific, verifiable number is in a materially stronger position than one who can only report a lower vendor count on a procurement dashboard.



