SAP Joule Studio implementation and integration services

Stop paying for BTP licences nobody uses. We customise, integrate and deploy SAP Joule so your teams query SAP and non-SAP data in one conversation, delivered in weeks, not years.

Book a Discovery CallCompare platforms

Jason, our COO, runs the call and tells you which Joule workflow to build first.

SAP Joule StudioSAP Business AI
Where
SAP Build on SAP BTPJoule is what users talk to. Joule Studio is where it gets extended.
Skills
Skill builderGenerally available since July 2025.
Agents
Agent builderGenerally available from December 2025.
Needs
An SAP BTP accountWith service assignments and Joule licensing.
Non-SAP data
BTP destinations and Integration SuiteCRMs, ticketing tools and external databases.

From SAP's Joule Studio product page, checked 19 October 2026.

Clients include

AudinatePinkcubeBizIQCourserAllClear Travel Insurance
From licence to production

Bridging the gap between SAP licensing and production AI

Most SAP teams are stretched across Basis maintenance and upgrades. Building custom Joule skills takes AI engineering depth on top of that.

Copilot configuration and skill extension

Custom conversational skills in Joule Studio, so teams run multi-source queries in plain language without a transaction code.

BTP AI services integration

Foundation models, vector engines and destination services configured for secure data access across your connected systems.

AI Audit and readiness

Your SAP architecture, data hygiene and integration readiness assessed before any code. Implementations that skip this step are the ones that stall.

End-to-end deployment

Sandbox configuration, transport management and production release, so your team is not left with an unfinished environment.

Three workflows we build in SAP Joule Studio

Each one answers a question that today takes a person, a few transactions and a spreadsheet.

Procurement

Joule for enterprise procurement

Procurement managers query S/4HANA and legacy vendor databases through one Joule interface. Joule pulls the data, surfaces discrepancies and drafts the follow-up in the same session.

HR

HR ticket resolution with SuccessFactors

Agents that connect SuccessFactors to ServiceNow. Routine questions are answered and tickets updated automatically, and sensitive cases go to an HR specialist straight away.

Supply chain

Context-aware supply chain forecasting

S/4HANA inventory read alongside external demand feeds through a context layer, with reorder recommendations inside the analyst's dashboard.

See the context layer

One question, SAP and non-SAP data, one answer

A procurement manager asks Joule what used to take three systems and a pivot table.

Joule, procurement skill
Procurement managerWhich active vendors have outstanding compliance flags?
JouleThree active vendors have open flags. Two are missing renewed certificates and one has a sanctions screening pending. I drafted a follow-up to each supplier contact for your review.
S/4HANA vendor masterLegacy vendor database3 drafts awaiting approval
What runs behind it
  1. Custom Joule skillBuilt in Joule Studio for this question type
  2. SAP dataVendor master read from S/4HANA
  3. Non-SAP dataLegacy vendor database reached through a BTP destination
  4. Manager approvesDrafts are sent only after review

Illustrative conversation. Skills, sources and approvals are designed per workflow during scoping.

Systems we connect Joule to

Inside BTP's compliance boundary the whole way.

  • S/4HANAVendors, inventory, orders and finance data.
  • SuccessFactorsEmployee profiles, onboarding steps and HR cases.
  • ServiceNow and ticketingTickets read, updated and routed from the conversation.
  • Legacy and external dataNon-SAP databases, CRMs and market feeds through Integration Suite.
  • Context layerShared business context so Joule answers with your rules, not general knowledge.
  • n8nWorkflows outside SAP that Joule results start. See n8n
In production today

AI built on top of an ERP, not inside it

A Dutch Odoo implementation partner tried for a year to build a dental care group's scheduling natively. We built an agent layer over the ERP that now schedules 1,500 appointments a week. It runs on n8n and Odoo, not SAP, and it is the same approach we take with Joule: the ERP stays the system of record and the AI works on top of it.

See all case studies
Dental care groupOdoo and n8n, scheduling
1,500
Appointments scheduled a week
200practitioners
25,000residents served
5sync workflows

How a Joule Studio build runs

Scoping sets the timeline for your workflow, and every build is tested in staging before it goes live. See how we work

AI pilot
2 to 6 weeks
AI Audit
4 to 8 weeks
Full build
Set in scoping
  1. Jason
    Jason, COO

    AI Audit and scoping

    We assess your SAP architecture, data hygiene and BTP setup, and agree the first skill with your team.

    • The question the skill answers
    • The SAP and non-SAP sources it reads
  2. Maciej
    Maciej, CTO

    Skill and agent build

    We build the skill or agent in Joule Studio and configure BTP AI services, destinations and Integration Suite.

    • Sandbox first, on test data
    • Transports prepared with your Basis team
  3. Jason
    Jason, COO

    Integration and approvals

    We connect the non-SAP systems and set the approvals before anything is written back.

    • Approvers named per action
    • Access through your BTP roles
  4. Maciej
    Maciej, CTO

    Release and run

    We release to production, train your team, and keep extending Joule in weekly sprints.

    • Error alerts to the engineers who built it
    • Weekly sprints that you direct

What teams ask about SAP Joule Studio

Ask us something else

What is the difference between SAP Joule and Joule Studio?

SAP Joule is the conversational copilot built into SAP cloud applications like SuccessFactors and S/4HANA. Joule Studio is the environment in SAP Build on BTP where developers and partners extend it, with custom skills, multi-step agents and non-SAP data sources. Users talk to Joule, and Joule Studio is where that experience is built.

How do you extend Joule to non-SAP systems?

With custom skills in Joule Studio and secure connections through BTP destinations and Integration Suite. Joule can then query external databases, CRMs and ticketing tools and combine the results in one answer, inside BTP's compliance boundary.

Does Joule Studio require SAP BTP?

Yes. Joule Studio runs on SAP BTP, so you need a BTP account with the right service assignments and Joule licensing. There is no supported way to run it outside BTP.

Where should we start?

With one question your team answers by hand every week. If you have several, the AI Audit ranks them over 4 to 8 weeks and ends in a 90-day roadmap.

Other platforms we build on

We pick the platform after we understand the workflow, so the same team can build on whichever of these fits it. Compare them all

Workflow automation

n8n

Trigger-and-steps workflows with AI inside them, billed per run and self-hostable in your own cloud.

See n8n
Enterprise AI platforms

Microsoft Foundry

Agents built in your Azure tenant under Entra ID, billed on the Azure account you already have.

See Microsoft Foundry
Simulation and digital twins

Sim AI

Digital twins and simulation runs connected to live R&D and manufacturing data.

See Sim AI
Workflow automation

Kestra

Open-source orchestration for data and AI pipelines, defined as code and run on your infrastructure.

See Kestra
Workplace AI

Claude Cowork

Anthropic's agent for knowledge work, set up with the plugins, connectors and approval steps your teams need.

See Claude Cowork
Workplace AI

ChatGPT for work

ChatGPT rolled out to your company with the connectors, custom GPTs and admin settings it needs.

Page coming

Your SAP Joule environment should be working for you today

If your team is stretched across Basis maintenance and lacks AI engineering hours, we work as a direct extension of it. Answer a few questions and Jason scopes the first skill.

Owen, Maciej, Jason, Oskar and Ben