AI Threat Assessment · 27 May 2026

SAP

Enterprise Software
STILL BREATHING
3.8/ 10

SAP built the most successful vendor lock-in operation in software history — 440,000 customers running mission-critical ERP systems so deeply embedded that migrating feels like performing open-heart surgery on a running patient. The beautiful irony is that their greatest achievement — making themselves impossible to leave — is also what makes them impossible to modernize, turning every AI integration into an archaeological expedition through 50 years of ABAP code and German engineering philosophy.

Business Model
4.5
Automation Risk
5.0
Moat Strength
2.5
Adaptability
4.5
Need Survival
3.0
AI Threat Level
BUSINESS MODEL REPLACEABILITY

SAP's core proposition is 'we are the system of record for everything important' — which remains true until Claude can read invoices, process payroll, and handle compliance workflows without needing a €2 million implementation project. The data stays; the complexity tax that funds Walldorf is under review.

4.5
WORKFORCE AUTOMATION RISK

ABAP developers, functional consultants, and the small army of systems integrators who speak SAP's peculiar German-accented English are all watching ChatGPT generate cleaner code in 30 seconds than most SAP customizations achieve in 30 sprints.

5.0
MOAT STRENGTH

This is the textbook example of structural switching costs done right — decades of financial data, compliance history, and workflow dependencies so deep that even mentioning migration makes CFOs break out in cold sweats. The moat isn't just wide; it's lined with auditors and backed by German engineering precision that treats backward compatibility as a religious obligation.

2.5
AI ADAPTABILITY SIGNALS

SAP's Business AI strategy involves bolting Joule onto existing workflows while carefully avoiding any mention of the elephant in the room — that most of what SAP charges for is complexity management that AI makes unnecessary. They're building AI tools to make SAP easier to use instead of asking whether SAP needs to exist.

4.5
WILL THE NEED SURVIVE AI?

Enterprise resource planning survives; the part where it requires a PhD in SAP-ology and a consulting army doesn't. AI doesn't eliminate the need to track inventory and process payroll — it just questions why doing so requires learning a programming language invented in Weinheim.

3.0
Verdict

SAP won't die — it will just become the COBOL of the 2030s, running critical systems that everyone agrees should be replaced but nobody can afford to migrate. The ultimate German engineering achievement: building software so essential and so painful that customers pay billions annually just to avoid the conversation about leaving.

Scores are based on public information and AI analysis. This is an affectionate roast, not a financial assessment. The best companies use this as a mirror, not a verdict.

Roast another →