Multi-agent systems split one job between several AI agents that work like a small team. This lesson explains how they work, where you will meet them, and when they are worth the extra cost.
In this lesson
- What a team of AI agents is: a lead that plans, specialists that work in parallel, and a reviewer that checks.
- The two main patterns: several agents trying the same task, and a lead splitting a job into parts.
- Where you will meet AI teams in products from the main AI makers, as they describe them.
- What it costs, and when it is worth it.
- Your role: the manager who sets the goal, the limits and the sign-off.
The team idea, and its limits
Lesson 7 described one agent working through a task step by step. Some systems split a job between several agents instead, a bit like a small team: a lead agent (sometimes called an orchestrator) plans the work and hands out parts, specialist agents do those parts, often at the same time, and a reviewer checks the result before it comes back to you.
The org chart below is drawn in the same way as the team charts in Lesson 5, so you can see the same shape used for people and for AI. People are amber; AI agents are ink and grey.
Org chart: you, a person, at the top, setting the goal, the limits and the sign-off. Under you, a lead agent that plans, splits and merges the work. Under the lead, four specialist agents in a row: research, drafting, data and checking. All their work comes together at a sign-off by a person before anything leaves the business.
- You: set the goal, the limits, the sign-off
- Lead agent: plans, splits, merges
- Research agent
- Drafting agent
- Data agent
- Checking agent
- Lead agent: plans, splits, merges
The metaphor helps, but do not take it too far. AI agents are not colleagues:
- They do not remember yesterday unless the system is built to keep notes.
- They do not know when to push back. A person might say “this brief doesn’t make sense”; an agent will usually do its best with it.
- They do not own the result. The business does, which means you do (Lesson 10).
That is why the chart has you at the top, setting the goal and the limits, and a sign-off box at the bottom before anything leaves the business.
Two patterns in multi-agent systems
Two patterns. Parallel: one question goes to several agents that each try the same task; a lead agent compares and merges their answers into one answer, which you check. Division of labor: a lead agent splits the job; research, drafting and data agents each do a part; a reviewer agent checks; the parts are merged into one result; a person signs off.
Parallel: several agents try the same task
Division of labor: each agent does a part
Parallel: several agents try the same task
Several agents work on the same question at once, independently. Their answers are compared, and the best one is chosen or the answers are merged. The idea is the same as asking three people for an estimate and comparing: where they agree you can be more confident, and where they differ you know to look harder.
Division of labour: a lead splits the job
A lead agent breaks a big task into parts and sends each part to a specialist agent. For example, to prepare a report on a new market, one agent might research competitors, another regulations, another prices, while a fourth checks the sources. The lead then combines their work.
Anthropic, which makes Claude, has described how its own research feature works this way: “The lead agent analyzes it, develops a strategy, and spawns subagents to explore different aspects simultaneously” (Anthropic). In its internal tests, “a multi-agent system with Claude Opus 4 as the lead agent and Claude Sonnet 4 subagents outperformed single-agent Claude Opus 4 by 90.2%” on research tasks. That is the company’s own test of its own product, so treat it as a description of what the design is for rather than independent proof.
Where you will meet AI teams
Most businesses will meet AI teams inside products rather than build them. The main AI makers describe features like these on their own pages (each read on the date shown in the table):
- Anthropic (Claude). Its Research feature “uses multiple Claude agents to explore complex topics more effectively” (Anthropic). In Claude Code, its coding agent, Claude can hand side tasks to sub-agents: “Each subagent runs in its own context window with a custom system prompt” (Claude Code docs).
- Google (Gemini). The Gemini Enterprise app offers “Google-made agents like Gemini Notebook and Deep Research,” and lets businesses “build custom agents for your specific workflows in Workflow Builder” (Google Cloud).
- Microsoft (Copilot). Copilot Studio, for building company agents without code, offers “multi-agent orchestration for complex processes, routing tasks to the right agent” (Microsoft).
- Mistral AI. Its developer platform lets agents hand work to each other: “Handoff capability to use different agents as part of a workflow” (Mistral docs).
- OpenAI (ChatGPT). ChatGPT Work takes a goal and “gathers context, makes a plan, and checks in when judgment or approval matters” (OpenAI). For developers, its agent tools let agents “plan and complete tasks using tools, work with other agents” (OpenAI developer docs).
- xAI (Grok). In the Grok app, “Multiple agents work in parallel for deeper answers on the hardest questions” (xAI). When it launched Grok 4 Heavy in July 2025, xAI described “parallel test-time compute, which allows Grok to consider multiple hypotheses at once” (xAI). Its developer platform has a research mode in which several agents discuss a question and “a designated leader agent is responsible for synthesizing the discussion” (xAI docs).
The two patterns above map onto these: Grok’s parallel agents are the first; Anthropic’s Research, Copilot Studio’s orchestration and the developer tools that hand work between agents are the second.
The full table of agent features, with the date each was read:
| Maker | Assistant | Agent features, as the maker describes them | Date read |
|---|---|---|---|
| Alibaba (Qwen) | Qwen Chat | Not stated on the pages we read. | October 6, 2026 |
| Anthropic | Claude |
| October 6, 2026 |
| DeepSeek | DeepSeek (chat at chat.deepseek.com) | DeepSeek Harness: An agent harness for developers, in developer preview; the API docs also list guides for running DeepSeek models inside other makers' coding agents. | October 6, 2026 |
| Gemini (Gemini app; Gemini Enterprise app for business) |
| October 6, 2026 | |
| Meta | Meta AI |
| October 6, 2026 |
| Microsoft | Microsoft Copilot (formerly Microsoft 365 Copilot); Microsoft Copilot Chat (formerly Microsoft 365 Copilot Chat) |
| October 6, 2026 |
| Mistral AI | Mistral Vibe (formerly Le Chat) |
| October 6, 2026 |
| OpenAI | ChatGPT |
| October 6, 2026 |
| xAI | Grok |
| October 6, 2026 |
These products change quickly. Names, plans and prices in this section will date; the table is refreshed every quarter.
What it costs
A team of agents does more work than one chat, so it uses more computing, and on usage-based plans you pay for that. Anthropic reported that in its data “agents typically use about 4× more tokens than chat interactions, and multi-agent systems use about 15× more tokens than chats” (Anthropic). On a flat monthly plan the cost may show up as usage limits instead, or the feature may be reserved for a higher-priced plan.
There are other costs too:
- More ways to go wrong. Each agent can make mistakes, and the lead can combine them badly. A reviewer agent helps, but it is still AI checking AI.
- Harder to follow. With several agents working at once, it is harder to see why the final answer says what it does. Ask for sources and check them.
- Time. Teams of agents can take minutes rather than seconds.
When it is worth it
Anthropic’s own write-up is a fair guide. It says multi-agent systems “excel at valuable tasks that involve heavy parallelization, information that exceeds single context windows, and interfacing with numerous complex tools,” and that tasks which “require all agents to share the same context or involve many dependencies between agents are not a good fit for multi-agent systems today” (Anthropic).
In small-business terms:
Worth considering for:
- broad research, such as comparing many suppliers, competitors or regulations at once;
- big jobs with separate parts, such as preparing a tender response with pricing, method and references;
- checking important work, where having separate agents produce and review an answer catches more mistakes.
Not worth it for:
- simple tasks a single assistant handles well, such as a reply, a summary or a rota;
- tasks where each step depends on the last, where splitting the work only adds confusion;
- anything where the extra cost and time outweigh the gain.
Your role: the manager
With an AI team, your job is the one a good manager does with a human team:
- Set the goal clearly. What you want, for whom, by when, in what form.
- Set the limits. What sources the agents may use, what they may not do, how much they may spend, when they must stop and ask.
- Sign off. Read the result, check the sources behind anything that matters, and decide what leaves the business. That sign-off is the amber box at the foot of the chart, and it is never delegated to another agent.
Should a small business build one?
Rarely, for now. For most businesses, AI teams will arrive inside products: a research feature in an assistant, a help desk that uses several agents behind one chat window, an accounting package that drafts and checks. What matters is knowing what is happening behind the chat box, so you can judge the cost, ask the vendor how the work is checked, and keep your own sign-off. If you do want something built, start with one agent (Lesson 7) and add a second only when you can say exactly what it would do better.
Key terms
- Multi-agent systemSeveral AI agents working on one job, either in parallel on the same task or each on a different part.It can help with broad research and big jobs, but uses much more computing than a single chat.Lesson 8: AI teams · More in the glossary
- Orchestrator (lead agent)In a team of AI agents, the agent that plans the job, hands parts to other agents and combines their results.Lesson 8: AI teams · More in the glossary
- AgentAn AI given a goal, tools and permission to take several steps on its own, such as booking, filling in forms or updating records.Because agents act, their mistakes have effects. Start with a person approving every action.Lesson 7: From chatbot to agent · More in the glossary
- TokenA small piece of text, roughly a short word or part of one, that a model reads and writes. Usage is often priced in tokens.More in the glossary
- Human in the loopA named person who checks or approves AI’s work before it takes effect, and answers for the result.Lesson 10: Risks and rules · More in the glossary
Every term is explained in the glossary.
Try this
Think of the biggest research or preparation job your business does a few times a year, such as a tender, an annual review of suppliers, or a plan for a new location. Sketch it as an org chart like the one above: the parts a lead agent could hand out, what each specialist would do, what the reviewer would check, and what you would sign off. Then ask: would one good assistant, given the same brief, do nearly as well? If yes, use one.
Sources
- Anthropic, “How we built our multi-agent research system”, 13 June 2025. Read 6 October 2026. https://www.anthropic.com/engineering/multi-agent-research-system
- Anthropic, “Claude Code: subagents” (docs). Read 6 October 2026. https://code.claude.com/docs/en/sub-agents
- Google Cloud, “Gemini Enterprise”. Read 6 October 2026. https://cloud.google.com/gemini-enterprise
- Microsoft, “Copilot Studio”. Read 6 October 2026. https://www.microsoft.com/en-us/copilot/products/copilot-studio
- Mistral AI, “Agents: introduction” (docs). Read 6 October 2026. https://docs.mistral.ai/studio/agents/introduction
- OpenAI, “ChatGPT Work”. Read 6 October 2026. https://chatgpt.com/work/
- OpenAI, “Agents” (developer docs). Read 6 October 2026. https://developers.openai.com/api/docs/guides/agents
- xAI, “Grok”. Read 6 October 2026. https://x.ai/grok
- xAI, “Grok 4” (announcement, July 2025). Read 6 October 2026. https://x.ai/news/grok-4
- xAI, “Multi-agent” (developer docs). Read 6 October 2026. https://docs.x.ai/developers/model-capabilities/text/multi-agent
- All vendor facts as recorded in our vendor data file, pipeline/data/learn/vendors-2026-10.json, fetched 6 October 2026.