The company brain: what it is and how to build one
A company brain is the approved, shared memory of how a company works: its processes, decisions, pricing, roles, clients, goals, issues and lessons. A named person approves each entry before it counts, and people and every AI tool the company uses answer from it, with the source shown on each answer.
Cerino, the company brain for every AI you use, is one way to build it. This guide explains the idea first and the product second: why companies need one now, how it differs from a wiki or a data warehouse, and how to build yours in a week.
Stephen Whitten, founder of Cerino
Stephen founded Cerino to give each company one approved memory that every AI tool answers from.
Last updated
Why companies need one now
Your team already asks AI assistants for help with quotes, emails and plans. The assistant is fluent, fast and confident. What it does not have is the way your company actually does things.
AI assistants know the internet, not your company
Claude and ChatGPT were trained on public text. They can explain how moving companies usually price a job, but not how yours does, which customers get a discount, or what you decided after last spring's damage claims. Without that, every answer is a well-written guess.
Answers drift between people and tools
When the rules live in old documents, inboxes and memory, the estimator gives one answer, the office gives another and the AI gives a third. Each person pastes different context into a different tool, so the answers drift a little further apart every week.
Knowledge sits in one person's head
In many owner-led companies, the answers live with the owner or a long-serving manager. When they are on a job site, on holiday or gone for good, the answers go with them. A company brain writes that knowledge down once, gets it approved, and makes it available to everyone and every tool.
A moving company, one ordinary question
A customer asks whether a third-floor walk-up costs extra. Without a company brain, three sources give three answers. With one, every tool gives the answer the owner approved, and says where it came from.
- Estimator“We usually add a bit for stairs.”
- Office“No charge under four floors, I think.”
- AI assistant“Many movers charge a flight fee.”
“Stairs are charged per flight after the first, on every local move.”
Company brain vs. wiki vs. AI memory vs. data warehouse
All four store something about your company. They differ in who decides what is true, and in which tools can use it.
A wiki records what someone wrote. A company brain records what the company approved.
| Question | Company brainfor example, Cerino | Wiki or knowledge basefor example, a shared drive of pages | AI assistant memorybuilt into ChatGPT or Claude | Data warehousetables copied from your systems |
|---|---|---|---|---|
| What it holds | Approved facts about how the company works: processes, decisions, pricing, roles, clients, goals, issues and lessons. | Pages and documents, written by whoever has edit rights. Current and out-of-date pages sit side by side. | What one assistant remembers, mostly about one person and their chats. | Numbers and records from your systems: sales, jobs, invoices. Not how or why the company works. |
| Who approves it | A named person, before anything counts. Every change is logged. | Usually no one formally. Pages stay right only while someone owns them. | The assistant or the user decides. There is no company approval step. | A data team defines tables and metrics. |
| Which AI can use it | Claude and ChatGPT today, through MCP, plus Cerino's own app. | Any AI connected to it, with no way to tell a current page from a stale one. | Only that assistant. Switch tools and the memory stays behind. | AI tools with a database connection and the right queries. |
| Source on every answer | Yes. Every answer shows the approved entry it came from. | Only if the AI chooses to cite the page. | Not as a rule. | Lineage exists if someone built it, rarely in plain words. |
| Access by role | Yes, by role and by area of the business. | Page or space permissions, set by hand. | Per user or workspace, not by company role. | Database permissions, managed by the data team. |
| Setup | Connect your assistant, upload documents, answer starter questions. Days, not months. | Quick to start, hard to keep current. | Built in, nothing to set up. | An engineering project: pipelines, models and upkeep. |
These categories overlap, and products change. The table describes each kind of tool as it is typically used, not any one vendor's full feature set. A data warehouse is not required for a company brain; if you have one, it is one more source beside the others.
How a company brain works
A company brain sits between the people who ask and the places information lives. It holds only what was approved, and it answers wherever your team already works.
People and their AI
Who asks, and what they ask with.
Your people
OwnerManagersStaffTheir AI assistants
Cerino's own app
Cerino, the governed memory
What your company decided, approved and kept.
What it holds
How something gets in
- Proposedby an assistant, an upload or a person
- Approved by a named personor sent back with a reason
- In the Brainand used in every answer from then on
How it is kept
How it connects
Two ways in today, one planned.
Through your AI assistant (MCP) Today
Your assistant reads your tools through its own connectors. It asks Cerino for approved answers and sends back what it learns as proposals.
Uploads Today
Add a document in Cerino. It becomes proposals for a named person to approve.
Direct connectors Later
Planned: Cerino reading your tools itself. Not available yet.
Where your information lives
Your tools stay as they are. Nothing moves.
Your assistant reads these through its own connectors, not through Cerino.
Documents
- Google Drive
- SharePoint and OneDrive
- Dropbox
- Box
- Files you upload
Communication
- Gmail
- Outlook
- Slack
- Microsoft Teams
- Meeting notes
Customers and jobs
- HubSpot
- Salesforce
- Your job system, e.g. SmartMoving
Finance
- QuickBooks
- Xero
Calendar and tasks
- Google Calendar
- Notion
- Asana
Data
- A data warehouse
- A BI tool
If you have one. One more source beside the others, not a layer in between.
How to build your company brain in a week
You do not need a data project to start. Six steps, most of them short, take a company from nothing written down to answers it can trust.
Connect Claude or ChatGPT
Estimated time: Day 1, about 10 minutesAdd Cerino as a connector in the assistant your team already uses, and sign in. From then on the assistant can ask Cerino for approved answers, and send back what it learns as proposals.
Upload the documents you have
Estimated time: Day 1, under an hourPrice sheets, procedures, the employee handbook, standard contracts. Cerino turns each document into proposals for a named person to approve; nothing counts until someone does.
Answer your industry's starter questions
Estimated time: Days 2 to 3, in short sittingsCerino asks the questions a company in your trade should be able to answer, such as how you price a job and who can approve a discount. Your answers fill the gaps your documents leave.
Approve what is right
Estimated time: Days 2 to 5, a few minutes a dayRead each proposal and approve it, edit it, or send it back with a reason. Approval is by a named person, and it is the step that turns a draft into company memory.
Invite your team, with their areas
Estimated time: Day 5, about 15 minutesGive each person a role and the areas of the business they work in. They see what their role allows, and the people who own an area decide what goes into it.
Ask, and check the source
Estimated time: From day 5, every dayAsk questions in Claude, ChatGPT or Cerino's app. Every answer shows the approved entry it came from, so anyone can check it, and gaps you find become the next proposals.
Times are estimates for a small company with its documents to hand. They depend on how much you have written down.
What goes in it
A company brain holds eight kinds of knowledge. Each example below is how a moving company might write one down.
Processes
How work gets done, step by step.
Example: how the crew wraps, loads and photographs a piano before it leaves the house.
Decisions
What was decided, when, by whom, and why.
Example: no same-day local moves on Saturdays, and the reason the owner gave.
Pricing
Rates, minimums, surcharges and discounts.
Example: the hourly crew rate for local moves, the minimum hours, and the charge for stairs.
Roles
Who does what, and who can approve what.
Example: only the operations manager can approve a discount below the standard rate.
Clients
What matters about each customer or account.
Example: a corporate relocation account needs a certificate of insurance before every job.
Goals
What the company is aiming for this year.
Example: grow long-distance moves while cutting the number of damage claims.
Issues
Known problems everyone should work around.
Example: one truck's liftgate is out of service, so book heavy items on the other truck.
Lessons
What the company learned the hard way.
Example: measure the stairwell before quoting a sofa move, after one would not fit.
Built for your industry
A company brain should start with your trade's words, documents and questions, not a blank page. Cerino starts each company from an industry starter structure, and moving and construction come first.
Moving companies
For household and commercial movers, from estimate to delivery.
- Estimates, rates and surcharges
- Crews, trucks and equipment
- Bills of lading and inventories
- Claims and how they are settled
Starts with questions like “How do you price a local move?”
Construction
For contractors who bid, build and hand over projects.
- Bids and estimating
- Change orders and RFIs
- Subcontracts, bonds and lien waivers
- Safety procedures
Starts with questions like “What is your bonding capacity?”
More industries coming
Each starter structure is built from real work in that trade, so we add industries one at a time rather than guessing from outside.
Run a different kind of company? Tell us your industry.
Trust: who sees what, and who decides
A company brain is only useful if people trust it. That comes from four rules: clear roles, clear areas, approval by name and a record of every change.
Roles
Owners, managers and staff each see and do what their role allows, in Cerino and through their assistant.
Areas
Knowledge is filed by area of the business, such as estimating or claims, and access follows the areas a person works in.
Approval by name
Nothing counts until a named person approves it. A proposal from an assistant, an upload or a colleague waits until then.
Audit log
Every proposal, approval and change is recorded: who did it, and when. Every answer shows its source.
Cerino connects to your assistant, not to your tools
Your assistant reads your email, files and systems through its own connectors, with the permissions you already gave it. Cerino holds only what is proposed and approved, plus documents you choose to upload. Direct connectors to your tools are planned, not available yet.
For how your information is handled, see the privacy policy.
Questions people ask
What is a company brain?
A company brain is the approved, shared memory of how a company works, which people and every AI tool the company uses answer from.
It holds eight kinds of knowledge: processes, decisions, pricing, roles, clients, goals, issues and lessons. A named person approves each entry before it counts, and every answer shows the entry it came from.
Is a company brain the same as a knowledge base?
No. A knowledge base stores pages anyone with edit rights can write; a company brain stores only what a named person approved.
A knowledge base mixes current and out-of-date pages, and an AI reading it cannot tell them apart. A company brain keeps one approved answer per question, by role and area, and shows its source on every answer.
Do I need a data warehouse?
No. A company brain does not require a data warehouse or a data team.
You start by connecting Claude or ChatGPT, uploading the documents you have and answering your industry's starter questions. If you already have a warehouse, it is one more source beside the others, not a layer in between.
Does Cerino copy our data from our tools?
No. Cerino does not connect to your tools today, so it does not copy data out of them.
Your AI assistant reads your tools through its own connectors, with the permissions you already gave it. Cerino holds what is proposed and approved, plus documents you choose to upload. Direct connectors are planned, not available yet.
Which AI tools work with Cerino?
Claude and ChatGPT, connected through MCP (the Model Context Protocol), plus Cerino's own app.
Once connected, the assistant asks Cerino for approved answers and sends back what it learns as proposals for a named person to approve.
What happens if we switch AI tools?
Your company brain stays where it is. You connect the new assistant, and it answers from the same approved memory.
Because the memory lives in Cerino rather than inside one assistant, nothing has to be rebuilt when your team changes tools, or uses Claude and ChatGPT side by side. Claude and ChatGPT are supported today.
Who can see what in a company brain?
Each person sees what their role and their areas of the business allow.
Owners, managers and staff have different access, and knowledge is filed by area, such as estimating or claims. The same rules apply in Cerino's app and through a connected assistant, and every change is recorded in an audit log.
How long does setup take?
Most of the work fits in a week: connecting an assistant takes minutes, and uploading documents and answering starter questions takes a few short sittings.
The longest part is approving what is right, a few minutes a day. How long it takes depends on how much your company has already written down.
What does Cerino cost?
Cerino is working with design partners now; pricing is on request.
Request access and tell us about your company, and we will talk through what fits.
How is a company brain different from ChatGPT or Claude memory?
Assistant memory belongs to one assistant and mostly to one person; a company brain belongs to the company and works across assistants.
In a company brain, a named person approves each entry, access follows roles and areas, and every answer shows its source. Assistant memory has no company approval step and stays behind when you switch tools.