Skip to content
All guidesAI systems

One AI assistant is useful. A team of them changes how you work

The next step past chatbots is agents that do real work, and the step past that is teams of agents with a manager. Here is how orchestration works, what it fixes, and the lessons we learned running it in our own business.

5 min read

Most businesses meet AI as a chat window: you ask, it answers, you copy the answer somewhere useful. An agent is the step past that. It is the same kind of model, but given tools, instructions and a goal, so it can read files, search, write documents and check its own results until the job is done. That one change turns AI from a clever assistant into something closer to a junior member of staff.

We run our own company this way, and the honest lesson from months of daily use is that one agent, however smart, hits a ceiling. The interesting work starts when you run a team of them. This guide explains why, in plain terms, and passes on the lessons we paid for so you do not have to.

Why one agent hits a ceiling

An AI model has a working memory called its context. Everything it reads during a task sits in that memory: your instructions, the documents it opened, the results of every search. The catch is that this memory is finite, and quality drops as it fills. An agent that has read forty documents to answer one question is carrying thirty nine documents of clutter, and you can watch its judgement get vaguer as the clutter builds. People in the trade call it context rot, and it is real.

So the naive approach, one heroic agent that reads everything and does everything, gets worse as the task gets bigger. That is exactly the wrong shape for business work, where the valuable jobs are the big ones.

The team pattern

The fix is the same one businesses discovered long before AI: delegation. One lead agent owns the goal and keeps its own working memory clean. When it needs to know something, it does not go reading for an hour. It sends out a scout, a separate agent with its own fresh memory, whose only job is to dig through the material and come back with a short, useful conclusion. The lead gets the conclusion without the clutter.

A real example from our own operation: we needed to know the exact state of two codebases before a day of building, so the lead agent sent two scouts out in parallel, one per codebase. Each read hundreds of files and returned a one page map. The lead read two pages, not two codebases, and started building within minutes on accurate information. The same pattern works for research, audits, competitor reviews, anything read heavy.

The brief is everything

The biggest lever on a delegated agent's output is the brief you send it with. It cannot pop back mid task and ask what you meant, so the brief has to carry the goal, the constraints, exactly where to look and what a good answer looks like. Too little and the scout wanders. Too much and it drowns in detail before it starts. If you have ever briefed a freelancer, you already have the skill: complete, not verbose.

Never let the maker mark its own work

An agent that built something will happily tell you the work is finished and excellent. Ours are not allowed to. Anything substantial gets checked by a fresh agent that had no part in building it, the same way a decent firm separates the person who does the work from the person who signs it off. Cheap, fast, and it catches things the builder is too close to see.

The guardrails that make it safe

Autonomy without limits is how you end up in the news. Two rules keep an agent team safe enough to leave running while you get on with your day.

  • Anything that touches the outside world goes through a human. Publishing, posting, sending an email, spending money: the agents prepare all of it, but a person presses the button. The queue of things waiting for approval becomes a nice five minute morning routine rather than a risk.
  • AI never calculates a number anyone relies on. Figures come from ordinary, checkable code that gives the same answer every time. The AI can explain a number, draft the commentary around it, and flag when one looks odd, but it does not produce it. A confident wrong figure in front of a customer costs more than every hour the agents ever saved you.

What this means for your business

You do not need a lab to use this. Start with one job that is big, boring and read heavy: compiling a monthly report from six sources, checking supplier contracts against your terms, researching a shortlist of prospects. Give one agent the job of producing the final piece, let it delegate the reading, and put a human approval step before anything leaves the building.

We built our own operation on these patterns before offering them to anyone else, which means the advice comes from running the thing, not reading about it. If you want to work out where an agent team would pay off in your business, that is a conversation we enjoy having.