Rob spent years trying to do everything himself. Most business owners do. The shift happened when he stopped adding more effort and started building systems that worked without him being in the middle of everything. Less chaos. More clarity. More time for what actually matters. That is the whole story behind Freedom Business. Now available as an audiobook on Spotify. What was the moment you realised effort alone was not enough? 👇

It is not just the big software costs that add up. It is the $10 here, the $15 there, the $20 a month for something someone signed up for six months ago and nobody uses anymore. We are hearing this from all kinds of businesses right now - including tradies - who are saying the same thing. "I am being smothered by systems, AI products, and software. Can someone just help me sort it all out?" That is exactly what a subscription audit does. We sit down, go through everything you are paying for, and work out what you actually need and what is just adding to the noise. Is your subscription list overdue for a proper audit? 👇

We can build the skills, instructions and connectors through Claude. Then you take over. Dashboards built. Connectors set up. Everything ready to use. And if something goes wrong, you can simply rewind. Simple, lean, and yours.

I've been playing with something that's a genuine time-saver for anyone running systemHUB. Video's below, but here's the gist. I've connected Claude Code to systemHUB via MCP. Told it: go into Systems, find the General Tech > Subscriptions folder, and turn every SOP in there into a learning track for a new technician. It worked through the folder, built the learning track, assigned it to the right team members, then went into Google Vid, pulled the summary wording from each SOP (keeping it under 800 characters for Google Vid's limit), and generated an avatar video talking through it. Same trick works for any role. New ops manager starting? Ask Claude to find every system tied to that role, create a training folder, and build the learning track automatically. Getting SOPs into systemHUB under the right department, tick. Turning them into onboarding learning tracks, also automated now. Still early days, but the more I connect Systems, Policies and Training together like this, the more gets automated. I'll keep sharing as I work through it.

When I map a Critical Client Flow with a client, I give them the same framing every time: start with the "Blue Skies" version. Blue Skies means everyone showed up, materials arrived, nobody called in sick, the client is ideal, the job is your most profitable one, and everything goes right from first contact to money in the bank. Map that version first. Not the exceptions. Not the edge cases. The perfect run. Why? Because the Blue Skies CCF is your Minimum Viable Systems. It is the lowest-hanging fruit in your whole business. The 20 per cent of daily activity that probably represents 80 per cent of your revenue lives inside that flow. Most owners stall on systemising because they try to document everything, including the weird scenarios that happen twice a year. They drown in edge cases before they have captured the core. Capture the spine first. The exceptions can wait. I wrote a whole chapter on this in my book Freedom Business, but the short version fits in one line: document the day where everything goes right, because that is the day you want your business to repeat without you. Who here has mapped their CCF? Did you start Blue Skies or did you get tangled in the exceptions first?