Founders are not bad at routing. They are too good at it. The rest of the team learned to wait.
There is a job in every founder-led company between five and forty people that nobody posted. The job is routing. You sit in the middle, the work comes to you, you decide who owns it, the work goes back out, the work returns with a question, you answer.
It looks like leadership. It pays nothing.
How you ended up doing it
On day one the company was you and a contractor. Every question came to you because you were the only one with the context. You answered fast. The contractor learned that asking you was efficient.
At seven people, you were still the fastest router because you had four years of context the new hires did not. At twenty people, you were the routing department by sediment. Nobody scheduled it. Nobody asked you to do it. It just kept happening.
I have seen this in every founder-led company I have spent real time inside, across every founder forum I sit in. Mine included for about three years longer than it should have.
What changes when you leave the job
Counterintuitive thing: when you actually leave it, the team gets faster, not slower. The routing tax has a hidden cost on the people you were routing for. They were waiting on you. The wait time was the bottleneck, not the routing itself.
First two weeks are uncomfortable. You feel out of the loop. The discomfort is the gap between your old position and your new one. The work is still shipping. You are just not in the middle of it.
Owner per surface, with bounds
Every recurring work surface gets one named owner. Inbound sales. Customer support. Partnership requests. Vendor renewal. Hiring referrals. Billing edge cases. Press inquiries. Each one belongs to a person (or a named agent role) by default.
The owner does not ask permission inside their bounds. The bounds are the same gates I described in the previous essay. Money cap. Public-claim line. Customer-data boundary. Inside those, the owner ships. Outside, the owner pauses for you.
AOS does this mechanically at install. Brand owns brand. Customer Success owns customer health. The CEO agent owns cross-department coordination. You can rename any of them, you can swap heads, but somebody is always named.
The Monday-morning test
When somebody on your team escalates to you, ask them: what would you do if you could not reach me until Monday? Eight times out of ten they have an answer. Two times out of ten they do not, and you give them a quick steer.
Most escalations are not decisions. They are permission requests. You are not the deciding party. You are the permission-granting party. If you make permission unnecessary inside the bounds, the escalations stop.
AOS handles this without the protocol. When a specialist agent is uncertain, it escalates to the department lead. The department lead either decides or routes it to one of the five gates. You only see the five.
The contract with your team
Your team needs to know what you read and what you do not. If everything is potentially on your radar, everyone hedges by sending you everything. The hedging is the noise that drowns out the actual signal.
The Friday founder summary is the contract. This is what I read. Everything else lives in Mission Control if you want to drill. The contract goes both ways. You commit to reading the summary. The team commits to writing it well, with the things you would actually want flagged.
Inside AOS the summary is generated automatically from the week's missions. You do not write it. You do not edit it. You read it in eight minutes on Friday afternoon and your team knows you read it.
What the first month looks like
Inbound to your personal Slack drops 60 to 80 percent inside week one if you actually hold the line. The early version of the drop is uncomfortable. The middle version is suspicious (where did the work go). The late version is the part where you start sleeping more.
Two weeks in, the discomfort shifts. You realize work is still shipping. Customers are still getting answers. Decisions that actually need you are arriving in the inbox already framed, with a recommendation attached.
By day 30 you are doing the four or five things only you can do. You are not faster. You are different.
If you do not have AOS yet
You can run the protocol with humans. Name an owner per surface. Set the cap. Write the Friday summary yourself for two weeks until somebody else can do it. Tell your team you read the summary and nothing else unless they tag you with one of the five gates.
This gets you 40 percent of the lift, with the discipline tax that you have to hold yourself to it. The version with AOS is the one where the discipline is built into the system and the lift is closer to 90 percent. Either is better than where you are now.