Your company brain is stuck in two people's heads

Company brain (definition): one maintained place that tells every AI tool who you are, what you sell, how you work and how you sound. For a small team, it is a handful of files in a folder the business owns, plus one rule: everyone works from the same files.

I just relaunched my website for brisk.vision. New look, new focus, and it's built around businesses like yours.

One piece of what I do now officially: building company brains and processes for small teams that don't have a tech person. Depending on the size of the project and how busy I am, I work with a small team of developers.

While I was rewriting the site, one Reddit post kept popping into my head. A small business owner on r/smallbusiness asked what to do because an employee won't give them access to the company's Facebook page. Their own page.

If you have a team, you probably know a version of this. The one person who knows the supplier login, the pricing exceptions and how the big client likes their invoices. And AI can make that worse before it makes it better.

Here's how. Three people on your team use Claude, and each one explains the business in their own chats. So worst case scenario, a customer gets one price in Monday's email and a different one on Thursday.

And you end up checking everything twice. Or triple. Which is the opposite of why you started using AI.

Honest upfront: I know this because I did it to myself first. The story below is mine, not a client's, so you get to see the mess without paying for it. And since it's my new website, yes, there's a call link at the end.

What is a company brain?

A company brain is one maintained place that tells every AI tool who you are, what you sell, how you work and how you sound.

Put simply: it's the onboarding pack you'd give a new hire, written down once, so Claude reads it before every answer.

It's not a new app. It's a handful of files in a folder you already have, plus one rule: everyone works from the same files. And this is the most important thing.

What you get: the same answer whoever on your team asks. Basically a new hire who's useful within week one. And fewer "quick questions" landing on you. If it's set up correctly.

What goes into a company brain?

• Who you are and who you serve
• Your offers and prices
• How you write and talk to customers
• How recurring tasks are done
• Decisions you've made, and why

Why does your team's AI give three different answers?

If you think this only happens once you have a big team, here's how fast it happened to me. On my own.

Until 13 October, my voice rules lived in four places. A file Codex used. A LinkedIn voice guide. A Substack voice file. And a pile of newer decisions that hadn't made it into any of them.

They partly disagreed. So every time I asked for a draft, I got a slightly different version of me back. It drove me up the wall.

The worst part? I'd update a voice file and feel very organised about it... and the next draft still broke the rule. Because there was another copy somewhere I didn't even know existed.

Claude was part of the mess too. It used whichever version it found. But to be fair, that one is fully on me. I'm the one who built the copies.

The fix was boring. I merged everything into one master file that every tool reads first. Channel files can add detail, but they never override it.

And the difference is real. Much less re-editing. Claude and Codex now work in the same folders, and I finally get back exactly what I want.

When something still goes wrong, I ask why straight away and change the instructions. And now, because there's only one main file, the change actually lands.

Now picture that in your business. Five people's chats and folders, five versions of how you work, and nobody knows which one is real.

Your customers notice before you do. And every fix you make lands in one copy while the other four keep the old version. Or worse, no version.

Frequently asked questions

These are the 10 questions I'd ask about a company brain if I were you. I checked the answers against Anthropic's own help pages (on 30 October 2026), so you don't have to dig through them. Prices and settings change, so check again before you buy.

Do I need to be technical to build a company brain?

No. If you can write an email explaining how you like things done, you can write a company brain. The hard part is getting your team to agree on what's true, especially around your processes.

Do I have to change my tools?

No. The brain is files, so your inbox, your CRM and your team's habits stay as they are. Nobody has to learn a new system on day one.

What goes into a company brain first?

Whatever you get asked about most. Usually that's what you sell and for how much, how you talk to customers, and how one recurring task is done.

One page each is plenty. Those three alone take a lot of "quick questions" off your plate.

What should never go into a company brain?

Passwords, API keys and bank details. Put simply: an API key is a password for software, so treat it like one.

Keep out client personal data you don't need, and salaries or HR notes too. Whatever goes in, every AI chat on your team can repeat.

Does Claude train on my business data?

