Use cases
Who this architecture is for.
The same structure, read from six different chairs. Each page states what it addresses in that situation and what it does not, because a page that fits everybody fits nobody.
- For agency ownersAgencies scale by hiring, train at real cost, and lose the training when people leave for the client or the competitor. The architecture in this book puts delivery in files instead.
- For ecommerce ownersRestocking, listings, customer questions, reporting, creative rotation. The work recurs, which is exactly the property that makes it writable, and writable is what makes it delegable.
- For consultants and freelancersThe usual answers are raise rates, hire, or work more. This is the fourth: write the method down well enough that something else can run the parts that are not judgment.
- For SaaS foundersSupport triage, onboarding, reporting, billing questions, the weekly numbers. The company around the product is where a small software team's time actually goes.
- For solo operatorsThe difference is structure. A solopreneur does everything personally. A company of one has departments, and the departments are folders that an AI operates while the operator judges.
- For small teamsThis is not only for companies of one. A small team gets more out of it, because the failure it prevents is the one small teams feel hardest.
The common thread
Every one of these situations has the same failure underneath it: the company lives in somebody's head, so it cannot be delegated, cannot be improved systematically, and resets whenever that person leaves or gets busy. The architecture moves it into files that an AI can operate and a person can judge.
What differs between them is where the judgment gates belong and which role is worth building first. That is what these pages are for.