The $10B Microsoft Deal Signaling Why Your SaaS Stack Is Bleeding Cash

Large organizations spent the last decade adding software every time a new problem appeared. A new marketing challenge? Buy a platform. A collaboration gap? Add another tool. A reporting need? Subscribe to something else. Now many of those same organizations are discovering that the next major cost-saving opportunity may not be another technology investment—it may be removing, consolidating, or connecting what they already own.

That shift became impossible to ignore in early 2026, when the U.S. Department of Defense announced a nearly $10 billion enterprise agreement with Microsoft to consolidate cloud, productivity, and security services across military branches. The headline was the price tag. The real story was the reasoning: even the largest, most complex organization in the world had concluded that owning too many overlapping platforms was costing more than it was worth.

That conversation is now happening in nearly every boardroom. And it’s no longer just an IT topic. It has become a CEO, CFO, and COO priority because software sprawl now shows up on the P&L, in productivity reports, in security audits, and in customer experience metrics.

How Software Sprawl Happens

No executive sets out to build a bloated technology stack. It happens gradually—one reasonable purchasing decision at a time.

Sales adopts a CRM. Marketing buys a separate marketing automation platform. Customer success layers on its own support tool. Finance signs up for a reporting application. Operations deploys a project management system. Engineering picks a different one. Each department chooses a communication app that fits its workflow. Security adds several point solutions to address specific threats. And behind all of that sits a legacy platform nobody wants to retire because “too much depends on it.”

Multiply that pattern across five years, three acquisitions, and a hybrid workforce, and a mid-sized enterprise can easily end up with:

• Multiple project management platforms
• Overlapping CRM and marketing systems
• Several reporting and analytics tools
• Two or three communication apps
• Duplicate security products
• Dozens of department-specific SaaS subscriptions
• Legacy operational systems still running critical workflows

Every one of those purchases made sense at the time. The combined environment, however, was never designed. It accumulated.

The Cost Is Bigger Than the Subscription

When leadership evaluates software cost, the conversation usually starts with license fees. That’s the smallest part of the number.

Duplicate and disconnected software creates costs that rarely appear on a single invoice:

• Employee training on multiple tools that do similar work
• Context switching between applications, which studies from Gartner and Microsoft have repeatedly linked to measurable productivity loss
• Duplicated data entry across systems that don’t talk to each other
• Integration development to force platforms to share information
• Reporting complexity when the same metric lives in three different tools
• Contract and vendor management overhead
• Security permissioning across dozens of separate identity systems
• Compliance reviews that multiply with every new vendor
• Ongoing maintenance and upgrades
• Fragmented customer and operational data that undermines decision-making

Industry research from Productiv, Zylo, and Flexera in 2025 consistently shows that enterprises use only 40–60% of the SaaS licenses they pay for. The rest sit idle, forgotten, or duplicated. For a company spending $50 million a year on software, that gap is not a rounding error.

The Spreadsheet Warning Sign

Here is one of the clearest signals that a company has an integration problem rather than a software shortage:

If a company owns an expensive CRM, a modern ERP, analytics platforms, project management tools, and operational software—but employees still export CSV files and combine everything in Excel to answer basic business questions—the technology stack is not doing its job.

That spreadsheet is telling leadership something important. It’s not evidence that employees lack tools. It’s evidence that the tools they already have aren’t connected. Every manual export is a symptom of fragmented data, and every merged spreadsheet is a hidden risk to accuracy, security, and speed.

When a CFO asks for revenue by region and the answer requires two analysts and four days of copy-paste work, the problem isn’t reporting. It’s architecture.

Consolidating Everything Is Not the Answer

It would be tempting to conclude that the solution is to cut aggressively and standardize on as few platforms as possible. That approach usually creates new problems.

Software rationalization works best when leadership evaluates each application against four possible decisions:

1. Keep – the platform provides unique, strategic value that no other tool replicates.
2. Consolidate – multiple tools perform substantially the same function, and one can absorb the others.
3. Integrate – different systems are all necessary, but they need to exchange information automatically instead of through manual work.
4. Replace, Modernize, or Custom Build – an existing application no longer supports an important business workflow efficiently.

Custom software should not be the automatic answer. Neither should consolidation. The right decision depends on what the business actually needs the technology to do.

