Where we've come from, what you walk out with, how the four weeks run, and everything you need done before Monday.
Sources: OutSystems State of AI Development 2026 (1,900 IT leaders) · Microsoft Work Trend Index 2026 (20,000 workers) · UC Berkeley, "Why Do Multi-Agent LLM Systems Fail?", NeurIPS 2025 (1,600+ traces)
| Why agent teams fail | The skill that fixes it | The mechanism in your org | Week |
|---|---|---|---|
| 44% a bad briefvague goal, no stop rule | Delegation · Department design | A Chief of Staff that turns one line into a job. A charter that says what done looks like. | 1, 3 |
| 32% agents not lining upno routing, no handoffs | Orchestration · Context engineering | Reporting lines, routing and handoffs written into files. Knowledge the org can check. | 1, 2 |
| 24% nobody checkingerrors amplify 17x without a lead, 4x with one | Governance · Evaluation | A gate before anything ships. Receipts for every run. Evals that score the work. | 1, 4 |
| Only 16% can direct multi-step workthe seat almost nobody has | The method | Agent design in plain English, and the practice of adding the next department yourself. | 3, all |
Every one of those mechanisms is a plain-English file you'll write. That's the whole trick: the skill isn't in your head, it's in the org.
Sitting in to decide? Welcome. Everything here is what enrolled students get. There's one card for you near the end.
Practitioners first. From chatbots to agent workforces. Why this course is an apprenticeship.
Our students are not developers. They're professionals, consultants, and founders. Everything we teach, we run on our own business first. The org you inherit on Monday is a distilled version of the one we built and run ourselves at AI Build Lab.
Practitioners first
SaraCurriculum, growth, your emails
TylerSystems, agents, the architecture
HunterThe build, the course, the demo
WadeYour home base, Essentials, delivery
MichaelInfrastructure, repos, the installerOne person, one prompt, one answer at a time.
AI does a task instead of answering a question.
Agents hand work to each other. A boss agent runs a small team inside one workflow.
Departments. Hierarchies. Directed by a person. Companies now hire for this.
One workflow, pointed at one job. You build it, it runs. That's what most of you learned with us.
Workflows started handing work to each other. A lead. Specialists. A check before anything shipped.
One seat we talk to. It routes, queues, escalates. We stopped being the switchboard.
Five people directing an org of agents that runs AI Build Lab day to day. Same rule as always: we learned it, so we bring it back to you.
You don't start from a blank page. You walk into an organization that already runs, take it apart, make it yours, then build one department of your own from scratch, so the method is yours forever.
Every other layer is rented. The folder is the org, and it outlives any model.
If you can write a job description and a house rule, you can read every part of this org.
What you walk out with, shown working, before we explain a single week.
Hunter's screen. Team HQ. One job, start to finish.
Live means live. If it breaks, you're watching the real thing.
Every week ends with something that works, and a skill you keep.
Where it landsOur org customized to your business, one department you built and proved, and the method to build every next one.
SkillsEvaluation at agent and outcome level, the improve-and-rerun loop, governance at scale, reusing the method.
ProjectA proof pack and a reusable department kit.
SkillsDepartment design, agent design in plain English, handoffs, the gate before anything ships.
ProjectA department of your own, end to end, running one job.
SkillsContext engineering, knowledge the org can check, customizing a supplied role in your voice, tracing any answer to its source.
ProjectYour customized org running a job on your facts.
SkillsHow the org is wired, delegating to a Chief of Staff, reporting lines and routing, setting the rules and gates.
ProjectYour Chief of Staff set up, your org briefed, first job routed.
The method is the part that outlasts the four weeks: you can keep adding departments on your own. And every week, alongside the build, we give you the tools and the scaffolding for how you'd implement that same step for another business.
Keep adding departments on your own. Install the same shape for other businesses. The skill that makes every other skill reusable.
Essentials, the installer, the workbench it builds, your stack, your weekly rhythm, and The Lab.
An app on your own computer, working in a folder that is yours. A note about you it reads every time you open it. Your work in two places. One connection to your real stuff, and one habit it runs for you.
Do it before Monday. Week 1 assumes your workbench exists.
All three are normal. Your Mac asks for your password, Windows asks to allow changes. The terminal is a chat window for your computer. If it feels new, you have a superpower.
It checks first, so it picks up where things stand.
The snapshot tool. What makes "put it back the way it was" possible.
Signs in to your GitHub in the browser. Creates your private copy in your name.
What the installer and the guard run on. Nothing to learn or open. They just have to be there.
The same engine in a terminal. It runs where there is no app window, so scripts and schedules can use it. You will not need it today.
A check that stops a password or a key from leaving your machine. On before you need it, in both apps.
The Mac's app store for tools that have no icon, and the developer basics Apple ships.
Installing a program is a change to your computer, and the operating system wants a human to approve it. Nothing shows as you type. That is on purpose.
Nothing runs on its own. Every one of these is a tool a developer already has on their machine.
Agent Workforce lands in its own folder inside the same workbench. That is Monday's first step, and we do it together in the live session.
Agent Workforce lands beside your work, not on top of it. Your note, your files and your history stay exactly as you left them.
It's Code you want. If your company gives you Claude, ask whoever manages licences. If not, a personal plan sorts it.
Monday 11:30 AM and Friday 2 PM were the plan at this session. Confirm current times on learn.aibuildlab.com.
The invite is in your calendar from Sara. If it isn't, DM her today.
The only slide to screenshot.
You'll get a Slack message the moment it is. Don't force it.
Doors close Sunday, September 20. Cohort starts Monday the 21st. Includes Agent Native Essentials, 3 months of The Lab (Sept 15 to Dec 15), and the perks library.
If September is the wrong month, take the next cohort instead. Nothing to ask, nothing to lose.
maven.com/aibuildlab · code WEEKEND · or scan the code Hunter drops in the chat
Raise your virtual hand. We'll call on you, then you can unmute.
Monday, September 21 · 11:30 AM ET · link on learn.aibuildlab.com
Go build.
For alumni and campers: how Workforce sits next to what you already did with us.
Agentic workflows. You built one, pointed it at a job, it ran. Every framework you drilled is load-bearing here.
A Chief of Staff that routes. Departments with charters. Agents handing work to each other. Gates. Receipts. You stop being the switchboard.
| Agent Native Camp | Agent Workforce | |
|---|---|---|
| The shape | An open system. Machinery, setup, customization, all yours to decide. Bespoke down to the rig. | A scoped product. One harness, one workbench, one org package, one method. Templated on purpose. |
| Runs on | Hermes on your own always-on machine. Its own address and channels. | Claude Code or Codex on your laptop. No server. |
| You get | A harness and a method. You stand up your own Chief of Staff and build the fleet. | Our wired org, copied in. A finished reference to take apart. |
| You build | Your fleet, then one workflow taken deep, to production. | One department end to end, and the method to add the next. |
| Axis | Depth. Point the fleet at one thing. | Breadth. Widen the org, department by department. |
You built from scratch. Now take apart a finished org someone else wired.
Camp went deep on one thing. This is the repeatable method for widening.
Same org every engagement, no server to keep alive. Productize the install.
Another business, another org, without building a second machine.
"A different approach to setting it up that some clients may prefer over a full-blown Camp setup. Less advanced, less tech setup."
A camper, this week"I want to productize the implementation over and over for other businesses, versus the specificity of what I'm delivering in Camp."
A camper, on the reunion call"I'm thinking of it for another rig, and another business of mine."
A camper, enrolling