How to use this plan
Treat the dates as a frame, not a forecast. Every company moves at its own speed, and nothing here promises a particular result. If a phase needs longer, take longer.
The shape is deliberate: prove one workflow end to end, make the controls routine, then add teams. Skipping the middle phase is the most common reason pilots do not turn into something the company relies on.
The three phases
Pilot
Prove one workflow with one team.
- Pick one bounded job and name an owner. Use the field guide to design it.
- Start on the free plan, connect your model provider key and build the workflow on the canvas.
- Put an approval before every hard-to-undo step and test with real cases.
- Run it with a small group and read every run trace together.
- Write down what worked, what was awkward and what the team wants next.
Governance
Make the controls routine before more people join.
- Decide who can build, run and approve, and set roles accordingly (custom roles are on the Team and Enterprise plans).
- Create a workspace per team and give each integration its own API key.
- Agree approval rules and what must be recorded, using the approvals guide.
- Look at the usage view and set quota and plan limits that match what you learned.
- Review the plan options and, if you need single sign-on or on-premises deployment, talk to us about Enterprise.
Scale
Widen carefully, with the same discipline.
- Add the next one or two teams, starting from the example workflows closest to their work.
- Keep knowledge current: name who refreshes each source and how often.
- Hold a short recurring review of runs, rejections, failures and spend.
- Turn what you learned into a short internal standard for new workflows.
- Decide what to retire, and what to build next.
Who to involve
- An owner for each workflow, who is accountable for the outcome.
- A builder comfortable with the canvas, with or without code.
- Approvers from the team whose work is affected.
- IT or security, early, for connections, access and where data may go.
Signs you are ready to move on
Do not move to the next phase on the calendar alone. Move when you can say yes to the questions below.
- Can the owner explain, from the run trace, why any given run did what it did?
- Do approvers know what they are approving and does a rejection do something sensible?
- Does each integration have its own key, and does each person have the role they need?
- Is someone responsible for the knowledge the agents rely on?
Questions about a rollout for your organisation? Book a demo and we will talk it through.
Keep going
Build your first governed workflow today.
Start on the free plan, bring your own model key, and see a real run traced end to end.