Service · AI training
Your team builds a working agent.
Hands-on AI training where your team leaves with something that runs, not notes from a lecture. Taught by an engineer who ships production AI every day, not a course reseller.
St. Augustine, Jacksonville, Ponte Vedra, and Northeast Florida.
Most AI training is a slideshow about what AI might do someday. Your team nods, forgets it by Friday, and nothing changes. I run it the other way: by the end of the session, your people have built and run a working agent against your own kind of work.
I teach what I actually do. I'm a shipping AI engineer with a Google Professional Machine Learning Engineer certification and a Master's in AI, embedded in a real business building production systems. The session is the real tools, the real workflow, and the real guardrails.
What you leave with
Something that runs, not notes.
A working agent
Built in the room, wired to a task your team actually does, running by the time you leave.
The mental model
What AI can do now, where it breaks, and how to tell the difference, so your team stops guessing and starts scoping.
Guardrails that hold
The prompt and review patterns that keep an AI tool from confidently making things up, the part most training skips.
A shortlist
The two or three places in your operation where this pays off first.
Two formats
Built around your team's actual work.
For teams: a $1,500 working session where your people build alongside me on their own laptops. For executives and owners: a $750 briefing on what is now buildable, what it costs, and how to spot the difference between a real use case and a demo.
The tools are the real ones, Claude Cowork and Claude Code, set up on your own work. What your team leaves with is the first harness your business can drive without me: the setup around the AI that connects it to your systems, enforces your rules, catches mistakes, and remembers what works.
Both formats are hands-on, and both end the same way. Not "now you know about AI," but "here is the thing you built, and here is what to build next." Both are on the menu.
Proof
I teach from production, not a curriculum.
The training is grounded in systems I run every day: a Northeast Florida contractor now running on software it owns, a legal evidence-search product with full citation coverage, an autonomous market scanner on fourteen cloud services. You learn the workflow that built those, not a generic syllabus.
When the session surfaces a real build worth doing, it routes straight into scoped work. Training is often how the first project starts.
FAQ
Common questions.
- Is this a strategy workshop?
- No. No strategy decks, no maturity frameworks. It's hands-on: your team builds a working agent against real work and leaves with it running.
- Do people need to code?
- No. The session meets your team where they are. Non-technical people build with plain language and the right guardrails; technical people go deeper. Everyone leaves with something that runs.
- What does my team need to bring?
- Laptops, and a couple of real tasks from your business. You build against your actual work, not a toy example.
Train your team on the real thing.
Thirty-minute call to scope a session for your team or a briefing for your leadership. Tell me what your people do all day; I'll build the training around it.