When SAP announced Business AI Platform at Sapphire in May, many filed it under rebrand and moved on. Big keynote, new name, roadmap that plays out over years.
Then the news about Michael Ameling came. Chief Product Officer for SAP BTP, and a member of SAP’s Extended Board. He isn’t moving into the new structure. He’s leaving the company. The man whose job title had “BTP” in it is gone, at the exact moment BTP gets folded into something bigger.
Companies rename products all the time. They don’t usually lose the executive who ran the product in the same month. So I went back and looked properly at what had happened since May. Rather a lot, as it turns out, and all of it pointing the same way.
I work at an SAP partner, so this one lands on my desk too.
What happened
Effective 1 July 2026, SAP rebuilt its leadership around this shift.
Muhammad Alam, SAP’s Head of Product and Engineering, had already decided not to renew his contract when it ends in spring 2027, for personal reasons. He stays on the Executive Board until then and keeps advising Klein on AI strategy. So what moved was operational control, not Alam. Klein handed parts of his responsibilities over early and split the Product and Engineering organisation into two pieces.
One piece is a new board area for Business AI Platform and the CTO organisation, led by Philipp Herzig. It pulls together Data and Analytics, Business Transformation Management, Platform and AI, and a large chunk of the old BTP organisation. One leader, one roadmap.
The other piece is a brand new Autonomous Suite organisation under Manoj Swaminathan, covering Finance and Spend Management, Supply Chain, HCM, Customer Experience, and Cloud ERP Private.
There’s a third piece too, smaller and less discussed. A new Industrial AI segment now sits with COO Sebastian Steinhäuser. It’s not part of the platform-versus-suite split, which is exactly why I’d watch it. Manufacturing and industry-specific AI getting carved out on its own suggests SAP doesn’t think one org can hold both the horizontal platform bet and the vertical industry one.
Ameling isn’t the only one going, either. Dan Beck, Chief Product Officer for SuccessFactors, is leaving with Siva Sundaresan replacing him, and Etosha Thurman, Co-Business Lead and Chief Marketing Officer for Finance and Spend Management, is out too. That changes how you should read the Ameling news, and I’d rather say so than leave it out. This isn’t one executive making a personal call. It’s a wave, and his happens to break exactly where the platform got renamed.
The shape of that split is the bit I’d sit with. When SAP had to divide its biggest organisation, the line it chose was platform versus autonomous suite. Not applications versus infrastructure. Not cloud versus on-premise. The exact two halves of the Sapphire announcement.
Then, on 30 June, quietly, SAP renamed the partner competency too. If your organisation held the SAP BTP competency, it now holds the SAP Business AI Platform competency. Automatically!
Quick detour if competencies aren’t your world. A competency is how SAP formally recognises that a partner organisation is good at something, at three tiers: Essential, Advanced and Expert. Specializations sit underneath as the building blocks, earned at product level through certified people and delivered projects. Enough of those at enough depth adds up to a competency.
One thing people get wrong. The competency is an organisation badge, not a personal one. The certifications you sit count toward your employer’s standing, and they stay on your record. Two different assets, and only one of them is yours. For the partner it’s commercial rather than decorative. Competencies feed partner tiers, co-selling, and which opportunities SAP thinks of you for.
What’s actually inside the new competency
SAP ran a partner session on 7 August 2026 called Road to SAP Business AI Platform expert competency. Between that and what’s already published, the shape under the new name is clear enough.
The SAP Business AI Platform competency holds four specializations. Application Development and Automation. Database and Data Management. Integration. Artificial Intelligence Foundation.
Read that list again. Three of them are the BTP you already know. The fourth is the bet.
And it’s not just an addition. The old BTP competency covered application development, integration, data and analytics. Analytics has moved out into its own SAP Business Data Cloud competency. Artificial Intelligence Foundation has moved in. One out, one in, and the one that came in is the one the whole strategy is named after.
The numbers tell you more than the tier names do. Essential wants three trained solution consultants and one delivered project in a single specialization, which most established partners already clear. Advanced steps up to five consultants, three delivered projects and two specializations. Expert is a different conversation: ten consultants, five delivered projects, all four specializations covered, five solution architects, and a partner solution built on BAIP.
That last requirement is the one I keep coming back to. To hold Expert you have to have shipped something on the platform. Not staffed it, not trained for it. Shipped it.
So has the bar moved yet? Partly, and unevenly. SAP’s June announcement framed the rename as a label change, with existing holders keeping their status, tiers and specializations. But going forward, it would be weighted more heavily toward data and AI. Both things seem to be true depending on when you last requalified.
What’s clearer is what’s still coming. In October, further specialization structure and product coverage changes land. In January 2027, new knowledge and proficiency requirements arrive, with safeguarding periods so nobody falls off a cliff overnight.
The order this happened in
Line up the dates and the direction is obvious.
- May 2026Sapphire, Orlando. SAP announces Business AI Platform and the Autonomous Enterprise.
- 30 June 2026The partner competency is renamed to match.
- 1 July 2026The board areas are redrawn to match. Herzig takes platform, Swaminathan takes the suite.
- You are here
- October 2026Specialization structures and product coverage change to match.
- January 2027Knowledge and proficiency requirements change to match.
Renames don’t work in that order. A marketing decision generally doesn’t reach into the Executive Board’s reporting lines a few weeks later, and it certainly doesn’t rewrite what partners are certified against. This ran the other way round. SAP decided what it wants to be, and everything since has been the company rearranging itself to fit. BTP didn’t get a new name. It got a new place in the hierarchy, and the name followed.
What I think it means
So the shift is real. The question worth more of your time is whether the bet underneath it is right.
For years the story was the Intelligent Enterprise. Better data, so humans make better decisions. The new bet is the Autonomous Enterprise: agents that carry the work through to completion themselves, inside the same controls a human would have to work within. BTP, the platform most of us built our careers around, becomes a piece inside SAP Business AI Platform rather than the foundation itself.
That’s why the name changed at all. BAIP is BTP repositioned as one layer inside a stack built to run agents.
Here’s my honest read. I don’t think the vision is wrong, exactly. I think it’s early. “Agents that carry the work through to completion” sounds great in a keynote and terrifying in a change advisory board meeting. Every BTP implementation I’ve been near has lived or died on governance, on knowing exactly who touched what and why. SAP is betting the market will trust agents with that same accountability before the tooling has proven it can hold up under audit. I think that bet pays off eventually. I don’t think it pays off on SAP’s timeline.
The certification list underneath the new competency backs that up. Ten certifications mapped for solution consultants. CAP, ABAP Cloud, SAP Build, Fiori, BTP administration, HANA database and data engineering, security, Integration Suite. Then one AI certification, Generative AI Developer, sitting on its own under AI Foundation. And the solution architect route is still called Becoming an SAP BTP Solution Architect. The code is still P_BTPA.
I’d read that as a timing signal rather than a gotcha. The strategy moved faster than the paperwork behind it, which is normal, and it’s roughly why I said early rather than wrong.
Which brings me to the part that touches you. Is your expertise ready for what AI Foundation asks for, or only for what BTP used to cover?
I’m not waiting for October to find out. Not because the scope is published, but because the gap I’d expect is specific and predictable. Heavy on integration and extension work, light on agent design and AI governance. That’s the shape of most BTP practices I know. You don’t need SAP to publish anything to work out which half of your team needs the runway more.
What to do about it
If this were cosmetic you could ignore it. It isn’t. The vision behind it has already moved reporting lines, job titles and certifications, and specializations are next. But the right move isn’t the same for everyone. It depends on where you sit.
If you’re a partner or consultant. You can audit yourself today. Count your trained consultants and delivered projects per specialization against the tier you claim, and be honest about the AI Foundation column specifically. My guess is most BTP practices will find three columns healthy and one close to empty. Then send your PDM one message asking what the October changes mean for your track. SAP’s own guidance in the competency announcement is to engage your Partner Development Manager as details release, and your PDM will know things before they’re public. Worth checking your competency status yourself too, rather than assuming the automatic rename caught everything. The easiest way to check this is log in to me.sap.com, go to Partnership, and look at your competencies. Takes two minutes and it’s better to find a gap yourself than have a customer find it for you.
If you’re an architect or developer. Don’t wait for the specialization structure to tell you where you stand. If your BTP work leaned on integration and extensions and stayed light on AI and agents, that gap is already there. October just makes it visible. Better to see it yourself than have a customer point it out. The Architecting the Autonomous Enterprise webinar series is the most useful free thing I’ve seen aimed squarely at this, and I’ve said more about it below.
If you’re leading a team. This is a staffing question before it’s a training question. Look at who on your bench is BTP-deep and AI-shallow, and be honest about how many billable conversations that combination can still support past January.
Then start now, rather than waiting for the tooling. Joule Studio isn’t generally available, and there’s an obvious temptation to park all of this until it is. Don’t. The transferable part is fluency, not the product. How you scope a task narrow enough for an agent to handle, where you put the human check, what you do when it confidently returns the wrong answer. Your team can learn that on whatever agent tooling they can get their hands on today, SAP or not, and carry it straight across when Joule Studio lands. The tool takes a fortnight to learn. The judgement doesn’t.
If you’re independent or between roles. Reasonable moment to specialise early, before the market fills up with people who waited for January to move. You don’t need a partner organisation behind you to start either. Almost everything worth working through right now is open to anyone, and the where to learn section below has the specifics.
Where to learn
A quick word on Joule Studio 2.0 first, because it’s where most of the AI Foundation work will eventually happen and people keep asking me how to get on it.
It isn’t generally available yet. A good number of customers and partners are already building on it through Early Adopter Care. My guess on timing is around TechEd in October, possibly slightly before, though that’s a read rather than anything SAP has committed to. If you want in before then, Early Adopter Care is the route, and it’s more self-service than people assume. It runs off SAP’s Customer Influence site. Log in with your SAP account, browse the open projects, register against the one you want. You’ll need a valid licence and maintenance contract behind you, and registration windows only stay open for the first few months after a release, so check rather than assume. You get a dedicated SAP coach through the implementation, which is the bit that makes it worth doing.
Also, Generative AI hub is available and the AI Foundation specialization is built on it, so that’s where the hands-on hours count today.
SAP is also running a webinar series called Architecting the Autonomous Enterprise, for architects, by architects. It covers Joule Work, the Autonomous Suite, the Business AI Platform, Knowledge Graph, agents and governance, which is close to a map of what AI Foundation is going to expect of you.
The Asia edition starts on 24 August 2026 and runs seven sessions through to 13 October, so there’s still time to register. Worth checking the clock before you commit though. 8:00 Berlin means 7:00 in the UK, 11:30 in Bangalore, 14:00 in Singapore, 16:00 in Sydney. If that doesn’t work, the European run has already finished and the slides and recordings are posted. All of it is free and open to anyone.
Gaurish Dessai, who I recorded the Sapphire episode with, is on the panel and is the reason this landed on my radar.
Then there are SAP’s own learning journeys. Positioning SAP Business AI Platform is open to everyone and the right place to start. If you’re a partner, two more are worth your time: Positioning the Autonomous Enterprise and Positioning AI in the Autonomous Enterprise, both partner-exclusive, both with certifications attached. I’d go there before any third-party course, since the fastest-moving material comes from SAP first and everyone else second.
What I keep watching
Michael Ameling’s exit is the bit I keep coming back to. Not because one departure changes anything on its own, but because of what had to be true for it to land in the same month as the rename.
SAP has moved its org chart, its job titles and its partner certifications to fit a bet it hasn’t proven yet. I still think that bet is early. That isn’t a reason to wait. October and January are on the calendar either way, and they arrive whether or not the tooling is ready.
Want to talk through what this means for your own roadmap? Book a call, or email me at vik@modishtech.co.uk. I read every message.