How to Build Your Company Brain Step by Step: From Scattered Docs to Cited Memory
How to build your company brain step by step: pick one domain, name the official sources, cite every fact and test with real questions before agents use it.

The problemYour knowledge lives in folders, duplicate versions and people's heads, and you do not know where to start turning it into memory for your agents.
Monday, 8:30 a.m. The COO of an industrial services company decides that the company's first agent will prepare quotes. She opens the pricing folder and finds "Prices_2025_final.xlsx", "Prices_2025_final_v2.xlsx" and "Prices_NEW_use_this_one.xlsx". She asks two salespeople which one is right. Each points to a different file.
That is the real starting point for almost any company. The knowledge exists, but it is spread across duplicate versions, email threads and the experience of a few people. This article explains how to build your company brain step by step: how to go from scattered documents to cited memory, with owners and permissions, that your agents can use without making things up.
If you are not yet clear on what a company brain is and how it differs from a shared drive or a chatbot over documents, start with what a company brain is.
Why loading everything does not work
The temptation is to connect the entire shared drive to an agent and let it search. It is fast and, in the demo, it seems to work. In operations it fails for three reasons: the agent does not know which version is official, it mixes outdated documents with current ones and it cannot justify its answers.
Building a brain is not moving files around. It is making decisions: what is official, who answers for each topic, what each agent can read and what happens when something changes. Technology matters, but those decisions matter more.

Eight steps to build your company brain
1. Pick one domain and write down its questions
Do not start with "all of the company's knowledge." Pick a domain tied to a specific process: quotes, support for one product line, client onboarding. Then write down the real questions that process needs answered: "What discount can I give a distributor?", "What does the maintenance plan include?" Those questions define what goes into the brain and, later on, how it gets tested.
2. Inventory the sources and declare the official one
For each topic in the domain, list where the information lives today and name a single official source with its owner.
| Topic | Official source | Owner | Review |
|---|---|---|---|
| List prices | Price sheet approved by leadership | VP of Sales | Every quarter |
| Discounts | Signed discount policy | VP of Sales | Every six months |
| Service scope | Current technical catalog | Engineering manager | With every change |
| Payment terms | Credit policy | Credit manager | Every six months |
Anything that is not an official source is archived out of the agents' reach. This step usually surfaces contradictions the company has been carrying for a long time.
3. Design the structure before loading anything
Decide the brain's sections and the format of each one. Whatever varies by client goes into one file per client, with clear sections such as terms, preferences and history; we cover the detailed design of that file in one file per client. Whatever applies to everyone, such as rules, prices and service scopes, goes into shared sections.
4. Convert and cite every fact
Each official document is split into fragments that stand on their own: a rule, a price table, a clause. Every fragment keeps its citation: document, section, effective date and owner. That way, when an agent answers, it can say exactly where the answer came from, and a person can verify it in seconds.
5. Capture what is not written down
A large part of the company's judgment is not in any document: which client accepts partial deliveries, which exception always gets approved, which mistake repeats every month-end. That knowledge is recovered through short interviews and by reviewing cases people had to correct. The full method is in tribal knowledge. Whatever is captured goes through its owner's approval before it enters the brain, like any other source.
6. Set permissions and expiry dates
For each agent, write down which sections it can read. The quoting agent needs prices and service scopes; it does not need employment contracts or margins for other product lines. In addition, every section carries a review date: when it expires, the owner gets a reminder and, if they do not confirm it, the section is flagged as pending instead of continuing to answer as if nothing happened.
7. Test with real questions before connecting agents
Take the questions from step 1 and add the correct answer and the source that should be cited. Have the brain answer them. A good result meets three conditions: the answer is correct, the citation points to the official source and, when the fact is not in memory, the system says so instead of inventing it. These questions become evals: tests that run again every time the brain changes, to catch anything that stopped answering well.
8. Connect it to the harness and turn on the learning loop
Once the brain passes its tests, it is connected to the harness: each agent queries only its sections and every query is logged. At the same time, the learning loop goes live: an agent reviews what happened in recent cases and proposes what to save or correct, and a person with the right role approves, edits or discards it. Only what is approved goes in.
Illustrative example: quotes, before and after
Illustrative example. Before, the industrial services company had three price sheets, a discount policy only the VP of Sales knew and service scopes each salesperson explained in their own way. An agent connected to that folder would have quoted from the wrong sheet.
After building the brain's first domain:
- There is a single official price source, with an owner and an effective date.
- The discount policy is written down, approved and cited.
- The exceptions the VP used to approve "from memory" are now recorded as rules.
- Every quote the agent prepares cites the prices and rules it used, and the VP signs it before it goes out.
- The test questions run every time a price list changes.
The next domain, technical support, reuses the same structure, the same permissions and the same learning loop.
Common mistakes when building your company brain
- Starting with everything. A company-wide brain without clear domains never gets finished.
- Loading contradictions. If you do not decide which source is official, the agent decides for you.
- Forgetting the citation. A fact without a source cannot be verified or corrected.
- Skipping review dates. The brain ages quietly and nobody notices until it fails in front of a customer.
- Letting agents write without approval. Memory fills up with guesses within weeks.
- Not testing before connecting. Without test questions, your brain's first evaluator will be your customer.
What to do on Monday
Pick the process where you want your first agent and write down the twenty questions that come up most often in it. For each one, note the official source and who owns it. Wherever there are two sources or no owner, you have the list of decisions your brain needs before any technology.
At Addabra we build the brain with this same method, domain by domain, connected to your harness and deployed on your infrastructure, with permissions per agent and human approval on every change. To see what it includes, take a look at our Company Brain Development service.
Frequently asked questions
Where should we start building the company brain?
With a single domain tied to a high-volume process, such as quotes or support for one product line. Starting with everything at once produces a huge repository with no owners. One well-built domain becomes the template for the next ones.
What do we do with documents that contradict each other?
Do not load them as they are. For each topic, the owner decides which source is official and the rest is archived out of the agents' reach. Resolving contradictions before loading is the most valuable part of the work, even if it is not the most visible.
How do we know the brain is ready to connect to agents?
When it correctly answers a set of real questions from your operations, citing the right source, and says "I do not know" when the answer is not in memory. Those questions become tests that run again every time the brain changes.


