What is an AI brain?

Chatbot vs AI brain: one jump

Most owners use AI like a very smart search box. You open a chat, explain your business again, ask for something, copy the answer out and do the rest yourself. Every session starts from zero.

An AI brain flips that. The explaining happens once, in files the AI reads every time. It already knows your prices, your customers and your tone, and it can reach the tools where the work actually lives. So instead of asking it things, you hand it jobs.

Two things make the jump work: memory and hands. The brain is the memory. Connections are the hands.

What's inside an AI brain

No magic, no database. An AI brain is a normal folder on your computer, full of text files you can open and read. Here's the shape of one.

CLAUDE.md: the front page

CLAUDE.md is a file Claude reads automatically when you open the folder. It says who you are, how the folder is laid out and what the house rules are. Think of it as the induction you'd give a new hire, written once.

Context: what it knows

Context files hold the facts about your business: offers and prices, customers, your voice, your processes. They're plain text, so you can read and fix them. When the AI gets something wrong, you correct it once and it updates the file, so the fix sticks.

Skills: jobs it already knows

A skill is a saved set of instructions for a job you do often. Quoting, replying to enquiries, chasing an invoice, writing a post. You type a slash and the skill's name, like /quote, and it does the job the same way every time.

Connections: what it can reach

Connections let the AI work inside your real tools: Gmail or Outlook, your calendar, Google Drive or OneDrive, and more. They're built on MCP (Model Context Protocol), an open standard for plugging AI into apps. You sign in to each one yourself and can switch any of them off in one click.

Routines: skills on a timer

Once a skill works, you can put it on a schedule. A morning brief, a Monday numbers check, an inbox sort. Scheduled jobs run on your computer while the Claude app is open, once you've set them up.

What an AI brain does for a small business

The boring jobs first. That's where the hours are.

A tradie

Turns job notes and site photos into a quote in their own format, with their own prices, ready to check and send.

A cafe

Drafts the supplier emails and the weekly roster message, in the owner's words, from what's already in the inbox.

A consultant

Writes the proposal from the call transcript, in their structure and their voice, with the right package and price.

A salon

Drafts rebooking messages and replies to reviews in the salon's tone, so nothing sits unanswered for a week.

An online shop

Writes product descriptions, answers the common customer emails and pulls the week's sales into a one-page brief.

In every case it drafts by default. You read it, fix anything that's off, and press send. If you want it to send on its own, you switch that on yourself in the Claude app's connector settings.

AI brain vs ChatGPT, Notion AI and second-brain apps

Fair question, because they overlap. The difference is where your knowledge lives, and whether the AI can do anything with it.

Plenty of owners keep one of these alongside a brain. If your notes already live in Notion or Google Drive, connect it and the brain can read from there. And if you've spent months teaching ChatGPT about your business, you can bring that across instead of starting again.

How to build an AI brain

Six steps, in this order.

1. Get the Claude desktop app and a paid plan

   Download the app from claude.com/download on a Mac or Windows computer. You need a paid Claude plan, Pro or above. The brain lives in the app's Code tab. A fresh Mac needs one copy-and-paste setup step, once, and Windows needs Git installed.

2. Make the folder and write CLAUDE.md

   One folder for the business. At the top, a CLAUDE.md that says who you are, what's in the folder and the house rules. It's the induction you'd give a new hire, written once.

3. Load your context

   Offers and prices, customers, your voice, how you work. The quick way is to drop in what you already have (old proposals, sent emails, your website copy) and let Claude write the files for you to check.

4. Connect your tools

   Email, calendar and files first. You sign in to each one yourself inside the Claude app. Start with reading and drafting, and turn on sending later if you want it.

5. Turn one repeat job into a skill

   Pick the job you do most and enjoy least. Do it once with Claude, fix what's wrong, then ask it to save the method as a skill. Next time it's one slash command.

6. Put the boring ones on a schedule

   Once a skill runs reliably, set it to run on a timer, like a morning brief or a Monday numbers check. Scheduled jobs run on your computer while the Claude app is open.

That's the method. The hard part isn't any single step, it's the blank page: knowing what to write in the files and which jobs to hand over first. That's exactly what the live webinar shortcuts, with a complete pre-built brain you load with your own business.

What an AI brain costs

• The Claude plan. You need a paid plan, Pro or above. Check claude.com/pricing for the current price where you are. Heavy use can need a bigger plan.
• Your time. From a pre-built brain, a first working version takes a few hours. From a blank folder, longer. After that it improves every week you use it.
• Help, if you want it. The live webinar is US$99 and includes the complete pre-built brain to set up yourself. The AI Brain Build is US$2,000: Kieren builds a brain around your business, then finishes it with you over two calls.

What an AI brain can't do

Everyone selling AI shows you the wins. Here's where it stops.

• It doesn't run while your computer is off. It works on your machine, while the Claude app is open. Close the lid and the scheduled jobs wait for you.
• It doesn't send anything until you say so. Out of the box it drafts. Sending is a switch you turn on yourself, app by app, in the Claude connector settings.
• It isn't software. It's not a CRM, a database or a client portal. It works inside the tools you already have.
• It's only as good as what you put in. Thin context gets you generic output. The files are the whole game, which is why it gets better every week you use it.
• It isn't private by magic. The files live on your computer, but Claude reads them in the cloud to do the work. Keep identifiable client records, like health or legal files, in the systems built for them.
• It still needs you. You approve the work, you press send on anything that matters, and you make the calls. It takes the typing, not the decisions.

Questions owners ask