A company brain is a shared, living memory of how a company works: its decisions and the reasoning behind them, its documents, meetings and operating records, kept in one place that people and AI can both ask. Unlike a wiki, it fills in from the work as it happens, and it controls who may retrieve what.
What a company brain holds
The useful test is simple: could a new colleague, or an AI assistant, answer a real question about the business without interrupting the person who knows? A company brain is whatever makes the answer yes. In practice it holds five kinds of material.
- Decisions, with the reasoning that produced them. Not only that the price changed, but why, who decided, and what was ruled out.
- Documents and files: plans, contracts, proposals, policies and the rest of what the company has written down.
- Meetings. Most of what a company works out is spoken, never written, so a company brain keeps what was agreed in the room.
- Operating records: projects, tasks, approvals and the state of work in the tools the team already uses.
- What people know but never wrote down: how the business actually runs, explained once so nobody has to explain it again.
Time matters as much as content. A fact that was true in March and replaced in June should not vanish, and it should not be quoted as current either. A company brain worth the name keeps the replaced fact readable beside the one that replaced it, with the dates each one held.
What a company brain is not
The phrase is new enough that it gets attached to almost anything with a search box. Four things are commonly called a company brain and are not one.
- A wiki. A wiki holds what somebody wrote down, and keeps holding it after it stops being true. It depends on people remembering to update it, which is the habit that fails first when a team gets busy.
- Search inside a chat tool. It finds the message. It does not hold the decision that came out of the thread, or the reasoning behind it.
- A chat assistant connected to your files. It reads what you point it at and answers from it. That is access. It does not keep decision history, apply each person's access rules, or leave a record of what was done.
- An integration layer. Connecting tools is one way knowledge gets in. It is never the whole of it, because the meeting nobody wrote up and the reasoning in one person's head are not in any tool.
What makes it an AI company brain
People can tolerate a messy memory, because they ask follow-up questions and know who to call. AI cannot. An AI company brain is a company brain built so that AI can read it safely, and that adds four requirements on top of storage.
- Memory with history. Decisions are kept with their reasoning, and facts carry when they applied and when the company learned them, so AI can tell current from replaced.
- Permissioned retrieval. When a person asks, or an agent asks on their behalf, retrieval applies that person's access rules, so AI does not surface what the asker may not see.
- Sources, or an honest blank. An answer names the record it came from, or says it has no source rather than filling the gap. A source supports attribution. It does not prove the answer is true, and a careful system says so.
- Boundaries for agents. If AI can act, not only answer, its emails and updates to customers or suppliers should wait for a person, and what it did should be recorded.
Those four together are what people mean by governed context, and they are the subject of the companion guide on the operating governance layer for AI.
Signs your company needs one
Size is a weak signal. A three-person company can need a company brain more than a fifty-person one, if the three are the only people who know how anything works. These are stronger signals.
- The same questions reach the same person every week, and that person is usually a founder.
- A new hire takes months to stop asking, and a contractor never gets there.
- A decision gets remade because nobody can find why it was made the first time.
- Meetings end with agreement and nothing written down, so the follow-up depends on memory.
- The team has started connecting AI tools to company systems, and nobody has decided what those tools may see.
The last signal is the newest and the most urgent. Connecting an assistant to your files takes an afternoon. Deciding what it should know, see and do takes longer, and is usually skipped.
How to build a company brain
Do not start by connecting everything. Start with one question the business answers badly today, and build outward from it.
- Pick one use case. For example: how we price a custom deal, how we onboard a customer, or what we promised each client this quarter.
- Bring the material that use case needs, not the whole company. A few documents, the relevant meetings and the records in the tool where that work happens.
- Write down the decisions behind it, with the reasoning, in the words the people involved would use.
- Decide who may see what before any AI reads it. Retrofitting access rules is far harder than starting with them.
- Ask a real question and check the answer's sources, its dates and whether the right people can see it.
- Make one thing repeat each week, such as a briefing or a review, so the memory keeps filling in as the work happens.
- When something changes, correct the record instead of overwriting it, so the old version stays readable with the dates it held.
A company brain built this way grows from use rather than from a migration project, which is the only way most small teams ever finish one.
About Hoppflow
Where Hoppflow fits
Hoppflow is a living company brain: shared memory and governed context for people and AI, for companies of 1 to 100 people. It keeps company knowledge, meetings, documents, connected tools and operating records in one company memory, with recorded decisions and the reasoning behind them.
- Recorded decisions keep their reasoning, and a replaced fact stays readable on supported record types.
- Supported company-brain retrieval paths apply each person's access rules.
- A company-brain answer names the record it came from, or says that it has no source.
- An agent can prepare an email or a CRM update, but a person decides whether it is sent.
Setup starts with one use case. You bring the material it needs, answer a short set of questions about how the business runs, and a founder sits with you while you run the first real question and check its sources. The details are on the Company Brain page and the controls are on Security and trust. Access is through the waitlist.
Questions people ask
How do you build a company brain?
Start with one use case rather than the whole company. Bring the documents, meetings and records that use case needs, write down the decisions behind it with their reasoning, and decide who may see what before any AI reads it. Then ask real questions, check each answer's sources and dates, and correct records instead of overwriting them.
Is a company brain the same as a knowledge base?
No. A knowledge base or wiki holds what somebody wrote down and keeps holding it after it stops being true. A company brain also keeps decisions with their reasoning, meetings and operating records, marks a replaced fact as replaced, and controls who may retrieve what.
What is an AI company brain?
An AI company brain is a company brain built so AI can read it safely. It keeps facts with their dates, applies each person's access rules when AI retrieves on their behalf, names the source of an answer or says it has none, and keeps an agent's outgoing drafts on hold until a person approves them.
Does a small company need a company brain?
Often more than a large one. In a company of a few people the business usually lives in one or two heads, so every absence, hire or new AI tool depends on those people explaining it again. A company brain is how a small company stops explaining its business twice.
Does a company brain replace the tools we already use?
No. The tools stay where the work happens. A company brain reads from them as one source among several, alongside meetings, documents and decisions. In Hoppflow, connecting a supported tool does not make its contents searchable by default: indexing is a separate choice.