SAP Joule Studio consultant: building, connecting and governing agents
As of 2026-11-21
A SAP Joule Studio consultant designs, builds and governs custom agents for Joule: scoping the use case, configuring the agent builder, wiring tools through MCP and A2A, placing approval points where an action cannot be undone, and handing the result to an operations owner. The product has its own guide; this page covers the person you hire. On 7 October 2026 none of the 1,657 live postings in the Analytics Legends corpus named Joule Studio, while 95 named Joule, so the skill is usually sold under a wider title.
Looking for a SAP AI consultant? Cédric Mary, SAP AI & Analytics Architect & Team Lead, takes SAP Business AI, Joule and Business Data Cloud missions.
The role in four jobs, and what it is not
The work has four parts: choose what to build, build it, connect it to the systems it acts on, and control what it may do. A consultant who only configures prebuilt agents does a different job: SAP's delivered agents are activated, not built. The Joule Studio consultant starts where that catalogue stops, when no standard agent exists for the process in the customer's edition and region, or the gap is limited to tools, instructions or data sources.
The role also differs from the platform engineer's: AI Core and the Generative AI Hub are where a pro-code agent calls its models, whereas the Joule Studio consultant decides whether the agent is worth building and owns how it behaves in a conversation.
Two studios, two skill sets
Joule Studio now exists in two forms. The classic edition sits in SAP Build: the skill builder became generally available in Q2 2025 and the agent builder in Q4 2025. The new studio, announced on 13 May 2026, opens from Joule Work and adds a command-line tool, a managed runtime and an Agent Gateway. At SAP TechEd on 27 October 2026, SAP gave its status as GA rolling out in phases (SAP TechEd 2026 Innovation News Guide, 27 October 2026). The two editions carry separate SKUs, roles and provisioning paths, so one subscription does not cover both.
The first question of every engagement is therefore which edition, and whether the client accepts programme conditions. Classic suits a low-code team; the new studio suits professional developers who want continuous delivery. Design-time access is free under fair-use limits with no end date, but SAP's continuous-improvement terms let it process configurations and execution logs, which matters before regulated data is involved.
Building: the agent builder and Build Process Automation
An agent in the classic builder is defined by its expertise, instructions, a planning model and a response model, a budget of thinking steps, and a small toolset: skills, document grounding, a calculator, subagents and MCP servers. The step budget runs from 1 to 100. A larger budget or a backup model trades latency and AI Units for resilience, so it belongs on agents whose failure is expensive.
Write actions are where reviews go wrong. SAP's reference pattern for an action that changes data is a process automation invoked from inside a skill, not a bare REST call from the agent, because stateful, multi-step actions need retry and approval behaviour. Agents are designed in Build Process Automation but run in a Joule instance that is often another subaccount; destinations such as MCP credentials must exist in both, and a missing one surfaces as a generic tenant error at deployment.
Treat multi-agent designs with suspicion: classic subagents run sequentially, up to 5 direct and 25 in total, so latency adds up. The default is one agent with three to five tools.
Connecting: MCP and A2A, hop by hop
The working rule: a person reaches the agent through the interface, the agent reaches SAP data and actions through MCP, and a foreign agent through A2A. Wrapping a partner agent as an MCP tool is acceptable only for short, synchronous work.
The limits are concrete. Joule expects an A2A agent server to answer within 60 seconds; longer work needs push notifications, which need identity trust between both sides. For code-based agents SAP's samples document direct A2A (one minute), an asynchronous REST interface (five minutes) and a streaming client service beyond that. The classic builder accepts MCP servers only over streamable HTTPS with client credentials and without principal propagation, so a server that needs per-user isolation cannot connect there at all. SAP's API policy limits agentic use of SAP APIs to endorsed routes such as the Integration Suite gateway, so scope this before designing tools.
Governing: approval points, guardrails, inventory
Three control points are easily confused: confirmation on a tool inside a turn, agent-initiated pauses for missing input, and lifecycle gates such as the approval before production deployment. Verify all three. Match the checkpoint to reversibility: postings, payments and HR data get a confirmation before execution; reversible, high-volume drafting can run with sampling afterwards. Where the AI Act's human-oversight article applies, a bare yes-or-no prompt lets no reviewer understand or override anything.
Guardrails sit at environment level, with masking and filtering at each step. SAP AI Agent Hub, built on SAP LeanIX, inventories agents, MCP servers and models; it governs, but does not run or trace them.
Decision table: which route for which case
Process already covered by a standard SAP agent — Route: activate or extend · Check: scope item, release status, edition and region · Risk: building what SAP ships.
No standard agent, low-code team — Route: classic agent builder · Check: environments, audit log, MCP constraints · Risk: a tool needing per-user identity cannot connect.
Pro-code agent or continuous delivery — Route: new studio command line, or AI Core plus A2A · Check: phased GA reached in the client's tenant, 60-second limit · Risk: go-live date set before the phased rollout reaches the tenant.
Write action to a core system — Route: process automation invoked from a skill · Check: approval step, retry behaviour · Risk: a bare call with no approval.
Several domains, separate scopes — Route: supervisor with subagents or A2A peers · Check: owner per specialist · Risk: sequential latency, blurred accountability.
Decisions about people or credit — Route: agent with a mandatory human decision, legal classification first · Check: provider or deployer status · Risk: a high-risk system built as a pilot.
Cost and market: a worked example
SAP meters delivered agents at 0.02 AI Units per Standard action and 0.05 per Advanced action (whitepaper, version 10.2026); assistants carry no separate charge. As an illustration with assumed volumes, an agent taking 3 actions per run and running 10,000 times a month consumes 30,000 actions, or 600 AI Units at the Standard rate and 1,500 at the Advanced rate. SAP's own example prices an AI Unit at EUR 7, an example rather than a list price, which would give EUR 4,200 or EUR 10,500 a month before negotiation. Custom-built agents are billed differently: productive runtime is billed on resources used through BTPEA, CPEA or pay-as-you-go, free until December 2026 only for select customers under a time-bound promotion. Consumption is SAP's fee, paid by the client to SAP; never blend it into a day rate.
In the corpus of 7 October 2026, 95 of 1,657 live postings name Joule: 87 permanent, 6 freelance and 2 contract, with Germany 35 and the United States 17.
SAP Joule agent consultant: the profile in one paragraph
A SAP Joule agent consultant decides which agent is worth building, builds it in the agent builder, connects it to the systems it acts on and fixes what it may do without a person. Two checks separate this profile from a generic AI title. Which Joule Studio edition has the person shipped on: the classic edition inside SAP Build, or the new studio announced on 13 May 2026? And which approval points did they place on write actions?
Ask for an agent that reached production, its tool list and the step where a person confirms. SAP's delivered agents are activated, not built, so activation experience alone does not show the skill.
SAP Joule agents architect and SAP Joule agent developer
The architect decides, the developer implements, and a small engagement often has one person doing both. A SAP Joule agents architect settles the edition, whether a standard agent already covers the process, the route for write actions (a process automation invoked from a skill, not a bare REST call), the MCP and A2A hops and the limits: classic subagents run sequentially, up to 5 direct and 25 in total, and an A2A agent server is expected to answer within 60 seconds.
A SAP Joule agent developer configures expertise, instructions, models, the step budget (1 to 100) and the toolset, then deploys across subaccounts where destinations must exist on both sides.
Joule Studio developer and Joule Studio architect: where the titles differ
The label Joule Studio developer fits a low-code builder user and a professional developer alike, so ask which. The classic builder is low-code. The new studio adds a command-line tool, a managed runtime and an Agent Gateway, and suits developers who want continuous delivery. A Joule Studio architect chooses between the two editions, checks that the client accepts programme conditions (the new studio's GA is rolling out in phases, SAP TechEd 2026 Innovation News Guide, 27 October 2026) and sets the governance: confirmations, guardrails and an inventory in SAP AI Agent Hub. Neither title implies a certification; we hold no source for a Joule Studio exam.
What we cannot assert
No SAP source we hold says when the phased GA of the new Joule Studio, announced at SAP TechEd on 27 October 2026 (SAP TechEd 2026 Innovation News Guide, 27 October 2026), reaches a given tenant, and no source publishes a day rate for the role. Corpus counts depend on how skills are tagged in postings and mix SAP-specific and generic AI wording; they measure advertised demand, not total demand. The AI Unit calculation uses assumed volumes.
Frequently asked
Is Joule Studio the same thing as SAP Build?
The classic edition is a component of SAP Build on Build Process Automation. The new studio opens from Joule Work and has its own SKU, roles and provisioning, so check which one the client holds.
Does a Joule Studio consultant need to write code?
Not in the classic builder, which is low-code; the new studio adds a command-line route. Either way MCP, A2A and approval design must be understood.
Which certification applies?
C_AIG_2604 tests the Generative AI Hub (3 hours, 76 % pass mark). We hold no source for a Joule Studio exam.
What does a SAP Joule agents consultant do day to day?
Scopes the use case, configures the agent, wires tools through MCP and A2A, tests the exception path and hands the agent to an operations owner. Consumption is a separate matter: SAP meters delivered agents at 0.02 AI Units per Standard action and 0.05 per Advanced action, paid by the client to SAP and never blended into a day rate.
Who counts as a SAP Joule Studio expert?
Someone who can name the edition they used, show an agent they took to production and explain its approval points, tool authentication and failure handling. The title is rare in adverts: on 7 October 2026 none of the 1,657 live postings in our corpus named Joule Studio, while 95 named Joule, so the skill is usually sold under a wider title.
Is a SAP Joule skills developer the same as an agent developer?
No. A skill is a bounded function that an agent can call, built in the skill builder (generally available in Q2 2025). An agent is a reasoning loop with instructions, models and tools, built in the agent builder (Q4 2025). Many consultants have built skills; fewer have put an agent into production.
What does a SAP Joule Studio architect decide?
Which route fits the case, which tools and protocols an agent may reach, where the approval points sit and how agents are inventoried. The builder then works within those limits. The decision table on this page sets out which route suits which case.
Engage the editor
This guide is written by Cédric Mary, SAP AI & Analytics Architect & Team Lead. 27 years of SAP — Datasphere, Business Data Cloud, SAC Planning, Joule. Freelance or permanent · Hybrid / remote · Anywhere in EMEA.
What this page is built on
- Joule Studio: classic edition and the new intent-based studio
- SAP Joule Agent Builder
- Agents in SAP Build Process Automation
- Multi-Agent Orchestration in Joule Studio
- Agent Communication in SAP — MCP vs A2A, Hop by Hop
- A2A — Agent-to-Agent protocol in Joule
- MCP — Model Context Protocol in SAP (mechanics)
- Human-in-the-Loop Checkpoints for Autonomous Workflows
- SAP AI Agent Hub — Vendor-Agnostic Agent Governance
- SAP AI Units & the SAP Business AI Commercial Model
- Joule Agents Library and Agent Catalogue
- Analytics Legends live contract corpus, 7 October 2026
- Understanding SAP's Business AI Commercial Model, whitepaper, version 10.2026 (SAP, read 7 November 2026)
External sources
- Understanding SAP's Business AI Commercial Model, whitepaper, version 10.2026 (SAP, read 7 November 2026)
- SAP News — SAP Business AI release highlights Q2 2025 (skill builder generally available)
- SAP News — New agentic capabilities on SAP BTP, 5 Nov 2025 (agent builder, A2A and MCP support)
- SAP News — SAP Business AI release highlights Q4 2025 (agent builder generally available, AI Agent Hub)
- SAP News — SAP Business AI release highlights Q1 2026 (Joule Studio code editor and CLI)
- SAP News — Announcing the new Joule Studio for enterprise-scale agentic development, 13 May 2026
Read next
- Joule Studio SAP: what is Joule Studio, and which edition is GA today
- SAP AI agents: what ships, what is roadmap, and what you build
- SAP AI Consultant
- Agent Communication in SAP — MCP vs A2A, Hop by Hop
- SAP Joule consultant: what the role delivers, and when you need an architect
- SAP AI Core consultant: plans, resource groups, deployments and cost
- What is SAP Joule? What SAP Joule for Consultants does, and what it does not
- SAP MCP servers list: which exist, who maintains them, and which pathway SAP allows
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
Related guides
These guides cite this page as a source.
- Hire SAP Joule consultant: layers, proof, price
- Joule Certification: The SAP Exams That Exist in 2026
- SAP AI team lead: what the role owns on a programme
- SAC Planning Consultant: Role, Skills and Market
- SAP AI Architect: Layers, Grounding, Agents, EU AI Act
- SAP generative AI consultant: role and what to check
Open missions
67 live roles and contracts in SAP AI & Joule right now — see the SAP AI & Joule missions · freelance SAP contracts.