Start here · Lesson 1.2
How to Choose Brand Brain AI Tools: A Checklist
Lists that claim to rank brand brain AI tools usually imply a test the author ran. I have not run one, so this is not a ranking. It is a checklist you can use to judge any tool against what a brand brain needs, using documented facts where they exist and questions you can answer yourself where they do not.
The setup the checklist supports is taught in Lesson 1.2, Build your brand's brain, which uses Claude Code. Choosing a tool is a separate decision from building the brain, and the brain is portable enough that you can change tools later.
A brand brain tool needs four things: access to your files, a way to remember between chats, control over what it saves, and notes you can take elsewhere.
What a brand brain needs from a tool
A brain is a folder plus a short notes file. For it to work, the tool must read that folder, load the notes at the start of each session, and let you correct what it saves. Anything beyond that is convenience.
Here is what Anthropic's documentation says about Claude Code on those points. It says that when you run claude in a directory, it can access files in that directory and subdirectories. It says CLAUDE.md files give persistent instructions that Claude reads at the start of every session. It describes auto memory, where Claude saves notes such as your preferences. It also says Claude Code is a terminal based assistant that can help with tasks beyond code, such as writing docs and searching files. Those are the documented facts, and everything below is a way to check any tool for equivalents.
The checklist
- File accessCan the tool read a whole folder on your computer, or only what you paste in? Folder access makes the single business folder possible.
- Start of session memoryDoes it load your notes automatically, or must you paste them each time?
- Saved notes you can seeCan you open and edit the file it saves to, in plain text?
- Permission controlDoes it ask before changing or deleting files? You want a scan to be read only.
- PortabilityAre your notes plain files you could use in another tool?
- Privacy termsWhat does the provider do with your files and chats? Read their documentation, not a summary.
- Ease for youCan you actually operate it? A powerful tool you avoid is worth nothing.
Scoring it yourself
Make a simple table with the tools you are considering. For each row of the checklist, write yes, partly or no, with a note on how you found out. Do not score anything you have not checked in the documentation or by trying it.
| Checklist item | Why it matters | How to verify |
|---|---|---|
| File access | One folder for the business | Read the tool's docs, try a small folder |
| Auto loading notes | Stops retyping context | Start a new chat and see if it knows you |
| Visible, editable notes | Lets you correct errors | Find the file and open it |
| Permission prompts | Protects your files | Ask it to scan and watch for prompts |
| Portability | Avoids lock in | Check the notes are plain text |
| Privacy terms | Protects customer data | Read the provider's official policy |
A light test you can run in an hour
Pick a tiny sample: five files and a one paragraph description of a pretend brand. In each tool, do the same three things. Ask it to summarise the folder. Close the chat, open a new one and ask for a short post. Then check whether the second chat remembered anything.
Record the result in your own words. This is your test, not a published benchmark, and it only tells you about your own situation.
Chat only tools versus folder tools
Many assistants work as a chat box you paste into. They can still hold a brain if you keep a notes file and paste it at the start of each chat. You lose automatic loading and folder access, but the principle works, and for a small brand it may be enough.
Tools that run with access to a folder, such as Claude Code, make the folder based version smoother. They also need more care, because they can change files. Ask yourself whether you are comfortable approving changes, and start in a folder with copies, not originals.
What not to base your choice on
Avoid choosing from feature lists on marketing pages, claims of the best output with no method shown, and any ranking without a described test. Prices change often, so check the current plan on the provider's own page instead of a blog.
After you choose
Once you pick a tool, start small. Create a copy of a few files, not your whole computer, and run the scan there first. Watch what the tool asks permission for and what it does without asking. Read its documentation on memory so you know where notes are saved and how to edit them. Keep a plain text backup of your brain file outside the tool. If you ever outgrow your choice, that backup is your exit. Revisit the checklist every few months, because tools add and change features, and what was missing last quarter may exist now. Check the provider's own documentation each time instead of relying on memory or a blog post, including this one. If a feature matters to you, confirm it works with a five minute test using your own files.
Next steps
To see a brain built end to end, follow Lesson 1.2, Build your brand's brain. If tool setup is your sticking point, start with Lesson 1.1. A page to fill in is in the free template, and the manual comparison helps you decide if you need a tool yet.
Questions people ask
Which tool is best?
This post does not rank tools. Use the checklist against your own needs.
Do I need a folder based tool?
Not strictly. A notes file pasted into a chat works, with more manual effort.
Is my data safe?
That depends on the provider. Read their official privacy documentation before uploading customer information.