Consolidate vs. Integrate vs. Custom Development

A simple framework helps executives cut through the noise:

• If capabilities overlap → Consolidate. Two CRMs or three project management tools rarely add value. Pick one and migrate.
• If valuable systems cannot communicate → Integrate. Build APIs or use integration platforms so data flows automatically between the tools you’re keeping.
• If a platform is outdated but strategically important → Modernize. Legacy software modernization or cloud modernization can preserve institutional value without a rip-and-replace project.
• If a unique business workflow cannot be supported by any available product → Consider custom development. This is where custom operational platforms or purpose-built web applications earn their keep.

Most enterprises need a mix of all four. The mistake is applying one strategy to every situation.

Questions Leadership Should Ask Before Renewing Another Software Contract

Before the next renewal or new subscription, leadership teams should be able to answer:

• How many employees actively use this platform?
• Which features are actually being used—and which are ignored?
• Do we already own another system with the same functionality?
• What would happen operationally if this platform disappeared tomorrow?
• Does it eliminate manual work, or does it create more of it?
• What other applications depend on it?
• Does it create another separate source of company data?
• Are employees copying information from this system into another one?
• Would an integration solve the problem without replacing the software?

If leadership cannot answer these questions confidently, the organization is not managing its software portfolio. It is being managed by it.

Why This Matters More in 2026

Several trends have converged to make enterprise software consolidation a boardroom-level topic this year:

• SaaS spending continues to grow faster than IT budgets
• Boards are demanding clearer ROI from technology investments
• Security teams are pushing to reduce vendor sprawl and attack surface
• Data fragmentation is limiting the value of AI and analytics initiatives
• Vendor management complexity is straining procurement and legal teams
• Operational efficiency pressure is intensifying across every industry

At the same time, AI is exposing a hard truth: AI models perform only as well as the data feeding them. Enterprises that have their customer, operational, and financial data scattered across 40 disconnected platforms cannot fully benefit from AI—no matter how much they spend on it.

That realization alone is prompting many CIOs and CFOs to revisit their entire technology stack.

A Familiar Scenario

Consider a mid-sized enterprise running:

• A CRM for the sales team
• A marketing automation platform
• A customer support tool
• Two project management platforms across different departments
• A cloud analytics tool
• A legacy operational system that finance and operations still depend on
• Dozens of internal spreadsheets that quietly hold the business together

Each product is individually useful. Combined, they create a complicated environment where customer data lives in three places, reports don’t reconcile, and employees spend hours moving information between systems.

Applying the framework, leadership might decide:

• Keep the CRM—it’s central to revenue operations.
• Consolidate the two project management platforms into one.
• Integrate marketing automation, support, and the CRM so customer data flows automatically.
• Modernize the legacy operational system with a cloud-based front end rather than replacing it outright.
• Replace the spreadsheet-based reporting with a proper analytics workflow connected to real data sources.

The outcome isn’t fewer tools for the sake of fewer tools. It’s a stack that reflects how the business actually operates.

The Bigger Message

The next stage of digital transformation may be less about adding software and more about making existing technology work together.

Software consolidation isn’t about having the fewest applications. It’s about removing unnecessary complexity while protecting the systems that genuinely create business value.

Organizations that go through this exercise often discover something important: not every issue can be solved by cancelling a subscription. Some problems require application integrations, API development, legacy modernization, cloud modernization, data integration, or a custom operational platform built around a workflow that no off-the-shelf product supports well.

That is where a technology partner becomes valuable—not to sell more software, but to help leadership determine whether the right answer is to integrate, modernize, consolidate, or build. Empirical Edge works with enterprise and growing SMB leadership teams on exactly those decisions: examining the technology stack as a whole, identifying where duplication is quietly draining resources, and building the integrations, modernizations, or custom applications that make the remaining investments actually pay off.

A Question Worth Asking

If your organization is paying for several systems that overlap, don’t communicate effectively, or still require employees to manually move information between them, it may be worth examining the technology stack before purchasing another platform.

The question every executive team should be sitting with right now is straightforward:

Are we solving business problems with our software—or are we paying to manage the complexity our software created?

If the answer isn’t clear, Empirical Edge can help evaluate whether consolidation, integration, modernization, or custom development makes the most business sense for your organization.