Isn't a shared Google Drive just a shortcut that will break later?

It's a first step that genuinely works up to a point and stops working beyond that point. The signal to upgrade is specific: team members regularly search for a system and can't find it within 30 seconds; documents have drifted out of date and nobody knows which version is current; new hires need a human guide to navigate the library. Below those signals, Google Docs are fine. Above them, a dedicated platform earns its cost. Most small businesses don't hit those signals until 40-80 active systems, which is later than owners usually think.

Why do so many owners upgrade prematurely?

Because buying a tool feels like making progress and maintaining a practice feels like stagnation. The truth is the opposite. Consistent practice on cheap tools produces more operational improvement than shiny tools with no practice. Owners who haven't yet built the practice often assume the tool is the missing ingredient; they buy the tool, the practice still doesn't form, and the library remains empty. The order matters: habit first, platform second.

Does this advice apply in regulated industries?

Partially. The documentation discipline is the same. The storage and access controls aren't — regulated industries need audit trails, role-based permissions, and defensible version histories that free tools can't reliably provide. The upgrade in that case is driven by compliance defensibility, not by systemisation quality. You can still build the library cheaply; you just can't run it on Google Docs long-term. Build cheap, then move to a compliant platform once the library and discipline exist.

What's the single biggest mistake with cheap systemisation?

Letting the library grow without a naming convention. 30 documents in a shared folder is manageable; 100 documents with inconsistent naming is chaos. The naming discipline is almost free to install and saves hours per week forever after. Most cheap systemisation efforts that collapse collapse at this specific failure mode — not because the tools were insufficient, but because the discipline drifted.

The Little Secret for Building Business Systems Cheaply

The best-built business system I've ever seen cost $0 to build.

It was a Google Doc, a Loom video, and a shared drive folder. The owner spent three hours documenting it, one hour training the team against it, and fifteen minutes a quarter keeping it current. Four years later the system is still running, still producing consistent output, and has outlasted three different "professional" platforms the business tried to upgrade to and quietly abandoned.

That's the little secret. The quality of a business system has almost nothing to do with the budget spent building it. It has almost everything to do with one specific discipline that the expensive version and the cheap version both require — and that the expensive version often obscures.

What the discipline actually is

The discipline is: the practitioner does the documenting, not the owner, not a consultant, not a writer. The person who does the work writes down how they do the work. Someone else (ideally a Systems Champion) reviews it for gaps and clarity. That's the entire secret.

Every expensive systemisation effort I've watched fail has violated this discipline. An external consultant interviews the practitioner, writes a polished document, and hands it back. The document reads beautifully and doesn't match what the practitioner actually does day-to-day. The team ignores it. The business spends $20,000 for an artefact that sits in a folder.

Every cheap systemisation effort I've watched succeed has honoured this discipline. The practitioner opens a Google Doc, writes their process in their own language, records a Loom showing the weird cases, and ships it. The document is less polished. The team actually uses it. The cost was zero.

Polish is not the variable. Practitioner voice is the variable. The practitioner's voice is cheap; a consultant's polish is expensive; and the cheap version produces the usable document.

The $30/month stack that covers 80%

For most small businesses with 5-50 people, the complete minimum viable systemisation toolkit costs about $30/month:

A shared drive (Google Workspace, Dropbox, or similar) — already paid
Google Docs or equivalent — included
A screen-recording tool (Loom, ScreenPal, or even the built-in OS recorder) — $0-15/month
A shared channel (Slack, Teams, or existing comms) — already paid
An AI assistant for drafting (Claude, ChatGPT, or similar) — $20/month

That's it. Every expensive alternative is an optimisation on one of these five categories, and most businesses are nowhere near having saturated the free tier's capability before they upgrade.

The pattern I see is that owners upgrade tools hoping the upgrade will produce the discipline. It doesn't. Bad discipline in a $10,000 platform is still bad discipline. Good discipline in a Google Doc is still good discipline. The platform follows the habit; the habit doesn't follow the platform. (For the broader pattern on this, how to build business systems on a small budget walks through when platform upgrades actually start paying back.)

Doug and Andrea Glanville and the multi-decade Google Docs library

Doug & Andrea Glanville on Sydney String Centre — a third-generation retailer whose systemisation library was built on shared documents and disciplined practice, not on expensive platforms. Read the full case study

