Wednesday, April 29, 2026
Independent Technology Journalism  ·  Est. 2026
Business & Startups

The Quiet Collapse of the ERP Monolith in Late 2026

A $400 Million System Nobody Wanted to Touch The story circulating among enterprise architects this fall involves a mid-sized logistics company in the Netherlands—roughly 8,000 employees, $2...

The Quiet Collapse of the ERP Monolith in Late 2026

A $400 Million System Nobody Wanted to Touch

The story circulating among enterprise architects this fall involves a mid-sized logistics company in the Netherlands—roughly 8,000 employees, $2.1 billion in annual revenue—that spent seven years and somewhere north of $400 million implementing a full SAP S/4HANA suite. By the time the project finished, the business had changed so fundamentally that three of the five core modules were underutilized. The integration layer alone required a dedicated team of eighteen consultants to keep alive. The CFO reportedly asked whether they could "just start over."

That anecdote might be extreme, but the underlying dynamic isn't. Enterprise software is in the middle of a genuine structural break—not a gradual shift but an accelerating fragmentation of what we've long called the monolithic ERP model. And the players scrambling to fill the gap are doing so with wildly different bets about what enterprise IT will look like in 2028.

Composable ERP: The Architecture Argument Finally Has Teeth

The concept of "composable enterprise" has been floating around Gartner briefings since roughly 2020, but it mostly remained theoretical. What's changed in 2026 is that the tooling has caught up to the idea. Platforms built on event-driven microservices, using standards like AsyncAPI 3.0 and the CloudEvents 1.0 specification, now make it genuinely feasible for a large organization to stitch together best-of-breed point solutions without writing bespoke middleware for every connection.

Workday, for example, has made a notable pivot. After years of positioning itself as an HCM and finance platform, it quietly rebranded its integration framework as "Workday Orchestrate" in early Q2 2026—essentially conceding that customers want Workday as a data layer, not necessarily as the system of record for everything. Microsoft has done something similar with Dynamics 365, leaning hard into its Azure integration fabric and positioning Power Platform as the connective tissue between Dynamics modules and third-party applications. The strategy is less "use our whole stack" and more "at least use our runtime."

We asked Dr. Priya Sundaram, a principal research scientist at MIT's Center for Information Systems Research, how durable this trend really is. Her read was unambiguous: "The composable model wins in environments where business requirements change faster than software vendors can ship. That describes most large enterprises right now. The question isn't whether composability beats monolithic architecture on paper—it clearly does for agile orgs. The question is whether companies actually have the internal capability to manage the added operational complexity."

"The composable model wins in environments where business requirements change faster than software vendors can ship. That describes most large enterprises right now." — Dr. Priya Sundaram, Principal Research Scientist, MIT Center for Information Systems Research

AI Agents Are Breaking the Workflow Assumptions ERP Was Built On

Traditional ERP systems were architected around a fundamental assumption: humans initiate transactions. A purchasing manager approves a PO. A warehouse supervisor confirms a shipment. An accountant closes the books. The entire permission model, audit trail design, and UI paradigm flows from that assumption. AI agents don't fit.

What's happening now is that organizations are deploying autonomous agents—built on models like GPT-4o, Anthropic's Claude 3.5 Sonnet, and increasingly fine-tuned vertical models—that want to read from and write to ERP systems at machine speed, without a human in the loop for routine decisions. SAP's own data from their Sapphire conference in May 2026 showed that 34% of their enterprise customers had already connected at least one AI agent to their S/4HANA environment, mostly through unofficial API wrappers rather than native integrations. SAP called this "innovation." Their security team probably called it something else.

The OAuth 2.0 authorization framework, which underpins most enterprise API authentication, was not designed for non-human principal entities acting on delegated authority across multiple organizational boundaries. There are active working groups at the IETF trying to address this—RFC 9396 on Rich Authorization Requests is one piece—but enterprise software vendors are each implementing agent authentication in incompatible ways. Marcus Teller, director of enterprise architecture at Forrester Research, told us the fragmentation is already creating audit nightmares: "You have finance teams that can't reconstruct who—or what—approved a transaction, because the agent that executed it was credentialed under a service account owned by the IT team, not the business unit."

The Vendor Consolidation That Didn't Happen

Five years ago, the consensus prediction was that the enterprise software market would consolidate around three or four mega-platforms. It hasn't. Instead we've seen the opposite: a proliferation of specialized vendors, many of them well-funded and technically capable, fragmenting categories that SAP and Oracle used to own outright.

Category Legacy Incumbent Notable Challenger (2026) Challenger ARR (est.) Key Differentiator
Supply Chain Planning SAP IBP o9 Solutions $480M Graph-based demand modeling with real-time ML inference
Financial Close & Consolidation Oracle FCCS Pigment $210M Collaborative planning UI; sub-10-minute model recalc
HR & Workforce Management Workday HCM Rippling $1.1B Unified employee graph spanning HR, IT, finance
Procurement SAP Ariba Zip $175M Intake-to-procure UX with embedded spend intelligence
Keep reading
More from Verodate