Introduction
You have built Skills, connected systems, and maintained Spaces. Joule Work is handling your personal workflows well.
Then two new requirements appear. A manager wants an agent that runs every Monday, pulls pipeline data from SAP, and sends a summary to the team automatically, with no prompt and no manual invocation. A finance team wants a workflow that approves purchase orders directly in S/4HANA, not just summarizes them.
These are production-grade workflows. They need scheduled execution, transactional writes, and deployment at scale. This is where Joule Work hands off to Joule Studio, and the entry point is already in the platform.
The Entry Point Is Already There
You have been working in Conversations and Spaces throughout this course. There is a third area in the Joule Work navigation: Develop. You have not needed it until now.
Develop is the entry point into Joule Studio. You do not sign up for a separate tool or open a different application. You select Develop in the Joule Work web format and you are in Studio.
What you build there surfaces back through Conversations and Spaces across desktop, web, and mobile. An agent created in Studio appears to users like any other Joule capability. The entry point is different. The experience is the same.
Joule Studio requires a separate entitlement and is available only in the web format of Joule Work.
When to Make the Move
The signal is scope, not complexity.
| Stay in Joule Work | Move to Joule Studio |
|---|---|
| Personal automation | Scheduled, autonomous execution |
| Data retrieval and summarization | SAP transactional writes |
| Meeting and document preparation | Multi-agent orchestration |
| One conversation at a time | Production deployment with governance |
If the workflow runs within a conversation, Skills and connectors are the right fit. If it needs to run without you, write back to SAP systems, or be deployed at production scale, that is Joule Studio.
Joule Work in Action

This is what Joule Work looks like when all three modes work together. A supply chain manager asks the Supply Chain Planning Assistant in Conversations about supply shortages. The agent spots a SKU shortage and notifies procurement automatically. The procurement director opens a Space that surfaces the supply and demand imbalance, runs agent-driven analysis, recommends a supplier, and generates an RFP. The supply chain manager then moves to Develop and builds an agent that monitors supplier performance on an ongoing basis.
One business problem. Three modes. Two people. No manual hand offs.
This is what the platform is designed for. Conversations handle the question. Spaces hold the ongoing picture. Develop builds what runs without you.
Lessons Summary
Skills handle personal automation within a conversation. When a workflow needs scheduled execution, transactional writes, or production deployment, that is Joule Studio.
Develop, which is available in the Joule Work web format, is the entry point into Joule Studio. It is already part of the platform.
What you build in Studio surfaces back through Conversations and Spaces across all formats.
If a workflow runs within a conversation, Skills are the right fit. If it needs to run without you or interact with SAP systems directly, Joule Studio takes over.