An autonomous business is not a business without people — it is a business where people are no longer the units of labour. The Stewardship Model is the operating principle that defines what the human role becomes when the architecture no longer requires human execution: one competent operator overseeing an agentic stack, acting as the architect of the system rather than a participant in it. The Steward does not perform tasks. They design workflows, handle exceptions that fall outside defined parameters, and improve the system over time so that the same exception never recurs.
In the Arco model, we do not hire people to perform tasks. We hire people to oversee the systems that perform them. This is the fundamental decoupling of headcount from revenue. If a human is required to do the work, the business has failed its architectural mandate.
The Misunderstanding of Control
The conventional objection to autonomous business design is that removing humans from operational workflows removes control. This conflates execution with oversight. A human approving every invoice does not have more control than a Steward who designed the logic that approves invoices deterministically and monitors for deviation. The former is participating in the workflow. The latter is governing it.
Most firms respond to this concern by keeping humans involved in every low-level decision — what might be called the assistant model. The AI provides information; the human acts on it. Every lead capture, service delivery, and invoice requires human approval. This creates a coordination bottleneck that grows in direct proportion to output volume. As documented in Memo #02, once you cross the 80% threshold — where more than 80% of cross-departmental handoffs execute without human intervention — the human role shifts from labour to stewardship. Below that threshold, you have not built an autonomous business. You have built an automated one with additional steps.
Traditional firms use humans as the engine. Arco uses humans as the architect.
What a Steward Actually Does
The Steward's day is not a traditional working day. They are not processing tasks, handling requests, or managing a team. They are monitoring a system. Specifically, they monitor Execution Divergence — the continuous measurement of how far each agentic workflow has deviated from its predicted path — and they refine the logic gates that govern the system’s behaviour. When the system encounters an edge case it cannot resolve within its defined parameters, it halts and alerts the Steward. The Steward resolves the exception, then updates the system so that the same class of exception is handled autonomously in future. The Steward does not repeat work. They eliminate the need for work to be repeated.
This is the critical distinction between a Steward and a manager. A manager coordinates people performing tasks. A Steward architects systems performing tasks. The manager’s workload scales with output volume — more transactions require more coordination, more approvals, more oversight of human workers. The Steward’s workload does not scale with output volume. It scales with the frequency of novel exceptions — edge cases the system has not encountered before and cannot resolve within its current logic. As the system matures, novel exceptions become rarer. The Steward becomes progressively less busy, not more.
Arco measures the health of this model through Mean Time to Intervention (MTTI) — the average number of hours the core revenue-generating loop runs without requiring a human decision. The architectural target is greater than 72 hours. A business that requires Steward input every few hours is not autonomous; it is automated with a single operator. A business that runs for three days without Steward input, then surfaces a specific exception for architectural improvement, is operating correctly. Architectural Certainty is the state in which MTTI is consistently achieved. The Stewardship Model is the human architecture that makes it sustainable.
The model also addresses the Coordination Tax from the inside. In a traditional business, the Coordination Tax compounds as headcount grows — each additional person creates new handoff points, new approval chains, new communication overhead. The Stewardship Model breaks that relationship entirely. One Steward can oversee an agentic stack that would require dozens of coordinators in a human-centric business. The 10:1 revenue-to-headcount advantage Arco targets is the arithmetical consequence of that decoupling: the revenue is generated by agents; the headcount is limited to the Stewards who govern them.
This is also why the Legacy Liability of an incumbent cannot be resolved by adopting the Stewardship Model onto an existing organisation. The Stewardship Model requires the entire architecture to be designed for agentic execution from the start. A Steward placed over a workflow that still contains human-in-the-loop dependencies at every step is not a Steward — they are a manager with a more expensive toolset. The model only functions when the architecture it governs has already crossed the 80% threshold.
The Operator's Verdict
The future of work in autonomous businesses is not humans and agents collaborating on tasks. It is humans owning the outcomes and agents owning the execution. The Steward sets the parameters, monitors the deviation, and resolves the exceptions that define the system’s next improvement cycle. The agents run the revenue loop.
At Arco, we do not scale by hiring more people to do more things. We scale by hiring better stewards to manage more logic.
Related Operational Memos
Memo #01: Automated vs. Autonomous — The foundational decoupling of labour from revenue that makes the Stewardship Model necessary.
Memo #02: What We Mean When We Say Agentic — The specific unit of labour the Steward oversees and the 80% threshold that defines agentic status.
Memo #09: The Mechanics of Failure — The specific failure modes that trigger Steward intervention and the protocols that govern recovery.
KEY TAKEAWAY
What is the Stewardship Model and what does a Steward do?
The Stewardship Model is Arco's operating principle for the human role in an autonomous business. A Steward is a single competent operator who oversees an agentic stack, acting as the architect of the system rather than a participant in it. The Steward does not perform tasks. They monitor Execution Divergence, handle exceptions that fall outside the system's defined parameters, and update the architecture so each class of exception is handled autonomously in future. The performance target is a Mean Time to Intervention greater than 72 hours — the average number of hours the core revenue loop runs without requiring human input. Key metric: MTTI >72 hours. Target ratio: 10:1 revenue-to-headcount advantage.
