superhelpful

The limits it runs inside

Every workflow runs inside limits you can see, and every one is enforced. Here's what keeps it in bounds, built before we built anything else.

Permissions it can't talk its way past

A workflow gets only the connections it needs, spelled out in plain words. If deleting an invoice isn't on the list, it physically can't delete one. This is enforced the moment it runs, through a proxy every action passes through. It isn't a setting we promise to honour.

The invoice chaser can
✓Read invoices in Xero
✓Draft emails in Gmail
✕Send to a new customer without your OK, delete anything, or see payroll.

Your OK, where it counts

Being allowed to do something and being cleared to do it right now are two different questions. A workflow can hold the permission to send an email and still stop for your say-so first. What waits is set by what the action is, not by how technical it sounds.

Runs on its own
Reading your data. Drafting something without sending it.
Waits for you by default
Messaging an existing customer. Writing to a system of record. A first message to someone new.
Always waits, no exceptions
Deleting or voiding a record. Anything that moves or requests money.

Approvals come to your phone with the actual draft, not a summary of it. You read what's about to go out before it goes. And nothing approves itself because you were busy: it holds, and reminds you. A gate that opens on its own isn't a gate.

Autonomy you hand over, and can take back

You decide how much rope. A workflow can start with everything held for your approval. As it proves itself, you can let it act and tell you after. You move that line yourself, or we suggest it with the count: "you've approved twenty of these in a row without changing one."

It moves the other way on its own. If something goes materially wrong, the workflow steps its own autonomy back down and writes up what happened. The system that granted more freedom takes it back without waiting for you to notice.

Always disclosed as AI

Any message a workflow sends for you says it's AI acting on behalf of your business. That's stamped by the system as it sends, not left to the model to remember, so it can't be dropped by a bad prompt or a confused step. You can word it to suit your business. You can't turn it off.

A hard cap, and a bill you can read

Paused at your capnot an overage charge

You set a monthly ceiling. We alert you at 50, 80 and 100 percent, and stop at the cap. Hitting it pauses the work and tells you, it never quietly runs up a bill. An automation that stops at a limit you set is behaving correctly, and the product treats it that way. See how the credits work on the pricing page.

Every action on the record

Who approved it, what it was allowed to touch, what it did, and when. The actions it was permitted, not only the ones it was refused. It reads like a bank statement, because "what did it do last Tuesday" is a question you should never have to guess at.

Control you can see beats confidence you can't.

We're building it now, AU businesses first. Join the waitlist and we'll show you the controls on your own work.

Free to join. We'll email you when it's your turn.