You’ve decided to document. The question is where it lives.

Because they do different jobs. Your AI is the engine. systemHUB is where the knowledge it runs on lives, in a form a human can also read.

Put your processes only inside an AI and they exist in one person’s account, with no owner, no review date, and no way for anyone else to know they’re there. That’s not a system, it’s an invisible one. Connect the two and the AI answers from your live processes instead of a copy somebody pasted in six months ago.

The full argument →

None of them, permanently. The leaderboard changes every quarter, and each platform quietly makes leaving expensive: chat history, custom instructions, and prompts that don’t transfer.

Keep the knowledge layer in systemHUB and the choice stops mattering. Whichever AI is best this month reads the same record through MCP, and swapping costs you nothing. Why you shouldn’t go all in on one AI →

You can, and plenty of businesses start there. The failure isn’t technical, it’s that nothing tells you what to document first, nobody owns each document, and there’s no signal about what’s current.

Six months in you’ve got a folder nobody opens, and the team is back to asking you. Storage is not documentation.

False starts are normal, and the conclusion people draw from them is usually wrong. It’s not that your business can’t be systemised. It’s that you stopped before reaching minimum viable systems.

In Dave’s words: “People then go, oh yes, we tried to systemise, but it doesn’t work, our business isn’t systemisable. And it reinforces that behaviour.” The fix is a smaller starting scope, a Systems Champion who isn’t you, and a real pain to solve first rather than a tool to roll out.

This is the most common concern we hear, and it’s almost always a tooling and culture problem rather than a people problem. Most of the resistance is front-loaded onto existing staff, and most owners quit right at that hump.

Every team member needs to understand what’s in it for them. As Dave puts it: “Do you know how you move your way up in our organisation? You capture your process and you delegate your tasks down. That doesn’t make you less valuable, that makes you more valuable.”

Your calendar is never going to open up on its own. Systems work is permanently important and never urgent, which is why “I don’t have time” is usually the signal you need it most.

It also isn’t your job. The person doing the work records themselves doing it once, and somebody else turns that into the procedure. Owners who try to write it all themselves burn out, give up, or both.

This is the question that stops people who already agree with everything else. It usually sounds like “our delivery process is enormous, how do we possibly capture that”, or “is booking a patient in sales or operations?”

You start with the Critical Client Flow. That’s the path a customer takes from first contact to money in the bank, and it’s usually 10 to 15 processes covering about 80% of what actually runs your business. Not the org chart, not every department, just that one line.

Document those, and the rest can wait. Most people who stall started too wide.

You shouldn’t, and it’s a real failure mode. One of our members puts it well: people get into their groove and start systemising anything with a heartbeat, including things that aren’t worth systemising yet.

A process earns documentation if it meets one of four tests. It happens often, it currently depends on one person, mistakes are expensive, or you’re about to hand it to someone else. If it fails all four, leave it.

Documentation is a cost as well as an asset. A hundred systems nobody opens is worse than fifteen the team actually runs off.

Fair question, and the honest answer is that you should be deliberate rather than paranoid. Truly sensitive material, personal, medical, or financial, shouldn’t be going into a general AI tool at all.

Inside systemHUB you control access document by document, for people and for the connected AI. Your AI can understand how you quote without ever seeing the salary review. That’s the point of putting permissions on the source rather than trusting a chat window.

Two different situations. If you genuinely don’t have product-market fit yet, don’t systemise. Find what works first, then document what you want repeated.

But if you’re established with a couple of staff or subbies, small is easier to systemise, not harder. There’s less to capture and less legacy to unpick. Start ugly, record yourself doing the work, and improve it later.

That’s a fair pet peeve and we share it. The trouble with a lot of ISO work is that the only time anybody opens the systems is when the audit comes around.

Worth noting that certification doesn’t solve this by itself. One of our members came to us already holding ISO 9001 and 27001 and still had the same problem: plenty of documented process, plenty of team pushback, nobody using it day to day.

This is the opposite. Active documents the team trains against and uses daily, with problems surfaced and fixed as they come up rather than at an annual review. If nobody opens it, it isn’t working, and that’s a design failure rather than a compliance one.