What is a company brain? A practical guide

A new hire asks where the deploy runbook lives. Someone in sales needs last quarter's win rate. A teammate wants to know why you dropped a feature a year ago. In each case the answer exists somewhere, or it lives in one person's head, and finding it means interrupting whoever knows. Multiply that across a growing team and a real share of the week goes to answering questions that have already been answered.

A company brain is the idea that this collective knowledge should live in one place you can simply ask. This post covers what a company brain is, how it works, how it differs from a wiki or a knowledge base, who needs one, and how to tell a real one from a rebranded search box.

What is a company brain?

A company brain is a single, living layer that holds your organization's knowledge and answers questions from it in plain language. It connects to the tools your team already uses, reads across them when you ask something, and returns an answer with the source attached. When the answer is not written down anywhere, a true company brain does not shrug. It asks the person who knows, captures their reply, and keeps it for the next person.

The word "brain" matters. A filing cabinet stores documents. A brain recalls what it has learned, notices what it does not know, and fills the gap. A company brain is meant to do the same for a team: not just store information, but make it answerable, and get smarter as people use it.

How does a company brain work?

Most company brains follow the same four steps.

First, it connects to your sources, Slack, Notion, Google Drive, a help desk, a CRM, wherever knowledge actually lives. Second, when someone asks a question, it reads across those sources and assembles an answer rather than handing back a list of ten links to read. Third, it shows its work, citing the document, message, or ticket the answer came from, so you can check it. Fourth, and this is what separates a brain from a search engine, when nothing written can answer the question, it routes the question to the person most likely to know, then saves that answer so it is there next time.

Two design choices shape how well this works. One is whether answers are pulled live from your tools or from a stored copy that has to be re-indexed. Live retrieval means the answer reflects what is true right now. The other is permissions: every answer should be filtered to what the individual asker is allowed to see, so a company brain never leaks a document across boundaries.

Company brain vs. wiki, knowledge base, and workplace search

These terms overlap, and the differences are the whole point.

A wiki or knowledge base is content a person writes and maintains by hand. It is only as complete and current as the last time someone updated it, and keeping it that way is ongoing work somebody owns.

Workplace search finds existing content across your tools. That is a real step up from opening each app one by one, but it can only surface what has already been written. Ask it something no document covers and it comes back empty.

A company brain includes workplace search and goes one step further. It pulls answers live, and when the answer was never written down, it captures it from the person who knows. The difference is the gap: a wiki needs the answer written in advance, search needs it written somewhere, and a company brain closes the case even when it was only ever in someone's head. That last part is where most tribal knowledge gets lost.

Who needs a company brain?

The pain scales with headcount and tool count. A five-person team can still get answers by turning around and asking. Somewhere past twenty or thirty people, that stops working: the person who knows is in a meeting, in another timezone, or gone, and the same questions get asked over and over.

The teams that feel it first are usually growing startups and small companies where knowledge outpaced documentation. New hires are the canary. If onboarding depends on a handful of people answering the same questions for every joiner, a company brain is the fix. We tested this idea in the extreme by running a company with almost no written docs and letting the brain fill in, and the results are here.

Why teams build one as they grow

Three costs push teams toward a company brain.

Repeated questions. The same handful of answers get requested weekly, each one a small interruption for whoever knows.

Context switching. People hop between tools to reconstruct an answer. The research on toggling between apps puts the tax at hours per week, per person.

Knowledge that walks out the door. When someone leaves, what they knew but never wrote down leaves with them. A company brain that captures answers as they are asked turns those moments into a growing record instead of a loss.

What a company brain can't do

An honest limit: a company brain cannot invent knowledge that no one in your company has. If the answer was never known by anyone and never written anywhere, no tool will produce it. What a good one does is make sure that when someone does know, the answer gets captured once and reused, so you are never paying for the same discovery twice.

It also depends on access. A company brain is only as useful as the tools it is allowed to connect to, and it should respect the same permissions those tools already enforce. And it is not a system of record. It answers from your sources; it does not replace them.

How Agentwork works as a company brain

Agentwork is a shared knowledge layer that answers questions across the tools your team already uses, with the source attached so you can check it. It retrieves live rather than from a stored index, so answers stay current. When something is not written down, it sends a request to the person who knows, captures the reply, and keeps it for the next person, so gaps close instead of coming back empty. Every answer is filtered to what the asker can see, your knowledge is reachable by your own models and agents over the open MCP standard, and you can choose EU data hosting. It is free to start, with per-seat pricing as you grow and no seat minimum.

How to evaluate a company brain

If you are comparing options, work through these:

• Coverage. Does it connect to the tools where your knowledge actually lives?
• Freshness. Are answers pulled live, or from a copy that lags behind your sources?
• Knowledge capture. When nothing is written, does it ask the person who knows and save the answer, or just return empty?
• Citations. Does every answer link to its source so you can verify it?
• Permissions. Is each answer scoped to what the individual asker is allowed to see?
• Openness and residency. Can your own models and agents reach the knowledge over an open standard, and can you control where data is hosted?

Frequently asked questions

What is a company brain in simple terms?

It is a single place you can ask questions and get answers drawn from all your company's tools, with sources attached, that also fills gaps by asking the people who know.

How is a company brain different from a knowledge base or wiki?

A wiki or knowledge base only holds what someone wrote and maintains by hand. A company brain answers live across your tools and captures answers that were never written down, so it stays current with far less upkeep.

Do I have to build or maintain a company brain?

No. Unlike a wiki, you do not curate it in advance. It connects to the tools you already use and grows as people ask questions.

How is a company brain different from ChatGPT?

General AI does not know anything about your company. A company brain answers from your team's own tools and knowledge, with citations and per-person permissions.

Is my company's data kept private?

It should be. A good company brain enforces the same permissions as your source tools and lets you control where data is hosted, including an EU option.