For most of SAP’s history, the company has sold applications. The consulting model that grew around that architecture was fundamentally about configuring those applications to match how a client’s business worked. Sapphire 2026 just marked a departure from that model that goes a little deeper than previous product cycles.

SAP introduced the SAP Business AI Platform as a consolidation of BTP, SAP Business Data Cloud, and SAP Business AI into a single governed environment, structured around three layers: context, build, and governance.

Christian Klein’s argument for SAP’s new competitive position rests on 50 years of process and domain knowledge, compliance controls, and company-specific configurations, now being infused into AI agents that can navigate thousands of business processes and verify identity and access authorizations before returning any output.

SAP is making the case that it now owns the layer where enterprise AI becomes trustworthy, and that no hyperscaler or AI-native vendor can really replicate that without decades of process depth.

The question this raises for practitioners is whether SAP is still primarily selling applications, or whether it is trying to own the control layer that sits above applications, data, process logic, and execution.

The answer from Sapphire is both, but the strategy has shifted decisively toward control. 

For consultants and consultancies, that redraws the map of where expertise becomes valuable.

The Agent Hub: Scope and Current State

The SAP AI Agent Hub is a vendor-agnostic command centre for inventorying and governing AI agents, LLMs, and Model Context Protocol servers, covering every agent regardless of who built it, with two of its six capabilities generally available now and four scheduled for Q3 2026.

The Hub sits within SAP LeanIX Application Portfolio Management, auto-discovers agents through integrations with SAP, Google, and Microsoft repositories, captures risk ratings and compliance mappings per agent, governs the agent lifecycle from proposed through to decommissioned, and makes approved agents discoverable to business users through a governed portal.

The Q3 additions include agent identity management via SAP Cloud Identity Services, AI observability with session-level monitoring, and performance monitoring tied to business KPIs.

Sitting beneath the Hub’s governance controls is NVIDIA OpenShell, an open-source runtime being embedded into SAP Business AI Platform, with SAP engineers co-developing it alongside NVIDIA, providing isolated execution environments and policy enforcement at the filesystem and network layers.

Joule Studio governs whether an agent action should occur from a business policy perspective, while OpenShell governs whether it can occur at the infrastructure level. Both layers are necessary because application-level controls alone cannot contain an agent that has access to shells, files, networks, and APIs.

SAP’s advantage is that it already maps the architecture through LeanIX, processes through Signavio, identities through Cloud Identity Services, and the org chart through SuccessFactors: components that any competing governance tool would need to add on from outside.

That integration depth is the reason the Hub is worth understanding as a platform rather than a dashboard.

The Regulatory Function

The EU AI Act reaches full enforcement in August 2026, and its scope covers AI systems operating in Finance, HR, and Procurement: which is precisely where SAP’s Autonomous Suite deploys agents.

Agents operating in these environments must have documented audit trails, verifiable access controls, human oversight mechanisms, and rapid revocation capability: and if an organization cannot trace an agent’s actions or demonstrate control over its authority, it cannot produce the evidence a regulator requires.

Penalties under Article 99 reach up to €35 million or 7% of global annual turnover (whichever is higher) for prohibited AI practices, and up to €15 million or 3% for high-risk system violations.

For any client with meaningful EU market exposure (which covers the overwhelming majority of SAP’s customer base) those figures make governance design a board-level risk conversation.

The Act applies extraterritorially. UK-based consultancies serving DACH clients, and US-based consultancies with EU-facing customers, are inside the compliance perimeter.

It also requires a monitoring system that captures all inputs, outputs, and relevant metadata to provide a transparent trail for internal reviews and regulatory requests, with continuous monitoring.

That requirement creates a standing operational workload that a go-live project cannot satisfy and then close. The governance work does not end at go-live. It begins there.

Agent Governance as a Delivery Workstream

SAP embeds the audit infrastructure and governance tooling, but enterprises must define their own approval matrices, fallback procedures, and accuracy thresholds.

That design work in determining what an agent is authorized to do autonomously, at what confidence threshold it escalates, who in the business holds revocation authority, and what the exception handling path looks like, is professional services work. It requires process knowledge, stakeholder management, and enough regulatory literacy to produce documentation that would survive an audit.

Configuring the Hub is a task; designing the governance model is a workstream.

Decision boundary modeling requires explicit definition of what the system may do on its own and when it must involve a person, and governance design becomes a formal stream of work that usually requires senior ownership because it affects multiple parts of the organization simultaneously.

In practice, this workstream sits uncomfortably across traditional project streams: it is not purely functional, not purely technical, and not purely compliance. That ambiguity is why clients need external expertise to own it, and why the consultants who can do so will command a premium.

The handover deliverable from a governance workstream is also distinct from a standard configuration document.

A governance handover includes a documented decision boundary framework, an agent registry with risk classifications, audit trail specifications by agent type, exception escalation workflows, and an operational monitoring runbook the client’s team can use with confidence.

Producing that package requires the consultant to understand both the technical capabilities of the Hub and the specific regulatory and operational context of the client’s business.

What This Means for Consultancies

The commercial model question for consultancy leaders appears to be whether agent governance is a project workstream or a managed service. It needs to be both, priced and staffed accordingly.

SAP’s position is that the Agent Hub continuously tracks where agents create value and surfaces where they can deliver more, because AI needs to remain accountable for outcomes in addition to uptime. That is an ongoing operational function.

