Eight years of business systemisation condensed into one real example

Executive overview

Most small businesses try to systemise too early, building SOPs and handbooks before they know what actually needs to happen. The right sequence is hypothesis first, then iteration, then documentation — only after enough reps to know what's true.

Start with the smallest possible experiment that can prove or disprove your assumption, and build the system around what survives.

Confirming product-market fit before building anything

• Run 50 short sales calls before writing a single process doc
• Use a one or two sentence email invite — no screening, no expectation-setting
• Let prospects describe their ideal outcome; if it matches your offer unprompted, that's signal
• Test pricing live on calls: quote a number, watch the reaction, raise it for the next call
• The goal is conversations, not conversions — information first

Setting up the minimum viable CRM

• Track every prospect from day one, even if the tool is simple
• Build a lightweight CRM inside your existing work management tool (ClickUp, Asana, Monday, etc.)
• Automate the intake: booking triggers a record; the record triggers three follow-up tasks
• This setup takes 60–90 minutes and removes reliance on memory
• Every small business — solo or 50-person team — needs a work management tool

Running fulfillment as a hypothesis

• Write down a sequenced list of ~10 delivery steps before the first client starts
• Attach a target date to each step — a guess is better than nothing
• Keep a running notes task inside each project for everything that felt off
• At project close, review those notes and implement small fixes before the next client
• Avoid big structural changes early — if it takes 10 hours to build, wait for more reps

Knowing when to make the bigger investment

• After five clients, patterns become clear enough to justify larger system changes
• Build the heavy-lift item (e.g. a client portal) only once you're confident it solves a recurring problem
• Roll it out as a beta to two clients, collect feedback, iterate, then release to all
• Over-systemising before you have enough data is a sophisticated form of procrastination

Documenting for others to deliver

• Once you know what needs to happen, by whom, when, and why — build the playbook
• Co-create documentation with the people who will use it; don't pre-build hypothetical handbooks
• Only build what the next step actually requires; add more only when someone asks for it
• If you build SOPs for things people don't need, you never get that time back

Attaching metrics to every phase

• Phase 1 metrics: number of sales calls and number of sales
• Phase 2 metrics: client satisfaction, personal enjoyment, profit margin
• Phase 3 metrics: per-coach scorecards, client satisfaction, overall margin
• Pair metrics with a workload view to schedule clients only when capacity exists
• Establish recurring routines: weekly call review, monthly metrics check, quarterly asset review