Mark Nguyen
CEOPassionate trainer focused on helping professionals realise better opportunities in work and business.
Stop doing the same job every week - leave with automations that run whether or not you remember to run them
Some of the companies where our students come from
An honest scoring of what's worth it, usually not the task you arrived wanting to fix.
Documents, spreadsheets and inbox reachable, without six tabs of copying and pasting.
Read the data, do the thinking, write the output, finished before the session is half over.
Checkpoints and sensible failure, so nothing quietly breaks for three weeks unnoticed.

You see the actual gap - not clever prompting, but giving Claude your context and your own material to work on.

Set up around your own work, and running on it before the session is half over.

The two places Claude will mislead you, caught in seconds - so using it well and using it safely become one habit.

Three of your own jobs, packaged up to rerun next week, without starting from a blank chat.
There’s a particular kind of work that survives every reorganisation: the report that goes out on Monday, the spreadsheet someone reconciles on Thursday, the chasing email that gets rewritten from scratch every single time. It isn’t hard. It’s just yours, forever, and it eats a morning a week.
The reason it hasn’t been automated is that it has judgement in the middle. Traditional automation is very good at moving a file from one place to another and completely stuck on “read these forty responses and tell me which three need a reply today”. That middle step is the bit that’s changed - and most people still using Claude as a chat window haven’t noticed it can now sit in the pipeline rather than beside it.
That’s what an afternoon is for. We start by working out what is actually worth automating, which for most people is not the job they walked in wanting to automate. Then we connect Claude to where your work already lives, build one chain end to end on your own material, and put it on a schedule while you’re still in the room to see what comes out.
We spend the last proper block on what happens when it breaks, because it will. Where a human still has to approve something, what a sensible failure looks like, and how it tells you rather than quietly doing nothing for three weeks. Anyone selling you fully hands-off automation is a few years ahead of what’s true.
It’s deliberately small, too. You’ll be able to say “our finance system won’t allow that” and get a real answer, which is the whole reason to do this live instead of watching a video at 1.5×.
You'll spend more of this afternoon typing than watching, and nothing here is a diagram of something that could work. Everything is built on your own accounts and your own material, running by the end of its block. The running order below is UK time; the session times at the top of the page are shown in yours.
A quick round of what everyone would stop doing tomorrow given the choice. We use your real jobs for the rest of the session, so this genuinely shapes the afternoon.
The scoring we use before writing anything: how often, how long, how bad if it's wrong, and how stable the inputs are. Also the three shapes of task that look automatable and reliably aren't.
Documents, spreadsheets, mail and chat - what connects, what it can see once it's connected, and the permissions conversation to have with IT before rather than after. We'll get at least one working for everyone.
Coffee, stand up, look out of a window. Back at twenty past.
Input to judgement to output to somewhere it lands. We build one together, then you build yours - on the job you named at the start, with your own data going through it.
Turning it into something repeatable and then something scheduled, so it happens on Monday whether or not you're at your desk. We'll trigger a run and watch what actually comes out.
Approval gates, sensible failure, and how it tells you something went wrong. Plus the honest limits: what still needs a human on it, and how to tell which is which before you find out the expensive way.
We write yours down so someone else could run it, and each pick the second job to automate when you're back at your desk.
Details, agenda and timing subject to change.
It has your joining details, your receipt and a calendar invite, ready to add straight away.
Everything installed and ready before the day, so no session time is lost to downloads. You and your fellow students start straight on real work.
Our instructors show you how to use Claude, drawn from their own experience in industry. Then you do the real work, and leave with workflows you can use the very next morning.
Need to move to another date, or can't make it any more? Reply to your confirmation email and we'll sort it. You can cancel up to 21 days before the workshop and we'll refund you in full.
Book 3 seats or more for this same date and the discount is applied automatically at checkout below. No code, no separate invoice.
Run this session privately, tailored to your stack and your own material, remote or on-site.
Explore team training
Passionate trainer focused on helping professionals realise better opportunities in work and business.
Leads curriculum design and workshop delivery at Atlas Learn. Formerly an educator and trainer, specialising in breaking down complex technical concepts into accessible, hands-on learning paths.
Three hours, a small group, and your own work on the screen. Change your mind? Cancel up to 21 days before and we'll refund you in full.
We'd like to set analytics and advertising cookies to see how this site is used and which ads bring people here. Nothing is loaded until you say yes. See our privacy policy.