What you actually build in sixteen weeks

People ask what a sixteen-week AI automation bootcamp actually produces. Not what it teaches — what you walk out with. Here's the honest answer.

Week one, you build a working automation in n8n — a trigger at one end, something useful at the other — while we cover what AI is actually doing to work and how these models work underneath: tokens, context, why they make things up. By week four you've put Claude inside an automation through its API and built a branching workflow with a database behind it. Not demos. Things that run.

Weeks five to eight are production work: a report a real business would pay for, a system that survives things going wrong, a process map and proposal for a real business. Weeks nine to twelve go up a level — your first working agent, MCP, deploying and monitoring what you've built — and the live client project starts: a real client, and your own business counts. Thirteen to sixteen you finish it, hand it over properly, write it up as the case study that anchors your portfolio, choose your track with your tutor, and present the lot on Demo Day.

So you leave with three things. Sixteen working automations you built, that you can open and run in front of someone. A portfolio with a live client delivery in it. And a certificate of completion from us — the Practitioner credential when all sixteen builds pass.

What you don't leave with is a promise of a job, because no honest provider can give you one. What we can give you is live teaching from two PGCE-qualified teachers who teach in classrooms every week, a cohort of people doing the same thing as you, and a programme built for beginners — no coding needed to start.

Cohort one starts on Monday 4 January 2027. Enrolment opens soon, and the founding price runs for the first thirty days after it does; enrolment closes on 18 December. If you'd rather talk before you apply, the form takes five minutes and a real person replies.