
Sign up to save your podcasts
Or


Episode 33 argues that the SAP competitive landscape has fundamentally shifted – the real contest is no longer with Salesforce, Oracle, and Workday but with Anthropic and OpenAI for control of the enterprise intelligence layer – and Klein's Project Fuji reorganization, personally taking direct control of AI product development, is the clearest signal that SAP recognizes this new competitive reality. The episode covers the concluded EU antitrust investigation from July 9 which gives every SAP customer new contractual leverage on maintenance and licensing terms, the closed Dremio acquisition from July 6 that completes the open data architecture, and the countdown to Q2 earnings on July 23 which will determine whether Klein's AI capital allocation strategy is credible. The core provocation of the episode is an open letter to Walldorf asking SAP to open the Generative AI Hub to bring-your-own-model options including the Chinese open-weight tier – because if governance is genuinely the moat as SAP claims, then model choice should genuinely be open, and anything less is a curated menu wearing an open-architecture costume.
Michael und ich sprechen über exklusive Einblicke in die SAP und ihrer internen Entwicklungen, die Marktentwicklung und die Möglichkeiten mit AI
Fabian und ich sprechen in aller Tiefe und Breite zu dem „latest shit“ der SAP
Episode 30 launches the new monthly SAP Mythbusters format with six current myths systematically refuted by evidence – from the false claim that Joule is just another Copilot clone, through the misreading of the DSAG three-percent adoption figure, the unfounded promise of five-times-faster transformation, the outdated picture of SAP as a closed system, the inverted logic that AI-native competitors will displace SAP, to the mistaken framing of Company Memory as an admission of failure. The central thesis is that myths cost real money because they distort investment decisions, derail architecture choices, and embarrass CXOs in front of their boards when the evidence catches up months later – and the single most valuable habit a CXO can build in 2026 is asking one question before accepting any claim about SAP: where is the evidence? Volume 2 in four weeks combines three more current myths with three historical myths about SAP’s founding – plus a personal story I have never told publicly before, about the moment in 1999 when I swore I would never touch SAP again.
June 2026 has been the most consequential month of the year for SAP – the company secured a unique German BSI VS-NfD sovereignty authorization that no European competitor can match, is closing a long-running EU antitrust investigation through customer-favorable concessions, and continues executing the Sapphire roadmap with Joule Studio 2.0 rolling out and 50+ AI assistants reaching general availability. Yet the share price hit a fresh 52-week low at €134.38 on June 19 – down 34 percent year-to-date – after Oracle's $95 billion capex announcement triggered a sector-wide repricing of enterprise software margins and Goldman Sachs trimmed SAP's second-half gross margin forecast to 72.8 percent. The gap between SAP's strategic execution and the market's perception is now at its widest point of the year, and the next inflection moment is the Q2 earnings release – CXOs who read the architecture rather than the ticker have a once-in-a-decade negotiating moment to act on EU antitrust remedies, sovereign cloud positioning, and AI adoption strategy before the broader market recognizes what the fundamentals are already showing.
Sources and Show Notes
On the productivity gap and the perception-versus-reality problem in AI-assisted coding:
On DORA research and organizational productivity:
On quality degradation and the AI engineering paradox:
On SAP-specific Joule for Developers measured impact:
On industry-wide AI coding adoption and productivity benchmarks:
On SAP's RISE migration efficiency claims (Sapphire 2026):
Three weeks after Sapphire, SAP has clawed back above €150 with BlackRock taking a 3% institutional stake and Goldman Sachs, Barclays, BMO, Jefferies, UBS, and TD Cowen all reiterating buy ratings – Jefferies framing Sapphire as "a logical evolution," which validates the Episode 24 thesis that SAP did not pivot but confirmed a five-year trajectory. The execution machine is real: JPMorgan migrating its general ledger to SAP, 60% of new RISE deployments running on Microsoft Azure, the n8n acquisition doubling that company's valuation to $5.2 billion, and Claude embedded as the primary reasoning engine across SAP's portfolio – while EY won the SAP Business AI Customer Adoption Award, signaling that adoption-at-scale is now the dominant partner discipline. But the API policy remains the single unresolved strategic vulnerability – Klein's verbal reassurances are not contractually binding, DSAG continues to push for transition time and fair-use clarity, and competitors like ServiceNow and Salesforce are exploiting the gap by positioning themselves as the open, neutral governance layers SAP refuses to be.
Armin and I speak about the latest SAPPHIRE 2026 News, current SAP Developments
Saskia und ich sprechen über die aktuellen Entwicklungen, wie Transformationen in die Organisation getragen werden müssen um erfolgreich zu sein
SAP unveiled the Autonomous Enterprise at Sapphire 2026 with five concrete pillars: a unified Business AI Platform anchored by one Knowledge Graph, a live Autonomous Suite with 50+ assistants and 200+ agents, Joule Work as the reimagined UX that turns the underlying modules into invisible infrastructure, a €100 million partner fund combined with 35% agent-led migration savings, and a power partnership slate spanning Anthropic, AWS, Google Cloud, Microsoft, NVIDIA, Palantir, and Accenture. The hybrid agent story is the most strategically important news for the broader installed base – ECC and on-prem customers can now generate AI value through three free Joule assistants under RISE while modernizing in parallel, removing the biggest CXO objection to AI investment and unlocking ARR previously gated by migration timelines. The architecture is the strongest SAP has presented in a decade and represents the logical next step in a five-year trajectory – but the unresolved API policy contradicts the openness narrative and remains the single strategic vulnerability that ServiceNow, Salesforce, and the hyperscalers will exploit unless Klein fixes it publicly, in writing, with grandfathering and transparent fair-use rules.
From the publisher's feed