The Workshop

Eight weeks andyou'll build ityourself.

You'll come out knowing exactly what this technology can do inside your business, able to point it at anything, with three working systems running to show for it. I teach, you build, on your own real work.

8 weeks2 sessions a weekMax 8 businessesBring your team
Why this exists

Everyone tells you AI matters. Almost nobody shows you the mechanics.

Most owners I talk to have already tried. A subscription somebody recommended, a tool that looked good in the demo, maybe an agency that took thirty thousand and delivered a chatbot. Six months later the business runs the way it always did, and AI is filed somewhere between hype and a money pit.

You've taught yourself harder things than this. What's been missing is somebody showing you the mechanics, on your own business, until you can do it without them.

There's a real difference between a company that uses AI and one that bought some.

The businesses on the right side of that line aren't running better software. Someone inside them understood how this actually works and pointed it at the parts of the operation holding everyone back. That's a skill, and it's learnable in eight weeks.

What you'll actually build

A system is a job that stops needing you.

Not a chat window you go and ask things. A job you repeat every week, turned into something you run in one line, or something that runs on a schedule while you're on site. Things like these.

The quote off the enquiry

Enquiry lands, the quote comes back drafted in your pricing and your words, waiting for you to check it rather than write it.

The invoice that chases itself

Day seven, a polite nudge. Day fourteen, a firmer one. Nobody has to notice it went unpaid.

Monday's report, from live numbers

Written off what's actually in your systems this morning, not off what you can remember about last week.

The meeting, filed

Notes written up, the project updated, the follow ups pulled out and put somewhere they'll get done.

Three of them, built by you, running in your business by week eight. Which three comes out of your own audit in week one. It doesn't come out of my curriculum.

What you walk away with

Three things, by the end of week eight.

01

You'll know what this can actually do

Look at any process in your business and tell whether AI can take it, what building it would involve, and whether it's worth doing.

02

Three systems you built yourself

Running in your business, used on a normal Tuesday. Plus your operation documented, which is what makes the fourth and fifth faster than these three.

03

Evidence, not a feeling

The same audit run in week one and week eight, so you can put a number on exactly what changed.

The systems are the visible part. The judgement is what you're really buying, because in twelve months the tools will have moved and the person who understands how it fits together will still be ahead.

Where you aim it

The audit.

In the first session you and I map your week. Every task that repeats, how often, roughly how long, and whether it's the work you're good at or the work that simply has to get done.

Most people who try AI alone point it at whatever they read about that week, get a mediocre result, and decide the technology is overrated. You'll be aiming deliberately, from week one.

Week one

The before

A map of how your operation runs, which becomes the shortlist of what you build. You never waste a week on the wrong thing.

e.g. 17h / week

On work that isn't your craft

Delta

Week eight

The after

Same questions, same method. The gap between the two is what the eight weeks were worth.

e.g. 9h / week

8 hours a week back

Figures illustrative. Your starting number is whatever your audit says it is.

Taking the risk off you

You shouldn't have to take my word for it.

Skill is hard to put a number on, so I'll guarantee the thing that's easy to measure. If the capability is real, it shows up in the audit.

Five hours a week back, per seat, or that seat runs free for the next eight weeks and I keep working with you until it does.

Every seat runs its own audit, so a team of three gets judged three times. Five is the floor I'll put in writing, not a description of a good result. If your audit opens at seventeen hours, I'd expect to beat it comfortably.

What I need from each seat

  • Both audits, week one and week eight
  • 12 of the 16 sessions, or catch up on the recordings
  • Three systems shipped from your own shortlist
  • Use your support rather than getting stuck quietly

If it falls short

That seat runs the following eight weeks at no charge and I work with whoever holds it until they're past five hours. No forms, no argument. If the audit says four and a half, that's a miss and I'll treat it as one.

The eight weeks

Eight weeks, one thing built at a time.

You learn something and use it on your own business the same week. No theory you'll get to later.

  1. 01Set up, and find where the time goes
  2. 02Teach it your business
  3. 03Why structure beats clever wording
  4. 04Build your first system
  5. 05Plug in your real data
  6. 06Make it permanent
  7. 07Get it running without you
  8. 08Prove it worked
Weeks 1 to 4 · Getting your own work in order
Week1

Set up, and find where the time goes

What you learn

Getting everything installed, and how to work without risk of breaking anything. It shows you what it plans to do before it does it, and you can undo back to any point.

Why it matters to you

Most people never really start because they're nervous about what it might do. Undo something once and that goes away.

You'll haveA working setup, one small win, and your audit
Week2

Teach it your business

What you learn

Writing down how your business works so the AI can use it. Services, pricing, clients, process, how you speak to people, what good looks like to you.

Why it matters to you

Generic AI gives generic answers because it knows nothing about you. This is why your version beats what a competitor gets out of the identical tool.

You'll haveYour business documented, in a form AI can work from
Week3

Why structure beats clever wording

What you learn

Organising week two into layers, so the AI picks up only what the current job needs instead of wading through everything. Files and folders, arranged on purpose.

Why it matters to you

Hand a new hire a fifty page manual and they'll spend the day reading. Give them a contents page and tell them which chapter to open, and they're useful by lunchtime. Same idea, and it's what makes everything after this week work.

You'll haveA setup that stays fast as it grows
Week4

Build your first system

What you learn

Turning a job you repeat into something you run in one line. You start by watching where it gets things wrong unaided, then write only what fixes that.

Why it matters to you

