Six pillars. One operating system for your business. Start wherever you're stuck.
This hub is the map for everything on alistairvermaak.com. Every guide, framework, and template sits under one of six pillars — from the chaos most solo founders start in, through to the systems and AI leverage that let a business run without you re-explaining it every day.
Find the pillar that matches where you're stuck.
The six pillars below are sequential — each one assumes the last is at least partly in place. Information Chaos is the diagnosis. Documentation and Knowledge Management build the raw material. Business Systems turns that material into a repeatable operation. AI Readiness and Growth & Leverage are where the system starts compounding on its own.
If you're not sure where you fit, start with Information Chaos — nearly everyone does, whether they realise it or not. If you already know your gap, use the jump links above or the links at the bottom of each pillar to go straight there.
Content isn't the bottleneck. The system underneath it is. Fix that, and the content takes care of itself.
Everything on this site lives under one of these.
Information Chaos
Most solo founders don't have a content problem. They have an information problem. Ideas live in a phone notes app, half-written docs, forty open browser tabs, and a memory that's supposed to hold the entire business together. Nothing is written down in one place, so nothing can be reused, delegated, or handed to a tool that could do the work for you.
This pillar names the actual bottleneck: you, holding operational knowledge in your head instead of in a system. It covers how information chaos shows up day to day — repeated decisions, re-explained context, content that starts from zero every single time — and why it quietly caps how much a one-person business can produce, no matter how many hours you put in.
Read this pillar first. Every other pillar assumes you've accepted this diagnosis: the fix isn't more effort or more tools, it's capturing what you already know in a structure that compounds. Everything downstream depends on getting honest about where your business currently lives — scattered, undocumented, and dependent on you remembering it correctly.
- Why solo founders default to memory-based operations
- The real cost of re-explaining context every time
- How to diagnose your own chaos before you fix it
Documentation
Documentation is where information chaos starts to become an asset. This pillar covers the discipline of getting what's in your head onto a page — not polished manuals, but working documents you actually use: process notes, decision logs, standard operating procedures, and the plain-language write-ups that let you explain a task once instead of relearning it every time you do it.
The focus here is practical, not academic. You'll find frameworks for deciding what's worth documenting first, templates for capturing a process while you're still doing it, and guidance on keeping documentation light enough that you'll actually maintain it. Over-engineered documentation fails because it takes more effort to update than it saves — this pillar is built around the opposite principle.
Treat documentation as the raw material for everything else. A knowledge base with nothing in it is just folders. A business system with no written process is a habit that dies when you're tired, sick, or scaling past what memory can hold. This is the bridge between "I know how to do this" and "this business knows how to do this without me repeating myself."
- What to document first when everything feels undocumented
- Lightweight templates for capturing process while you work
- Why documentation has to be maintained, not just written once
Knowledge Management
Documentation gives you pages. Knowledge management gives you a system for finding, connecting, and reusing them. This pillar covers how to take scattered documents and turn them into a structured, searchable base — the difference between a folder of files and an actual second brain for your business.
You'll find practical approaches to tagging and categorising business knowledge, structuring a personal or team wiki that doesn't collapse under its own complexity, and building retrieval habits so information gets found in seconds instead of searched for in frustration. The goal isn't a perfect taxonomy — it's a structure good enough that future-you, or anyone you eventually bring in, can locate the right answer without asking you directly.
This pillar also covers the handoff moment: when your knowledge base stops being a personal reference and starts being infrastructure other systems can plug into — automations, AI agents, even a future hire. A knowledge base only you can navigate isn't leverage yet. This is about building structure that turns individual documents into a compounding, queryable asset for the whole business.
- Structuring a knowledge base that survives its own growth
- Tagging and categorisation that makes retrieval fast
- Turning personal notes into infrastructure others can use
Business Systems
A business system is what happens when documented, well-organised knowledge gets turned into a repeatable process — something that runs the same way whether you're rested, distracted, or on the other side of the world. This pillar covers how to design systems for the recurring work in a solo business: content production, client delivery, sales follow-up, admin, and anything you find yourself doing the same way more than twice.
You'll find guidance on identifying which processes are worth systemising first, how to design a system that's resilient rather than brittle, and how to build in checkpoints so systems stay accurate as your business evolves instead of quietly rotting in the background. The emphasis throughout is on systems designed for one person to run, not adapted from team or agency playbooks that assume headcount you don't have.
This is where the earlier pillars pay off. Documentation gives you the steps. Knowledge management gives you the reference structure. Business systems is where those pieces become an operating rhythm — the machine that keeps producing results whether or not you're the one actively pushing it that day.
- Choosing which recurring tasks to systemise first
- Designing systems built for a team of one
- Keeping systems accurate as the business changes
AI Readiness
AI tools are only as useful as the context you give them, and most solo founders feed AI the same scattered, undocumented information that's already causing chaos everywhere else in the business. This pillar covers what it actually takes to make your business "AI-ready": structured documentation, a navigable knowledge base, and clearly defined systems that an AI tool or agent can be pointed at and actually use.
You'll find practical guidance on preparing business knowledge for AI — writing context in a format models can work with, building prompt libraries from your own documented systems instead of generic templates, and identifying where an AI agent can safely take over a step in a process you've already defined. This isn't about chasing every new AI tool that launches. It's about making sure the infrastructure underneath is solid enough that AI adds leverage instead of adding another source of noise.
Readiness comes before automation. A founder who documents and structures their business well can hand real work to AI. A founder who doesn't ends up doing the AI's thinking for it every single time, which defeats the point entirely.
- What "AI-ready" documentation actually looks like
- Building prompt libraries from your own systems, not templates
- Where AI can safely take over a defined process step
Growth & Leverage
This is the compounding stage — where documentation, knowledge management, business systems, and AI readiness stop being separate projects and start working together as a single operating system for the business. This pillar covers what growth looks like once the underlying infrastructure is in place: less founder-dependent output, faster content and delivery cycles, and the operational slack that makes a location-independent, async-first business actually possible.
You'll find frameworks for identifying where leverage is being lost to manual, undocumented work, how to sequence which system to build or automate next, and how to protect the systems you've already built from quietly decaying as the business grows past them. Growth here isn't about doing more — it's about the business producing more without you personally doing more.
This pillar is the payoff for everything upstream. A founder who's fixed the chaos, documented the process, structured the knowledge, and built the systems is finally in a position to scale without becoming the bottleneck again. That's the entire premise of running a system instead of creating content from scratch every day: it compounds, and eventually it runs without you in the room.
- Spotting where leverage is lost to manual work
- Sequencing what to build or automate next
- Protecting systems from decaying as you grow
Not sure which pillar to open first?
Start With Information Chaos If
- Your business runs mostly from memory and open browser tabs
- You re-explain the same context to yourself every time you sit down to work
- Nothing you've built so far has stuck as an actual system
Skip Ahead If
- You've already got processes written down — head to Knowledge Management or Business Systems
- Your systems exist but you're trying to plug AI into them — go to AI Readiness
- The foundation is solid and you're ready to scale — go to Growth & Leverage
Get the next piece of the system every week.
The Systems Letter follows this same six-pillar path — one practical piece at a time, built for founders running the whole business themselves.
Join The Systems Letter →