A podcast recap carrying one checkable sentence

SAP News Center published a recap of SAP's own podcast on September 24, 2026, written by Benedikt Gieger and Julia Kloppenburg. No release, no general availability date, no new product. The reason to read it is one sentence sitting inside a summary of sixteen episodes, and that sentence is aimed squarely at customers who are already live.

Uma Rani, president and chief product officer for SAP Cloud ERP Private, is quoted saying "The Autonomous Enterprise is not a future road map item; it is available now for customers on the 2025 and 2023 releases." Other attributions in the recap did not hold up when our desk checked the page a second time, so Rani is the only voice we are quoting from it and no customer is named here.

Read that slowly. Rani names two specific releases, the 2025 and the 2023, which makes the claim something a customer can carry into a meeting and press on. We cannot confirm it independently. This is SAP describing the content of its own releases, with nothing from outside SAP behind it.

Naming the 2023 release cuts against the usual assumption

Most customers carry one assumption into upgrade planning, which is that the interesting capability lives on the newest thing and everything older is in maintenance. That assumption quietly decides sequencing. It decides which programme gets funded this year and which conversation slides into the next budget round.

Rani's sentence contradicts that assumption on purpose. If autonomous capability genuinely sits in the 2023 release, an architect running S/4HANA on that release has something to evaluate before they have something to buy. The order of work changes. You test what you already own, then you write the business case for the move against what is actually missing, which is the same discipline we argued for when we wrote that clean core is a budget decision.

That is a lot of weight for one sentence in a vendor podcast recap to carry. We have no visibility into what is switched on in any particular system, and neither does anyone else writing about this. The claim is still useful, because it is specific enough to be tested, and a specific vendor claim beats a vague one every time.

What available now has covered before

The words available now are SAP's characterisation of its own release content, and that phrase has covered a lot of different realities over the years. Sometimes it means the code is in the release and a switch turns it on. Sometimes it means the capability exists and the configuration work to reach it is measured in months of a consultant's time.

Sometimes it means the capability is present and the entitlement is not, so the customer needs a licence they have never bought. Sometimes it depends on a component carrying its own subscription line. All of those situations can be described with the same two words, honestly, by a vendor employee who believes every word of it.

None of that makes Rani wrong. It makes the sentence incomplete, and the completion is work the customer has to do rather than work SAP will volunteer. Our checklist on reading a licensing change covers the same gap from the other side, where the wording shifts and the invoice follows.

Forty episodes is a messaging plan you can read early

The podcast itself is a modest thing. It launched on June 1, 2026 as a weekly series, sixteen episodes have published so far, and they run in three formats, one built around SAP itself, one around customers and one around industries. It sits inside the rest of SAP's Business AI messaging and nothing about the format is surprising.

The number that matters is the commitment. SAP says more than forty episodes are planned for the first year. A vendor booking that much airtime on a single theme has already decided what its next eighteen months of messaging will sound like, and it has published the decision. Every quarterly review and every roadmap session in that window will be framed by the same word.

Knowing that before you sit down for a multi-year renewal is worth something on its own. SAP Connect follows in early October, so the substantive material is days away rather than quarters. The recap is a warm-up, and the detail should arrive with the event.

The question to send your account team this week

The useful move with a claim of this kind is neither to swallow it nor to wave it away. Turn it into a question narrow enough that someone at SAP has to answer with specifics. Which capabilities does that sentence cover. In which modules. Under which entitlement, and whether that entitlement is one your organisation already holds.

Then the part that decides your plan. What would a customer sitting on the 2023 release have to do to use those capabilities this quarter, in configuration, in licensing and in consulting days. Ask for the answer in writing, by email, from the person who will be sitting across the table at renewal.

An answer naming real capabilities and real entitlements gives you something to plan against, and possibly a reason to resequence an upgrade you had already funded. An answer that repeats the phrase available now tells you what the sentence was there to do. Either way you learn something and the cost of asking is one email. Send it before SAP Connect, so you can hold the October material against an answer you already have on file.