Cornerstone
Simple Systems Saturday

AI for people who run a business.

Grab a coffee on Saturday morning and I'll show you one simple system you can actually use. Plain English, about sixty seconds, free.

One email a week. It's free, and you can unsubscribe in a click.

Most AI advice is written for people who write code.

I got tired of watching business owners get told they were falling behind, usually by someone demoing a thing they were never going to use. Meanwhile the change that would have helped was small, a bit boring, and sitting right there in their week.

So that's what I write about. One job, one system, every Saturday. How any of it works underneath is my problem.

And if an issue doesn't give you something you can use, I've wasted your minute. I'd honestly rather skip a week than pad one out.

Every issue

The same five parts, every week.

  • The mess

    The job as it runs right now, before anyone's built a system for it. You'll usually recognise it before the end of the first line.

  • The system

    The fix, in plain English. Three or four steps, and I'll skip the tool names unless the tool is the whole point.

  • Build it

    The bit you copy and paste. Twenty minutes or so, using software you're already paying for, ready to go on Monday.

  • Where it breaks

    In every single issue. Where it falls over, who it won't suit, and what I got wrong the first time I tried it.

  • The upgrade

    What the same system looks like once it runs on its own, and nobody has to remember it.

What one looks like

Have a read before you decide.

No sense asking for your email on a promise. Here's a whole issue.

Subject

The Friday report you rebuild every week

The mess

Friday afternoon. You're writing the same client update you wrote last Friday, from a blank page, digging back through Slack and your own memory to work out what actually happened this week. Four clients, about thirty five minutes each. You know the feeling.

The system

Two changes. First, cut the update down to five lines (what shipped, what's in progress, what you need from them, what's next, anything about money). Go and look in your sent folder. The replies you get are almost all about lines three and five. Second, stop reconstructing the week on a Friday. Remembering is the expensive part. The writing only takes four minutes.

Build it

  1. Pick one place per client for notes. The notes app on your phone is fine.
  2. Every time a piece of work finishes, add one line: the date, what shipped, one sentence on why it mattered. Twenty seconds, while it's still fresh in your head.
  3. On Friday, paste the week's lines into ChatGPT or Claude with this:
Here are this week's notes for [client]. Write their update using these exact headings: [paste your five]. Plain language, no adjectives, flag anything I'm waiting on them for, under 150 words.

Read it, fix the one line that sounds off, send it.

Where it breaks

Skip the twenty second note and you're straight back to thirty five minutes, except now you don't trust the drafts either. I'll be upfront: the first fortnight reads a bit flat, because your notes are still thin. Week three is when it gets good. Most people quit in week two, which is a shame.

The upgrade

The version running in a client's business collects the week's work on its own and leaves four drafts sitting there on Friday morning. Nobody writes notes. Nobody remembers to run anything. That's the job I do during the week, and it's where these all end up eventually.

Is this for you?

Come on in if

  • You run a service business and you're still doing the delivery yourself
  • You've got a small team and no real desire to hire your way out of it
  • You want AI doing actual work in the business, not writing your LinkedIn posts

Give it a miss if

  • You're a developer and you want the technical depth
  • You're after model releases, benchmarks and tool roundups

There are better newsletters than mine for both of those, and I'd rather you read those instead.

Who sends it
Cristo Van Rensburg

I'm Cristo. I started my first business at 16, selling firewood to the neighbours, and I was cold calling from my high school classroom a year later. Since then I've built systems in hospitality, construction, real estate, insurance, fintech and franchise operations, and for the founders of a podcast, a financing platform, an accounting practice and a sport academy.

Different industries, same bottleneck every time. The founder had become the operating system of their own business.

My job is working out the few places where AI can genuinely grow a business, building those properly, and leaving the rest of the noise alone. Nobody gets replaced along the way. I've also got no interest in tech that looks impressive on a slide deck and then does nothing for you on a Tuesday.

I'm not writing this from the sidelines either. I run a consultancy and development agency where I build custom operating systems for founders, using the exact things I write about in here. Every issue comes out of that week's work, which is why the steps are specific and why I can tell you where each one falls over. I've usually fallen over it myself first.

Some of what I try doesn't work, and I'll tell you about those weeks too. They tend to be the more useful ones anyway.

One system. Every Saturday.

The next one lands on Saturday morning. Put your email in below and I'll see you then.

One email a week. It's free, and you can unsubscribe in a click.