Processes the way your team already works.
A process hangs on its channel: the steps, the schedule, the tools it may touch and the person who says yes. A worker runs it. Reads can proceed; anything that changes a system waits in Needs you.
Every Monday, a price check.
Compare competitor prices for the best sellers, prepare a price proposal and post a memo. Shopify is read; the proposal is the output.
Reads the best sellersShopify
Their prices and stock, from the shop.
Compares competitor prices
On the competitors’ public pages.
Prepares a price proposal
With the sources it used.
The proposal waits for a yes
Nothing in the shop changes before that.
Posts a memoSlack
Write it once. See it run.
Author it once
Capture who decides, what gets checked and what would be written where. A playbook proposed from a host AI waits for approval before it is live.
Run it where you can see it
The worker’s steps are visible. Pause it or edit it when the world changes. A host AI can start a process only where its owner allows that, and the run still stops for a yes before it changes anything.
The same shape on another stack
Every Friday: list the rent contracts that end in the next three months in Bloxs, a Dutch property system on a custom connector, check the notes on each unit in Google Drive, prepare a renewal draft per tenant and post an overview in Teams.
Every draft waits
A draft, a card or a change to a connected system waits in Needs you, together with the rest of what waits, until a person approves it.
Reads run. Changes wait for a yes.
A worker reads what it needs on its own. Anything that would change a system, send mail or publish waits in Needs you until a person approves it.
Bring one process you already run by hand.
We will put it on a channel and show where the approval sits.