At Sapphire in Orlando this May, SAP spent its opening day launching AI brands, and its main ERP products barely came up. When S/4HANA did get a mention, it was mostly as the road you travel to reach the AI. Christian Klein still told the room that the ERP is “the trusted system of record.” He’s right about that. But the morning belonged to Joule Work, a dashboard for running every ERP operation through an assistant instead of through the applications themselves.1
The screen is the lock
Nobody in accounts payable loves the vendor invoice journal. What they love is knowing where everything on it lives, after years of finding out the hard way, and that knowledge is the real switching cost in an ERP replacement, whatever the business case says. The business case talks about licensing and hosting. The fight that stalls the project is about retraining a few thousand people who already know where the buttons are. “Nobody ever got fired for buying IBM” was never really about IBM.2 It was about not having to explain a new screen to everyone in the building.
Strangle it one form at a time
Martin Fowler named the strangler fig pattern after a vine he saw in the Queensland rain forest, one that seeds high in a host tree and grows down around it until the tree is no longer needed.3 Developers have used it for more than two decades to replace old code without a big-bang cutover. Wrap the legacy system and route one function at a time to something new until the old thing does nothing. No rewrite to approve. Now point it at the user interface instead of the code.
Start with the screens people touch least and resent most. PO approvals and vendor lookups are the obvious first candidates, along with expense entry and timesheets. Replace each one with a sentence: “approve the Henderson PO,” or “what bank details do we have for Contoso Supplies.” The agent does what the form did, under the same security role, and the manager who opens that approval screen twice a month never has to remember where the button went. Every screen you retire this way is one nobody gets retrained on at the next upgrade. And in D365 F&O this isn’t speculative: Microsoft’s ERP MCP server includes form tools that let an agent work the application “like a human with the same security access.”4
Keep doing that and something shifts. Users stop knowing, or caring, which ERP sits behind the agent, because to them the system is the thing they type to. At that point D365 or S/4HANA becomes plumbing, and plumbing gets replaced when it’s cheaper to replace, not when a few thousand people agree to it.
The vendors already know
This is why every ERP vendor is racing to own the chat box. SAP’s entry is Joule Work, with general availability planned for Q4 2026, plus Joule Studio for building agents that reach tools over MCP and hand work to third-party agents.5 Microsoft’s runs through Copilot and that same MCP server. Neither of them is doing this out of generosity. If the conversation is where the user lives, then the conversation is the new lock, and whoever owns it decides how hard it is for you to swap what sits underneath.
So the lock-in doesn’t disappear. It moves into your agent configurations and into the prompts your power users have tuned until the thing finally understands what “the Chicago account” means, all of it living on someone’s platform.
Where it leaks
Joel Spolsky argued back in 2002 that every non-trivial abstraction leaks to some degree,6 and an AI front end over an ERP is about as non-trivial as abstractions get. The agent can hide where the button is. It can’t hide that your new system calculates available inventory differently or posts at a different point in the process. Users won’t complain about the screen anymore. They’ll complain that the numbers moved. And they’ll be right, because the training you thought you skipped comes back as “why did the agent do that?”
Your heaviest users won’t come quietly either. The AP clerk keying a stack of invoices and the warehouse worker with a scanner are faster on forms than they will ever be in a chat window, so let them keep the forms. My bet is they’re a minority of your headcount. The argument was never that every screen dies, only that most of them can, and the survivors stop being the reason you can’t touch the system behind them.
None of this works on an ERP that is merely interfaced, the kind where the agent gets a handful of APIs and the rest of the system stays locked behind the forms. It needs one that is actually headless, where anything a user can do, an agent can do too. Microsoft’s current answer is to let the agent operate the forms directly, which keeps every retired screen loading in the background with nobody looking at it, and I still haven’t decided whether that counts.
Notes
1 David Essex, “SAP unveils agentic AI tools to partially automate ERP suite,” Informa TechTarget, May 12, 2026. Coverage of opening day at SAP Sapphire in Orlando, including how rarely S/4HANA came up, Christian Klein’s keynote remark, and the description of Joule Work. TechTarget
2 An old procurement adage from IBM’s mainframe era. Nobody seems sure who said it first, so treat the attribution as folklore.
3 Martin Fowler, “Strangler Fig Application,” martinfowler.com. First posted June 29, 2004 as “Strangler Application” and renamed in 2019 to keep the botanical origin in view. martinfowler.com
4 Microsoft Learn, “Use Model Context Protocol for finance and operations apps.” The Dynamics 365 ERP MCP server is in preview, requires version 10.0.47 or later, and its form tools let an agent act with the same security access as the user it runs as. Microsoft Learn
5 SAP, “SAP Sapphire 2026 Innovation News Guide.” Covers Joule Work, Joule Studio support for MCP and Agent2Agent, and the planned Q4 2026 general availability. SAP
6 Joel Spolsky, “The Law of Leaky Abstractions,” Joel on Software, November 11, 2002. Joel on Software
My book, Gamifying the Enterprise: Game Mechanics for Continuous Proficiency, is on Amazon. All my books are on my Amazon author page.
The AD&D365 configuration guides are at adnd365.com/start.
Connect with me on LinkedIn.
