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 seatLive workshop · 3 hours · only 15 spots
Master Claude
Cowork
In three hours you will learn how to automate the highest-leverage tasks in your job.
Training professionals across trusted brands
Here’s what we cover
Level up your Claude Cowork skills in 3 hours, or your money back.
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.
Is this workshop for you?
Yeah, probably…
Workshop Agenda
The Schedule
Times are elapsed from the start of your cohort. We confirm your date and clock time when you book.
0:000:20
0:00 – 0:20
Welcome, and the shape of a Cowork run
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.
0:200:50
0:20 – 0:50
The three automations worth building in your job
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.
0:501:25
0:50 – 1:25
Context, skills, and connectors — wired live
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.
1:252:05
1:25 – 2:05
Your first real automation, built end to end
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.
2:052:15
2:05 – 2:15
Break
2:152:50
2:15 – 2:50
The skill file, and a cron trigger underneath it
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.
2:503:15
2:50 – 3:15
Real data in, a dashboard out
Your numbers, an interactive view you can leave open on a second monitor, and the document that comes out of it when somebody asks.
3:153:30
3:15 – 3:30
Q&A, and what to build on Monday
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
Trusted Anthropic Claude Experts
Scotty has spent the last 10 years in tech working in data analysis, development, and large language model fine tuning. He architects backend systems, automation pipelines, and AI infrastructure, turning strategic roadmaps into production-grade solutions that run reliably at scale.
Austin has spent his career in information intelligence and B2B enterprise SaaS sales at executive level, on a systems analysis foundation. As solutions architect he scopes every engagement and decides what it actually is, turning business requirements into architecture that holds up in production.
Every attendee walks away with:
01The automation you built in the room, in your account
02The skill file behind it, re-runnable and editable by you
03A cron trigger already firing it on the schedule you set
04Your connectors wired into the tools you already use
05A dashboard on your own data, and the report it writes
06The recording and full chat transcript from your cohort
07Three ranked build candidates out of your own week
NextFifteen seats a cohort.Reserve your seatYou don’t have time
to watch hundreds of tutorials.
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.
What you get
This workshop
YouTube & blog posts
A general AI course
Live, not a recording of someone else’s account
Somebody watching when it breaks on your machine
Maybe
Claude specifically, not “AI” generally
Maybe
Built on your own work, not a sample dataset
Something actually running before you close the laptop
Maybe
You get the file, not a screenshot of the file
Small enough that you get the screen when you need it
A recording and a transcript afterwards
Costs nothing
▸ Common questions
Got questions?
Still stuck on something? Email hello@aiatwork.com and one of us answers it — actually one of us. There are only two.