People already named the jobs. Hire those.

Nobody is waiting for a list of thirty clever bots. The jobs already have names.

Invoice chaser. Inbox triage. Weekly report. Competitor watch. Meeting notes. Cold outreach. Those are not brainstorms. Those are holes in a Tuesday. Someone used to do them, or nobody did and you felt it on Friday.

The internet will sell you a catalog. Thirty documented bots. Fifty demos someone claims they audited. I did not sit through anyone's demo reel. I ran a company. The useful pattern is smaller than the list.

The shape of a fleet that actually runs

Four things. Skip one and you have a chat window in a costume.

One coordinator. Call it Chief. Chief does not chase invoices. Chief reads the board, hands work to the right teammate, and parks anything that needs you. Without a coordinator, you become the coordinator. That is how "I hired five bots" turns into five pings at 11pm.

One job per teammate. Clerk chases money. Mail sorts the inbox. Watch reads the competitors. Maker writes the thing. Scout finds the list. Two jobs in one teammate and they average. SEO wants long. Social wants short. One brain splits the difference and calls it a plan.

A standing routine. Weekdays at 9. Mondays at 7. After every call. A job without a clock is a prompt you will forget to run the week you actually need it.

A draft that waits. The reminder is written. The reply is ready. The report is in the folder. Send, spend, and "just ship it to the customer" wait for a human yes. Guessing is the failure mode. Unsure means it sits in Needs you.

That is the architecture. Specialist plus Chief plus no-send. Fancy names are optional. The clock is not.

What people actually hand over

These sit on the Octopus landing because founders already say them out loud. I am not inventing a zoo.

Invoice chaser. Clerk, weekdays at 9. Pull the overdue list. Write the reminder in your voice. Stop before send. You tap two. Bell & Rowe is always late. The teammate should know that by week three, or you are still the memory.

Inbox triage. Mail, weekdays at 7. Sort. Answer the four routine ones. Flag the supplier. The angry customer does not get a clever reply at 6am. It gets a draft and a flag.

Weekly report. Maker, or Clerk if the numbers live in the books. Mondays at 7. The artifact is a sheet or a short brief, not a feeling. You iterate the artifact. Next Monday is better because last Monday existed.

Competitor watch. Watch, Mondays at 7. What shipped. What they priced. What changed on the homepage. A brief, not a novel. You decide what to do with it.

Meeting notes. Maker, on every call. Write-up, three actions, owners. The teammate does not own the relationship. It owns the file.

Cold outreach. Scout finds the list. Maker writes the first pass. Mail never hits send without you. Cold email without a stop rule is how you get a reputation you then have to buy your way out of.

Customer support and release QA live in the same family if a person already does them on a clock. Same shape: one lane, a schedule, a draft or a ticket, a human on the edge.

What this is not allowed to mean

It does not mean a person. It will not walk onto a job site and read the room. It will not know the vendor is going through a divorce unless you write that down.

It does not mean unsupervised money, unsupervised legal, unsupervised customers. Those stay in your hands.

It does not mean one mega-bot that "just handles ops." That is how you get a confident mess with no owner.

If you cannot write the job like a hire ("Chase unpaid invoices every weekday at 9, draft the reminder, stop before send"), you do not have a teammate yet. You have a prompt you are emotionally attached to.

Which work actually fits is the filter. This page is the roster.

Agencies, isolation, the computer

If you have clients, the fleet still looks the same. The wall is the difference.

Per-client work should not share a login, a thread, or a hard drive with another client. Octopus gives you a dedicated workspace. Keys live in a vault, not in the chat. Access is per teammate: Clerk can read the books, Mail can draft, nobody else needs Stripe. Receipts show who touched what.

A dedicated VM for agencies is a conversation with us, not a checkbox on the pricing page. If you need that wall, say so. If you do not, do not pretend a shared laptop is "fine for now." Now is when the leak happens.

$99 covers OSS models, a computer, and a board. Bring ChatGPT, Claude, Gemini, or Grok if you already pay. No token markup. Stack accounts so a job can fall over to the next one mid-task. Every teammate gets its own email. We never train on your data. Seven days to get your money back if the Tuesday does not show up.

Hire the boring ones first

Start with Clerk or Mail. They have clocks. They have artifacts. You will feel the yes/no on send in week one.

Then Watch or Maker. Then Scout if you actually have a list worth working.

Chief last, or first if you already know you will hire three. Someone has to route. How you run that without it eating itself is the next conversation, not a personality pack.

The jobs were already named. Hire those.