Tomorrow at 10 AM ET, a small group of people is going to spend four hours building something that changes how they work.
Not watching a demo of something that changes how they work. Not learning about something that could theoretically change how they work. Actually building it, live, and using it before the call ends.
That's Claude OS in a Day. And it's tomorrow.
Here's the thing I've noticed about the night before: people are usually in one of two places. Either they've cleared their schedule and are genuinely excited. Or they're still not sure they should have signed up. Both groups leave with the same system. The second group is often more surprised.
What Changes the Morning After
The first thing people notice isn't the automations. It's the briefing.
You wake up, type one command, and Claude — which now has live access to your Gmail and your calendar — tells you what's actually in front of you today. Not a weather widget. Not a to-do list you built yourself. Your actual email, synthesized. Your actual day, summarized. The three things that need a decision before lunch.
That doesn't sound like much until you compare it to the alternative: opening five tabs, reading through everything, reconstructing context you had yesterday, then starting work an hour later than you meant to.
The second thing people notice is the follow-up that happened without them.
The lead who submitted a contact form on Sunday got a personalized response while you were making coffee. The meeting you had Monday has notes in Notion with action items already categorized. The invoice that was due got a follow-up reminder sent to the client. None of that required you to think about it.
That's what a Claude OS does. It runs the operational layer of your work so you're only making decisions that actually need you.
Why Most People Keep Putting It Off
The answer is never "I don't want this." It's always some version of "I'll set it up when I have time to figure it out properly."
That window doesn't open.
The configuration isn't hard — the workshop gets through it in 90 minutes — but it's specific enough that most people stall on one thing (usually the OAuth for Gmail MCP), can't fix it without a reference point, and shelve it. The system stays on the to-do list. The manual work keeps happening.
A live session collapses that gap. Every failure mode gets solved in real time, in context, with someone who's debugged it before. You're not reading a tutorial and hoping the version they used matches yours. You're building alongside someone who's built this dozens of times.
What You're Actually Signing Up For
Four hours. Monday at 10 AM.
You leave with:
- Your CLAUDE.md — the operating manual Claude uses to understand your business, your style, and your rules
- Three MCP servers installed and running — Gmail, Calendar, Notion, connected to your real accounts
- Three automated workflows — morning briefing, meeting prep, end-of-day log
- A personal Claude playbook documenting every config decision you made
Everything lives on your machine. No subscription after today. No third-party platform to trust with your data.
The next morning, the briefing runs itself. That's the test. Not whether it works in the workshop — it will. Whether it's still running three weeks later because you actually built it right.
Seats are limited because the session is genuinely small. Five left as of this morning.
Reserve your seat for tomorrow →
If not tomorrow, Claude for Agencies runs Wednesday the 29th — same format, same size, built for agency owners who want to remove themselves as the delivery bottleneck.
— Murph
