Module 1sales-page clause 2.1
A company is an org chart before it is a payroll.
When you picture “company” you picture people. But the thing that makes a company work is not the people — it is the structure: who decides, who checks, who remembers, who answers to whom. Payroll is one way to fill that structure. It is not the only way.
A role filled by an AI agent works like this: the agent does the work the role defines, under the authority the role grants, and produces artifacts you can inspect. What does not transfer is accountability. If the marketing agent publishes something embarrassing, “the agent did it” is not a defense to a customer, a tax office, or a court. You are the one operator. The agents extend your hands; they do not sign for you.
Keep that in mind and the design questions become simple. You are not asking “how do I replace my team with robots?” You are asking “which parts of my company produce, check, and remember — and which of those parts can a file do?”
The layer map
Our parent company runs fourteen roles in five layers. This is the whole org chart — no hidden floors:
| Layer | Question it answers | Roles |
|---|---|---|
| Strategy | What do we do — and refuse to do? | Chief executive, chief technology, critic |
| Product | What gets built, and how does it feel to use? | Product lead, UI director, interaction designer |
| Engineering | Is it built, verified, and running? | Fullstack engineer, QA director, devops engineer |
| Business | Do people find it, stay, pay — and what does it cost? | Marketing, operations, sales, CFO |
| Intelligence | What is actually true out there? | Research director |
Notice the shape. Three strategy roles, and one of them — the critic — produces nothing at all. Its only job is to stop the other thirteen from doing something fatal. More on that in Module 5.
Three roles on day one
You do not need fourteen. You need one of each fundamental function:
- A Builder — produces the artifacts: code, copy, plans, files.
- A Checker — reviews artifacts before they count as done. Verification is not optional when the author is fast, confident, and structurally incapable of being embarrassed by its own mistakes.
- A Recorder — keeps the baton file and the loop, so memory survives restarts. Production and verification without memory means re-deciding your whole company every morning.
Everything else is a specialization you add when the workload proves it. Add a role the week the work arrives, not before. A role with nothing to do drifts, and a drifting agent invents work — usually for you.
Build your layer diagram (25 minutes)
- List every job you personally did last week. Ugly list, twenty lines, no editing.
- Mark each line P, C, or R — produce, check, remember.
- Group the P lines into the five layers above. Some lines will not fit; those are usually chores for an automation, not a role. Leave them.
- Circle the three that would pay for themselves first — the ones that eat your evenings.
- That circle is your day-one roster. Everything else goes on a “someday” list with a date.