You lead a team that uses AI
Your engineers or ops people are already using Claude, ChatGPT, Cursor, or n8n. You sign off the work but you can't honestly evaluate it. You want to fix that without becoming an engineer.
You leave this course with a working AI system installed on your business, in a repo you own. Not another course you watched: a scored baseline on day one, a running system and handover doc by week six.
This is built for one specific kind of founder. If that's you, the rest of the page will feel obvious.
Your engineers or ops people are already using Claude, ChatGPT, Cursor, or n8n. You sign off the work but you can't honestly evaluate it. You want to fix that without becoming an engineer.
You've read the LinkedIn posts, joined the free communities, watched the demo videos. You can run a prompt. What you don't have is a system that runs your actual work, built on your actual context, that survives the next model release.
You're tired of collecting frameworks you never install. You want to finish something: a baseline score that moved, workflows that run every week, and an asset you keep when the course ends.
Small cohort. Your real business as the build material. One human you can actually ask.
Every week ends with something committed to your repo. By week six the repo is the system.
Limited to 10 places in the first cohort. Waitlist members get first refusal.
If you go on to an AI Brain Sprint within 30 days of finishing, your £2,250 course fee is credited against it. The course pays for itself if you upgrade.
Name and email gets you on the list. No spam, no sales sequences with seven follow-ups. When the cohort opens, you'll hear from me directly.
Check your inbox for a confirmation. When the first cohort opens, you'll hear from me directly.
No. You will not be writing code. You will be installing a working system on your own business with guidance at every step: connecting the knowledge you already have, tuning the workflows you already run, and writing role definitions in plain English. If you can organise a shared drive, you can do this.
The free communities and published methodologies are genuinely good, and you should read them. What they give you is method. What this course gives you is installation: a scored baseline of your setup, live build sessions on your real business data, a 1:1 with an operator who runs these systems inside real companies, and a repo you own at the end. The gap is between studying the method and leaving with the machine running.
The system you build lives as plain files in a version-controlled repo you own. From there it deploys to today's surfaces, Claude skills and project instructions, and re-targets whatever comes next. When a vendor changes the rules, you redeploy. You don't rebuild. Read the framework for the full portability argument.
Calls run on UK time (GMT/BST), scheduled to be workable from Europe, the UK, and the East Coast of the US. Exact times are confirmed with the cohort before kick-off. Every live call is recorded for anyone who can't make it.
Course content is delivered through a dedicated learning platform. You get an account on day one and keep access after the cohort ends. Live calls run on Zoom or Google Meet. The 1:1 session is booked through Cal.com. Your system lives in your own private GitHub repo, set up in week one from a template.
Every live call is recorded and posted to the learning platform within 24 hours. You can submit questions in advance if you know you'll miss one, and I'll answer them on the call so the recording is useful to you.
Yes. If you complete the first week and decide it's not for you, email me before the second live call and I'll refund you in full. After that point the content and 1:1 prep are already in your hands, so refunds are at my discretion.