The Business Brain - Field Notes

This is the thinking behind the lesson, from someone who runs his company this way every day. Read it after the lesson. Steal anything.

What it actually is

A Business Brain is one folder of plain files that holds everything an AI agent needs to work for a business: who the business is, what it sells, its numbers, its customers, its rules, and what it is working on right now. The agent reads the files, does the work, and cites where every fact came from.

It is not an app, not a database, not a SaaS subscription. Plain files win for reasons that compound: any AI tool can read them, you can version them, you can diff them, the client can read them, and nothing about them expires when a vendor changes pricing. The intelligence layer keeps improving every few months; your files just sit there getting more valuable.

One brain, clients inside it

You do not build a brain per client. You have ONE brain - your company's working memory - and every client is a profile inside it. This matters more than it looks:

• Your delivery gets better with every client, because your rules, templates, and lessons live at the brain level, not trapped inside one client's folder.
• The agent can answer cross-client questions: which clients are waiting on me, what did I quote last time, which offer landed.
• Onboarding client five takes an afternoon, because the structure already exists. You are filling a profile, not designing a system.

The brain grows folders as your business grows. Mine has grown folders for content, playbooks, money, and tools that did not exist when it started. Do not build those on day one. Add a folder the week you actually need it.

The three rules carry everything

1. One owner per fact. Every fact lives in exactly one file. When it changes, you update one place. The moment a price lives in three files, your system starts lying to you slowly.
2. Nothing external without approval. The agent drafts; a human sends. This is not caution theater - it is the exact reason a business owner will let your system near their customers.
3. Scratch is not truth. Drafts and working files live in output/. Anything worth keeping gets promoted into the file that owns it. Never cite a draft as a source.

Everything else in the template is just folders. These three rules are the architecture.

Evidence discipline is the product

The habits from this lesson are not beginner training wheels - they are the whole difference between a system a business trusts and a demo:

• A call records what someone said on a date. It is evidence, not an approved fact.
• When two written sources disagree, the system shows both and names who decides. A good model usually catches this on its own; the brain makes it guaranteed instead of probabilistic.
• Unknown is a valid answer. A system that fills gaps with plausible guesses is worse than no system.
• Spot-check one citation on every build. Not because the AI is careless - because "I verified it" is what clients pay for.

The graduation ladder

Where this goes over the rest of the course, and in your client work:

1. Brain - the files exist, facts have owners, the agent answers from evidence. (This lesson.)
2. Reports - the brain produces something an owner reads weekly and acts on. First money. (Next lesson.)
3. Messy reality - PDFs, screenshots, voice memos flow in and the report absorbs them without lying. (Lesson after.)
4. Checks - the dangerous cases are saved in plain English and rerun after every change. Your test suite. (Stress-test lesson.)
5. Systems - revenue follow-up, ads, content: repeatable motions built on the brain, each with its own console and approval gate.
6. Connections - read-only API and MCP access to live tools, earned only after a recurring answer justifies it. Exports first, always.
7. Skills - packaged instructions the agent loads for specific jobs, so your best process runs the same way every time.

Each rung earns the next. Skipping to connections before the brain is solid is how you end up with an impressive demo that texts a stranger.

Prompts worth stealing

Paste these into your own agent, any time, and reverse-engineer what comes back:

Read my brain's structure only - folder names and file names, not
contents. Tell me which of the three rules I am most at risk of breaking
and why.

Pick one file in my brain and audit it: which claims have a source,
which are stale, which have no owner. Do not fix anything - show me the
list.

I am about to take on a new client. From my template and my last client
profile, list the exact questions I should ask in the kickoff call so
the profile fills itself from the transcript.

What never goes in

Passwords, API keys, login codes, anyone's data you do not have permission to hold, and employer material. The checklists folder in your download exists for exactly this. A brain full of things you should not have is not an asset - it is a liability with good formatting.