Building solutions in Joule Studio follows an intent-driven lifecycle that transforms business problems into production-ready agents, applications, and workflows. This process ensures that the final output is grounded in enterprise context and remains maintainable throughout its lifecycle.

Business Intent Analysis

The process begins with intent, where teams describe desired business outcomes in natural language. Rather than jumping straight into solution design, Joule Studio captures a clear problem statement that defines success and identifies affected stakeholders.
The system enriches this input by drawing on SAP enterprise context, including:
SAP Signavio for process insights
SAP LeanIX for architecture constraints
SAP Knowledge Graph and domain models for reality-based grounding
Teams can choose a fast-track approach for clear intents or use guided refinement to align business and IT requirements before development begins.
Product Requirements Document (PRD)

Once the intent is defined, Joule Studio generates a PRD to serve as a single reference point for all teams. This document summarizes the problem, target users, and success measures while maintaining traceability back to the original business intent.
During this phase, teams make early delivery decisions to determine whether to activate standard SAP capabilities, configure existing solutions, or build new custom agents and workflows.
Implementation Specification

The PRD is translated into a technical blueprint or specification. This step makes the domain explicit by defining business objects, system contracts, interfaces, and attributes. Key benefits of this phase include:
Reduced rework by locking in technical choices and integration points early.
Higher output quality by providing the building agent with a concrete technical blueprint.
Early establishment of guardrails for compliance and security.
Code Generation and Development

Joule Studio turns the specification into working code using SAP-aware generation. The build agent creates agents and workflows using the appropriate SAP Domain Models and integration approaches, such as SAP Integration Suite or n8n.
Developers maintain full control through an open ecosystem:
Flexible environments: Work in the web-based experience for speed or switch to preferred IDEs like Visual Studio Code.
Standardized output: Code is portable and follows standard engineering disciplines.
Reviewability: The full codebase is exposed for inspection, refactoring, and versioning in Git.
- Developer tools supported: Vercel, Cline, n8n, Cursor, and Codex
- Agent frameworks supported: Langchain, Pydantic AI, Llamaindex, LangGraph
Testing and Validation

Before release, Joule Studio validates the end-to-end flow to catch failures early. For agent-based solutions, the system runs automated evaluations to measure behavior and performance.
A comprehensive test report provides pass/fail signals, coverage metrics, and behavioral checks. If issues arise, the report helps pinpoint the specific failing component to accelerate iterations.
Deployment and Operations

Final solutions are deployed to an SAP-managed runtime service that handles scaling, security, and monitoring. The deployment process integrates with standard software lifecycles:
Version control: Solutions are pushed to GitHub for review and repeatability.
Observability: Continuous tracking of performance, cost, and usage signals.
Lifecycle management: Tracing, metrics, and logging allow for ongoing optimization and production sign-off.
The SAP AI Agent Hub serves as the central control point to discover, manage, and govern deployed agents across the enterprise.