Analytics Legends logoAI & Analytics Legends Sign inSign up
Guide

SAP AI architect: the decisions the build team cannot take alone

As of 2026-11-21

A SAP AI architect decides which layer of SAP's AI portfolio a use case belongs to, where its data comes from, what an agent may do, which regulation applies and who pays for each call. SAP groups the portfolio as the SAP Business AI Platform, announced at Sapphire in May 2026, in three pillars: Build, Contextualise and Reason, and Govern. On 7 October 2026 the Analytics Legends contract corpus held 62 postings whose titles combine an architect word with AI wording, 35 freelance and 27 permanent, while 95 named Joule, 87 of them permanent. The title is common; the content varies from one posting to the next.

Looking for a ? Cédric Mary, SAP AI & Analytics Architect & Team Lead, takes SAP Business AI, Joule and Business Data Cloud missions.

Choose the layer before the tool

Five placements cover most cases: a feature SAP ships inside an application, a standard Joule agent that is activated rather than built, a custom agent in Joule Studio, a custom application calling models through the generative AI hub, and a pro-code agent on BTP reached over A2A. Embedded scenarios in S/4HANA have their own promotion gate, separate from AI Core's deployment step. The first duty is to say which capabilities should not be built because SAP already ships them.

Two cautions apply. A standard agent's release status, whether beta, early adopter, restricted or generally available, is itself a contract condition. And SAP's figure of more than 200 agents announced in 2026 is a roadmap ceiling, not an availability count. For discovery, SAP catalogues over 240 pre-valued use cases on its Discovery Center; the architect filters them against data readiness and risk class instead of starting from a blank whiteboard. Fewer than five quick wins after two workshops usually means the filter was too narrow.

SAP's own reference: the AI Golden Path in the SAP Architecture Center

SAP publishes its architecture guidance for AI on the SAP Architecture Center. Its AI Golden Path, updated on 23 April 2026, calls itself the starting point for developing AI applications across the SAP ecosystem. It offers a technology decision tree across the agent, AI and data layers; a choice between agentic workflows, generative AI with large language models, classic machine learning and relational foundation models; and a use-case lifecycle running from explore and design to deliver, run and scale, evaluate and extend, with build guidance for Joule skills, AI agents, generative AI applications and document AI.

An SAP AI architect should be able to place each of the client's use cases on that tree and say where the design departs from it, and why. The reference describes options; it does not settle licence entitlement, the EU AI Act classification of a scenario or who pays for each call. Those decisions stay with the architect, and they are what the rest of this page is about.

Data and grounding: three paths, one common mistake

Datasphere grounds Joule in three different ways: navigational answers on Datasphere's own metadata, analytical insights over analytic models exposed through the catalogue, and Joule Studio agents anchored in the SAP Knowledge Graph. Document grounding on the vector store is a fourth, separate channel. Confusing them explains most tickets saying Joule does not know the client's data. A private, ungoverned view is invisible to Joule by design.

SAP's phrase AI-ready data bundles three problems: quality, semantics and lineage. Score them as three lines, each with its own owner. Zero-copy sharing of data products to Databricks or Snowflake solves duplication, not ambiguity or access control. On HANA Cloud a hybrid pattern is available: master data in the graph engine, transactions in SQL over data products, text through vectors. Do not confuse the SAP-managed Knowledge Graph with the HANA Cloud graph engine, the triple store you populate yourself.

Agents and protocols: smaller than the slide suggests

Default to one agent with three to five tools, and split into subagents or A2A peers only for a concrete isolation, ownership or reuse reason. A subagent shares its parent's guardrail profile; an A2A peer is a separate trust boundary with its own agent card, authentication and audit trail. The hop rule is simple: person to agent through the interface, agent to SAP data through MCP, agent to a foreign agent through A2A.

Two SAP constraints shape the design. SAP's API policy allows agentic use of SAP APIs only through endorsed routes; hosting an MCP server over business APIs is best done as an Integration Suite artefact, limited to 30 tools, rather than as a custom proxy. And approval design follows reversibility: confirm before irreversible writes, sample reversible high-volume work, and register every agent and server in the Agent Hub inventory.

Regulation: the classification is a design decision

