A Board Email That Reorders Priorities
On July 2, 2026, SAP told staff in an executive-board email that it will freeze most new hiring and pause all non-AI business travel, redirecting the savings into what the company called a significant push into artificial intelligence. Going forward, SAP said it will exclusively focus new hiring on selected profiles only, mainly core AI roles, while also looking for ways to cut supplier spend. We read this less as routine belt-tightening and more as a deliberate reallocation of capital toward a single strategic bet. When a vendor of SAP's scale narrows hiring to AI profiles and halts everything else, it is telling its own organization, and its customers, exactly where the future budget will live.
The framing matters because SAP is not describing this as a cost crisis. It is describing it as a funding mechanism. The company insists the exercise is reskilling rather than layoffs, publicly committing to move existing staff into AI roles instead of showing them the door. That distinction will be tested over the coming quarters, but the intent is clear enough. SAP wants to convert the overhead of a traditional software business, travel budgets, generalist headcount and supplier contracts, into fuel for an AI-first operating model. For CIOs, the signal is that their strategic vendor is willing to disrupt its own cost structure to chase this transition, which raises the stakes on whether the resulting products actually land.
Project Fuji and a Leadership Reshuffle
The cost squeeze accompanies a significant leadership reshuffle. CEO Christian Klein has personally taken control of AI product development under an internal program dubbed Project Fuji, absorbing most of the responsibilities of product-and-engineering board member Muhammad Alam, who declined to renew his contract expiring March 2027. Industrial AI moves to COO Sebastian Steinhaeuser, while Thomas Saueressig became chief customer officer in a March reorganization that created a Customer Value Group. SAP will run an external search, focused on the US, for a new product lead. When a CEO inserts himself directly into product development, it concentrates accountability at the very top, which can accelerate decisions or expose the strategy to a single point of failure.
Analysts read the move as a statement about ownership. As Jason Andersen, VP and Principal Analyst at Moor Insights and Strategy, put it: "The shift in Christian's focus is to help drive what will be an equally big job of shifting SAP from a SaaS-first company to an AI-first company." That is the crux of Project Fuji. SAP spent years convincing customers to move from on-premise licenses to cloud subscriptions, and now it is asking them to absorb another platform shift while the first one is still in flight. We would note that concentrating this effort under the CEO makes the transformation legible internally, but it also means the market will judge the outcome as a personal bet by Klein rather than a distributed engineering achievement.
Strong Numbers, Weak Stock
The paradox in this story is that SAP is tightening its belt from a position of operational strength. Q1 2026 showed a 30 percent operating margin, its highest in 13 quarters, alongside 27 percent constant-currency cloud growth. Those are numbers most enterprise software vendors would celebrate. Yet SAP shares fell roughly 32 to 47 percent over the trailing year, trading around 138.92 euros on Xetra, well below the 161.16 euro average of its Q1 buyback. The disconnect between operating performance and market valuation is exactly the kind of pressure that pushes a management team to make bold structural moves rather than defend a steady-state business.
We think the share-price slide, rather than any weakness in the core business, is the real engine behind the urgency. Investors have re-rated legacy software franchises against a wave of fast-growing AI firms, and SAP's premium is no longer assured simply because its ERP systems sit at the center of global commerce. Freezing hiring and travel is a way to demonstrate discipline to the market while funding a growth narrative the market currently doubts. For technology leaders, the lesson is that even a highly profitable strategic supplier can feel compelled to reorganize aggressively when its valuation stops reflecting its fundamentals, and that turbulence inevitably reaches the roadmap.
The Cognite Loss in the Background
The reorganization did not happen in a vacuum. In late June, SAP reportedly lost the bid for industrial-AI vendor Cognite, which instead sold to Schneider Electric for 3.1 billion dollars. Losing a strategic acquisition days before announcing a hiring freeze and an AI reshuffle is an uncomfortable sequence, and it reinforces the sense that SAP is under real competitive pressure in industrial AI specifically. When a company cannot buy the capability it wants, it has to build it, and Project Fuji is at least partly an answer to that constraint. The competitive backdrop of fast-growing AI firms only sharpens the point.
Klein has been candid about how far he expects the transformation to go. "I'm not sure if here someone in two or three years will still code software," he said. "I don't expect to operate with a smaller work force, but with a very, very different work force." That is a striking admission from the leader of a company whose value rests on software engineering. It reframes the hiring freeze not as a temporary austerity measure but as the leading edge of a permanent change in what SAP employees will do. We would take Klein at his word that the workforce will be different, and we would watch closely whether the reskilling promise survives contact with the timeline he is describing.
What CIOs Should Actually Scrutinize
For CIOs, the temptation is to treat this as vendor housekeeping and move on. We would resist that. The more useful posture is skepticism about execution, echoed by Sanchit Vir Gogia, Chief Analyst at Greyhound Research, who cautioned that "SAP's reshuffle is best read as a signal about accountability, not as proof that the AI execution problem is already solved." A reorganization clarifies who is responsible. It does not deliver working AI features into your S/4HANA environment. Buyers should press SAP account teams for concrete roadmap commitments and delivery dates, not organizational charts, before assuming Project Fuji changes anything in their own deployments.
The deeper diligence sits in the contracts. Analysts urged scrutiny of contract language around AI model providers, data usage, opt-out rights and accountability boundaries rather than taking the reorganization at face value. As SAP embeds AI more deeply into its platform, customers need to know whose models are processing their data, whether that data trains external systems, how to opt out, and who is liable when an AI-driven process fails. Those questions are governance fundamentals, and they matter more, not less, when a vendor is moving this fast. Project Fuji may or may not succeed, but the CIOs who protect their data rights in the fine print will be the ones who benefit regardless of the outcome.
