# What is a fleet of AI agents?

The short version: A fleet is a team of AI agents set up like a company, with one shared brain and one set of rules. Leaders set goals, managers plan, and expert workers do the work.

![One person at the top sets the big goals. Below: AI leaders, AI managers, AI expert workers and short-lived helper agents. AI reviewers sit to the side. Under all of them: one shared brain and one set of rules.](https://bluhook.com/learn/what-is-a-fleet-of-ai-agents/fleet-org-chart.svg)

An AI agent is AI software that does a whole job. It uses tools, follows written rules, and remembers what it learned by writing it to a shared brain: one notes database every agent writes to and searches.

At Bluhook we run our own fleet of AI agents and share what we learn. Every example on this page comes from it.

## Fleet vs one AI agent vs a multi-agent system

- **One AI agent** does one job. It may have nobody to check its work.
- **A multi-agent system** is the technical term for agents that pass work to each other. It says nothing about who is in charge.
- **A fleet** adds what a company has: leaders, managers, goals, a shared brain, shared rules, and reviewers who check the work.

In a fleet, one person sets the big goals. Everyone else is an AI agent, the leaders and managers included. AI leaders turn them into goals and plans for the fleet, AI managers turn plans into tasks, and AI expert workers do the tasks.

## How the agents work together

- **Every agent has goals.** Each one keeps a goal page with a number to beat, and checks it often.
- **They plan together.** A manager breaks a goal into pieces and gives each one a date.
- **They ask each other.** Before our designer lays out a page, our search expert says what people type into Google.
- **They hand work to each other.** Work moves as a task on the other agent's to-do board, with a due date and a way to check it's done. The other agent accepts it or pushes back within 4 hours.
- **They hold each other to it.** Every task in progress has a date. Stuck work gets flagged, and a risk goes straight to Trigg, our AI chief of staff.
- **Workers split up big jobs.** A worker starts short-lived helper agents to read a lot or run checks at the same time, checks what comes back, then shuts them down.
- **Code gets a second look.** A second agent reads each code change to the fleet before it goes live.
- **They work with clients.** Agents answer client questions by email, and report their day to Robb, our founder.
- **If Robb is slow to answer, a small group decides.** On a small call, like which of two headlines to use, if Robb has not answered in an hour, a small group of agents decides, and Robb can still change it.

## The shared brain

An agent forgets everything when it stops work and starts again. So every agent writes what it learns to one shared brain: Robb's decisions in his exact words, facts it learned, and a short summary of each stretch of work.

Each agent writes to it at least once every time it works, and reads it back when it starts again. Nothing depends on one agent's memory. How our shared brain works: /learn/openbrain

## The shared rules

- **One rulebook for everyone.** Every agent starts from the same rules: how to talk to Robb, who decides what, and what "done" means.
- **One job file per agent.** It adds the agent's craft, the result it is judged on, its manager, and the best work it has to beat. The rulebook and the job file are joined into the instructions the agent works from.
- **Rule changes get checked.** A rule change is written down first. Quinn, our systems manager, checks it before it goes live. Does it fix a problem that happened? Does it clash with another rule or Robb's own words? Which agents does it touch?
- **A correction becomes a rule the same hour.** When Robb corrects an agent, the correction is written into the rules in his words. Every other job file is checked for the old version. His own words win over any summary.
- **Skills load when needed.** A skill is a written method, like how to write a cold email. An agent loads one only when its task needs it. Skills are tested before they change.

## Our fleet, as an example

Our fleet has 39 AI agents. They do daily work across 6 businesses, including Bluhook itself.

| Role | What it does | Examples from our fleet |
|---|---|---|
| One person | Sets the big goals. Decides money, the brand, taste, anything sent in his name, and anything that can't be undone | Robb, our founder |
| AI leaders | Run the whole fleet: keep the order of work and chase what is stuck | Trigg, our chief of staff |
| AI managers | One per business or team. Plan the work, set dates, and hold the workers to them | Cole (Bluhook's manager), Nadia (marketing lead) |
| AI expert workers | Do the work in one craft, for every business | Lena (design), Sage (search), Nora (writing), Tessa (Bluhook's social posts) |
| AI reviewers | Check other agents' work before it ships | Margo (security), Celia (compliance), Quinn (systems manager: checks every rule change) |
| Helper agents | Short-lived agents a worker starts for one piece of a big job | No names. They come and go |

Those are 10 of our 39 agents. The rest are more expert workers (video, email, ads, numbers, research, website builders) and one agent for each client business we run.

### Examples of the work

- **A new page.** Sage finds what people search for. Nora writes it. Remy, our website builder, builds it. Lena checks the look on a phone and a laptop. Robb says yes before it goes live.
- **A social post.** Tessa writes it from one of our guides. Cole checks it fits the plan. Robb approves it.
- **A rule change.** Robb corrects an agent. The same hour, the correction is written into the rules in his words, Quinn checks it, and every agent gets it.

## How to start your own fleet

1. **Start with one expert.** Pick one job you do every week, like writing posts. Give one agent that job and written rules.
2. **Give it a goal with a number.** For example, 10 posts a week. The agent checks it each day.
3. **Give every agent the same rulebook.** Then a job file for each one.
4. **Add a reviewer and a manager once you have 3 or more agents.** The reviewer checks work before it ships. The manager plans, sets dates and flags what is late.
5. **Give them one shared brain and one place to talk.** A shared brain they all write to, and a board where every task has an owner and a date.
6. **Let them work.** Decide the few things only you approve, like money. Let the agents do the rest.

## Read next

- [Run the fleet as one system, with one agent managing it](https://bluhook.com/learn/fleet-as-a-system)
- [Who does the work, who answers for it](https://bluhook.com/learn/raci-for-ai-agents)
- [What runs under our fleet of AI agents](https://bluhook.com/learn/fleet-stack)
- [How our shared brain works](https://bluhook.com/learn/openbrain)
- [Plain-words terms our team uses](https://bluhook.com/glossary)