- A company brain is a company’s operating knowledge, decisions, state, rules, open questions, next steps, in a place people and agents can read.
- It’s not a knowledge base or a vendor’s memory: those are content to look up or opaque recollections, the company brain is the live context you work from.
- It isn’t on or off: it lives at a level, from “in heads” (L0) to “agent-operated” (L4). The five in brief here, the diagnosis elsewhere.
- The question that decides everything is ownership: is that context yours and governed, or rented inside a tool?
A company’s operating knowledge, in one place
We call “company brain” the set of things a team needs to know in order to work: decisions made, project state, rules, exceptions, open questions, next steps. Every company already has it. The problem isn’t having it, it’s where it lives: as long as it sits in heads, in Slack, and in disconnected documents, no one sees all of it and every AI chat starts from zero.
It becomes a company brain, rather than a pile of files, when that knowledge sits in one place, written so that both people and the AI can read it. That’s the difference between knowing “it’s written down somewhere” and having context the team, and an agent, can re-read and apply without asking around.
Every company already has a company brain. The question isn’t whether you have one: it’s where it lives, and whether anyone besides the person who wrote it can read it.
It’s not a wiki, and it’s not a vendor’s memory
It’s easy to confuse it with two things that look alike. A knowledge base, a wiki or a Notion, is an archive to consult: useful, but static, often stale, and the AI never looks at it. A tool’s automatic memory, on the other hand, remembers something about you, but it’s opaque (you can’t see what it learned), it lives where the vendor decides, and it stays behind when you switch tools. The company brain is neither: it’s the live operating context you work from, that you own and govern.
The difference is clearest row by row. On the right is context on files you own, the idea behind our open-source kits cowork-os and code-os; on the left is a vendor’s automatic memory. One row leans toward the vendor on purpose: it’s not advertising, it’s a criterion for choosing.
The company brain isn’t on or off
It’s not a yes-or-no question. A company’s brain lives at a precise level, and the level tells you how much its knowledge is yours, alive, and useful, for people and for AI. It ranges from L0, where everything lives in heads and chats, to L4, where agents run the work on the brain and keep it fresh. Here are the five, in brief.
- L0In heads and chats
Knowledge lives in people and disconnected chats. Every AI chat starts from zero.
- L1Written but dead
A wiki exists, but it’s stale and nobody updates it. The AI ignores it: a false sense of safety.
- L2Owned and structured
Decisions, state and rules in files you own and govern, updated by habit. People and agents read them.
- L3Self-updating and queryable
It absorbs from email, chat and calls, answers with the source, and captures tacit knowledge through interviews.
- L4Agent-operated
Agents run the work on the brain and keep it fresh. The company operates from it.
Knowing your level is the first concrete step: it gives a name to a problem you already have and points to the right jump, without switching tools. If you want the precise picture, take the 2-minute self-check and find out your next step.
The question that matters: is it yours or rented?
When you put the company brain inside an AI, it scales: it stops depending on who happens to be in the office that day. But at that point the question is no longer technical, it’s about ownership. Two axes change everything: where the data lives, inside a vendor’s infrastructure or in a place you control, and how it’s governed, automatically and opaquely or explicitly and auditably. The combination of the two tells you who really owns your company brain.
It’s not a holy war: for many teams vendor memory is fine. It becomes a problem when you operate in a regulated industry, handle sensitive data, need to prove what the AI learned, or want the know-how to stay if you change tools or people. We wrote a piece dedicated to this question: who owns the company brain.
You start from files you own, not from a tool
Building it doesn’t mean buying software: it means putting decisions, state, and rules in files you govern, updated by habit, readable by you and by Claude. Our open-source kit cowork-os gives you the structure for free: you paste in a file, answer six questions, and the workspace builds itself[1]. From there the company’s context sits in one place, on your computer, and grows every week instead of rotting.
Plus the instructions, the routine automations, and a real, already filled-in example to copy from.
The hard part isn’t creating folders, it’s transferring the knowledge that lives in heads into those files. The practical method, with interviews, transcription, and validation, we wrote here: how to build a company brain on files.
Company brain, in practice
What is a company brain, in one sentence?
It’s the set of things a team needs to know in order to work, decisions, project state, rules, open questions, next steps, kept in one place and written so both people and the AI can read it. Every company already has one: it usually lives scattered across heads, chats, and documents.
What’s the difference between a company brain and a knowledge base?
A knowledge base or a wiki is an archive to consult: static, often stale, and the AI usually never looks at it. The company brain is the live operating context you work from, updated by habit and readable by agents. The knowledge base tells you “how it’s built”, the company brain tells you “how we work, right now”.
Is the company brain the AI’s memory?
No, and the difference matters. A tool’s automatic memory remembers something about you, but it’s opaque and lives inside the vendor. The company brain is explicit context on files you own and govern: readable, auditable, and independent of the tool. An AI can read your company brain, but the brain stays yours.
Do I need to buy software to have a company brain?
No. The starting point is a method: put decisions, state, and rules in files you own. The open-source cowork-os kit gives you the structure for free. Tools and automations come in at the higher levels, but getting started costs nothing and is yours from day one.
Where do I start with a company brain?
First find out your level with the maturity model self-check, then follow the practical method to put context on files. You don’t need to switch tools to start: you need to choose an operating boundary, write it down, and keep it alive with a routine.
Sources
- [1]cowork-os, open-source repository. github.com
This page is written by Raffaele Zarrelli and Simone Bova, founders of Yempik, with editing done with Claude. The company brain and its maturity model are Yempik editorial models. The kits cited are our open-source cowork-os and code-os (MIT license). Where we cite a number, you’ll find the source below.
Want to put your company brain on files you own?
We start from your process, not the tool. We help you put decisions, state, and rules on files you own, governed, and bring automations into production when do-it-yourself isn’t enough. Fixed price and timeline, the code is yours.