My whole business runs on a system I built for myself. One person, a stack of live projects, and every piece of context about every client held somewhere my AI tools can actually read.

This month, I watched EightyOne Media - a Wellington advertising and media agency, a tight team who don't know what GitHub is, and have no reason to - start running the same system on their own client accounts.

I've been quietly celebrating ever since.

There was no path except through

The engagement started somewhere much smaller. Individual AI projects, built for individual people, delivered to one machine at a time.

Each one worked. And each one surfaced the same problem: the tools were disconnected from the client information.

For a B2B service business, the client information is the whole thing.

That realisation only comes from building. There was no path to it other than through.

What 81M needed was what Growth Medium AI already runs on. So I proposed exactly that, they agreed, and we built it together - with them as design partners as well as the first business I've delivered it for.

What a client brain actually is

We built one "brain" for one of the agency's customers. It's the agency's tool - their customer never sees it - and we build one per client, so each customer's information is completely separated from every other's.

A brain holds every piece of context the business has about that client. The strategy documents. The meeting transcripts. The email threads. What was decided, what's still open, and who owns the answer.

The plainest description I have is a context management system. Everyone knows what a content management system does for a website - this does the same job for what your business knows about a client.

Under the hood, we were deliberate about what does which job. Where a task is mechanical, plain code does it - no AI involved, same answer every time. Where judgement is required, AI skills carry it. And where the agency's values require a human, a human is in the loop by design.

In parallel, everything we learned got backfilled into a template. Client number one took weeks of teething. Clients two through one hundred can be set up in seconds.

The muscle, not the brain

I call these systems brains, and I want to be careful with that word.

When this agency talks to their own customers about AI, their line is that AI is the muscle, not the brain. I think they've got that exactly right.

The brain we built is really a memory. The judgement, the taste, the years of knowing why a campaign will or won't land - that stays with the people.

We're not extracting the human judgement and expertise from the process. We're clearing space for more of it, because that expertise is what actually drives value for the client.

The system remembers, so the people can think.

The real test was never technical

A system like this dies on a shelf if the team can't drive it. The people using it every day aren't developers, and they shouldn't have to become developers to benefit.

So the day-to-day is a handful of habits. Start your session with one command. Feed in anything new. Save your work with another command when you're done.

That's more or less it. The version control, the file management, the consistency checks - all of it happens underneath, and nobody on the team ever has to see it.

I made cheat-sheets for which skill does what and why. My guess is that within a few weeks nobody will need them.

And the adoption is the part I'm celebrating. The team are asking smart questions, suggesting genuinely important enhancements, and starting to describe what their business looks like now this exists.

We've also identified an internal owner, who I'll coach to take over the day-to-day running and troubleshooting from me. A business asset you can only operate through your consultant isn't really yours.

Beer o'clock

If you're a business leader weighing up spend on something like this, the argument I'd actually put in front of you is about headspace.

The information your team used to carry between meetings, or dig back out of email threads, is now managed for them. They can close their laptops at beer o'clock and genuinely stop thinking about work.

Better yet - they can pick up tomorrow from exactly where they left off, just by running a couple of skills.

That's headspace back. Space to think strategically, to zoom out, to stop only fighting fires. Take back your weeknights and weekends.

I'd go as far as to say it's a quality of life improvement.

Your customers feel it from the other side, too. Nothing about their account slips through the cracks, the context behind every piece of work is current, and the thinking that reaches them is sharper because the grind isn't eating it.

It's an important reframe - this was never just a productivity tool. It's a driver of business growth and customer happiness.

Infrastructure, at last

Before we went down this road, we were dealing with challenges piecemeal. A tool here, an assistant there, each one useful and each one an island.

This is infrastructure. It's a business asset that compounds as the team feeds it, and it means a far broader scope of tools and capabilities can now be built on top of it.

It's really exciting that the system I trust enough to run my own business on does translate to a team - habits, cheat-sheets, beer o'clock and all. Making it a multiplayer was the hardest part, but we did it.

Watching that land has been the best part of this year's work.

I've Just Delivered My First Client Brain