The EU AI Act applies in stages. Transparency duties apply since 2 August 2026. The Digital Omnibus, in force since 27 July 2026, moved high-risk obligations to 2 December 2027 for Annex III systems and 2 August 2028 for Annex I. The architect's first scoping question is provider or deployer: building or repurposing an agent can make the customer a provider. Two SAP cases already reach Annex III: Joule used for performance or promotion decisions, and supplier scoring that feeds payment terms. Fines for most operator obligations reach EUR 15 million or 3 % of turnover.

The European Commission's impact assessment, as cited in our material, puts documentation at 200 to 800 person-days per high-risk system, with technical documentation alone at 60 to 120 days for a medium Joule agent integrated with S/4HANA and Datasphere. Existing ISO 27001 and SOC 2 certification cuts the lower bound by 30 to 40 %. Separately, ask three privacy questions per engagement: which model and region, whether masking covers the languages in use, and whether the contract restricts general R&D use of customer data. Not retained by the provider is a retention commitment, not a residency guarantee.

Cost: three layers, kept out of the day rate

SAP prices AI in three layers: Base AI included in eligible subscriptions, Premium AI paid in AI Units, and custom-built AI billed at runtime. A delivered agent consumes 0.02 AI Units per Standard action and 0.05 per Advanced action (SAP whitepaper, version 10.2026), and Joule for Consultants is the one per-user offer left, at 35 AI Units per user per month including 22,900 requests. SAP's own example: 5 users for 12 months is 2,100 AI Units, or EUR 14,700 at the EUR 7 per unit used in that example, read on 23 September 2026 and not a list price.

The rule for a statement of work is to present three lines separately: SAP's consumption cost, passed through; the consultant's day rate; and delivery effort in days. Never blend AI Units into a day rate, and add a re-pricing clause given how often SAP changed its model in 2025 and 2026.

Decision table: who decides what

A feature SAP already ships — Decision: activate, do not build · Evidence: scope item, licence, release status · Failure: duplicated build.

Custom application on models — Decision: orchestration deployment, resource groups, cost labels · Evidence: promotion gate passed · Failure: proof of concept promoted as is.

Questions over reporting data — Decision: which models are exposed and how they are described · Evidence: semantic readiness · Failure: good data, poor answers.

Agent acting across systems — Decision: tool scope, approval points, protocol per hop · Evidence: agent registered, owner named · Failure: wider access than purpose.

People or credit decisions — Decision: provider or deployer, Annex III classification · Evidence: documentation plan · Failure: high-risk system treated as a pilot.

SAP data and AI architect: scope, deliverables and how to choose

An SAP data and AI architect takes the same decisions as an SAP AI architect, with the data route weighted more heavily: where grounding data lives, who owns its quality, semantics and lineage, and which models Joule is allowed to see. The deliverables are a layer map per use case, a grounding decision that separates Datasphere metadata, exposed analytic models, the Knowledge Graph and document stores, a cost model in three separate lines, and an AI Act classification before the build starts.

To choose one, ask for a decision they owned and a build they finished. On 7 October 2026 the corpus held 62 postings pairing an architect word with AI wording, 35 of them freelance. The title is common; read what each posting actually asks for.

SAP BTP AI architect, SAP embedded AI architect and S/4HANA AI architect

These three titles describe three placements, not three products. An SAP BTP AI architect designs what you build: a custom application calling models through the generative AI hub, or a pro-code agent reached over A2A, with resource groups, an orchestration deployment and cost labels settled before the first deployment. An SAP embedded AI architect works on the other side, with features SAP already ships inside an application, activated rather than built.

An S/4HANA AI architect sits between the two. Embedded scenarios in S/4HANA, such as cash application, are trained on the customer's data through intelligent scenario lifecycle management and have their own promotion gate, separate from AI Core's deployment step. The rule is the same for all three: say what should not be built because SAP already delivers it.

SAP AI governance architect: what the role owns

An SAP AI governance architect owns the controls that let a deployment pass an audit: provider or deployer status under the EU AI Act, Annex III classification, approval points for agents, the inventory of agents and MCP servers, and the cost attribution that shows which use case spends what. Approval design follows reversibility: confirm before irreversible writes, sample reversible high-volume work.

