What is a company brain? A plain guide.
What one is made of, why a wiki is not one, and how a new hire learns the business from it. Written by a firm that runs its own business on one.
The short answer
A company brain is a set of linked pages on how a business works: its workflows, the systems they run on, the decisions behind them and the people who own them. Every person and every AI agent in the business reads it before acting and writes back to it when they learn something. It differs from a wiki in three ways: agents read it, not just people; the work keeps it current, not a person remembering to; and it is checked every day for pages that have gone stale or contradict each other.
What a company brain is made of
Four kinds of page do most of the work. Each one has a type, an owner and links to the others, so a question can start anywhere and follow the links to the answer.
Workflows
How a job is done, how often it runs, which tools it touches and which skill or person does it. The page an agent reads before it starts the job.
Systems
What each tool holds, what it is the source of truth for, and who owns it. So an agent knows where to look and where not to write.
Decisions
What was settled, when, by whom and why. The page that stops the same argument happening twice, and stops an agent undoing a choice it never heard about.
People
Who does what, who owns which workflow, and who to ask. Linked from every page they touch, so the graph knows who to route a question to.
Departments group the workflows. Meeting notes, client history and research link into all four. The test of a good page is simple: could an agent that has never met your team do the job from it, and know who to ask when it cannot?
Why a wiki is not a company brain
Most businesses already have a wiki, an intranet or a shared drive full of process documents. The content is often fine. What fails is who reads it, who keeps it current, and what happens when two pages disagree.
| A wiki | A company brain | |
|---|---|---|
| Written for | People browsing | People and every AI agent, before they act |
| Kept current by | Someone remembering to update it | The work: what a job learned is written back when it finishes |
| Structure | Pages by topic, loosely linked | Typed pages (workflow, system, decision, person) linked to each other |
| When two pages disagree | Nobody notices | A daily check flags stale pages, orphans and contradictions for a person to settle |
| Corrections | Said once in a meeting, then lost | Written down as a rule, so the next answer changes |
| Measured by | Page views | Whether the work it feeds gets faster against a measured baseline |
The difference that matters most is the second row. A wiki depends on someone choosing to update it after the work is done. A company brain is updated as part of the work: the agent that ran the job writes down what it learned before it finishes, and a person approves anything that changes how the business runs.
How a new hire learns the business from it
The quickest way to judge a company brain is to give it to someone on their first day. If it is good, they need far fewer people to explain how things work.
Day one: the department page
Every workflow the department runs, with how often it runs. The new starter sees the shape of the job before anyone explains it.
Week one: follow the links
Each workflow names its systems, its owner and the decisions behind it. Reading three or four of them end to end teaches how the work is actually done here, not how a policy document says it is.
Every day after: ask, then do
The new starter asks an assistant that has read the same pages, and gets the answer the team would give. When the answer is wrong, the correction goes back in, so the next new starter does not hit the same gap.
Where it sits
A brain is the last step, not the first
A company brain grows out of a team already working with AI every day: the skills and context files people use are the first written form of how the business works. That is why we build one as part of moving a team onto AI, which our AI operating system methodology sets out step by step, rather than as a separate project. The company brain page covers how one gets built, and ours shows one running.
Frequently asked questions
What is a company brain, in one sentence?
A company brain is a set of linked pages on how a business works, its workflows, systems, decisions and people, that every person and every AI agent in the business reads before it acts and writes back to when it learns something.
Is a company brain the same as a wiki or an intranet?
No. A wiki is written for people to browse and is usually out of date by the time anyone needs it. A company brain is written to be read by agents as well as people, every page has a type and an owner, the pages link to each other so a question can follow the links, and it is checked every day for pages that have gone stale or contradict each other.
What goes into a company brain?
Four kinds of page do most of the work. Workflows say how a job is done, how often and with which tools. Systems say what each tool holds and who owns it. Decisions record what was settled, when and why. People pages say who does what and who to ask. Departments group the workflows, and meeting notes and client history link into all of them.
Who writes it?
Mostly the work itself. When a person or an agent finishes a piece of work, what it learned is banked as a new page or an edit to one. When someone corrects an agent, the correction is written down as a rule so the next answer changes. People settle the disagreements, such as which of two policies is current. Nobody is asked to sit down and document the business from scratch.
How does a new hire use it?
They start at their department page, which lists every workflow the department runs and how often. Each workflow names the systems it touches and links to the decisions and people behind it. A new starter follows those links to learn how the job is actually done, and asks an assistant that has read the same pages instead of interrupting a colleague.
Do we need a lot of data before it is useful?
No. It needs the right pages, not a large volume of files. A business with a few dozen accurate workflow pages gets more from a brain than one with ten thousand unsorted documents, because the agents can tell which page is current and who owns it.
Does it lock us in to one AI vendor?
It should not. A company brain is plain linked pages, readable by Claude, ChatGPT, Copilot or Gemini over an open interface. If you change the model, the brain stays where it is. The one we build for a client belongs to the client.
Read next
More on the company brain
The company brain
What one is made of, how one gets built, and what it is not.
A second brain for your business
How the second brain idea changes when a whole team, and every agent working for it, has to share one.
Our company brain, live and growing
Sentry AI runs its own business on its own brain. The page count, the departments, and how it grows.
Want to know what your brain would hold?
The free AI readiness check maps the tools your business already runs as a graph and shows where the first pages of a brain would come from.
Ask an AI about this page
Opens the assistant with this page loaded: read it, summarise it, cite it.