Most guides on this topic are written by people describing a thing from the outside. This one is not. We run a persistent context system of our own, a “second brain” for the business, and it sits behind the tools we build. So rather than tell you what a business brain is in theory, here is what it is actually like to run one, including the parts that are more tedious than the sales pitch admits.
Two honest notes before we start. This is our own setup and how we use it, not a product you can buy off us. And nothing here needs a big budget or a technical team; the principles are the same whether your brain is a polished system or a well-kept folder of documents. The value is in the discipline, not the software.
What it actually is
Strip away the name and a persistent context system is a single, organised, always-available store of everything the AI needs to answer and act as our business would.
That means the boring, load-bearing facts written down in one place the AI can always reach: our prices and how we scope work, our policies and the way we handle a job from enquiry to sign-off, the way we write to people so drafts come out in our voice, and the questions that come up again and again with the answers we actually give. When we ask the AI to draft something or help with a task, it is working from that, not from a blank slate. It is the difference between briefing a colleague who knows the business and briefing a stranger every single morning.
The “persistent” part is the point. It does not forget between conversations. What we taught it last month is still there this month. That is what turns a clever chat assistant into something that feels like it works here, rather than somewhere generic.
What we learned putting things in
The first lesson was about what belongs in a brain and what does not.
Good context is specific and stable. Prices, policies, product details, tone, standard answers. Things that are true across many jobs and do not change by the hour. Those earn their place because the AI leans on them constantly.
What does not belong is the noise. Early on the temptation is to pour everything in, on the theory that more must be better. It is not. A brain stuffed with one-off details, half-finished thoughts and things that contradict each other makes answers worse, not better, because the AI cannot tell what still matters. We got more value from a smaller, cleaner brain than from a bigger, messier one. Deciding what to leave out turned out to be as important as deciding what to put in.
The second lesson: write it the way you would explain it to a sharp new hire. Plain, direct, with the reasoning where it helps. Vague inputs give vague outputs. The clearer we wrote the source, the better the AI performed, every time.
The lesson nobody warns you about: maintenance
If there is one thing to take from this, it is this. Setting a brain up is the easy, satisfying part. Keeping it true is the real job, and it never fully ends.
A business changes. Prices move, policies get revised, you stop offering something and start offering something else. Every one of those changes has to make it back into the brain, or the AI will keep confidently answering with yesterday’s facts. And a wrong answer delivered with total confidence is worse than no answer, because you might not catch it before it reaches a customer.
So a stale brain is a genuine liability, not a neutral one. We learned to treat maintenance as a standing habit rather than a project with an end date: when something changes in the business, updating the brain is part of making that change, not an afterthought. It is unglamorous and it is the whole difference between a system you can trust and one you quietly stop relying on.
The upside, and it is a real one, is that maintenance is cheap once it is a habit. You change a document and every future answer changes with it. No retraining, no rebuild. You keep the source of truth current, and the tools that read it simply stay correct.
Why it changed what we can build
Here is the part that surprised us most, and the reason we bother.
Once the context was solid and trusted, building things on top of it got dramatically faster. Every tool we make, from quoting to job scheduling to the smaller helpers we spin up, would otherwise have to be told about the business from scratch. With the brain in place, that knowledge is already there to draw on. We stopped re-explaining who we are and what we do at the start of every build, and started from a running position instead.
That compounds. The first tool is the hard one. The tenth is far easier, because it inherits the same shared understanding of prices, policies and voice that everything else uses. A good brain is not just a better chat assistant; it becomes the foundation the rest of your AI work stands on. That shift, from re-explaining every time to building on top of what the AI already knows, is the honest reason we invested in it, and the reason we now build the way we do.
If you want to start your own
You do not need what we have to get the benefit. Start small and start with the truth.
Open one document. Write your prices, your core policies, the way you talk to customers, and your ten most common questions with your real answers. Put it in front of the AI whenever you ask it to work. That, kept current, is a business brain in its simplest honest form. Everything fancier is just a better way of storing and retrieving the same thing.
Where to take this next
Our flagship course, “Build an AI-ready business: give your AI a brain”, takes you through building and, just as importantly, maintaining your own version, step by honest step. It is on our courses shelf.
To pick the first things to write down, the AI Readiness Checklist on our free resources shelf is the fastest place to start.
And if you would rather build yours in a room with the people who run ours, come to our AI Automation Masterclass in Manchester. Tickets are normally £20. This one’s free, a limited-time offer to launch the series.