Make a clear, safer operating decision.
You will be able to tell when a simple rule, a human-written response, an AI assistant, or an agent is the right fit. That decision keeps the build cheaper, easier to test, and easier to explain to a client.
Good agent work is useful before it is impressive.
A lead-routing rule does not need a model. A high-stakes refund should not be handed to an agent. The useful middle ground is work that needs judgement from bounded context, has a repeatable outcome, and still has a named human owner.
Make the relationship visible.
The language that keeps the work clear.
Work through the decision in order.
Name the job
Write one sentence: ‘When this happens, help this person reach this outcome.’
List the judgement
Underline the parts where rules alone break down: unclear intent, incomplete facts, or several valid next steps.
Separate actions
Mark which actions are safe to automate, which need approval, and which must stay human.
Choose the simplest design
Use a rule where a rule works. Add an assistant or agent only where its judgement has a measurable purpose.
A realistic, bounded implementation.
A home-services business wants faster replies to web enquiries. The first version does not need an ‘AI sales employee.’
A form rule stores location and service type. An assistant turns the customer’s free-text note into a short summary. An agent may ask one approved follow-up question when the request is unclear, then routes the record to the right dispatcher.
The dispatcher still owns urgent requests and pricing. The result is a useful hybrid workflow, not a vague automation promise.
Use this copyable working template.
Adapt it to the client’s evidence, policy, people, and tools. Do not treat placeholders as approved instructions.
Put the operating system around the agent.
Use forms, CRM routing, automations, and task ownership for the deterministic parts first. Add AI only where it improves a clearly defined handoff or decision.
Before you move on
- Choose one repeated workflow from your own business or a prospective client.
- Classify every step as rule, assistant, agent, or human decision.
- Remove any agent behaviour that has no clear reason to exist.
- The job has one user and one intended outcome.
- The agent is not being used where a rule is enough.
- A human owner is named.
- High-impact actions are not implied to be autonomous.
Build the operating layer around your agent.
Use the free Spacebrain workspace to keep contact context, handoffs, tasks, automation, and reporting together.