On Anthropic's business plans (Team and Enterprise), Anthropic says it doesn't use your chats to train its models by default. The exception: if someone clicks thumbs up or down, that conversation can be used, but the account owner can switch that off in the settings.

On Pro or Max you're on the personal plan terms, which have their own privacy setting. If you're sharing client or business data across a team, that's a good reason to be on Team.

Can every employee see everything?

On the Team plan, a Claude project is either open to everyone in your company or private to the people you invite. Invited people get either "can view" or "can edit".

So your whole team can use the brain while only you (or one trusted person) can change it. Anything confidential, like finances or HR, goes in a separate private project.

What about GDPR and client data?

Anthropic has a data processing agreement that includes the EU's standard contract clauses where the law requires them. Put simply: the paperwork GDPR expects when your data is handled by another company.

The simplest protection is the one you control: keep client personal data out of the brain unless you really need it. For the rest, read the agreement and check with whoever advises you on data protection. I'm not a lawyer.

Who changes the company brain, and how does it stay one source of truth?

One owner. Everyone else reads. On the Team plan, give the owner "can edit" and everyone else "can view" rights.

If something's wrong, your team tells the owner instead of saving their own fixed copy. That's exactly how I ended up with four. The same goes for skills you share across your company as plugins: your team can use them but can't edit them.

What happens when someone leaves?

Nothing, if you set it up right. Keep the files in a folder the business owns, not in someone's personal account, and have the business owner set up the Claude project.

Then knowledge stays when people go. That's the Facebook page story in reverse.

What does a company brain cost?

A Claude Team standard seat is $25 per person per month billed monthly, or $20 billed annually, with a minimum of two people. Those are Anthropic's US prices. Prices vary slightly in Europe and taxes come on top.

The brain itself costs nothing but your time. Compare that to how many hours your team spends re-explaining things every week.

How do you start a company brain this week?

1. Pick one folder the business owns.
2. Write three files: what you sell, how you write, how you do one recurring task.
3. Name one owner.
4. Put the files into one shared Claude project.
5. Test it: two people ask the same question.

Same answer? It works. Different answers? Something in a file is unclear or missing, and now you know where to look.

Don't set up an automation just yet. Live with this setup until you are sure each team member gets the results they expect. When you do automate later (sorting emails, drafting replies), every automation reads the same brain, so it sounds like you from the very first day.

Want the long version? My free Build your own AI brain guide walks you through your first file.

Is Claude's Small Business plugin a company brain?

No. Maybe you've already seen this one. Anthropic launched Claude for Small Business in May. A plugin is a bundle of ready-made skills, workflows and connectors you add to Claude, and this one covers typical small business jobs.

To be fair, it's a useful starting point, and it comes with every paid Claude plan. But it doesn't know your prices, your tone or how your team handles a complaint.

The brain is the part it's missing. Plugin for the generic jobs, brain on top so the answers sound like your business.

Verdict: start with three files, not a plugin. One owner, one shared place, one test. Skip it for now if your team can't agree how the business works yet; sort that out on paper first.

What won't a company brain fix?

• It needs an owner. Without one, it goes stale and people quietly stop trusting it.
• More isn't better. Long, contradictory files make answers worse. Short and current beats complete.
• It won't fix a process nobody agrees on. It'll just hand you the disagreement faster.
• Claude can still get things wrong. Someone checks before anything goes to a customer.

PS: No time to write the files yourself? That's exactly what I now build for small teams. Book a free 30-minute call, bring one workflow, and I'll tell you honestly whether a brain would help.

Keep going: Prompt vs Skill vs Workflow · Claude Code without the terminal

Sources

All checked on 30 October 2026.

• Claude plans and pricing and What is the Team plan?, Anthropic
• Is my data used for model training?, Anthropic Privacy Center
• Manage project visibility and sharing, Anthropic Help Center
• How do I view and sign your Data Processing Addendum?, Anthropic Privacy Center
• Introducing Claude for Small Business, Anthropic

This article first appeared in my Substack newsletter, where I send one practical AI article every week.