FoundersWire Claude into your calendar and inbox, then have it brief your whole week every Monday before you're up. Save the workflow as a one-command skill your team can reuse.
Get a seatThree and a half hours, live, on your own work. You leave with an automation running in your own account.
Training professionals across trusted brands

Most people install Cowork, poke at it for twenty minutes, and go back to the chat box. A new tool is not worth anything until it is set up.
We tour the desktop app: where the work actually lives, what a session is, and the handful of settings nobody changes, because nobody tells them to. You do it on your own machine while we watch the screen.
Everybody in the room ends this block on the same setup, which is the only reason the next three hours work at fifteen people.

The hard part is never the building. It is knowing which of the fourteen annoying things in your week is the one that pays you back.
We bring the questions, and a custom agent that asks them. You leave this block with three named candidates from your own calendar, ranked by how much of your week they give back, and a ready-to-run prompt for each.
Nobody picks your automation for you. It comes from your real work, not a demo.

Connectors and skills are the two customizations that change what Claude can actually do, and almost nobody sets them up.
Mail, calendar, drive, your chat tool, your own file system: you wire them up live on your own account, in the order that keeps you from locking yourself out of your own data.
You leave with Claude plugged into the stack you already work in, not a screenshot of somebody else's.

Not a demo. One of the three candidates you named an hour ago, built on your data, with both instructors on the floor.
It runs while everyone watches. It gets fixed in the room the first time it falls over, which it will. Watching that fix is worth more than watching it work.
Forty minutes, because this is the part that matters.

This is the block that separates people who use Claude from people who have Claude working for them, and almost nobody reaches it on their own.
The session you just ran becomes a file. Drop it in, say one thing, and the whole job runs start to finish. Then it goes on a schedule underneath.
The difference is a job you remember to run versus a job that already ran before you opened the laptop.

Every job runs on numbers somebody has to read, and raw data means nothing until someone can see it.
Your numbers, not a sample set. We pull in live data and build an interactive view you can leave open on a second monitor.
Then we generate the document that comes out of it: the deck or PDF you would actually send to someone asking how it is going.
Workshop Agenda
Times are elapsed from the start of your cohort. We confirm your date and clock time when you book.
Every run has the same shape: request, clarifying question, plan, then files in your folder. We set yours up first — it's what a mistake can reach.
A task earns automation when it spans more than one source, takes more than one step, and ends in a file. Run your week through that and leave with three candidates, each with a prompt.
Claude only knows what you give it — standing context, a skill, or a connector you wire live. We wire your mail, calendar, and drive, in the order that keeps you out of trouble.
You write the request: an outcome, a scope, a stopping condition. Then you steer it while it runs, and check the file yourself when it's done.
Describe today's automation in one sentence, and Claude turns it into a file. Put that on a schedule, and it has already run before you open the laptop.
Your numbers, an interactive view you can leave open on a second monitor, and the document that comes out of it when somebody asks.
The cheapest safety habit is scoping the task narrowly before you trust the output. The rest is open floor, and everybody leaves with a named next build.
Meet your instructors

Builds it on the client’s own repo — skills, MCP servers, hook rigs, subagents — then writes the genericised version before the engagement closes.

Scopes every engagement and decides what it actually is, then specs the system to come apart again so the pattern underneath can be published.
Genuinely — all of it is out there. A good channel and three free weekends gets you most of the way. The question is whether anything is running at the end of it. That gap is what a seat buys.
Still stuck on something? Email hello@claudeguys.com and one of us answers it — actually one of us. There are only two.