HeadcountZero ← All entries

What is company as code?

Roles, procedures, and the reasons behind decisions kept as versioned files.

Glossary3 min readUpdated 1 Aug 2026

THE SHAPE ON DISKcompany/CLAUDE.mdthe front doororg/roles, access, assignmentsbrains/one folder per roleoperations/craft, memory, playbooksmarketing/same shape, different craftplaybooks/procedures a stranger can runWHY-LOG.mddecisions with reasoning attached

Definition

company as code (n.) – an arrangement in which a company's roles, procedures, and decision records are kept as versioned files rather than as knowledge held in the heads of the people doing the work.

Company as code means the company is written down: the knowledge a person would otherwise carry in their head sits in files that whoever takes over a role, person or agent, can read and run. The arrangement has three parts. Roles are repositories: a role is a directory holding what the role knows, the procedures it runs, and the standards it is judged against, readable by whoever or whatever currently occupies it. Procedures are playbooks: documents written to be run without asking their author a clarifying question. Decisions keep their reasons: a recorded choice states the condition that produced it, so a later reader can check whether that condition still holds instead of guessing at intent.

Version history then serves as institutional memory. The question a company usually cannot answer, why the process is shaped this way, is answered by the record rather than by the longest-serving person available.

Knowledge held in heads accumulates faster and costs nothing while the people stay. Its price is paid at every exit and every arrival: the company has been renting its own operating knowledge, and each departure repossesses part of it. The same knowledge in files is slower to produce and does not leave.

The costs are real and usually understated. Writing a procedure takes longer than performing it. Documents drift from practice unless each run amends them, and a repository that no longer matches reality is worse than no repository, because it is still trusted. What keeps it honest is amending at the moment of surprise rather than on a schedule.

The arrangement is also the precondition for anything agents do. An agent can occupy only a role that has been written down, and can run only a procedure specific enough to execute without its author present. A company that has not written itself down has nothing for an agent to run, which is why documentation precedes automation rather than following it.

The borrowed idea

The phrase adapts a convention from software operations, where the configuration of a system stopped being something an administrator remembered and became a file that could be reviewed, versioned, and rebuilt from nothing. The claim here is that a company's operating knowledge suffers the failure that convention was invented to fix: it works until the person holding it is unavailable, and is discovered at that moment to have been undocumented the whole time.

Prediction, not a result
“In my little group chat with my tech CEO friends there's this betting pool for the first year that there is a one-person billion-dollar company. Which would have been unimaginable without AI and now will happen.”
Sam Altman CEO, OpenAI, in conversation with Alexis Ohanian Fortune, 4 February 2024 · source

Company as code meaning, with an example

The phrase describes how the knowledge is handled, not what it is written in. Company as code, also searched as company as a code, treats a company's operating knowledge the way software teams treat source code: kept in files, changed through versions, readable by whoever comes next. Most of those files are plain text rather than programs. It does not mean the company sells software, and it does not mean every rule is a script. The unit is one role in one folder, a brain repo, and company as code is the sum of those folders plus the rules that hold across them.

A hypothetical: say one person pays supplier invoices and remembers which suppliers are paid early, which amounts get a second look, and why one supplier was dropped two years ago. Held in a head, all of that leaves when the person does. Under company as code, the role becomes a folder. A playbook holds the payment procedure, with a verify step after each action. A standards document states what a correct payment looks like. A decision record states why the supplier was dropped and the condition that caused it, so a later reader can check whether that condition still holds. A new hire opens the folder and runs the work. So does an agent allowed only to propose each payment for a person to apply.

The example carries the failure mode too. If the early-payment rule changes and nobody amends the playbook, the next reader follows the old rule with confidence, and an agent follows it on every run. The files beat memory only while each surprise is written back into them.