A hands-on workshop where analysts, operators, researchers, and leaders build small sites, tools, and apps with Claude Code, hand repeatable multi-step work to Claude Cowork, and learn to review what Claude produces.
Best for people who understand the work deeply and want a practical way to build their own tools and hand the repeatable parts of their work to Claude.
People who already understand the work and need a faster way to turn ideas into small tools, dashboards, and repeatable workflows.
Teams with a backlog of internal process fixes, prototypes, intake flows, and reporting helpers that never quite reach the top of engineering's list.
Leaders who need practical fluency in AI coding agents before making broad adoption or vendor decisions.
Founder/operator groups that need a concrete way to test ideas, build demos, and understand what should move to a professional build later.
Faculty, staff, and research teams that want to build useful tools without pretending everyone is becoming a full-time software engineer.
Groups whose weeks fill up with the same reports, document reviews, file wrangling, and handoffs, and who want Claude to take on the repeatable parts.
Pick a tool, site, or app that is useful but small enough to finish, and write a plan Claude can follow.
Give Claude Code clear context, constraints, and acceptance checks, then steer it to a working prototype.
Hand multi-step work across files, research, and spreadsheets to Claude Cowork and check what comes back.
Turn the parts of a process that work into reusable prompts, skills, and workflows the team can share.
Read output with judgment, use errors and logs to steer Claude when work breaks, and know when to ask for a rewrite.
Understand privacy, security, shadow-IT, and quality boundaries, and recognize work that should not be automated.
The format depends on whether your goal is leadership education, team fluency, or a real internal pilot.
A practical leadership session on what Claude Code can do, where it fails, and how to structure a safe pilot.
A focused team session covering setup, one guided build with Claude Code, and one recurring task handed to Claude Cowork.
The core Make & Automate day: the morning goes to scoping and building a working prototype with Claude Code, the afternoon to delegating recurring work to Claude Cowork and improving the process around it.
Training plus follow-up: pick tools to build and tasks to automate, work on them between sessions, review the results together, and leave with a practical adoption playbook.
Participants spend the day building a small tool and handing real, repeatable work to Claude, then reviewing what it produced.
Participants learn how to supervise Claude Code and make sound product/workflow decisions, not memorize syntax.
We talk directly about data privacy, tool access, account setup, failure modes, and when the work needs professional engineering.
Stephen uses Claude Code and Claude Cowork for prototypes, client work, production apps, and his own recurring work, so the class focuses on what actually works.
It builds on the public workshop, first run in June and July 2026: small groups, setup help, real building, and a workflow people keep using after the day ends.
The team version adapts that day for departments, leadership groups, and organizations deciding how to adopt Claude Code and Claude Cowork.
I can now seamlessly plan, build, and deploy with a trusted workflow.
Dr. Hill encouraged me in a way that takes away the intimidation of being a beginner and seeing a pathway toward being only limited by imagination and time.
Taking a course that made me confident I can stay ahead of the curve took AI integration from uncomfortable to capable.
Tell us who would attend, what they want to build or automate, and whether you're thinking briefing, workshop, or pilot sprint.