One Document the AI Reads First
10 min read
If you took the skills course, each of your skills went through a setup interview: it asked for your prices, your services, your tone, and it kept those answers. That works beautifully for one skill. Install five, and you have created a problem the skills course never had to face: your business now exists in five slightly different versions.
The drift problem
Say you raise your service-call rate in March. You remember to update the Quote Builder, because quoting is where prices live in your head. You do not think of the invoice-chasing skill, which mentions the old rate in a payment reminder two weeks later, or the marketing skill, which quotes it in an April promotion. Each skill is doing exactly what it was told. The problem is that "what it was told" was five separate tellings, and only one of them got the news.
This is drift, and it compounds. Every fact you store in more than one place will eventually disagree with itself, and the disagreement always surfaces in front of a customer.
The Brain: store once, reference everywhere
The fix is a rule borrowed from every well-run database: store each fact once. The Business Brain is a single document that holds everything true about your business that more than one skill needs: identity, offers, prices, customers, voice, policies, and a dated section for what is true right now, this month.
Skills stop storing this context themselves. Instead, each skill's setup section changes from "ask the user for their rate card" to one line:
## Setup
Read the Business Brain document provided at the start of
the conversation. All prices, services, policies, and voice
guidance come from it. If the Brain is missing or a needed
fact is not in it, say so and stop; do not guess.In practice, running a workflow starts with pasting or attaching the Brain (in Claude Projects or a ChatGPT equivalent, it can sit in the project files permanently). The skill carries the job knowledge, how to build a quote, how to chase an invoice; the Brain carries the business. One update to the Brain, and every workflow gets the news at its next run.
What goes in, what stays out
In: anything two or more workflows need, and anything that changes on a schedule. Prices, service definitions, hours, service area, your three customer types, voice rules, standing policies (deposit terms, warranty language, response-time promises), and this month's promotions or closures.
Out: three categories.
- Job-specific instructions. How to structure a quote belongs in the Quote Builder skill, not the Brain. The Brain is what your business knows; skills are what your workers know how to do.
- Anything secret. Passwords, banking details, customer personal records, employee matters. Chapter 5 draws this line precisely; for now, the rule is that the Brain should be a document you could show a new hire on day one without checking with anyone.
- History. Last year's prices, discontinued services, old promotions. The Brain describes the business as it is today. History goes to the archive folder.
Why one document beats a clever memory feature
Assistants increasingly offer built-in memory, and it is tempting to let the tool remember for you. Resist it, for one reason: you cannot read, correct, or hand over a memory you cannot see. The Brain is a file. You can open it, spot the stale price, fix it, date the change, and give a copy to your office manager. Every alternative fails at least one of those tests.
Try it now
Open the skills you currently have installed and list every business fact each one stores: prices, services, tone notes, policies. Put them in one list and mark the duplicates. Anywhere the same fact appears twice, check whether the two versions still agree. Most people find at least one disagreement, and finding it now, on paper, beats finding it in a sent quote. This list is the raw material for the next lesson, where you write the Brain itself.