Enterprise software portfolios were built one decision at a time. A team needed a capability, a manager found a tool, and a department added another subscription. Cloud software made those purchases fast, flexible and relatively easy to reverse.
The result is an operating environment with more applications, more integrations and more overlapping promises. Okta’s Businesses at Work 2025 report found that the average number of apps used by its customers had reached 101. Now generative AI is adding assistants, agents and embedded features to an already crowded portfolio.
The next software cycle is therefore likely to be defined as much by subtraction as adoption.
Consolidation is not simply cost cutting
Reducing license expense is the easiest argument for consolidation, but it is rarely the only one. Every additional platform can introduce another identity system, permission model, data copy, vendor relationship and integration to maintain. Overlap makes it harder for employees to know where work belongs and harder for leaders to see which system contains the authoritative record.
AI raises the stakes. When software only stored information, duplication was inefficient. When software can summarize, recommend and take action, unclear boundaries become a control problem. Two tools may draw from different versions of the same customer record or apply different rules to the same task.
The goal is not to reach the lowest possible app count. It is to create an intelligible operating environment.
Why the cycle has started
Several forces are pushing companies toward a portfolio review at the same time.
- Suites are expanding. Large platforms are adding capabilities that once required specialist products, including analytics, automation and generative AI.
- Security teams need visibility. Each tool expands the identity, access and data-governance surface that must be monitored.
- Budgets are being scrutinized. Renewal decisions are receiving more attention as leaders ask whether adoption produced measurable value.
- AI features are multiplying. Companies may be paying for similar assistants in productivity, collaboration, customer and creative platforms.
- Workflows cross departments. A local tool choice can now affect a process owned by several teams.
These pressures make consolidation rational, but they do not make every consolidation decision good.
The danger of consolidating by category alone
A spreadsheet may show three project-management tools or two analytics platforms and suggest an obvious cut. The operating reality is often more complicated. One tool may support a regulated workflow, a critical integration or a team whose process would be expensive to rebuild.
Broad suites can reduce administrative complexity, but they may also provide a weaker fit for specialized work. Moving everything to one vendor can increase switching costs and concentrate operational risk. A lower license bill can be offset by migration work, retraining, lost productivity or features that never perform as expected.
That is why the unit of analysis should be the workflow, not the product category.
Four tests for every tool
A useful portfolio review can begin with four questions.
- Is the capability genuinely distinct? Compare the work users perform, not the labels vendors use. Two products called “automation” may solve very different problems; two products in different categories may duplicate the same step.
- Does it create measurable operating value? Active seats are only a starting point. Look at cycle time, error reduction, revenue impact, service quality and the amount of work that would return if the tool disappeared.
- What would it cost to leave? Map integrations, data exports, retention requirements, custom workflows, contractual commitments and the time required to retrain users.
- Does it fit the future architecture? A product may be useful today but incompatible with the identity, data and AI controls the company is establishing.
Build tiers, not one approved list
Organizations can make the portfolio easier to govern by assigning tools to clear tiers.
Systems of record hold authoritative customer, financial, employee or product data. They require the strongest governance and the longest planning horizon.
Systems of work coordinate common processes across teams. They should integrate cleanly with systems of record and have defined owners.
Specialist tools support a distinctive capability that a general platform cannot adequately provide. Their value should be explicit and periodically reviewed.
Experiments are time-limited tests with a named sponsor, a defined data boundary and a decision date. An experiment should not become permanent infrastructure simply because no one canceled it.
This approach gives teams room to test new technology without allowing every trial to become an indefinite subscription.
AI requires a more demanding inventory
For AI-enabled products, a standard license audit is insufficient. Companies need to know which data the tool can access, which models it uses, whether prompts or outputs are retained, what actions it can take, how activity is logged and what happens when the underlying model changes.
An embedded assistant may appear free inside a larger contract but still carry training, governance and workflow costs. Conversely, a specialist product may justify its price if it offers better evaluation, controls or domain performance than the bundled alternative.
Consolidation should make those tradeoffs visible rather than predetermine the answer.
A portfolio is an operating choice
The strongest consolidation programs do not begin with a target number of vendors. They begin with a map of the company’s essential workflows and the systems each one requires.
That changes the executive conversation. Procurement can negotiate from a defined architecture. Security can focus on meaningful access paths. Teams can understand which tools are standard, which are specialized and which are temporary. Vendors must demonstrate operational value rather than rely on passive renewal.
The tool consolidation cycle has begun because software is no longer a collection of departmental utilities. It is the environment in which the company operates. Simplifying that environment is not merely a finance exercise; it is a decision about how the organization will work.