Florian Noutsos
← All articles

AI brain: what it is, and why you should build one

Published on

Every time you open a new conversation with an AI, you start from scratch. You explain again who you are, what you sell, to whom, and in what tone. It does good work, then it forgets. The next day, you start over.

An AI brain fixes that. It isn’t one more piece of software: it’s a folder.

A folder your whole AI team reads

An AI brain is a folder of text files holding what your business knows: what you do, your offers, your rules, your decisions, where each project stands. Every AI employee reads it before starting work. Instead of explaining again, you point to the brain.

It’s also what sets an AI employee apart from a simple agent: it doesn’t work from a one-off instruction, but from everything your business has already written down.

What goes in it

An AI brain has four main parts, plus a few map files at the root:

What’s insideFour folders, three map files
your-brain/
ContextWho you are, your offers, how you writebusiness.md · offers.md · style.md
EmployeesOne job description per AI employeewriter.md · bookkeeper.md
ProjectsWhere each one standswebsite.md · launch.md
SkillsThe procedures that keep coming backinvoice.md · follow-up.md
README.mdThe map: where to find what
AGENTS.mdThe AI’s working rules
CLAUDE.mdSame job, read by Claude
  • Context: your business, your offers, your typical clients, the way you write.
  • Employees: the job description of each AI employee. What it does, how often, with which tools, and what it isn’t allowed to do.
  • Projects: where each one stands, what’s been decided, what’s left to do.
  • Skills: the procedures that keep coming back. Preparing an invoice, writing a proposal, editing a reel.

The map files tell the AI where to find what and which rules to follow. Their names change from one tool to the next, but their job stays the same. And the AI keeps them up to date: when a decision is made, it writes it down in the right place.

How an AI employee uses it

Take a very simple request. Each piece of the sentence points to a folder in the brain:

ExampleOne request, and what it pulls from the brain

“Writer1: write a follow-up2 on my3 Tuesday quote4.”

  1. 1EmployeesWho gets the request: its job description, what it does and what it doesn’t.
  2. 2SkillsHow follow-ups are written in your business.
  3. 3ContextWho you are, your tone, your offers.
  4. 4ProjectsThat quote, that client, and where things stand.

Without a brain, your request would have had to contain everything: who you are, how you follow up, which quote you mean. With a brain, one sentence is enough. The employee fetches the rest.

Why not your AI tool’s built-in memory?

Almost every AI tool has a memory now. It helps, but it doesn’t replace an AI brain:

Side by sideYour tool’s memory, or an AI brain?
Your tool’s memory
  • The tool chooses what to remember, summarized its own way.
  • It’s locked inside that tool: switch tools and you start from scratch.
  • It’s yours alone: another AI employee, or a colleague, can’t reach it.
An AI brain
  • You can see what’s in it, and fix it.
  • It’s files: they move from one tool to another.
  • The whole team, human or AI, reads the same version.

How I keep mine

My agency runs on an AI brain. I built it because what I knew was scattered: instruction files in my projects, dozens of documents, about a hundred notes, several Notion databases. Four places means four possible versions of the same information. And a tool updated in one project could leave an old copy behind in another.

Now everything starts from a single folder:

My AI brain, simplifiedA map, rules, and folders
  • index.mdThe map: one line per project, decision and tool
  • CLAUDE.mdThe rules: how to write, what goes in, what never does
  • log.mdThe log: what changed, and when
  • projects/Where each one stands
  • decisions/Dated, with who decided and what they cancel
  • measurements/Every number, with its source and date
  • learnings/What I’ve learned, reusable elsewhere
  • tools/Where each shared tool lives

And a health check looks through it for contradictions, outdated decisions and numbers without a source.

My AI employees read it before they work, and add to it as they go. When I pick a project back up, they find the context there: I have nothing to explain again.

One rule has served me more than any other: wrong information is worse than missing information. An AI employee that reads a mistake repeats it with confidence. So an AI brain is worth what it holds that’s true, not its size.

Where to start

  1. Create a folder. Put one first file in it: who you are, what you sell, to whom, and how you write.
  2. Add a page for each task you already hand over to AI.
  3. Every time you catch yourself explaining something to an AI again, write it in the folder instead of the conversation.
  4. Ask your tool to read that folder at the start of every session. Most of them let you, with an instructions file or a project.

An AI brain can’t be bought off the shelf: it’s built from what you know. That’s why, in my offers, it comes before the first AI employee.