Mark Nguyen
CEOPassionate trainer focused on helping professionals realise better opportunities in work and business.
Build a real, working app and put it live on the internet in one afternoon - without writing a line of code yourself
Some of the companies where our students come from
Claude Code, Next.js, Supabase and Vercel, wired together so a non-engineer can reach a live app.
Who it's for and what it does, reviewed in plain English before any code exists.
Authentication wired up - the difference between a demo and something someone can actually use.
How to read a failure and describe it to Claude, without needing to know what the error means.

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.
Most people with an app idea are not stuck on the idea. They’re stuck on everything after it - the accounts, the setup, the words nobody explains, the sense that there’s a step-one you were supposed to already know. The idea has been fine for a year. It’s step one that never happened.
What’s changed is that the building is no longer the hard part. Claude writes the code. Your job is the part you were always good at: knowing who this is for, what it should do, and whether what came back is right. That turns out to be most of software, and it’s the half nobody could outsource until recently.
So we spend the afternoon on the path rather than the theory. Plan the app before building it, so you’re reviewing something you can argue with instead of hoping. Get it running on your own machine. Put it on GitHub, deploy it to a real address, and wire up logins so somebody who isn’t you can sign in. Four modules, each one ending with something that works.
We also spend real time on things going wrong, because they will, and because that’s the moment most people quietly stop. Knowing how to read a failure and describe it well is the difference between an afternoon that was interesting and one that changes what you do next.
It’s deliberately small. When your deploy fails at twenty to six, somebody needs to get to you before the module ends - which is the whole reason to do this live rather than watching a video at 1.5×.
Four modules, each ending with something that works. You'll spend almost all of this afternoon building rather than watching. The running order below is UK time; the session times at the top of the page are shown in yours.
A quick round of ideas. Bring your own, or take one from the list we provide - a renewal tracker, a habit app, an onboarding checklist. We use whatever you choose for the rest of the session.
Claude Desktop's Code tab, a new project folder, and the four accounts that do the work: Claude, GitHub, Vercel, Supabase. By the end of this block everyone is set up to build any app they can describe.
Plan Mode: describe the user, the problem, the flow and the data, review the plan Claude writes back, change what's wrong, then accept it and watch the app get built. We finish with it running on your machine.
Coffee, stand up, look out of a window. Back at half past.
Publish to GitHub, import it into Vercel, and get a public URL. Then the part everyone gets wrong on their own: telling Supabase which addresses are now allowed to talk to it.
Pick one and do it properly: "Sign in with Google" through Supabase, or Stripe and a paid monthly subscription. Both have moving parts we'll walk through rather than hand-wave.
Everyone shares their URL and shows the thing they've built. Genuinely the best twenty minutes of the session, and the reason we keep the group small enough that everyone gets a turn.
What to build next, what the free tiers cost you when you outgrow them, and the two habits that separate people who keep shipping from people whose app stops at version one.
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 app on the screen. You'll leave with a URL you can send to someone. 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.