The flagship
From Claude user to Claude operator.
Two live days, twenty people, and your own work on screen the whole time. Day one wires Claude into how you already operate. Day two builds and ships something real.
Next cohort Sep 15 – Sep 16, 2026 · 4 of 20 seats left
$ claude /morning
- read inbox, calendar, Stripe
- drafted 3 replies
- flagged 2 invoices past 30 days
- ad spend drifted 18% off target
Waiting on you · 2
- Approve
Send 3 drafted replies
gmail · awaiting you
- Approve
Pause the overspending ad set
meta ads · awaiting you
Nothing sends itself. You wire the gate where you want it.
// you build this on day one
Every program runs on the same stack.
claude.ai, Cowork, Claude Design, and Claude Code, plus the layers underneath that almost nobody reaches: context, control, agents, and automation.
The surfaces
claude.ai
chat · projects · artifacts
Q4 launch plan
project · 4 artifacts
Claude Cowork
tasks · schedules · briefs
Daily brief
runs 6:00 AM
✓ invoices reconciled
✓ 3 replies drafted
Claude Design
brand · assets · mocks
brand tokens · exported
Claude Code
terminal · plan mode · agents
$ claude
→ 3 files changed
→ shipped ✓
The layers underneath
Context
- CLAUDE.md
- memory
- rules
Extend
- skills
- commands
- MCP
Control
- permissions
- plan mode
- hooks
Scale
- subagents
- teams
- workflows
Automate
- routines
- scheduled
- triggers
Build
- Messages API
- Agent SDK
- managed agents
Day one
Wire Claude into the work you already do.
No sandbox project. We start from your actual accounts, your actual inbox, your actual documents, and leave you with something running that you will still be using next Monday.
- Project instructions and memory that match how you think
- Connectors into the tools you already live in
- A daily brief that assembles itself before you sit down
- Skills and MCP, so Claude learns your tools instead of guessing
Operators, founders, and managers. No programming required, and roughly half of every cohort has never written production code.
If you already live in the terminal, this is the day you find out how much of your non-coding work was automatable the whole time.
Day two
Ship something real, in the room.
Day two moves into building. You pick something from your own backlog, and it gets built live with help on hand the moment you get stuck.
- Claude Code on a real repository, not a tutorial clone
- Agents that run without you watching them
- The Agent SDK and the API, and when each is the right call
- Debugging live, which is the part documentation cannot teach
- Both live days, three hours each
- Twenty seats, live Q&A throughout
- A prep call before day one
- A 30-minute 1:1 after the cohort
- Starter repo, toolkit, and recordings
- The alumni community
Go deeper
Want the third day?
Engineering Day is the technical room: a company brain on your real knowledge, an agent on top of it, deployed live. $399 on its own, or $299 added to your 2-Day seat.
Who teaches it
Taught by people who ship with Claude every day.
Two instructors, one operator and one engineer, because the room is always a mix of both.
Charles J Dove
Founder, C&C Strategic Consulting
12 years building businesses · 3,200-member community
Twelve years building businesses, the last stretch of it building AI systems that run without anyone watching them. The material here comes out of client work and shipped software, not out of a slide deck written to fill two days.
That matters for one reason. When something breaks live in the session, and it will, you watch it get debugged in real time. That is the part you cannot get from documentation.
Sal Shirgaleev
Senior backend engineer
Self-taught engineer · ex-Dataminr · 60K on Instagram
Sal is a senior backend engineer with 7 years across AI and fintech, automating production systems with AI agents like Claude Code and Codex.
He builds systems that handle over $8 billion, where being wrong is expensive. So he has spent years learning how to direct agents to produce correct code instead of confident mistakes.
He was putting LLMs, the kind ChatGPT is built on, into production before ChatGPT existed.
Dates
Live cohorts, real seats.
Every cohort is capped at 20 people. No countdown timers here, just the actual count.
September Cohort
Sep 15 – Sep 16, 2026
October Cohort
Oct 13 – Oct 14, 2026
November Cohort
Nov 10 – Nov 11, 2026
Questions
Before you book.
No, and that is not a hedge. Day one is entirely about wiring Claude into how you already work, which requires no programming. Day two goes further into building, and roughly half of every cohort has never written production code. You will still ship something.
Fully. Two three-hour sessions, one per day, capped at twenty people. You can interrupt, share your screen, and get unstuck in real time. Recordings go out after, but the value is in the room.
No. We do not issue one and we do not run an exam. Completion certificates are handed out for attendance, everyone knows it, and they carry no weight. You leave instead with working software you built during the session and a setup that still runs the following week.
A separate technical day for people who already live in Claude Code and want the full system: a company brain on your real knowledge, an agent on top of it, deployed. It is $399 on its own, or $299 added to a 2-Day seat. Most people do not need it on day one.
Usually yes. Most companies cover this under an existing education or professional development budget. There is a page at /for-managers with the numbers and an email you can forward without editing.
A Claude account and a terminal. Claude Pro is the minimum. Max is worth it for the cohort, because Pro's usage limits are shared across Claude and Claude Code and can run out partway through a full day of hands-on building. You get a setup checklist a week ahead.
Join the interest list and you will hear about the next cohort before it goes public. Cohorts run monthly, and seats in the current one are usually gone before the date is close.
Full refund up to seven days before the cohort starts. After that the seat is held and cannot be resold in time, so it becomes a credit toward a later cohort instead.
Two days that change how you work.
20 seats, your own work, and something running by the end of it.
Next cohort: Sep 15 – Sep 16, 2026 · 4 of 20 seats left