The AI Fluent CoS: 6 Week CohortÂ
Build it live, with us, in six weeks.
$3,000 · Employer-expenseable
Â
What changes when someone builds it with you
You could watch every video in this program, understand every concept, follow every step — and still end up with nothing running in your stack three weeks later. Not because you didn't try. Because your CEO needed something, your calendar imploded, and "finish the Zapier build" got pushed again.
The cohort is designed for exactly that reality.
You watch the pre-recorded video before each session. When you show up live, we don't re-teach it — we build it. In your tools, your stack, your workflows. Melanie (an expert in the Chief of Staff profession) facilitates. Dan (an AI developer and expert in the AI automation space) handles every technical moment in real time. Twelve peers on the journey with you. And by the time the session ends, something is running that wasn't before, time that was being lost is now regained.
That's the structure that actually produces change.
Â
Who this is for
Chiefs of staff who are ready to stop operating on adrenaline and start operating on systems. Senior operators stepping into a CoS role who want to arrive AI-fluent from day one. Anyone who wants to get ahead of the AI wave and whose company will invest in this (and we've made it easy to ask them to, with an employer expense justification document written and ready for you to send.)
Â
What you get
Everything in DIY
Every video module. Every template. Every prompt. Every workflow blueprint. The resource library. The lifetime access. The 6-week interactive cohort includes the full DIY track — you're not choosing between content and live sessions, you get both.
Â
6 Live Weekly Implementation Workshops
60 minutes each · Capped at 12 studentsÂ
This is where the building happens. Each workshop corresponds to the module you watched that week — and when you arrive, we get to work.
Workshop 1 — Voice Document + First Pre-Meeting Brief You arrive with a draft voice document built from Module 1. One volunteer puts theirs on screen and we refine it together — the whole cohort learns from one example and applies it to their own. Then we run a live pre-meeting brief for a real meeting happening this week. You leave with a voice document that works and a brief your CEO sees tomorrow.
Workshop 2 — Board Deck Narrative Generator + Meeting Pipeline You bring your real metrics, even if anonymized. We build the board deck narrative generator with your actual numbers — and watch a 45-second Claude output that sounds like your CEO wrote it. Then the meeting-to-action pipeline: Fathom records, Claude extracts action items, they land in Notion with owners assigned. Both running before the session ends.
Workshop 3 — Weekly Digest System Your first full automation, built end-to-end with live support. Google Form for team inputs, Zapier connecting it to a Google Sheet, Claude generating the narrative, automatic delivery to Slack or email. Every single student leaves this session with it running. Not in progress — running.
Workshop 4 — CEO Context Packet The AI developer leads this one. Scheduled trigger, Perplexity pulling competitor news and industry signals, Claude formatting it into a brief in your CEO's voice, delivered automatically each week without you. You build it simultaneously in your own account. By the end of the session it's configured and live.
Workshop 5 — Pre-Meeting Intelligence Workflow A volunteer brings a real high-stakes meeting they have coming up and we build their brief live — full Perplexity research, Claude synthesis, NotebookLM analysis of the relevant documents. Then every student runs the same workflow for their own upcoming meeting. You leave with something your CEO will use tomorrow.
Workshop 6 — Portfolio + Org Roadmap Every student demos one system they built — three minutes, live demonstration. The cohort reflects back what's working. Then we workshop your AI opportunity audit and org roadmap together. You leave with a document ready to put in front of your CEO and a clear picture of what comes next.
Â
6 Weekly Office Hours
45 minutes each · Open to full cohortÂ
The day after each workshop, office hours open. Bring whatever broke overnight. Bring the edge case your specific stack threw at you. Bring the question you didn't want to ask in front of the group.
Melanie and Dan will be there to walk you through any roadblocks. The builds get finished. The gaps get closed. This is where the real learning compounds, because you've had time to try it in your actual environment and now you know exactly where you need help.
Â
AI Developer Co-Facilitator — In Every Session
Standalone value: Incalculable for a non-technical operator
This is what makes The AI Fluent Chief of Staff cohort different from anything else in this space.
An AI developer who has built automation systems for chiefs of staff at growth-stage companies is in the room every week — for every workshop and every office hour. When your Zapier trigger isn't firing, he diagnoses it in real time. When your Claude prompt is producing inconsistent output, he knows how to fix it. When your stack requires a different approach than the standard build, he adapts on the spot.
You don't have to be technical. You just have to show up. He handles the rest.
Â
Private Cohort Slack Community
Access continues after the program ends
Same Chief of Staff role. Same pressures. Same builds. Going through it at the same time.
This cohort becomes your AI brain trust even beyond the six weeks. After the program, you move into the alumni community together. A growing network of AI-fluent CoS operators who share what they're building, answer straight questions, and understand your role the way most people around you don't.
That compounds over time in ways that are hard to predict and consistently valuable.
Â
Employer Expense Justification Document
One page that makes the ROI case to your CEO or CFO, including the math: a chief of staff reclaiming 10 hours per week at a $180K salary recovers $90/hour in productive capacity. This program quickly pays for itself, and the systems keep running long after the cohort ends.
