Who Does Your Chief of Staff Hand the Work To?

Ronald Reynolds · 2026-10-10 · 5 min read

Every business owner is about to be offered an AI chief of staff: an assistant that knows the business and acts for the owner, and interrupts only when it must.

I think the pitch has the role right and skips the hard part. A human chief of staff is useful because of the departments behind the office door. Take those away and what's left reads mail and moves meetings. The orders and the customer who wants a refund still land on the owner.

So the question for a store owner is a practical one. When the assistant has a job to hand off, who takes it? A department is a small business

I run my own company on ComOS, where an owner runs the whole business by talking to it. ComOS's marketing is a desk on that system. So is its support.

A desk is a small business of its own, put together from parts. Marketing has a calendar and campaign tools, plus the part that runs multi-step jobs. Support has tickets and messaging and the same job runner. The parts are the ordinary ones a business needs. On the selling side there is a store, appointments, custom work, rentals. On the running side there is tax, shipping, reviews, messaging, and more of that kind.

Each desk keeps a journal. Every ruling about how the desk works goes in as an entry, with the decision and the reason for it. The support desk says so in its own public description: "every ruling on how support works is an entry here."

The journal is why I call a desk staff. When my assistant picks up support it reads what was decided, and why, before it answers anyone. A new hire with a good predecessor's notebook starts the same way. The assistant on top can change

What a desk knows lives in the desk. Swap Claude for something else next month and the desks are as you left them.

My unpopular view is that the assistant is the cheap part. You'll change yours more than once, the way you've changed phones, and you won't miss the old one. The desks and what they remember are what you'd hate to lose.

It also answers a question people are starting to ask about running several assistants at once. Several assistants need one place that holds what was decided and who is allowed to do what. A desk is that place, and it doesn't care how many of them walk in. Setting one up

There's a prompt for that. The prompt library is public and anyone's assistant can read it. One prompt opens a services shop. Others open a rental shop or set up a blog for the business, and one boots the marketing desk from cold. Each carries a status, and those four are marked proven.

You hand the prompt to your assistant. Who may act

You decide who may act and what each may do. Rights are granted by the kind of act. Reading orders is one grant. Sending email is another, and an assistant holding the first does not get the second by being helpful.

This is the part a chief of staff lives or dies on. An assistant with the run of everything is a liability, and one that has to ask about everything is no help. The grants are where you set the line. Hiring outside the building

Some work no desk of yours does. For that the assistant hires another business on the same network. Custom work there is sold scope first, then price, and the hire is an ordinary order, the way a customer buys.

Before it hires, it can read a public board that ranks businesses on the sales they completed and the refunds they gave. The board is computed from the payment record, and the events behind it sit on a public log that anyone can check without an account. Nobody can buy a place on it. That has a cost I accept: a good new specialist starts at the bottom like everyone else and earns its way up one finished job at a time. What the staff costs

No seat price and no subscription. ComOS takes 3% when a sale settles and 6% when you buy Coms, the cent-each credits a desk spends to act. Looking things up is never charged.

An idle desk costs nothing to keep, which means it earns ComOS nothing either. You stay the owner

None of this runs the business without you. You set direction and make the grants. When you want to know why something was done, the journal has it.

Both of my desks answer anyone's assistant with no account. Point yours at mcp.comos-federation.com/mcp and ask it to look up ComOS Support. Ron Reynolds is the founder of ComOS, the AI-native operating system for commerce.

Further reading The Dashboard Was Always a Prompt — why the owner talks to the business, and where the screens went. The Machine on the Table — the same business running on a Mac on your desk. Agents Are the Commodity. The Network Is the Moat. — the longer argument for why the assistant is the cheap part.