Buyers also search for a freelance SAP AI governance consultant, an SAP AI governance freelancer or an SAP AI governance contractor. The label matters less than the evidence: ask for a classification they made, an agent they registered with a named owner, and a use case they stopped.

Hiring an SAP AI architect: what the engagement should leave behind

An SAP AI architect is usually engaged before the build team, for a bounded design phase, then kept on as a design authority. The deliverables are documents a build team and an auditor can both read: a use-case register with the layer each case belongs to (delivered Joule capability, Joule Studio build, or a BTP build on SAP AI Core and the Generative AI Hub); a grounding decision per case, naming the data source and its owner; for each agent, its tool list and the points where a human confirms; an EU AI Act classification note per scenario; and a cost model that keeps SAP AI Units, BTP runtime and consultant days as separate lines.

Ask a candidate for an anonymised version of each. An architect who can only show slides of target pictures has drawn the architecture without taking the decisions in it.

SAP business AI solution architect: one use case, end to end

An SAP business AI solution architect works at the level of one solution rather than the whole portfolio: a single process, such as invoice handling or a service case, from the business requirement to the running AI capability. The job is to choose between a capability SAP already ships in the application, a Joule skill or agent built in Joule Studio, and a custom build on the Generative AI Hub, then to define the data it needs, the human checkpoints and the measures of answer quality.

The enterprise-level SAP AI architect described above sets the rules this role works within: approved layers and models, the regulatory classification and cost ownership. Ask a candidate for one solution they took into production and for what they decided not to automate.

What SAP TechEd 2026 changed for the architecture

At SAP TechEd 2026, SAP announced 40 assistants and 300 agents between SAP and its partners (SAP News, 28 October 2026). For the agent gateway, through which third-party agents invoke Joule Agents over A2A, SAP sources differ: not yet GA (SAP Architecture Center, 26 October 2026), phased (SAP Innovation News Guide, 27 October 2026), GA for inbound A2A (SAP Architecture Center, 27 October 2026), GA (SAP News, 28 October 2026). SAP said the full scope of the Databricks platform will be available natively in SAP Business Data Cloud, an expansion that is announced, no availability date (SAP News, 27 and 28 October 2026). Joule Studio is GA rolling out in phases.

Three consequences for the architect. Once confirmed in your tenant, the agent gateway makes third-party agents a first-class caller of Joule Agents, so the trust boundary and the A2A security review move into the architecture document, not the integration backlog. A native Databricks scope inside Business Data Cloud changes the data-and-grounding choice, but plan on it only once SAP dates it. And with 300 agents on offer, the build-or-reuse decision comes first: check the catalogue before designing a custom agent in Joule Studio.

What we cannot assert

No source we hold publishes a day rate or a certification for the SAP AI architect role. The compliance effort range is an estimate from the impact assessment cited in our material, not an observed project cost. Corpus counts mix SAP-specific and generic AI postings.

Frequently asked

What is the difference between a SAP AI architect and a SAP AI consultant?

The consultant delivers within a chosen layer. The architect decides the layer, the data route, the controls and the cost model before delivery starts. On small scopes one person can do both.

What does an SAP AI architect deliver?

A use-case register by layer, a grounding decision per case with its data owner, the tool list and human confirmation points of each agent, an EU AI Act classification note per scenario, and a cost model that separates SAP AI Units, BTP runtime and consultant days. SAP's AI Golden Path is the reference those decisions are checked against.

Which certification is relevant?

C_AIG_2604, the Generative AI Developer associate (3 hours, system-based, 76 % pass mark), covers the hub layer. We found no SAP certification for the architect role as such.

Does the AI Act apply to a Joule deployment?

Yes, in stages. Transparency duties apply now; high-risk duties for Annex III systems apply from 2 December 2027. Classification depends on the use case, not on Joule.

Can I hire a freelance SAP AI governance consultant?

Yes, though few are advertised under that name. On 7 October 2026, 35 of the 62 architect-and-AI postings in the corpus were freelance. We hold no published day rate for the role, so judge the person on a classification, an approval design and a cost model they produced.

Is an SAP AI governance freelancer or SAP AI governance contractor different from an architect?

