Serious AI, Serious Process: An APAC SAP Reality Check After Appian World 2026

When Matt Calkins, CEO and Founder of Appian, took the stage at Appian World 2026, he reached for an unusually old metaphor to describe a new technology. The light bulb, he reminded the audience, was a breathtaking invention that did almost nothing for the economy until the electrical grid arrived a generation later. He argued that Agentic AI is in its light-bulb moment. Until enterprises build the grid consisting of the process, governance, and data fabric to carry it, most agents will keep flickering in proofs of concept.

That diagnosis lands with precision for SAP customers in the Asia-Pacific (APAC) region. Across Australia, Japan, India, Singapore, and the ASEAN economies, SAP S/4HANA migrations are mid-flight, SAP ECC’s 2027 mainstream maintenance deadline is closing in, and boards are asking why that AI line item hasn’t moved the P&L yet.

Highlights From Appian World 2026

Roughly three-quarters of Appian’s customer base, the company said on stage, is already using AI inside a process. That is a striking number and a useful contrast to the rest of the market.

As a result, the headline announcements pointed in one direction. Agents are only as good as the processes they live inside. Sessions by Sanat Joshi, Executive Vice President, Product and Innovations at Appian, on adaptive customer experiences; Michael Beckley, founder and CTO of Appian, on architecture deep dives; and the unveiling of MCP-style governed agent access all rest on a single thesis: agents need context, guardrails, and an orchestrator. Without those three, they hallucinate confidently into an organisation’s SAP system of record.

HBR Data Confirms the Gap

A Harvard Business Review study titled “What Drives AI Value,” commissioned with Appian, makes the same point with sharper numbers. According to the report, 92% of leaders agree that agents need rules-based guardrails. Only 48% have them in place. The report also flags an uncomfortable pattern that agentic AI is being eagerly applied to coding and marketing. At the same time, procurement, supply chain, and finance, which form a large chunk of SAP processes, remain largely untapped.

For APAC SAP teams, that gap is amplified by regulation. For instance, India’s DPDP Act, Australia’s Privacy Act reforms, Japan’s APPI updates, and Singapore’s Model AI Governance Framework are all tightening at the same time. An agent that drafts a marketing email is one thing. However, an agent that posts a journal entry, releases a payment, or modifies a purchase order touches SOX-equivalent controls, and APAC regulators are watching these developments.

Where This Gets Interesting for SAP Customers

Today, SAP Business Technology Platform (BTP), Joule, Build Process Automation, and Integration Suite have closed real gaps inside the SAP clean core. They are the right tool for customising a finance screen in SAP S/4HANA or grounding Joule in an organisation’s master data.

However, cross-system orchestration, the procurement workflow that touches SAP, Coupa, Workday, a SharePoint contract, and a regional bank API, is where most APAC SAP customers still rely on spreadsheets and email. That is the grid that Calkins referred to. Whether an organisation builds it inside SAP BTP alongside Appian, or with a different orchestration layer, is a sequencing decision worth making deliberately rather than by default.

The key takeaway from Appian World 2026 was that the agent conversation has moved past models and into plumbing and APAC SAP shops, where the plumbing will compound advantage faster than those still arguing about which LLM to license.

What This Means for Mastering SAP Insiders

Organisations should audit their AI grid before the next agent pilot. Map the top three cross-system processes where SAP is the system of record but not the orchestrator. These could include procure-to-pay, order-to-cash, and record-to-report. If those processes still live in spreadsheets and inboxes, no model upgrade will fix the outcome.

Close the 92/48 guardrail gap deliberately. The HBR findings should be used as a board-level checklist. For every agent that touches an SAP transaction, IT teams should document the rules-based guardrails, the human-in-the-loop checkpoints, and the audit trail before go-live, especially under APAC’s tightening privacy and AI regimes.

IT leaders should make the SAP BTP-versus-orchestration-layer decision deliberately. They must decide which workflows are SAP-clean and belong in SAP BTP/Joule, and which are genuinely cross-system and need a separate orchestration layer. Either answer is defensible, but drifting into both by accident is not.