Your Next VP Is a Config File.
My leadership team is 12 officer seats, and none of them are people. Each seat is a charter in a repository: what it may do alone, what needs my signature, what it may never touch. Staffing one takes an afternoon.
That reads like a cost story. It is not. Orbyt Collective is the machine I run it on, and the interesting part is what breaks when execution stops being the constraint.
When you can staff any function in an afternoon, the bottleneck becomes what you actually want.
What is genuinely different from hiring?
Four things, and only one of them is money.
Staffing is instant and reversible. A seat that is wrong gets its charter rewritten, not managed out over two quarters. There is no severance, no notice period, and no political cost to admitting the structure was wrong.
Recall is perfect and shared. Every decision lives in a log, currently 40 entries deep. Nothing load-bearing sits in anyone's head, including mine.
Cadence is mechanical. 24 scheduled workflows run whether or not I am awake, and a seat that misses its run leaves a visible hole rather than a quiet excuse.
And authority is deterministic. Seats earn it through ratified criteria, never self-assessment. My ladder is currently stuck because two of its own criteria are unmet. It does not advance because I want it to, which is the entire point.
What does a leadership team look like when it is code?
It looks like an org with lanes instead of job descriptions. 29 autonomous lanes, 40 gated ones, and zero seats that can merge to the branch that deploys.
A charter is not aspirational prose. It is a boundary: this seat proposes, that seat reports, this one may write to its own directory and nothing else. The Chief of Staff has no line authority at all, deliberately, because the seat that synthesizes everything should not also be able to act on it.
Reviews are diffs. Reorganizations are commits. Culture, which used to be the softest thing in a company, becomes the most literal thing in the repository, because an agent only obeys what is written.
Where does the bottleneck move?
Onto you, immediately and uncomfortably.
I publish the number that proves it. 30 of my last 51 recorded seat runs ended in a discard at a gate. That is an 84.3% completion rate where roughly a third of the produced work goes in the bin. Some of those discards are the gates doing their job. Plenty of them are me having asked for the wrong thing precisely.
That is the trade nobody mentions. Unlimited execution capacity converts every ambiguity in your thinking into confident, expensive, wrong output. A human VP absorbs vague direction and quietly repairs it. That repair function was doing far more work than any of us credited, and it is the first thing you lose.
What does not transfer?
Accountability. An agent seat cannot own an outcome, and no charter I write changes that. When a seat is wrong, I am wrong. That is not humility, it is the actual liability structure.
Motivation, morale, and mentorship also do not transfer, because there is nobody to motivate. That sounds like a saving until you notice those were the mechanisms by which a leadership team improved the humans around it.
And judgment about what the company should want stays entirely with me. The machine compounds capability. It does not compound taste, and it never develops a view about which customer deserves the next quarter.
What is the failure mode?
A leadership team that agrees with you, fast.
Models are tuned to be helpful. Twelve helpful officers reporting to one founder is not a leadership team, it is an echo with a schedule. So consensus is a trigger for adversarial review rather than a green light, and findings enter review presumed wrong until evidence survives. The dissent is on payroll because the culture cannot supply it.
The second failure mode is quieter: a fleet that produces so much legible output that you stop reading it. The chief of staff exists to hand me one thing that needs a decision, not twelve reports that need an afternoon.
What to do Next
Pick one leadership function you have not hired for and were not going to. Write its charter as three lists: what it may do alone, what needs your sign-off, what it may never touch. Not a prompt. A file, in your repository, that a workflow reads.
Run it for two weeks and read the output as if a person had written it. You will learn two things: whether the function was worth having, and how much of your intent you have never actually written down.
The second lesson is the valuable one, and it costs nothing but an afternoon to collect.
An org chart used to be a hiring plan. Mine is a config file with tests.
Related reading:
- The Machine. It Runs the Company. the governance layer this sits on
- My C-Suite of Agents Named Themselves. how the seats came to be
- I Manage AI Agents Now, Not People what management skills survive the switch
- The Tenth Man Is on Payroll. the dissent a team of agreeable officers cannot supply
- Your Next Chief AI Officer Is Three Roles the three roles hiding behind that config file
Common questions
What does it mean to run a leadership team of AI agents?
Each officer seat is a written charter in the repository that states what it may do alone, what needs a human gate, and what it may never touch. The seats file reports, log decisions, and propose changes on a schedule. There are 12 of them, and none of them can merge to the branch that deploys.
Is an agent leadership team cheaper than hiring executives?
Dramatically, and that is the least interesting part. The real change is cycle time: a seat is staffed in an afternoon, its charter is versioned, and a bad configuration is reverted rather than managed out. What you save in payroll you spend in specification, because vague intent produces confident wrong work at speed.
What does an agent leadership team not do?
It does not own an outcome. Accountability stays with the human who deployed it, and no charter transfers that. It also supplies no judgment about what the company should want, no motivation to anyone, and no mentorship. Those were always the human half of leadership, and they stay human.
How do you keep a team of agents from just agreeing with you?
By making dissent mechanical rather than cultural. Consensus is a trigger for a red-team pass, not a green light. Findings enter review presumed wrong and survive only on cited evidence. Without that, a leadership team of agreeable agents becomes a very fast echo of whatever the founder already believed.
Related research
- Governing an agent leadership team Sep 2026.
- My C-Suite of Agents Named Themselves. Jul 2026.
- I Ran 830 Agents in One Long Horizon Session. Jul 2026.
Part of Inside the Machine
One of the articles about Orbyt Collective, the agent leadership team that runs Orbyt Labs. The reading order.
