Give it the work that comes back as a draft

Most "use cases" are chores you already hate, wearing a robot hat. That is not an insult. That is the filter.

The work that fits a teammate is recurring. It ends in a draft you still want to see. If you cannot point at the artifact (the reminder, the brief, the ticket, the build), you do not have a use case. You have a wish.

The roster is already named: Clerk, Mail, Maker, Scout, Watch, plus Chief to route. This page is which piles of work survive contact with a Tuesday.

1. Watches and briefs

Someone should notice. You should not have to remember to notice.

Competitor pages on Monday at 7. Vendor prices once a quarter. A mention of your name that is not a compliment. A number in the sheet that moved the wrong way.

Watch does this. The output is a brief, not a TED talk. What changed. Since when. What you might do. You decide. If it "just reached out" because the brief felt spicy, you hired a loose cannon.

Weekly numbers live here too. Maker or Clerk, Mondays, one sheet. Iterate the sheet. Do not ask for "insights" with no column to put them in.

2. Drafts for review

This is the biggest honest pile.

Invoice reminders. Inbox replies. The outreach first pass. Meeting notes with three actions and owners. The newsletter. The pricing page that cannot go live until you say the bump is real.

Maker writes. Mail drafts. Clerk writes the nudge. None of them hit send. You keep the relationship, the legal risk, and the "we do not talk to customers like that."

Cold outreach is in this bucket even if Scout found the list. Finding is not sending. Sending without a stop is how a domain gets burned.

Customer support sits here if the teammate answers the routine four and flags the rest. Continuous does not mean unsupervised. It means the inbox is always being sorted, and the weird ones wait.

3. Portal work the API cannot see

A lot of your business still lives in a website that was designed in 2014 and will not give you a key.

Insurance portals. City permit sites. A vendor's "partner dashboard" that only works in Chrome if you squint. The bank export that is a button, not a webhook.

A teammate with a computer can sign in, click the thing, drop the PDF in the folder, and write you a note. That is a real job. Do not wait for the API. The button is the job.

Scope the login. Read-only when you can. Receipts on every session. If the portal can wire money, it waits for you. A browser is a pair of hands you can still slap.

4. Build and test on a computer

Release QA on every deploy. A staging click-through. A script that was supposed to be a one-off and became the business.

Maker or a named builder teammate gets a machine, a repo, a checklist. It opens the PR or files the bug. It does not push to prod because you had a good feeling.

A teammate can run the suite. You still read the failure that would make a customer write in all caps.

The computer is the point. Chat cannot hold a browser, a terminal, and last Tuesday's fixture data in a way you can inspect. A desk can.

5. Personal ops

Calendar. Travel. The "remind me if Bell & Rowe still has not paid" you say at 6:10pm with the laptop half closed.

This is real work and it is also how founders hide from the other four buckets. If personal ops is the only thing you hire, you bought a fancy alarm clock.

Do it anyway for the jobs that already steal the morning. Then put Clerk on invoices. The personal pile should shrink because the business pile is no longer living in your head.

Chief can hold the "park it until November 1" instruction so Maker does not write the page early. That is ops. That is also a stop rule. Keep both.

What does not fit (say it before the vendor does)

One vendor, one ceiling. If you only bring Grok, you get Grok's usage, Grok's outage, Grok's taste. Fine for a lane. Fragile for a company. Octopus lets you bring ChatGPT, Claude, Gemini, Grok, or the OSS models in the $99 plan. Stack accounts. Work continues mid-task on a fallback.

Email as a trigger, not a firehose. A teammate with its own inbox can be mailed, can start a thread, can receive the reply. That is how follow-up lands with the one who started it. What it cannot do is spray a list at 8am because Scout got excited. Your yes is the trigger for anything that leaves. Their inbox is the trigger for work that comes in.

A shared machine versus a wall. One computer for your studio is a gift. One computer for two clients is a story. Dedicated workspace is the default on Octopus. Dedicated VM for agencies: talk to us. Do not "just for this month" two books onto one disk.

Client-account walls. Per-teammate access. Clerk reads Stripe. Mail never does. Scout never sees the other client's Drive. Vault for keys. Receipts if you have to explain it later. We never train on your data. You still have to not paste the other client's roster into the wrong thread.

Judgment, rooms, money. It will not read the room. It will not be the friend. It will not spend. Those are not upcoming features. Those are you.

A test you can run

Pick one recurring job that already ends in a file. Put it on a clock. Require the yes. See a Tuesday.

If you cannot name the file, keep it a prompt. If you can, hire the teammate and let Chief hold the board.

Sign up when you have the sentence. Not when you have a list of thirty.