Happy Operators AI Cohort
Five builders, five stacks, one week: each shipping an agent suited to their own work.
A week of building for their own work
I facilitated a one-week AI cohort for the Happy Operators community. Five people joined, each with something they wanted to build for their own business. There was no shared stack or set project to work through. My role was to help each person choose something useful they could finish within the week and support them as they built it.
Different starting points
One member arrived with an agent system already half built. They wanted help with evaluating and improving it, along with the accountability of a deadline. Another had never installed a command-line tool and needed a one-to-one before they could run anything on their own machine.
Those different starting points shaped the support. Some people built agents on their own cloud infrastructure, others worked locally, and others used tools such as Claude Desktop, Claude Code and Apify. Each person worked with an approach that suited their project.
Support through the week
We had daily group check-ins, with office hours, one-to-ones and support between sessions. The group calls gave everyone a chance to share progress and see what others were working through. Individual sessions made room for the questions and setup problems specific to each person's build.
We set the Friday demo day at the beginning of the week. That gave us a clear point to work towards and helped keep the projects small enough to demonstrate.
Five demos on Friday
All five members showed their work on Friday. Each had made progress from a different starting point, with a build of their own.
The week was intensive, but there was also a real sense of community. People were working on different projects at their own pace, with a small group around them to share problems, offer support and keep things moving.
Built with: Claude Code, Claude Desktop, Apify, self-hosted cloud agents, local runtimes
Part of the Rolling Waves work archive.