Usually the same person under a different engagement form. Freelancer and contractor describe the contract; governance architect describes the scope. Name the open decisions in the statement of work and keep SAP's consumption cost as a separate line from the day rate.

What does an SAP Joule Studio architect, SAP business AI solution architect or SAP agentic AI architect decide?

Which edition is in scope: classic Joule Studio in SAP Build, with the skill builder generally available since July 2025 and the agent builder since the fourth quarter of 2025, or the new intent-based studio announced on 13 May 2026, for which we found no SAP statement of general availability as of 23 September 2026. Then the tool list, the confirmation points and whether the design stays within the documented subagent limits of 5 direct and 25 in total. An SAP business AI solution architect and an SAP agentic AI architect take the same decisions as an SAP AI architect, scoped to one solution or to agents: which layer the use case belongs to, where its data comes from, which tools an agent may call, where a human must confirm and which regulation applies. The word solution usually signals a single delivery rather than a portfolio, and the decisions come before the build, not during it. The section on agents and protocols above covers why this is smaller than the slide suggests, and our guide on the SAP business AI consultant sets out how architect and consultant differ.

What does an SAP HANA Cloud vector engine architect decide?

Whether document grounding goes through Joule or straight to the vector engine. For Joule, ingested documents are visible to all Joule users of the tenant, with no per-user filtering; where access rules matter, query the vector engine directly and keep row-level security. A hybrid pattern also exists: master data in the graph engine, transactions in SQL over data products, text through vectors.

What is an SAP AI services architect?

No SAP product carries that name in our material. SAP describes Business AI as capabilities embedded in an application, exposed through Joule, packaged as an agent, sold as a service or offered as a platform, so an AI services architect places a use case on the service route rather than a build route. The decisions are the same: which layer, which data, which cost line.

SAP Joule solution architect or SAP analytics cloud AI architect: which layer do they decide on?

An SAP Joule solution architect takes the same decisions as an SAP AI architect for one Joule solution: which scenarios, which tools an agent may call and where a human confirms. An SAP analytics cloud AI architect works on the analytics layer: which models are released for natural-language questions in SAP Analytics Cloud, how hierarchies and descriptions are maintained and which authorisations the assistant inherits.

SAP AI architect jobs: who is hiring, and on what terms?

On 7 October 2026 the Analytics Legends contract corpus held 62 postings whose titles combine an architect word with AI wording, 35 freelance and 27 permanent, while 95 postings named Joule, 87 of them permanent. The title is common and the content varies from one posting to the next, so ask which decisions the role owns: layer, data route, controls and cost model. We found no SAP certification for the architect role as such.

What is SAP AI architecture, or SAP business AI architecture?

SAP AI architecture, also searched as SAP business AI architecture, is how a use case is placed across SAP's portfolio. SAP groups the SAP Business AI Platform, announced at Sapphire in May 2026, in three pillars: Build, Contextualise and Reason, and Govern. The architect places each use case in one of five options: a feature SAP ships inside an application, a standard Joule agent, a custom agent in Joule Studio, a custom application calling models through the generative AI hub, or a pro-code agent on BTP reached over A2A. Data route, controls and cost model follow from that placement.

What does an SAP data and AI architect own that an SAP AI architect does not?

An SAP data and AI architect also carries the data side: which data products, Datasphere models or Business Data Cloud shares feed the AI use cases, how they are governed and who owns them. A pure SAP AI architect can treat the data as given and concentrate on layers, agents, regulation and cost. When grounding quality is the main risk, ask for the combined data and AI profile rather than two separate roles that hand over at the boundary.

Engage the editor

This guide is written by . 27 years of SAP — Datasphere, Business Data Cloud, SAC Planning, Joule. Freelance or permanent · Hybrid / remote · Anywhere in EMEA.

Profile and contact

What this page is built on

External sources

Read next

Alert me to new SAP Business AI & Joule missions

No account needed. We first ask you to confirm by e-mail; nothing is sent without that confirmation, and every alert has a one-click unsubscribe link. Privacy

Open missions

67 live roles and contracts in SAP AI & Joule right now — see the SAP AI & Joule missions · freelance SAP contracts.