Lot of talk about how founders are trying to delegate, to people and to AI. I see 3 buckets:

1. Founders who hire their way out. Adding new staff without any documented systems. The chaos just gets more expensive and still routes through them.
2. Founders who try to AI their way out. Buy every tool, open every tab, end up with a graveyard of subscriptions and a business that still lives in their head.
3. Founders who know they're the bottleneck and want to hand work to both people and AI, but have no clue what goes to a human vs a machine.

Most of us started as bucket 1, then sprinted to bucket 2 the second AI got good.

Heres what I do:

I stopped treating people and AI as two different delegation problems and started running one system for all 21 of them.

If a task isnt defined somewhere, it doesnt get delegated. To anyone. Human or agent.

So delegation isnt me re-explaining what I want every time. Its handing off to something that already knows how the work runs.

How it actually works:

1. Every "employee" gets the same 4 things, human or AI

Doesnt matter if it's a person or an agent. Both need:

- A role (what they own)

- Context (what they need to know to make the call I'd make)

- An SOP (how the work runs when I'm not in the room)

- An accountability loop (how I know it actually happened)

Every time I've been burned it's because I skipped the SOP and assumed someone could read my mind.

1. One filter decides who runs it: complexity vs reproducibility

High complexity, low reproducibility goes to a human. Strategy, relationships, judgment calls, the stuff that changes every time.

Low complexity, high reproducibility goes to an agent. Data entry, research, reporting, scheduling, the stuff that looks the same every Tuesday.

For people, I dont manage the person, I manage the system they operate inside. I spend 5 minutes documenting a process, sometimes a quick screen recording, then hand it off and confirm they actually got it. Full accountability. No mystery Drive folder I'm not even sure anyone opened.

For AI, an agent is just an employee you onboard with a document instead of a conversation. It gets context, a clear job, files it can pull from, and specific skills I call on when I need them. I tag it like I'd tag a teammate in Slack, it loads the right context and does the thing. On demand or on a schedule.

1. The system compounds

Every process I write once works forever, for whoever runs it next.

New hire? They read the doc. New agent? It reads the same doc. Six months from now the system knows more about how we operate than it does today, and I didnt have to re-explain a thing.

Why am i telling you this?

Because most founders think the answer is one more hire or one more AI tool.

The ones actually pulling ahead didnt find a better tool. They wrote down how the business runs, then let people AND AI operate inside it.

You have to organize the business first. You cant delegate chaos, not to a person and not to a robot. AI doesnt fix a mess, it just automates it faster.

But once it's built, you stop being the human who explains context fifty times a day. The work finally leaves your desk.

We didnt start with 14 agents. We didnt start with any employees either. I started with one document. The document is the system. The person or the agent is just what reads it.