01UNDERSTAND
Start with the work you have.
Capture activities, exceptions, participants and systems. Review the proposed structure and resolve gaps before accepting it.
Back to homeDesign how
Design how
the work works.
Make the tasks, people, agents and coordination part of one explicit design.
Describe the work in your own words, bring an existing process — a BPMN model, an event log or a procedure — or build on the canvas. Explore how a different arrangement could improve the work before you invest in implementation.
How work is arrangedExplore
PrepareAgent gathers the information
ReviewPerson checks the proposal
SubmitAuthorized person sends it
Work progresses through an explicit order.
Proposal leadPerson accepts the combined result
delegates
ResearchEvidence agent
DraftingWriting agent
The lead commissions the parts and accepts the result.
Shared proposalOne shared work state
contribute
ResearchEvidence agent
Bid leadPerson accepts & submits
Participants contribute to a shared state; acceptance remains explicit.
DesignSimulateRealize
The question that matters
Changing who does a task is only one design choice.
Work can follow a sequence, be delegated by a lead, or be coordinated around shared state. Those arrangements differ in how work advances, who may act, and what makes the result official.
From intent to implementation
02IMPROVE
Test a change to the current design.
Explore where an agent might assist, take on work, or relieve a constraint while preserving the surrounding arrangement.
03RESTRUCTURE
Try a different way to coordinate.
Explore a lead with specialists, shared work, or another supported arrangement. Make responsibility for the outcome explicit.
A model you can question. A design you can develop.
Keep the meaning of the work visible as it moves from a description to an accepted version.
Tasks and formations
Represent both individual activities and groups of participants working through an explicit coordination arrangement.
People, agents and systems
Staff the work with roles and connect tasks to the systems they read or change.
Versions with consequences
Carry a selected design into simulation, then use an accepted saved version as the basis for realization.
Before you get started.
Is every work system a workflow?
A workflow is one way of organizing work. A work system can also contain formations: groups with a declared way of coordinating and accepting an outcome.
Can I design something that has never run?
You can author a proposed work system without execution history. Its assumptions still need to be explicit, and simulation results remain conditional on those assumptions.
Do you do process mining?
No, and you don't need us to. Bring your event log or the model your mining tool discovered, and Bot0 turns it into a work system — with measured branch shares and a check of how many cases follow the design — that you can redesign and simulate.
Can I take my design elsewhere?
Yes — as standard BPMN that any process tool reads. The flow, the roles and the teams go with it. What makes it run — each agent's authority, its grounding and the realization plan — stays with the work system in Bot0, where Realization Studio carries it the rest of the way.
Does the model become live automation immediately?
Design, simulation and realization are distinct stages. A saved model becomes an input to realization; execution depends on the chosen destination and its completed setup.
Design · Simulate · Realize
Bring one piece of work. Explore what it could become.
Design it, evaluate it, and realize the version you choose with Bot0.