Yesterday we ran the last live session of the April 2026 cohort.
Six workshops in three weeks. Each one a build — not a lecture, not a presentation. Someone came in with a problem they were tired of doing manually, and left with an agent or workflow handling it.
Here's what actually happened across all six.
Session 1: Introduction to Claude (Weekly, $29)
This one runs every week and it's not glamorous. Account setup, interface tour, live demo of what Claude can actually do versus what people expect it to do.
The insight that lands every time: Claude isn't a search engine and it isn't autocomplete. It's a thinking partner that can execute. Most people have been using 10% of it.
We'll keep running this one weekly. It's the front door.
Session 2: AI for Local SEO (Apr 15, $97)
90 minutes on the thing that matters most for local service businesses: showing up when someone searches for what you do.
What people built: content calendars driven by actual local search data, automated Google Business Profile update workflows, and review response templates that sound human because they were trained on human responses.
One HVAC company left with a process that takes their weekly five-star reviews and turns each one into a neighborhood-specific SEO page. That's the kind of thing that compounds quietly for years.
Session 3: Automate 80% of Your Work (Apr 20, $147)
Two hours on the 80/20 of business automation — the stuff that actually kills your week.
Inbox triage. Meeting prep. Proposal drafts. Status updates. The repetitive cognitive work that eats four hours a day and produces nothing proprietary.
The exercise: attendees listed every task they did in the last five business days. Then we categorized them. The average was 72% automatable. One person hit 84%.
Not automated yet. Automatable. That's the starting point.
Session 4: Build Your AI Employee (Apr 23, $197)
This is the one I've written about before. Three hours, one agent per person, built live.
The intake agent for the law firm. The follow-up sequence for the home services company. The LinkedIn post generator for the consultant.
The thing that keeps surprising me: people expect the hard part to be technical. It isn't. The hard part is writing the job description — the system prompt. When you've never had to think about what a role actually requires, you realize you've been doing it on autopilot for years.
The AI forces you to make it explicit. That turns out to be useful regardless of whether the agent ever runs.
Session 5: Claude OS in a Day (Apr 27, $247)
Four hours. The full operating system.
CLAUDE.md — the document that gives Claude full context about your business so you never have to re-explain yourself. MCP servers — the connections that let Claude read your calendar, query your database, send emails, post to social, without you being in the middle of it. Three automated workflows — things that run without you initiating them.
This is the session where people get quiet for a while. Not because it's confusing — because they're doing math. How many hours per week does this recover? What does that free me up to do?
One person realized she'd been spending 12 hours a week on work that was now automated by the end of the session. Her response: "Why didn't anyone tell me this existed?"
To be fair: it barely did exist six months ago.
Session 6: Claude for Agencies (Apr 29, $297)
Yesterday. For people running client-facing service businesses who are the bottleneck in their own delivery.
The problem in most agencies: the owner is the smartest person in the room, and every client knows it, so every client wants them personally. That doesn't scale. The answer isn't "hire more people" — it's building a delivery layer that encodes what you know.
What that looks like in practice: an intake workflow that classifies new projects and extracts the brief before the first call. A quality review agent that checks deliverables against the scope before they go out. A client update generator that pulls from project notes and sends weekly status without anyone writing it.
The owner stops being the person who does the work. They become the person who defined what good looks like. The system executes it.
That's a different business.
What April Proved
Three things I'm taking into the June cohort:
Non-developers can build production agents. Every attendee across all six sessions. Zero developers. Zero coding. The constraint isn't technical — it's clarity about what you want the system to do.
The 3-hour session is the right format. Long enough to finish something, short enough that people stay focused. The 4-hour sessions pushed it. Everything delivered, but we'll tighten the Claude OS and Agencies sessions.
The real unlock is the CLAUDE.md. Every advanced workshop traces back to this. When Claude has full context — your business, your voice, your clients, your constraints — the quality of everything else goes up. This should be the first thing anyone builds, even before the agents.
June cohort is forming. If you were on the fence about April, the June session structure will be sharper for it.
Or if you want to start now, the free audit shows you what your site needs.
— Murph
