← How it works

Build a workflow by describing it

Brief the architect the way you'd brief a new teammate. It drafts the plan on the Canvas, asks questions as it goes, and tests it before anything goes live.

Describe the work in plain English, and the plan takes shape on the Canvas, stage by stage.

Describe the work

Say what needs to happen and why. Add documents you already have, like a policy or a price list.

Read the plan

The architect lays out the stages on the Canvas: who's involved, which tools each stage uses, and what it needs before it's done. The Canvas is what runs.

It asks as it goes

When something isn't clear, it asks instead of guessing.

It tests its work

Before anything goes live, it runs the workflow on sample cases and fixes what doesn't match what you asked for.

Built once, run many times

The architect uses the most capable model to work out the plan. Each run follows that plan on a smaller, faster model.

Change it anytime

When the work changes, say what's different. The architect edits the plan instead of starting over, and the change starts as a draft.

Build, onceWork out the stages, the rules and who to askMost capable model
Run, every timeFollow the plan for each new case
  • Email 1
  • Email 2
  • Email 3
  • Email 4
  • Email 5
  • …
Smaller, faster model
The hard thinking happens once, when the workflow is built. Every run follows that plan on a faster model.

For example

An operations lead writes: "Jobs more than 50 miles away need a second technician, and every new customer gets a site survey first." The architect adds a survey stage and the staffing rule. Once the lead publishes the change, the next job follows it.

See a full workflow like this →