I get the same question every week: "What do I actually walk out with?"
Fair. The Claude Code workshop space is filling up with hype — AI this, automation that — and nobody tells you what you're building. So here's the full breakdown of what happens in Claude OS in a Day, our live 4-hour workshop on April 27. Every deliverable. No fluff.
Hour 1: Your CLAUDE.md — The Operating Manual
The first thing we build is your CLAUDE.md file. This is the configuration document that tells Claude Code who you are, how you work, and what rules to follow.
Think of it as an employee handbook for your AI. Without it, Claude guesses. With it, Claude executes.
Your CLAUDE.md includes your communication style, your project structure, file permissions, tool preferences, and behavioral guardrails. We write it together, live, tuned to your actual business — not some generic template you grabbed off GitHub.
This alone changes how Claude Code operates for you. Every command, every suggestion, every workflow downstream inherits from this document. Get it wrong and you're fighting Claude all day. Get it right and it feels like a second brain.
Hour 2: MCP Servers — Gmail, Calendar, Notion
This is where most self-learners hit a wall. MCP (Model Context Protocol) servers are how Claude Code connects to external tools. They're powerful but the setup is unforgiving — one wrong path in your config and nothing works, with zero useful error messages.
In the workshop, we install and configure three MCP servers:
Gmail MCP — Claude reads your inbox, drafts replies, sends emails on your behalf. Not "summarize my inbox" chatbot stuff. Actual send-and-receive with your real email account.
Calendar MCP — Claude sees your schedule, creates events, checks availability, and blocks focus time. It becomes your scheduling assistant that actually has calendar access.
Notion MCP — Claude reads and writes to your Notion workspace. Meeting notes, project databases, task boards — Claude operates inside them instead of just talking about them.
Each one takes about 15 minutes with guided setup. On your own? I've seen people spend entire weekends on Gmail MCP alone, stuck on OAuth scopes and credential paths. The live debugging loop is the difference between "I gave up" and "it's running."
Hour 3: Three Custom Workflows
Once your MCP servers are live, we build three workflows that chain them together. These aren't toy demos. They're repeatable automations you'll use every day.
Workflow 1: Morning Briefing — Claude checks your email, scans your calendar, pulls relevant Notion pages, and generates a single briefing. One command, every morning, everything you need to know.
Workflow 2: Meeting Prep — Give Claude a meeting on your calendar and it pulls the attendee context from your email history, grabs the relevant Notion project page, and drafts your talking points. You walk into every meeting with receipts.
Workflow 3: End-of-Day Log — Claude reviews what you did today — emails sent, meetings attended, tasks completed — and writes a structured log to Notion. No manual journaling. No forgetting what happened at 10 AM by the time you close your laptop at 6.
These workflows are yours. They live on your machine. No subscription. No SaaS. No third-party platform that gets acquired and shuts down.
Hour 4: Your Claude Playbook
The last hour is open build time. You take everything from hours 1-3 and we extend it to your specific use case.
Sales team? We wire up a lead follow-up sequence. Content creator? We build a publishing pipeline. Agency owner? We set up a client intake workflow.
By the end, you have a documented playbook — your personal reference for every workflow, every MCP config, every CLAUDE.md rule. It's the thing that makes this stick after the workshop ends instead of collecting dust.
Why Live Beats Self-Taught
I could write a tutorial. I could link you to the MCP docs. Here's why that doesn't work for most people learning Claude Code:
Config debugging is brutal. MCP servers fail silently. Permission errors look like connection errors. One typo in a JSON path kills the whole server. In the workshop, we catch these in seconds because we've seen every failure mode.
Context matters. The docs tell you what's possible. They don't tell you what's useful for your workflow. A live session lets us skip the 80% you'll never use and focus on the 20% that changes your day.
You leave with a working system. Not a half-configured experiment. Not a bookmark folder of "things to try later." A complete, tested, operational Claude OS that's already connected to your email, calendar, and workspace.
The Details
Claude OS in a Day — April 27, 2026. Four hours. $247.
You get: CLAUDE.md, 3 MCP servers configured, 3 custom workflows, your personal Claude playbook, and access to our private community for ongoing support.
This isn't a lecture. It's a build session. You show up, you build, you leave with a system that works.
