The AI System That Runs My Business (I Wrote It Up as a Research Paper)

You do not need a big software platform to run a capable AI system. A well-organised set of plain text files is enough.

Let the machine handle the boring upkeep: deciding what to load, remembering decisions, running on a schedule, and staying inside a budget.

Keep your AI readable and yours, not a black box you rent. You should be able to open the whole thing in a text editor.

Never let automation take an irreversible step, like sending an email or spending money, without a human saying yes.

For a long stretch now, almost everything in my business has been run by a single AI system I built on a normal laptop. It writes and publishes my brand’s product pages, drafts and schedules content, sorts three inboxes, files my invoices, plans my week, and even keeps its own memory so it does not forget what we decided last month. Most of it happens on a schedule, while I am asleep or at the bench.

I sat down and wrote the whole thing up properly, as a research paper. Not because I need an academic stamp, but because writing it the rigorous way forced me to be honest about what actually works, what the real numbers are, and where it falls short. Here is the plain version, and you can download the full paper at the end.

What it actually is

The idea at the centre is simple. You do not need a heavy software framework to run a capable AI system. You need a well-organised set of plain text files. Folders and simple documents hold the instructions, and the AI reads the right file at the right moment. The entire system is something you could open and read in a text editor. Nothing is hidden.

That is the same principle I teach inside the academy: your AI should be something you own and can understand, not a black box you rent by the month.

What it does, in plain numbers

The system carries more than ninety distinct skills and over a dozen specialised helper agents, all reached through one simple router that decides what to use for each request. It runs thousands of scheduled jobs across the weeks, quietly, and it keeps itself reliable: nearly every skill sits at a clean, error-free state.

It also looks after itself. It keeps its running costs in check with a built-in budget limit, and it keeps its own memory small enough to stay fast by archiving what it no longer needs, automatically. When it once let its own notes balloon, it noticed and now trims them on its own.

Tip
Want the full technical write-up? Download the research paper (PDF). It is readable in an afternoon, and the most useful parts are the architecture overview and the honest limitations at the end.

Why I am sharing this with you

Two reasons. First, proof. When I tell you the AI methods I teach are real and not hype, this is the evidence: a working system, measured honestly, limitations and all.

Second, this paper is essentially the blueprint behind the system I help makers build for their own studios. You will recognise the ideas: own your tools, keep them readable, let the machine handle the dull upkeep, and never let it act irreversibly without your say-so. You do not need to be technical to apply any of it.

Build your own version

This is the engine. Inside the membership, we build your version of it together, one piece at a time, shaped around your craft and your business rather than someone else’s. If you want the system that looks after the admin so you can stay at the bench, that is exactly what we work on together.