Some spectacular demos made terrible business systems.
Too expensive. Too brittle. Too complicated. Or simply automating the wrong thing.
BACK TO SCHOOL / 3-WEEK FIELD COURSE
The kids are back
in school.
Entrepreneurs should be too.
Three Wednesdays. Nearly four years of field notes from building AI inside real businesses.
No pitch at the end.Just class.
OCT 2022OpenAI developer
227+projects delivered
52+agencies served
16industries
01
WHY I'M TEACHING THIS
the first classroom
My first teacher in technology
was my dad.
By 14, he had taught me roughly a dozen development languages. But knowing syntax was never the point. If I wanted to work alongside him as a freelancer, I had to build something first.
So I built my first application: a truly terrible version of Dungeons & Dragons.
It was not elegant. It was not impressive. But it worked. And apparently that was enough to earn my seat at the table.
Learn enough to try. Build it. Break it. Figure out why. Build something better.
That became the way I learned technology for the rest of my life.
OCTOBER 2022
Then the computer started learning my language.
I started working with OpenAI before ChatGPT was publicly released. For most of my life, using a computer meant translating an idea into its language: logic, commands, syntax, structure.
Suddenly, the computer was beginning to understand mine.
So I did what my father taught me to do. I started building.
02
WHAT HAPPENED NEXT
Four years of learning in public.
Prompting became workflows. Workflows became assistants. Text became voice. Models began using tools, reading documents, processing data, calling APIs, writing software, and taking action.
Some of the simplest systems created the most value.
Faster follow-up. Better information. Fewer missed handoffs. Minutes removed from work that happened hundreds of times.
AI is not valuable because it looks impressive.
It becomes valuable when it changes an outcome.
03
CHOOSE HOW YOU LEARN
two paths
You can chase tools. Or learn how to think in systems.
Collect prompts. Save videos. Try whatever launched today.
- Isolated tricks
- Disconnected tools
- Constantly starting over
VS
Learn the operating model behind useful AI systems.
- Start with the business outcome
- Map the intelligence and workflow
- Build, measure, and improve
04
THE SYLLABUS
three Wednesdays
We're going back to school.
Not a list of shiny tools. A progression from understanding the technology to using it intelligently inside a business.
01
WEDSEP 23
AI 101
Stop Using AI Like Google
Understand the shift from prompts to context, assistants, workflows, agents, and systems. Learn what actually matters before you start automating anything.
02
WEDSEP 30
AI LAB
Build Your AI Workforce
Map the repetitive thinking, creating, deciding, and executing inside your company. Turn one real business process into an AI-enabled workflow.
03
WEDOCT 07
AI BUSINESS
Make AI Pay for Itself
Connect AI to measurable value: revenue created, cost avoided, capacity gained, conversion improved, and opportunities unlocked.
05
THE FRAMEWORK
one operating model
LEARN → MAP → BUILD → MEASURE → SCALE
Learn what the technology can do. Map the repetitive intelligence inside your company. Build the smallest useful system. Measure what changed. Scale what produces value.
ONE IMPORTANT DETAIL
There is nothing waiting for you at the end.
No course.
No mastermind.
No paid community.
No surprise offer behind Week 3.
I had someone teach me. I've had nearly four years to learn this particular technological shift by building inside it. For three Wednesdays, I'm pulling up a few more chairs.
06
QUESTIONS BEFORE CLASS
before you enroll
Frequently asked.
Is this actually free?
Yes. There is no course fee, paid community, mastermind, or required purchase attached to the three-week series.
Is there a sales pitch at the end?
No. The point of the series is to share the field notes, frameworks, mistakes, and practical lessons I have accumulated since October 2022.
Do I need to be technical?
No. The course is designed for entrepreneurs. We will discuss technical ideas when they matter, but the goal is business understanding and implementation judgment, not turning you into a software engineer.
What should I bring?
Bring a real business problem, repetitive process, bottleneck, or opportunity. The more concrete the problem, the more useful the framework becomes.
class is back in session
Come to class.
I'll share the notes, the mistakes, the systems, and the things I wish I understood sooner.
SEP 23 · SEP 30 · OCT 07