Workshop
From operator
to orchestrator.
Two days, hands-on. Day one you build a working AI employee for your own business and put it live on the internet. Day two you give it a UI system so it stops looking like every other AI page.
What this solves
Most founders have used AI to write a message or summarize a doc. Few have used it to build and ship a real tool: something with a live link, running on their own laptop, doing a job.
This workshop closes that gap in a room, not a video. You leave with software you built yourself, deployed, and yours.
It does not replace your team. It takes the repetitive work none of them should be doing: the same reply forty times, the message at 11pm, off their plate.
The two days
Day 1
Building an AI employee
- The difference between a tool and an employee: a job, instructions, tools, and a place to work
- Set up Claude Code on your own machine (Mac and Windows commands, walked through live)
- Write the build prompt for your own business: what you sell, who buys it, what the tool should do
- Build a single-page tool, no setup and no accounts for the person using it
- Ship it live with a public link before the session ends
Day 2
Your own UI system
- Why every AI-built page looks AI-made: same fonts, same gradients, same cards
- What a UI system actually is: fonts, colors, spacing, and rules you never break
- Install the JTL AgentKit inside Claude Code (two commands)
- Write your system down as a DESIGN.md file your AI must follow on every page
- Apply it to yesterday's tool, have the reviewer agent judge it against your own rules, and re-publish before and after
What you walk out with
- A working AI employee you built yourself, live on the internet
- A design system in a file, not in your head, reusable on your next build
- A repeatable process for turning a business problem into shipped software
Preview
Already attended? Your access page has the commands and the code from your room.
Get your setup pageBook a call
Talk through whether this workshop fits your team before you commit.