Why I Started the AI Automation Hub
Quiet, unglamorous AI automation work for businesses, and the same question kept coming back from the people watching: can you teach me to do this myself?
- ai
- automation
- community
Learn to build and sell AI automation that businesses pay for. I am a UK software engineer with ten years of shipping software, and I still build this for clients in n8n and Claude Code. The retries, the error branches and the row that arrives malformed at two in the morning are in the lessons alongside the happy path.
Free live evenings, 10 to 12 November: register free.
The Hub is free while the first courses are being recorded. 2 of the 5 courses are live in the classroom today and the rest are marked in production or coming soon. When it does become paid, one email inside thirty days gets you a refund.

Not ready to join? Get the posts by email.
One email when a post goes live, and nothing else. Unsubscribe in one click.
Live online and recorded. Real jobs on screen, with what each one costs to run.
They are for people who run a business or hold a technical job and have work that repeats every week.
One registration covers all three nights.
Night 1: The four-question test, and one real job run three ways
Tuesday 10 November, 19:00 to 21:30 UK
Night 2: What starts the system without you
Wednesday 11 November, 19:00 to 21:30 UK
Night 3: One agent becomes a team
Thursday 12 November, 19:00 to 21:30 UK
Most AI training stops at the build. You come out of it with a workflow running on your own laptop, no idea which business would pay for it, and no idea what to charge.
I have spent ten years building and shipping software for businesses, and between us the team behind the Hub has over twenty. Most of what I teach here has had to keep working long after the demo was over, which is a different job from getting it working once: retries and back-off, a branch for the row that arrives malformed, credentials that rotate without anyone noticing, idempotency so a retry does not bill a customer twice, and monitoring so the client hears about a failure before their customer does.
You work out what a business needs, build the smallest version of it that holds up, then go and sell it. Most of my time here goes on the two parts that usually get skipped, the diagnosis at the start and the pricing conversation at the end. A workflow that reads a form submission and writes a row into a CRM is a fifteen minute build. Working out whether it saves the receptionist enough time to be worth paying for, and roughly what that time is worth to the owner, is the part that took me longest to learn.
There are no revenue figures anywhere on this site, and no affiliate links to any tool I teach.
Everything in the Hub follows the same three stages. Taken in order they head off the usual outcome, which is a half-finished workflow and nobody to sell it to.
How LLMs work, what prompts and data do to the output, where APIs fit, and how to tell which business problem is worth solving with AI at all.
Course 1: AI Foundations
Set up Claude Code and n8n, then build three workflows that each take a job someone is currently doing by hand. They are being recorded now and go up lesson by lesson.
Course 2: Build Your AI Toolkit
Work out which businesses are worth approaching, then run a 15-minute audit and take them one quick win. Pricing that first build as a monthly arrangement rather than a one-off invoice is what this stage spends most of its time on.
Course 3: The Business of AI
Four parts, and you do not need all of them on day one. Start with the courses, post in the forum and turn up to the first live call.
Structured courses that go from how AI works through to building in n8n and Claude Code. Every lesson is a video with a written summary and one thing to do next.
Live calls start as the courses go up. I build in front of you and you follow along on your own machine, the room is small enough that you can bring your own broken workflow, and the recording goes into the classroom afterwards. Dates go up inside the community rather than here, because I would rather move a date there than promise you a fixed slot on a public page and miss it.
n8n blueprints for content generation, weekly reports and support triage, built the way I build them for clients, which means the retries, the error branches and the rate limit handling are in the workflow rather than left to you as an exercise. The 15-minute audit spreadsheet so you walk into a first meeting with questions rather than a demo, and the CLAUDE.md starters I use on client work so Claude Code picks up a codebase the way you would want a contractor to.
Post your intro and say what you are building. Bring the workflow and the error message with you and I will answer it myself, because I still read every post that goes up. That is a promise with a size limit on it, and the day it stops being true I will say so here rather than quietly stop answering.
Some people get nothing out of this, and it is cheaper for both of us if you work that out here rather than in week three.
If you are after passive income, this is not it. It is client work, which means calls with an owner who changes their mind halfway through, a scope you have to hold, and an invoice you sometimes have to chase twice.
Being told which tool to buy this week is somebody else's channel. What gets taught here is the layer underneath, the part about how a model behaves and how data moves between systems, because the tools get replaced and that layer does not.
If you will not put your own laptop in front of a business owner and walk them through what you built, half of this is closed to you, and it is the half that pays.
And if you want AI to write the whole thing while you watch, most of the work in Claude Code is reading what it just produced and telling it where it went wrong. The same goes for a workflow that has to run every day without you standing over it.
If any of those are you, the YouTube channel is free and you will get more out of it than out of joining.
Everything on this list comes out of finishing the builds and taking them to a business that has the problem. The courses that get you there are still shipping, and the catalogue shows which ones are live today.
Run a 15-minute audit on a business and come out with a scored list of what to automate first.
Build a workflow in n8n that takes a job off someone's desk and keeps running when the input is messy.
Set up Claude Code so it can work in a client's codebase without you babysitting it.
Walk into a first meeting with a script and a price rather than a demo.
Write the proposal that puts a build on a monthly arrangement rather than a one-off invoice, and know what to charge for it.
Every video on the channel is a build from start to finish, including the parts where it does not work first time. Posts go up here before they go anywhere else.
I am a UK software engineer, ten years into the trade, and most of the client work I take on now is AI automation. One build reads every enquiry that lands in a shared inbox, pulls the job details out of it and writes the row into the CRM, which somebody had been doing by hand. Another sorts support tickets into the right queue before anyone opens them.
The question I kept getting was whether I could teach people to do this themselves, and the Hub is my answer to it.
Join the Hub, post an intro so people know what you are working on, and open Start Here. It takes about twenty minutes and it ends with you knowing which course to take next.
It is free while the first courses are being recorded. When it does become paid, you can email support@eduard-vlase.com inside thirty days and I will refund you, with no conversation attached.