Case study 03SAP Build2020 — 2026
ShippedTurning fragmented tools into one platform.
SAP Build brought together three previously separate products for creating applications, automating processes, and building business sites. I helped shape a unified experience across the platform, defining a North Star vision, shared interaction models, and a more coherent way for users to move between capabilities. The work later expanded into exploring how people, applications, and AI agents could collaborate through SAP Build Runtime.
At a glance
01The problem
Three products, three mental models
Apps, process automation and business sites each had their own entry point, structure and route to deployment. Together they felt like three products sharing a login.
02What I did
Created the vision, integrated the experience
I created the North Star experience vision, led the experience integration around one shared model, and later developed the Build Runtime concept.
03The result
One platform experience, and groundwork for agents
Three product areas integrated with shared information architecture, navigation and interaction models. The Build Runtime concept fed into SAP's later direction for agentic experiences.
01
The problem
Three products, three mental models
I joined while three previously separate products were being consolidated into one low-code platform. Each was capable on its own. Together they felt like three products sharing a login.
One covered building applications, one process automation, one business sites. Each had its own entry point, its own way of organising work, its own name for the things people create, and its own route to deployment. Someone building a simple approval app needed all three and had to understand where each one's boundaries lay.
The audience made it harder. A low-code platform serves business experts who are new to building software alongside professional developers who expect precision and control. The integrated experience had to feel approachable to the first group without slowing down the second.
Entry point 1
App development
Entry point 2
Process automation
Entry point 3
Business sites
To build one solution, a person needs all three, and has to learn three ways of naming, finding and deploying their work.
02
North Star
A destination everyone could argue with
Consolidation projects tend to drift into lowest-common-denominator compromises: a shared header, a shared colour palette, and three products underneath. I created a North Star vision to give product, design and engineering a concrete picture of the destination before negotiating each step towards it.
A good North Star is specific enough to disagree with. It showed how one person would go from an idea to a running solution without noticing which original product they were in. That made the real integration questions visible: shared objects, a shared lifecycle, shared roles. The vision influenced strategic roadmap priorities.
03
Information architecture
Organise around the work, not the tools
04
Interaction alignment
The same moment should feel the same everywhere
Shared IA only works if the moments inside it match. We aligned interaction models and design patterns for the moments that recur across every editor: creating something new, finding it again, understanding its state, sharing it, deploying it. The aim wasn't visual sameness. It was predictability, so that someone who had deployed an app knew how to deploy a process.
05
Build Runtime
What happens after people stop building and start running
Once the platform held together, a more interesting question came up. Low-code platforms are good at creating applications. But people don't want applications. They want outcomes. What if the runtime itself understood intent?
I conceptualised SAP Build Runtime as an intent-driven experience where people, applications and AI agents work together towards business outcomes. Instead of one more app to open, the runtime would understand what someone is trying to achieve, bring in the right applications, automations and agents, and keep the person involved where judgment is needed.
That work fed into SAP's later direction for agentic experiences, and it's the groundwork for the delegation model in the first case study.
- 01 · Build
Create applications
Low-code tools make it faster to build apps, automations and sites. People still navigate to each one to get work done.
- Person → App
- Person → App
- Person → App
- 02 · Build Runtime
Coordinate around intent
The runtime understands what a person is trying to achieve and brings in the right apps, automations and agents, keeping the person involved where judgment matters.
- Intent
- Apps · Automations · Agents
- Person at decisions
- 03 · Joule Work · Jobs
Delegate outcomes
The idea grows into a cross-application model where outcomes are delegated as Jobs, supervised in one place and governed by explicit boundaries.
- Job
- Orchestrated agents
- Checkpoints & record
06
Reflection
What changed
- Shipped
One platform experience
Three product areas integrated with shared information architecture, navigation, interaction models and patterns.
- Influence
Roadmap priorities
The North Star vision aligned product, design and engineering and influenced strategic roadmap priorities.
- Direction
Groundwork for delegation
The Build Runtime concept fed into SAP's later direction for agentic experiences, and into my work on Jobs.
What I learned
Integration is mostly a negotiation, and a concrete vision makes it a much shorter one.
The shared object model mattered more than the shared visual language.