Getting started

Set up your Operator

Create your workspace, connect the systems Operator needs and set sensible approval boundaries before you expand.

6 min read

The common mistake is trying to hand over the whole company at once. Setup goes better in the opposite direction: one business motion, only the systems that motion touches, and clear approval boundaries before anything runs.

Before you begin

Pick the first business motion you want Operator to carry. A good candidate happens often, follows a recognisable pattern and currently costs somebody time every day: lead response, the Morning Brief, meeting follow-up or inbox triage.

Everything else in this guide follows from that choice. The motion decides which systems you connect, which signals Operator watches and which approvals matter.

What you need

  • one repeatable process to start with
  • access to the connected systems that process touches
  • agreement on who reviews sensitive actions

Setup steps

  1. 01

    Choose the process

    Pick the motion where a delay is most expensive for the business.

    • lead response
    • Morning Brief
    • meeting follow-up
    • inbox triage
  2. 02

    Identify the systems involved

    Connect only what the process actually needs. Lead response usually needs a form intake, CRM, email and calendar; the Morning Brief needs whichever systems hold the overnight activity you would otherwise check by hand.

  3. 03

    Define what Operator should watch

    Decide which signals start the workflow.

    • new messages
    • new leads
    • meeting events
    • CRM changes
    • scheduled checks
  4. 04

    Define what Operator may prepare

    Preparation is safe work: nothing has left the company yet.

    • response drafts
    • CRM updates
    • tasks
    • reminders
    • summaries
  5. 05

    Decide what requires approval

    New workflows should begin conservatively. External communication, financial activity, deletion and significant data changes stay human-controlled.

  6. 06

    Test with real but controlled examples

    Run the process end to end on real cases you are watching, before anyone relies on it.

  7. 07

    Expand once it is reliable

    Add the next system or the next action type only after the first loop has run without correction for a while.

The workflow itself follows Trigger, Reason, Act and Approve. Launch your first workflow

What to check before continuing

  • the context Operator gathered is the context you would have gathered
  • the suggested action matches what you would have done
  • approval boundaries hold for anything customer-facing or financial

Human checkpoint

If a proposed action would be awkward to undo, keep it behind an approval until the loop has proven itself.

What happens next

Once the workflow is reliable, expand its responsibility or connect an additional system. Widen one thing at a time so a change stays easy to attribute.

Key takeaway

Start with one motion. Prove the loop. Then expand.

Continue learning

Launch your first workflow

Take one repetitive business motion from connected systems to a working Operator workflow using Trigger, Reason, Act and Approve.

6 min read

How integrations work

Scoped access, connected per workflow and revocable at any time.

4 min read

Changing autonomy rules

Loosen the leash one action type at a time, based on evidence.

4 min read