Doug and Andrea Glanville run Sydney String Centre — a third-generation musical instrument retailer with ~40 staff, two stores, a rental programme serving thousands of school-age musicians every year, and operations that have stayed reliable across decades of economic cycles that closed every other independent competitor in their category.

The systemisation infrastructure underneath the operation is not exotic. The family has built and maintained the systems library primarily in shared documents with supporting videos. No enterprise BPM platform. No five-figure consulting engagement. No certifications on the wall. What they have, instead, is disciplined practice: every process owned by the practitioner who runs it, every system reviewed on a known cadence, every new hire trained against the documented standard, every gap closed by someone specifically accountable for closing it.

The result, over thirty-plus years, is a business that feels systemised because it is — built on tools that most owners would dismiss as insufficient. The lesson isn't that expensive tools are bad. It's that they're optional. The real investment was the discipline of practitioner-led documentation, reviewed regularly, held to a quality standard the team actually cares about.

Where cheap genuinely does break down

Not everything can be systemised cheaply forever. Three honest exceptions.

Very large libraries. Once your library exceeds roughly 50-80 active systems, finding things in Google Docs starts breaking. The search is imprecise, relationships between systems aren't visible, and version control becomes fragile. At that scale a dedicated platform does real work that free tools don't. The signal is: team members are searching for things and not finding them.

Compliance-heavy industries. Regulated industries (medical, financial, legal in specific contexts) need audit trails, access controls, and version histories that free tools can't reliably provide. If your business has compliance requirements, the upgrade is about legal defensibility, not systemisation quality.

Distributed teams at scale. Beyond 30-50 people across multiple time zones, asynchronous collaboration starts requiring better tooling than a shared drive. The upgrade is communication infrastructure, not systemisation infrastructure — but they intersect.

Outside those three, cheap usually wins. And even inside those three, most businesses overestimate how close they are to the breakdown point. The honest answer for most 5-50 person small businesses is: the cheap stack is enough, and upgrading prematurely is one of the most common budget leaks in small business operations.

What AI changes in the budget equation

The newest element in the equation is AI — specifically how dramatically it compresses the cost of documenting and maintaining a library.

An AI assistant can draft a first-pass system from a 20-minute voice recording with the practitioner. It can review existing documents for gaps. It can keep the library current by auto-flagging documents that reference obsolete tools or procedures. It can produce training materials from a single documented system. All for $20/month.

The consequence: the "professional" version of systemisation — the expensive consultants and enterprise platforms — is losing its economic moat against disciplined practitioners armed with AI. The quality gap between the $500/hour version and the $20/month version keeps narrowing. The remaining gap is discipline, which, as established, doesn't scale with budget.

The owners who will win the next five years of systemisation aren't the ones investing in platforms. They're the ones installing the practitioner-led discipline with AI augmentation. The budget required is trivial. The returns are compounded by the fact that most of their competitors will still be spending 20x more for the same or worse outcome.

The first brick

Pick one process in your business tomorrow. Not a big one. A small one. How you invoice a client. How you onboard a new team member's first week. How you respond to an inbound enquiry.

Have the practitioner — the person who actually does the work — open a Google Doc and write down the steps. Record a Loom walking through it with commentary. Link the two in a shared folder. Share the folder with the team. Run a quick 15-minute review with someone else (ideally a Systems Champion) to flag anything unclear.

That's the first brick. Time cost: about two hours. Dollar cost: $0. Quality of the resulting system: comparable to or better than what a consultant would have produced in a week for $5,000.

The second brick is the second process next month. The third the month after. Twelve processes a year, built cheap, owned by the practitioners, reviewed regularly, compounded over three to five years — that's a genuinely systemised small business, built for less than the cost of one consultant engagement most owners assume they need.

Quantify what un-systemised costs right now: Cost of Chaos

Most un-systemised operations carry 5-15% of revenue as operational drag. Cost of Chaos makes the number visible — which is almost always larger than the $30/month the cheap systemisation stack would cost.

Ready to start cheap? The Cost of Chaos Calculator quantifies what the current un-systemised state is costing you — which is almost always more than the $30/month the fix would require. Before spending on platforms, run the SYSTEMology Starting Point to see which process to document first. Then house the library in a systemHUB free trial when you're ready for the upgrade.