Where it stops being a chat window and starts being a system. Pick the task from your audit that annoys you most.

You'll haveSystem one, live
Weeks 5 to 8 · Connecting it to your real business
Week5

Plug in your real data

What you learn

Connecting the tools you already use so it works from your actual numbers, jobs and clients. How to do that safely, and what to keep well away from it.

Why it matters to you

Until now it worked from what you told it. Now it works from what's true today. That's the difference between a smart assistant and something you'd trust with a client quote.

You'll haveLive data connected, safely
Week6

Make it permanent

What you learn

Keeping a proper history so nothing gets lost and any change rolls back. Putting rules in place that always apply, whether or not the AI decides to follow them.

Why it matters to you

Systems that only live on your laptop disappear when the laptop does. This is the week yours becomes something the business owns.

You'll haveSystem two, live and backed up
Week7

Get it running without you

What you learn

Putting work on a schedule so it happens on its own. The Monday report that writes itself, the follow ups nobody has to remember. I'll also be straight about where the do it yourself version stops.

Why it matters to you

Everything so far helps while you're working. This part keeps working when you're not.

You'll haveSystem three, plus something on a schedule
Week8

Prove it worked

What you learn

Checking your systems still do their job as things change, and keeping running costs sensible. Then you run the audit again.

Why it matters to you

A number instead of a feeling. My guess is the biggest saving comes from something you'd have called minor in week one.

You'll haveYour measured result
How it runs

Two sessions a week, and me on hand between them.

This is training that happens in a group setting. Everyone builds on their own business, in the same room, at the same time. It isn't a course you watch on your own and it isn't a community to hang around in.

Every week

  • A teaching session. I share my screen and walk that week's build start to finish. Recorded.
  • A working session where everyone builds and asks whatever they're stuck on. Not recorded, so people talk freely about their actual business.

Between sessions

  • Two private sessions, just you.
  • Six written support requests. Send a recording or a description, get a fix back.
  • The shared library: everything I build, plus whatever other members publish.

The room

  • Eight businesses maximum, and never two direct competitors.
  • Founders and owners in the room, not the people they'd delegate this to.
  • Extra seats at $750. Skill spreads faster than systems, and every seat runs its own audit.

Weeks 5 and 6 involve your live data. None of it needs to go on a group call. Anything private goes through your private sessions or written requests, and when a problem is worth teaching I rebuild it on my own machine so the group learns without ever seeing your books.

Being straight with you

What this doesn't do.

Better you know now than in week six.

  • I'm not building it for you. You build, I teach and unstick you. If you'd rather have it built around your business instead, that's The Build, and plenty of people are better served by it.

  • What you build runs on your machine and your accounts. You'll get scheduled work running, which is genuinely useful. You won't get one shared system your whole team logs into with different permissions and a full audit trail.

  • It doesn't do your delivery work. If your team fits kitchens or treats patients, this clears the paperwork wrapped around that work and those hours are real. It won't put another van on the road.

  • It isn't a course you watch. Skip the work between sessions and you won't hit the guarantee. I'd rather you kept the money.

A good fit

  • You run the business. This is built for founders and owners, the people who decide what's worth building, in any industry.
  • You're already good at what you do, and this is the one gap that hasn't closed yet.
  • Ten or more hours a week across the business going on work that isn't your craft.
  • You want to understand this yourself rather than depend on someone who does.

Not a good fit

  • You'd send your developer or IT person in your place. The judgement being taught is about your business, and you're the only one who holds it.
  • You're after developer training. This teaches you to point the technology at the right problems, not software engineering.
  • Under ten hours of non craft work across the business. The maths doesn't favour you yet.
  • You need it working inside a fortnight.
The other door

Would you rather I just built it?

Some owners want the skill in the building. Some want the thing running and their attention back on the work they actually do. Both are reasonable, and the second one is The Build.

Same eight weeks, except I do the building. A system built around how your business actually runs, hosted on your accounts, permissioned for your whole team, with an audit trail on everything it touches. You get a finished system instead of the ability to make more of them.

You're here

The Workshop

Done for you

The Build

Who builds it

You do, with me in the room

 

I do

What you end up with

The skill, plus three systems

 

One system, finished

Where it runs

Your machine, your accounts

 

Your accounts, your whole team

What it costs

$2,000 a seat

 

$5,500

See The Build

Neither one is the junior version of the other. Tell me which problem you've actually got on the call and I'll point you at the right one.

What it costs

Two thousand a seat, for the eight weeks.

Agreed in writing before week one. Eight businesses in the room, never two direct competitors, and nothing renews on its own when it's over.

Your seat

$2,000

USD, all eight weeks

  • Sixteen sessions, two a week for eight weeks
  • Two private sessions, just you and me
  • Six written support requests, answered with a fix
  • Both audits, week one and week eight
  • The shared library, and everything you build is yours
Every extra seat

$750

Bring whoever runs the work with you. Skill spreads faster than systems, and every seat runs its own audit against its own guarantee.

After the eight weeks

$1,500

Another block, if you want one. When the eight weeks are up you're done unless you'd rather not be, and you keep everything you built either way.

If you finish and decide you want the whole operation built properly around their team. That's separate work, I'll tell you honestly whether you need it, and nobody gets pushed towards it.

Eight weeks from now
you'll know how this works.

Properly, on your own business, with three systems running to prove it. And if the audit doesn't back that up, the seat runs free until it does.

$2,000 per seatTeam seats $7508 places per intake