Consultancies that scope governance purely as a phase within an implementation project will deliver something technically complete but commercially incomplete: handing over a monitoring responsibility that the client’s team is not resourced to deal with.

The firms building recurring governance review cycles, quarterly KPI drift assessments, and annual regulatory update reviews into their service catalogue are providing the engagement continuity that one-off projects cannot.

The differentiation question matters just as much as the service model question.

At Sapphire this year Rob Fisher (Global Head of Advisory at KPMG) said that KPMG has deployed Joule across 270,000 users internally, with 3,000 consultants already working with 20 agents on the platform, and is targeting $120 million in reduced contract leakage for one client engagement.

The value KPMG is capturing there is not Hub configuration (a competent BTP practice can configure the Hub). It is process authority, governance design, and outcome accountability delivered by people who understand the client’s procurement and legal processes well enough to define decision boundaries that are both operationally useful and legally defensible. That combination is the consulting layer that distinguishes professional services from activation support.

For boutique consultancies with deep functional expertise in S/4HANA Finance, SuccessFactors, or Supply Chain, the governance workstream aligns with that depth. 

A firm that understands period-end close can design governance parameters for a Financial Closing Agent that a generalist large firm cannot create based on a methodology template.

The governance question needs an owner and a plan before agent sprawl becomes agent risk: and clients in regulated industries will favor domain expertise over firm size when selecting that owner, particularly when the governance design comes with regulatory exposure.

SAP has committed €100 million to its partner ecosystem for agent development, with Joule Studio 2.0 available at no charge through year-end.

On staffing, the governance workstream requires a specific mix that most consultancies are not yet offering as a named team.

A senior functional consultant with regulatory literacy holds the design authority. A BTP or LeanIX-experienced architect handles the technical Hub configuration and integration with Cloud Identity Services. A change management specialist manages the client-side governance ownership transition.

That three-person core is deployable on most mid-market governance engagements, with compliance specialism brought in as needed for heavily regulated sectors. Sourcing that team configuration now is the practice investment with the shortest payback period available.

Career Strategy for Individual Consultants

The most useful thing a senior SAP consultant can do in response to the Agent Hub announcement is read it as a skills extension signal, not a retraining requirement.

The governance workstream rewards the capabilities that experienced SAP practitioners have already acquired: process depth, client-facing communication across business and IT audiences, and the ability to translate complex system behavior into terms that a CFO or compliance officer can approve and defend.

The consultant’s role in this area involves defining what a system is allowed to do: and that requires breadth, clarity, and comfort with responsibility over tool familiarity.

An S/4HANA Finance consultant who understands document splitting, substitution rules, and the audit requirements around financial posting already has the domain foundation for designing governance parameters on a cash management agent.

The additional skill required is the ability to frame those parameters as decision boundaries, document them in audit-ready form, and explain their regulatory basis to a client stakeholder.

The T-shaped profile that opens governance engagements has deep functional SAP expertise as its vertical, paired with working knowledge of the Agent Hub lifecycle framework, and knowledge of the EU AI Act risk classification model for SAP’s core process domains, and SAP Cloud Identity Services agent identity management as its horizontal.

Process depth without governance framework knowledge will produce governance designs that are operationally sound but technically incomplete. Governance framework knowledge without process depth will result in documentation that satisfies a checklist but fails in production when agent behavior meets real business complexity.

The Hub’s registry and lifecycle governance features are available now in SAP LeanIX: getting hands-on time through SAP Learning Hub or an Early Adopter Care environment is the starting point, prioritizing the features that are already generally available rather than waiting for the Q3 full release.

SAP’s updated certifications now use performance-based assessment formats incorporating practical Joule for Consultants scenarios, which means hands-on practice with the actual tooling is both the preparation and the proof. This also makes it easier to prove competence in application of these skills.

CVs and project summaries will benefit from shifting emphasis from tasks configured to decisions owned: describing how authority was distributed between people and systems, what governance artifacts were produced, and how escalation paths were designed gives hiring managers and clients the evidence of governance readiness that they require to make hiring decisions.

A governance artifact from a current or recent project (such as a decision boundary document, an exception escalation workflow, an agent risk classification) should accompany any certification on a profile, or be related during interviews, because it demonstrates applied judgement rather than just completed training.

Every large enterprise will eventually manage hundreds of agents from multiple vendors. The consultants who govern the first 20 agents in a client environment are the ones that client calls when the next 100 need governing.

The scarcity window for governance expertise is open now, and in SAP’s history, the specialists who moved early into S/4HANA and or BTP architecture set the rate benchmarks and career trajectories that the rest of the market spent years catching up with.

The Workstream That Was Missing

Every previous wave of SAP innovation created a gap between what the platform could do and what clients were equipped to govern.

S/4HANA created a clean core imperative that most clients underestimated until customization debt became a migration problem.

Cloud adoption created a security and integration governance gap that took years to close properly.

Agentic AI creates the same pattern, compressed into a much shorter timeline by regulatory enforcement that does not wait for organizations to catch up.

The Agent Hub is SAP’s acknowledgement that AI agent governance is not a feature but a discipline. And disciplines, in the SAP ecosystem, have always required specialists to make them happen inside client organizations.

If you are an SAP professional looking for a new role in the SAP ecosystem our team of dedicated recruitment consultants can match you with your ideal employer and negotiate a competitive compensation package for your extremely valuable skills, so join our exclusive community at IgniteSAP.

Share