AI Workshops · BrainIT Consulting
Short, practical sessions on artificial intelligence and process automation for small businesses — explained with things you already understand.
Emile du Toit
brainitconsulting.com
The shortest way in, and hands on from the first minute. You plan this Saturday in your own town, and along the way see what an AI model is on its own, what tools change, and what people mean by an agent. Every step is a prompt with a copy button, and a free account is enough.
Open the thirty-minute introduction Forty-five minutes · an extraA software workshop drawn as a medieval dungeon, where the coders are real AI coding agents working through a project’s GitHub issues. I show it running for half an hour, then we take questions. You see who does what, how one job goes from a request to finished work, and what you need to try it at home.
Open the Code Dungeon workshop Ninety minutes · or at your own paceTurn saved video links into a collection you can search. Choose the basic path with readable files and an HTML page, or the editable local app with SQLite search. Both paths include copyable prompts, practical checks, and clear stopping points so you can finish at home.
Open the video-library workshop The short versionThe whole series in one session. Two hours, six hands-on exercises, and you leave with a live web address for your own business — built in the last hour, and yours to change tomorrow. Nothing to buy, and a free account is enough.
Open the one-session version →The twelve pages have no clock on them, so they work at any pace at a kitchen table. This one puts them into an in-person day: the timings, what to demo rather than have people work, what to cut when the day runs short, and what to ask a host before agreeing a date.
Written for whoever is running the session — me, usually. Nothing in it is secret, so have a look if you are curious. It will just read a little oddly, because it is talking to the person at the front of the room rather than to you.
Open the run sheet →What a chatbot actually is. A large language model is a horse with no saddle: strong, fast, and no use to you yet. This session fits the bridle and the saddle — steering it with words, and writing your standing instructions once so every conversation starts properly.
Covers Large language models · prompting · the context window · standing instructions · how it goes wrong · getting an account open
Open workshop #001 DownloadWhen a chatbot starts doing a job. Tools are what let it reach the real world — read your price list, put a draft in a file, go and look something up. Add a goal and a loop and you have an agent, which is a much duller word than it sounds.
Covers Tool use · the agentic loop · when a mistake repeats · rules of the barn · three worked examples · picking your first job
Open workshop #002 DownloadWhere your work actually lives. You have been carrying every fact out to the horse by hand and every answer back — that is what a chat window costs you. This session is files, folders, and the one idea that keeps everything after it safe: one folder, one job.
Covers Why the chat window has a ceiling · files and folders · the project folder · nothing to install
Open workshop #003 DownloadThe building where the gear hangs ready. What a code editor actually is, the three parts of the screen worth knowing, and the black panel that turns out to be a door rather than a test. You leave with it installed and working.
Covers The editor · the three regions · the terminal, gently · what can and can't go wrong · a twenty-minute setup
Open workshop #004 DownloadIt starts doing the actual work — reading your files, writing new ones, running things. And it stops at every gate to ask first. That pause is what makes it safe, and this session is about what it means and how to read it.
Covers What an agent is · the permission prompt · the three approval modes · what it can and can't reach · taking the reins back
Open workshop #005 DownloadSafe is not the same as useful. This session is how to describe a job so you get the thing you meant, how to write your house rules into the folder so you stop repeating them, and which jobs are worth handing over first.
Covers Describing a job · standing instructions in the folder · Claude Code and Codex · good first jobs · what to keep away from it
Open workshop #006 DownloadEverybody has a folder with four copies of the same file in it. This session replaces all of that with one file and a trail of markers behind it, so any mistake becomes a step backwards rather than a rebuild. It is the session that lets you stop working on copies.
Covers Version control in plain English · markers and notes · putting a file back · GitHub · what to say instead of typing commands
Open workshop #007 DownloadAsk for “something to track my estimates” and you will get something that tracks estimates — and is no use at six in the morning. This session is how to write one page that says what you actually want, and how to get the assistant to ask you the questions you would not have thought of.
Covers Why plain requests go wrong · the five headings · a real map, in full · making it interview you · plan mode
Open workshop #008 DownloadA folder of files works until two people need it at once, until you want it on your phone, or until the same fact is written in two places and one of them is wrong. This session is what replaces it — one place the information lives — and the equally useful question of when you do not need one at all.
Covers When a folder is still right · who is going to use it · rows and columns · reading a query · getting a free database
Open workshop #009 DownloadEverything you have built so far can be seen by exactly one person. This session closes that gap — a real address on the internet, the fenced middle step that stops you publishing mistakes, and how to put yesterday's version back in about two seconds when something goes wrong in front of customers.
Covers What “on the internet” really is · preview against production · deploying · rolling back · keeping secrets out of the page
Open workshop #010 DownloadThings do not break loudly. A change in March quietly stops the phone number working, and you find out in July from somebody who tried to call you in April. This session is the short list of things that must never quietly stop being true, and how to have a machine check them every single time.
Covers What to check and what to ignore · checking work you cannot read · tests in plain English · running them automatically · the five-minute monthly round
Open workshop #011 DownloadEverything you have built so far has had one user, and it was you. This is what changes the moment somebody else needs to get in — how a thing works out who somebody is, how to keep one customer out of another’s business, and why you should never be in the password business. It is also the last session in the series.
Covers Sign-in without passwords · who may see what · sending mail that arrives · what to do next · where the line is
Open workshop #012 DownloadEach session runs about forty-five minutes and ends somewhere useful, so missing one does not leave you stranded. Sessions #001 to #009 are the beginner track and assume nothing. From #010 they are marked Intermediate — not harder to follow, but they assume you have done the ones before.
That is the whole series. Twelve sessions, start to finish. Every one stays online, stays printable and stays free, and the class folder keeps a marker for the end of each one — so you can pick up anything you missed whenever it becomes useful, rather than whenever it was taught.
Pro riders · optionalOne extra page, outside the twelve and not needed by any of them. What an agent skill actually is, how to install one and read it first, how to turn a job you keep explaining into one of your own — and the three times a skill is the wrong tool and something simpler is right.
Open the pro page A field guide · Windows-firstA practical route from your first project folder to an app you can open on the web. You choose what it is for, Codex does the coding, and you both check the result. Your first goal is one page that opens on your own computer. Then it goes on GitHub and Vercel, and a database, sign-in, email and file uploads come later, only when the app needs them. Vercel’s free Hobby plan covers a personal learning project; for Codex, check what your own plan includes.
Open the app-building companion About ten minutes · a handoutConnect the Gmail account you choose to whichever of the two you already have, and ask it to find and explain your email. You sign in on Google’s own page, start with a question that only reads, check the answer against the original email, and learn how to disconnect it later. You need a Claude or ChatGPT account. Whether Gmail shows up in it can depend on your plan, and a work or school account may need its administrator’s approval.
Open the Gmail guide