What Is a Company Brain?
A Company Brain is the shared repository of a company's approved expertise — how each team member actually does their work — organised so that every team member's AI Wingman can use it, with every piece cited to the person who taught it.
Where a wiki stores what happened and enterprise search retrieves it, a Company Brain holds the working knowledge itself: how this company measures conversion, how this team qualifies a lead, which funnel steps matter, what the design system allows. Each piece is approved expertise — taught by a named teammate, approved by them, and usable by every colleague's Wingman from the moment it's approved.
The structure: functions → team members → approved expertise
A Company Brain mirrors the company itself, not a folder tree:
- Job functions — Growth, Design, Product, Marketing — are the top level.
- Team members sit under their function. People, not pages, are the unit of organisation.
- Approved expertise attaches to the person who taught it: "Conversion Metric — taught by Mark, Growth", "App Design System — taught by Sara, Design", "Paid Conversion Playbook — by Emma".
This is why every answer out of the brain can say whose expertise it used — attribution isn't a citation bolted on afterwards; it's how the brain is shaped.
Why the category exists now
- AI teammates arrived, and they need company-specific how, not prose. A model can read your documents, but "improve paid subscriptions" requires knowing how this company defines a paid subscription, which funnel it watches, and what the design system permits. That knowledge lives in people's heads — until it's taught to the brain.
- Retrieval hit its ceiling. Enterprise search made finding documents easy and changed little: the bottleneck was never finding the runbook, it was that a document still needs a skilled human to interpret and execute it. See Company Brain vs enterprise search.
- Expertise kept walking out the door. When the person who knew how left, the company re-learned at full price. A Company Brain makes each person's know-how outlive the moment — with their name still on it.
How expertise gets in: the approval loop
Nobody writes documentation for the brain. A team member finishes a solve that worked, their Wingman asks one question — "Want me to add this to the Company Brain as approved expertise?" — and a yes is all it takes. Capture that depends on someone writing it up afterwards produces a wiki, not a brain.
Company Brain vs the tools you already have
| Company wiki | Enterprise search | Generic AI agents | Company Brain | |
|---|---|---|---|---|
| Unit of knowledge | A page | A search result | A prompt | Approved expertise, cited to its author |
| What you do with it | Read it | Find it | Hope it generalises | Your Wingman acts on it |
| Quality guarantee | None (goes stale) | Relevance ranking | None | A named teammate approved it |
| Gets better when… | Someone edits | More docs indexed | Model upgrades | Every teammate's solve |
| Who benefits | Whoever searches | Whoever searches | One user | Every team member's Wingman, instantly |
What a Company Brain changes operationally
Solve it once. Every team member gets better.
- The second solve is nearly free. When Emma's paid-conversion playbook joins the brain, the next growth question starts from it — cited back to her.
- Expertise compounds across functions. Marketing's template craft, Product's usage data, Design's system rules — one solve draws on all of them, and each author's work multiplies through everyone else's Wingman.
- Repeatable work leaves the humans. Once an approach is proven, an AI Employee runs it on schedule and reports back — see use cases.
- Answers come with provenance. Ask in Slack, get the number, the source, and the author — marked high-confidence when it's built on approved expertise.
How Catalyst implements it
Catalyst gives every team member an AI Wingman, and what they approve becomes the Company Brain. A solve happens in conversation with your real data, APIs, and tools; teammates' approved expertise arrives cited by name; work ships as tasks, campaigns, dashboards, and internal tools; and when the human approves the solve, every colleague's Wingman acquires it. Catalyst runs as a plugin inside Claude Code and Codex on your own model subscription, with the workspace in your own cloud (BYOC/VPC). The loop end to end: How Catalyst works.
Frequently asked questions
What is a Company Brain in one sentence?
The shared repository of a company's approved expertise — how each team member actually does their work — organised so every teammate's AI Wingman can use it, cited to the person who taught it.
How is it different from a wiki or enterprise search?
A wiki stores documents a human must read and interpret; a Company Brain stores approved expertise an AI Wingman can act on directly, with the author's name on every use.
How does expertise get in?
As a by-product of real work: solve with your Wingman, approve when it asks, and every teammate's Wingman acquires it instantly.
Who can use it?
Every team member — through their Wingman or Slack — and AI Employees running repeatable work. Every answer names its source.
Does a Company Brain replace people?
It multiplies them. Each person's expertise reaches every teammate's Wingman, repeatable work moves to AI Employees, and people spend their time on problems nobody has solved yet.
See the Company Brain learn your work
Bring one real problem. Solve it with your Wingman, approve it, and watch every teammate get better.