From process
to SOP to agent.
Write down how a job is done, once. We turn it into an SOP, then into a skill in your Department Brain. The agent follows it, and a named person approves what it produces.
One path, one approval
Left to right: how a process you already run becomes work an agent does. The purple step is where a person decides. Nothing after it happens without that yes.
A sample SOP, step by step
A quote request from a website, for a business that sells from a price list. Switch views to see the same SOP as the skill file the agent reads.
Answer a website quote request Sample
- 1Read the request and find the customer in the CRM, or draft a new contact.Agent
- 2Check the price list and stock for each item asked for.Read onlyAgent
- 3Draft the quote at the customer’s price level, with lead times from the stock data.Agent
- 4Flag anything outside the rules: a discount above the limit, an item not on the list, a new customer.Flags go to the top of the queueAgent
- 5Review the quote, edit it if needed, and approve it.Nothing is sent before this stepSales lead approves
- 6Send the quote from the sales inbox and log it on the deal in the CRM.After approval onlyAgent
- 7Follow up after three business days without a reply, using the approved follow-up text.Agent
- Changes a price list or a discount rule
- Promises a delivery date the stock data does not support
- Sends anything before the sales lead approves it
Who decides, and when
Each skill has one posture. You set it, and only you can move it.
Waits for you
Every new skill starts here. The agent drafts and a named person approves each one. Prices, budgets and anything public stay here.
Ships within limits
Once a skill has run clean for a set number of cycles, you can let it ship on its own inside limits you set, like routine replies. You can pull it back any time.
Signed by a person
If the output needs a licensed person’s signature, like legal, tax or medical advice, the agent only ever drafts. The person signs and stays responsible.
From a rough description to a skill
- 1
Show us how it is done
A call, a screen recording or the document you already have. Rough is fine.
- 2
We write the SOP
Steps, owner, rules and what done looks like. You correct it in plain language.
- 3
It becomes a skill
We add the tools it may use, the model tier and the approval step, then test it on past examples.
- 4
It runs supervised
Each draft waits for its approver. Edits are logged and fed back into the skill.
- 5
You decide when it graduates
Only you can move a skill to shipping within limits.
Bring one process
Pick a job your team repeats every week. We write the SOP with you and show you the skill.
Book a call