I travel to you
Your office, your kitchen table, a meeting room, or a branch of Austin Public Library if you would rather not host. You pick the place. I bring the curriculum and a laptop.
Twelve hours, one student, your own desk.
A four session bootcamp on Claude Code and OpenAI Codex, taught one on one in Austin. I come to your office, your home, or a library, and you learn to build real things by describing them in plain English. No coding experience needed.
4sessions
12hours total
15hands on labs
1student, always
In person
This is not a course you watch.
Everyone has bought a video course they never finished. The reason is rarely the material. It is that nobody was there when it got hard.
It is your own project on the screen
Not a demo built for teaching. We work on something you actually want to exist, so everything you learn is already attached to your own work rather than to an exercise.
Nobody else is in the room
No cohort, no queue, no chat window. If something has not landed, we stay on it and cut something else. The pace is set entirely by you.
You keep everything
The setup we build, the labs, the starter projects and a printed workbook. It all stays on your laptop after the last session, and none of it is locked to a platform.
Who it suits
Four places people start from
The course adapts because there is only one of you. Tell me where you are on the discovery call and we weight the time accordingly.
You have never written a line of code
The most common starting point, and the one the course is built around. You say what you want in ordinary English and learn how to check what comes back. There is no syntax to memorise.
You run something and keep paying for small jobs
A landing page, a booking form, a report that takes somebody two days every month. Most of that you can do yourself in an afternoon once you know how to ask.
You are technical in a different field
Analysts, scientists, designers, operations people. You already think in systems and processes. This removes the one step you were handing to somebody else.
You already write some code
Then sessions two and three are where the value is. Method and setup are where experienced people stall, not the writing.
If you have never touched these tools
- Nothing is assumed. Session one starts with an empty screen and ends with both tools working on something of yours.
- You type what you want in plain English. Every instruction in the course is written the same way, with no jargon left unexplained.
- You are never behind, because there is no cohort to be behind. The pace is whatever yours is.
- Every lab says plainly what done looks like, so you always know whether it worked rather than guessing.
- You learn how to check the work. That one habit is what separates people who can trust these tools from people who get burned by them.
- Everything runs on your own laptop, on something you care about, so nothing you learn is stranded in a practice project.
The shape
Three hours, planned to the minute
Here is session one exactly as it runs. Roughly half of every session is you at the keyboard, and there is one break. Nobody sells a course by showing you the timetable, which is precisely why you should see it.
StartMinutesWhat happensFormat
00:0010 minWelcome, outcomes, how we workteach
00:1015 minThe shift from autocomplete to agentteach
00:2525 minLab 1.1 Install and authenticate Claude Codelab
00:5020 minYour first loop, end to end, on your repositorydemo
01:1010 minBreakbreak
01:2030 minSteering: context, plan mode, permissionsteach
01:5020 minLab 1.2 A memory file that changes behaviourlab
02:1025 minCodex: install, sandbox modes, AGENTS.mdteach
02:3520 minLab 1.3 The same task through both toolslab
02:555 minDebrief and the take home labwrap
How we work in the room
- You drive. Your hands stay on the keyboard. I talk, show it on my screen, then you do it on yours. Watching does not transfer.
- Your own project. Every lab runs on something you actually want, wherever it can. Practice projects teach practice habits.
- Check the work. Nothing gets accepted that you have not looked at. I will show you how to read what the tool did, in plain terms. This is the habit the whole course is built on.
- Break it on purpose. We deliberately let the tools fail, so you learn the recovery moves while somebody is sitting next to you.
- Stop me. One on one means no queue. If something has not landed we stay on it and cut something later.
Curriculum
Four sessions, fifteen labs
Eleven labs in the room and four to take home. Every lab states what done looks like, so you are never guessing whether it worked.
SESSION 01
Foundations and setup
Both tools installed, signed in, and doing something useful on a project of yours before you leave the room.
Labs in the room
1.1Install and authenticate Claude Code
1.2Write a memory file that changes behaviour
1.3Run the same task through both tools
AShip a small command line tool end to end
Take home, 90 minutes
Take home, 90 minutes
SESSION 02
Directing the agent
The gap between people who get good output and people who do not is almost entirely method. This session is the method.
Labs in the room
2.1Plan a feature without writing any code
2.2Ship that feature, test first
2.3Find and fix a seeded bug
BA full feature, planned, tested and reviewed
Take home, 2 hours
Take home, 2 hours
SESSION 03
Making the tools yours
Everything you had to correct by hand in session two gets written down once, so the tools stop making the same mistakes. This is where they start fitting you rather than the other way round.
Labs in the room
3.1Build three commands you will use daily
3.2Package your own expertise as a skill
3.3Write a hook that enforces one standard
CBuild the toolkit your team inherits
Take home, 90 minutes
Take home, 90 minutes
SESSION 04
Delegation, design and Codex
Handing off whole jobs, designing what things look like, Codex at full depth, and the judgement to send each task to the right tool.
Labs in the room
4.1Delegate a real piece of your work
4.2Take a mockup through to a shipped page
4.3Hand a task to a Codex cloud run
DCapstone: ship something small using everything
Take home, one week
Take home, one week
What you can build
Things you will be able to make yourself
You describe what you want and the tool writes it. Twelve hours is enough to get good at the describing, the checking and the shipping, which is all that stands between an idea and a working thing.
A website you own
Design it, build it, and put it online under your own domain. Not a template with your logo dropped into it, and no monthly fee to a page builder for the privilege of editing your own words.
Decks and documents that look designed
Slides, reports and one pagers produced from a brief you write in a couple of sentences. The course spends real time on why most output looks generated, and how to stop yours looking that way.
Small apps and internal tools
The spreadsheet that has outgrown itself. The form that should be a form. The dashboard somebody asks you to rebuild by hand every Monday.
The repetitive work, handed over
Renaming a thousand files, pulling figures out of a folder of invoices, turning a messy export into something a person can read. Once, properly, instead of every month.
An answer out of a pile of files
Give it a folder and a question and get back a written answer with its sources named, rather than a summary of the folder. Session four is built around doing this well.
A prototype before you pay anyone
Show the idea working before you commit money to a developer or an agency. Changing your mind at this stage costs an evening instead of an invoice.
And you keep all of it
The setup we build, the starter projects, the labs and a printed workbook stay on your laptop after the last session. Nothing is locked to a platform, nothing expires, and there is no subscription to keep paying to use what you learned.
Instructor
Jules Kabore
I was a software engineer before I was a founder. I sold my first startup, a fintech company, and I built yourUSA.ai. These days I use Claude Code and Codex every day on my own products, which is the only reason I am willing to teach them.
I am not a full time trainer and I do not run cohorts. I take a small number of students at a time because the format only works if I can give each one the whole session.
Why I teach it in person
The hard part of these tools is not the typing. It is judgement: when to plan first, when to stop and look properly, and how to spot the moment one of them tells you confidently that something works when it does not.
You cannot get that from a video, because a video cannot see your screen at the moment you are about to accept something broken. Somebody sitting next to you can.
Questions before booking? Write to support@yourusa.ai.
Where
I come to you, anywhere around Austin
You pick the room. I bring the curriculum, the starter projects and a laptop.
AustinRound RockCedar ParkPflugervilleGeorgetownLeanderLakewayBee CaveManorBudaKyleSan MarcosDripping Springs
Places that work well
- Your office or a meeting room you can book
- Your home, if that is where you work
- A branch of Austin Public Library, which is free and quiet
- A coworking space you already belong to
Further out
If you are further out than this, ask anyway. Some weeks the drive works and some weeks it does not, and it costs nothing to find out.
Price
One price, and an exit after the first session
Twelve hours of one on one instruction is a real amount of money, so the terms are on the page rather than in a contract you sign later.
Full course$2,000
Book a discovery call firstFour sessions, twelve hours, fifteen labs, every starter project and the workbook.
What it coversAll four sessions, twelve hours of instruction, every lab, the starter projects and the workbook.
When you payIn full, before the first session begins.
If it is not for youTell me after the first session and you get half of it back, one thousand dollars, no argument and no exit interview.
After the second sessionNo refund. By then you have had six hours and most of the method.
SchedulingUsually one session a week over a month. If you would rather get it done, the whole course can run inside a single week.
TravelIncluded anywhere in the service area below. Further out, ask and we will work it out.
The refund in plain words
Pay $2,000 before we start. If you finish session one and decide it is not for you, tell me and I send back $1,000. Once session two has happened there is no refund. That is the whole policy, and it is deliberately short enough to hold in your head.
Questions
Questions people ask first
Do I need to know how to code?
No, and that is the whole point of these tools. You describe what you want in plain English, the tool writes it, and the course teaches you how to direct it and how to check what came back. If you can write a clear email you can do this. You will spend time in a terminal, and I will walk you through every part of that.
Do I need to have used Claude Code or Codex before?
No. Session one starts with installing them. If you already use them daily, say so on the discovery call and we will weight the time towards sessions two and three, which is where experienced people usually have the gap.
What do I need to have ready?
A laptop you can install software on, and one thing you would like to exist: a website, a small tool, a report that takes too long by hand. Paid accounts for Claude and ChatGPT, or API keys with credit. I send a short setup check to run beforehand so we do not spend session one on it.
Where do we actually meet?
Wherever suits you. Your office, your home, a library branch, or a coworking space. I bring everything except the room. If you would rather not host, a library study room is free to book and works well.
How quickly can we finish?
The usual shape is one three hour session a week for four weeks, which leaves time for the take home labs. If you want it compressed, the whole course fits inside a single week. It is more tiring and it does work.
What if I need to reschedule?
Give me as much notice as you can and we will move it. This is one on one, so there is no cohort to hold up. Repeated same day cancellations are the only thing that becomes a problem.
Is this useful if my company has not approved these tools yet?
Yes, and session three is the part to point at. You leave with a written setup and the reasoning behind it, which is a much better basis for a conversation with your company than an opinion.
Do you teach pairs or teams?
The course is built for one person and the format is most of the value. If two of you genuinely work on the same things every day, ask on the call and we will talk about whether it would still work.
What happens after the last session?
You get a capstone brief and a thirty day plan. Send me the thing you ship and I will read it. That part is not a paid service, it is just how I would rather this ended.
Book
Start with a twenty minute call
No charge and no pitch. Tell me what you build and where you keep getting stuck, and I will tell you honestly whether this course is the right thing for you.
Book a discovery call
Twenty minutes, no charge. Tell me what you build, what you have already tried, and where you keep getting stuck. If the course is not the right thing for you, I will say so on the call.