The argument in one line.
When AI cuts prep time from days to minutes, founders stop rationing what they ship -- the real constraint was never ideas, it was the cost of execution.
Read if. Skip if.
READ IF YOU ARE…
- A solo founder or small-team operator who spends Sunday catching up instead of setting up.
- You use Claude already but trigger it ad hoc rather than through structured projects with loaded context.
- You have recurring deliverables every week -- proposals, community recaps, course modules -- that take hours and feel like overhead.
- You want a practical walkthrough of how Scheduled, Event-driven, and Manual AI workflows divide labor differently.
SKIP IF…
- You are looking for a technical build tutorial -- this is a workflow demonstration, not a step-by-step setup guide.
- You do not yet have an audience, community, or client pipeline to feed these workflows.
The full version, fast.
The video argues that most founders waste Monday reacting because they never designed their week before it started. The fix is a 1-hour Sunday ritual anchored by an RPM planning framework (Result, Purpose, Massive Action) and a command center that aggregates all business signals in one view. From there, six workflows fire -- some on schedule, some triggered by events like a meeting recording dropping, some manually for judgment-call launches -- each producing a polished Gamma deck with a single Claude prompt. The core thesis is not about efficiency; it is about removing the execution cost that causes founders to avoid the work they already know they should ship.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.
00:00 – 00:44
01 · The weekly ritual
Binary contrast opener -- two types of founders. Personal credibility: built businesses while working full-time and raising a son. The 1-hour Sunday bet introduced.
00:44 – 02:00
02 · Why to-do lists fail
Task management vs. result-committed planning. RPM framework introduced. Tasks without a committed outcome should not make the cut.
02:00 – 03:00
03 · The command center
Live demo of aggregated dashboard: calendar, pipeline, editorial calendar, community pulse, client engagements. RPM updated first; everything downstream serves those results.
03:00 – 06:15
04 · Workflow 1 -- Sales deck (manual)
Launch sales deck for Social Brand Accelerator. Claude project preloaded with offer, audience, pricing, prior decks, and three skills. One-sentence prompt triggers the build; Gamma connector produces the polished deck. Sponsor segment embedded.
06:15 – 08:52
05 · Workflow 2 -- Proposal (event-driven)
Calendly ends, Fathom recording drops, routine detects call type, updates pipeline, kicks off proposal generation. By Sunday the proposal is already drafted; founder reviews and approves. Draft mirrors prospect transcript language exactly.
08:52 – 09:46
06 · Three workflow types explained
Scheduled (predictable recurring), Event-driven (fires on triggers), Manual (judgment-required). Design principle: AI handles predictable so brainpower goes to situational.
09:06 – 11:06
07 · Workflow 3 -- Team training (manual)
SOP training deck for new studio team. Claude pulls live Notion scenarios at runtime so deck reflects current state. One command, Gamma builds step-by-step role-by-role layout.
09:46 – 11:45
08 · Workflow 4 -- Community call deck (scheduled)
Every-other-Friday scheduled task fires: Claude pulls top community posts, questions, engagement winner, drafts prep doc and deck. Founder reviews and tweaks agenda Sunday in a few minutes.
11:45 – 12:30
09 · Workflow 5 -- Course module (manual)
Weekly course module deck. Full curriculum, audience profile, prior modules, and brand kit loaded. Gamma stays consistent across all modules.
12:30 – 14:10
10 · Workflow 6 -- Brand mood board (manual)
Visual concept for studio launch. Brand guidelines, prior mood boards, aesthetic keywords loaded. One-paragraph prompt produces full editorial mood board. Designer equivalent: weeks and thousands.
14:10 – 14:50
11 · Synthesis and CTA
Reframe: not about the decks -- about leverage. When prep costs one hour you stop rationing what you ship. Call to Founders Hive community and upcoming skills video.
Lines worth screenshotting.
- A to-do list has no accountability to an outcome -- you can check every box and still not move the business forward.
- RPM forces you to name the result you are committed to before listing a single action, which kills tasks that serve busyness but not goals.
- Three workflow types divide AI labor correctly: Scheduled handles predictable recurrence, Event-driven fires on triggers, Manual preserves human judgment for one-time decisions.
- Proposal quality jumps when the draft is built directly from the meeting transcript -- it mirrors the exact language the prospect used about the problem, outcomes, and constraints.
- A command center is worth building only after you know which recurring decisions happen every week -- it surfaces what the week needs so you trigger workflows instead of hunting for context.
- A course feels like a course, not a folder of random slides, when every module is generated from the same loaded brand kit -- consistency is a system output, not a design effort.
- A mood board that would have cost thousands and two weeks from a designer now comes from one paragraph of aesthetic intent -- the price drop changes which ideas get a visual.
- When prep only costs one hour, you stop rationing what you ship -- the launches you were avoiding and the pitches you were skipping all become affordable.
- Claude skills preload offer architecture, voice, and presentation style so a one-sentence prompt triggers the full build without re-explaining context.
- Event-driven automation means the proposal is already drafted by Sunday -- the founder's job is review and approval, not creation.
Design your week before it starts, not during it.
WHAT TO LEARN
The founders who move fastest are not better at executing tasks -- they are better at committing to outcomes before the week begins, then letting AI handle the prep.
- Starting a week from your inbox means the agenda was written by other people -- open Monday reactive and you have already lost the initiative.
- The RPM model forces you to name what you are committed to before listing actions; tasks that do not serve a committed outcome should not exist on your list.
- A command center is worth building once you can name the three to five recurring decisions you make every week -- it makes those signals visible in one place so you trigger workflows instead of hunting for context.
- Dividing workflows into Scheduled, Event-driven, and Manual prevents over-automation: let AI handle anything predictable; keep human judgment for anything situational or one-time.
- Loading prior winning examples into a Claude project as standing context means a one-sentence prompt produces something calibrated to your voice and brand, not a generic draft.
- Proposal quality rises sharply when it is built from the meeting transcript, mirroring the prospect's exact language -- it reads like you were paying attention, not selling.
- Consistency across a course, community, or brand feels designed when it is a system output -- the same loaded brand kit in every generation is the mechanism, not manual taste.
- When prep costs one hour instead of a day, you stop rationing what you ship: the pitch you avoided, the launch you deferred, the meeting you skipped prep for all become affordable decisions.
- A visual concept that previously required a designer and two weeks now costs one paragraph of aesthetic intent -- the price drop changes which ideas get explored, not just which ones get executed.
Terms worth knowing.
- RPM
- A planning framework by Tony Robbins: Result (the outcome you are committed to), Purpose (why it matters), Massive Action (only the moves large enough to produce the result). All three are defined before any tasks are listed.
- Command Center
- A single dashboard view that aggregates a founder's calendar, sales pipeline, editorial calendar, community activity, and client engagements so all weekly decisions can be made in one sitting.
- Claude Skill
- A reusable instruction set loaded into a Claude project that encodes a specific competency -- offer architecture, brand voice, or presentation style -- so it fires automatically without being re-stated each session.
- Gamma Connector
- An embedded integration between Claude and Gamma that passes Claude narrative output directly into Gamma's design engine, producing a formatted deck without manual copy-paste.
- Fathom
- An AI meeting recorder and note-taker that transcribes calls and generates summaries; used here as the event trigger that fires the proposal-generation workflow after a Calendly meeting ends.
- Event-Driven Workflow
- An automation that runs when a specific event occurs -- such as a meeting recording being saved -- rather than on a fixed schedule or by manual trigger.
Things they pointed at.
03:15toolCommand Center (Notion dashboard)
04:00toolFathom (AI meeting recorder)
09:00toolCalendly (meeting scheduling)
09:35toolNotion (SOP and scenario storage)
09:50toolSchool (community platform)
Lines you could clip.
01:10
“The list has no accountability to a specific outcome. You can finish every single item and still not have moved the business forward.”
01:40
“Tasks that don't serve a committed outcome should not even make the cut.”
13:50
“When prep only costs one hour, you don't ration what you ship.”
07:15
“The proposal ends up mirroring the prospect's exact language about the problem, the outcomes that they want, and the constraints that they mentioned.”
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
metaphor
00:00There are two kinds of founders. The ones who let the week happen to them, and the ones who decide the week before it starts. The former open Monday with their flooded inbox and grind at a to do list all day.
00:09The latter are the ones who commit to specific outcomes and then design the days around them. And honestly, I've been on the latter track my whole career. I had to be honestly.
00:17I built my first two businesses while working a really demanding full time job and raising my son. The thing that's made it possible is a one hour Sunday ritual. I'm going to show you the whole thing today so you can run your week and not let the week run you.
00:31I'm gonna show you every workflow, every output, and AI is going to help me along the way so you can copy everything. And I'll make you a bet. If you watch the next fifteen minutes or so, you will never start a Monday by opening your inbox again.
00:43I promise. Now here's why I believe most people feel defeated and overwhelmed with work. What they do is they open Monday morning, they look at the calendar, they look at the inbox, and then they make a to do list.
00:54Are you one of them? Most of the time, people write down everything they need to do, maybe build a fancy tracker or even an app to check off boxes, and then feel great for a moment, but then totally defeated when they have to start grinding it because that's not planning. That is task management.
01:08The list has no accountability to a specific outcome. You can finish every single item and still not have moved the business forward. The framework that I choose to use is something that Tony Robbins teaches.
01:17It is called RPM, result purpose massive action. And I honestly have been using this for many, many years, and it has never done me wrong because you don't start with tasks. You need to start with the results that you're committed to by the end of the week, and then you ask why does that make any difference to you?
01:32What does hitting it actually mean for your business or yourself? And only then, you list only the actions that are massive enough to produce that result. And honestly, tasks that don't serve a committed outcome should not even make the cut.
01:44When you do that for an entire week in one sitting, Monday morning is no longer going to be a question anymore. I promise you. It is already going to be answered, and every day after that is going to be in service of something that you already decided was worth it.
01:57Let me show you mine so I can give you a full example, a real one, actually. This is where my Sunday starts. I call it my command center.
02:05It's basically the page that pulls in everything happening across my businesses. My calendar for the week, my sales pipeline, the editorial calendar, the community pulse from my two school communities, the active client engagements, everything that I need to make the week's decision in one single view. The first thing that I do when I sit down, and this takes only a few minutes, is update my RPM at the top.
02:25The result for the week, the focus for me, and then the purpose, what does it mean to us for the business, and then we map the massive actions that are required. That's basically the brain of the whole hour.
02:36Everything that I build next will be in service of those results. And then I start scanning down which calls are coming up, which prospects need attention, which content is going to go live? What the community needs from me this week?
02:48The command center is going to surface what the week actually needs from me, and then I trigger the workflows that build it. As easy as that. And I know it sounds easy.
02:55It took quite a while to build all of this, but I wanna show you everything. Okay? So this week, we are actually launching the social brand accelerator.
03:03That is a new program for business owners and creators who want to grow on YouTube and turn that audience into a real lead generation engine. It's honestly the biggest launch of the quarter for us, and that means that we need a sales deck that lands the moment a creator opens it. This one, I need to trigger manually from the command center because the launch is a decision.
03:20It's not a recurring task. I hope that makes sense. Right?
03:23So the project I open has everything the deck needs already loaded. The program positioning, the audience profile, my pricing tiers, uh, prior winning sales decks as reference, and then three skills will fire when I run this.
03:36One that handles the offer architecture, one that holds my voice, and one that knows our presentation style and brand elements. And then Claude pulls recent prospect calls from Fathom for the language that matches exactly what business owners and creators have told us they need when we asked them. Now if you're curious about the Claude skills that I use, I'm gonna make sure we link the video here as well as in the description because I made a video where I walked you through the top 20 skills that I could not live without in Claude.
04:00So what I do next is I type one sentence. I ask my chief of staff to build the sales deck for the social brand accelerator launch and to lead, for example, with the YouTube growth pillar. That's it.
04:10The skill will know what sales deck means in the project. The context knows the offer. The data knows the language, and then Claude basically drafts the narrative and hands it to Gamma through the Claude embedded connector.
04:21And guess what? In a few minutes, the entire deck is ready. We have a polished sales deck that is brand aligned with a few slides done in about ten minutes.
04:30Honestly, I would send this to a business owner tonight. That presentation, like I said, was created in Gamma using the Cloud Connector. Gamma is the tool turning every output that you're going to see today into something polished, and they're also partnering with us on this video.
04:44Now if you've been around, you might know that I have been using Gamma for over a year, and the reason that I keep using it is literally what you just saw. I described the deck that I need, and then Gamma turns it into a presentation that looks like an agency built it. And you don't need design skills, you don't need blank page wrestling, and you also don't need to start from scratch because their new template library is huge.
05:04You get case studies, mood boards, brand guidelines, investor decks, campaign concepts. Most of what I'm building today uses one of those as a starting point, actually, and Claude customizes from there. And if you think about it, it's the combination between Claude doing the thinking and Gamma doing the design that makes this whole hour so productive and honestly possible.
05:23Now let me give you a quick example of what it looks like to finalize a deck when Claude hands it to Gamma. Once the deck is generated, you can tweak anything, basically. You can pull a different layout from the template library.
05:33Let's say you want the slides to feel more editorial and you want two columns instead of one. It's easy to do that.
05:38You can swap a color from the brand palette, and then Gamma respects the kit so it stays on brand without you having to think about You can, I don't know, regenerate any text block that doesn't quite sound like you? Gamma can rewrite just that block, not the whole slide, actually. You can drop a new image.
05:53You can change a heading. You can restructure a slide, and it feels less like editing slides and more like editing a single document, honestly. With five minutes of polish, you've got something that you would be really proud to send.
06:05Now if you wanna try Gamma, the link is gonna be in the description so you can see the difference on the first deck that you built. Thank you, Gamma, for partnering with us on this video. Now back to the hour.
06:14We need to go into workflow number two. Next on the list are proposals. This week, we had an ideation workshop with a manufacturing company looking to automate their lead qualification.
06:23Now the workshop went really well, and that means that we need to send them a proposal on Monday. This one is the second example of an automated workflow, but the trigger is different. Okay?
06:32It's not a trigger that runs on schedule, but it runs on an event. Let me show you what I mean. So, basically, every time a Calendly meeting ends and the Fathom recording lands for me, a routine fires automatically.
06:44It is going to read the recording, figure out what kind of call that was, whether it was a discovery call, an ideation workshop, a kickoff meeting, and then updates the pipeline status in our pipeline manager. If the status moves to ideation workshop completed, needs proposal, then it kicks off the proposal generation right then.
06:59I don't have to do anything or much anymore. So by the time I end up sitting down on Sunday, actually, and open my command center, the proposal is already drafted in the pipeline, and my job is clearly to read it, to refine everything that I feel needs to be changed, and approve it for sending. The project the routine uses has everything.
07:17The proposal template, our service tiers, prior winning proposals as standing context. The key piece and the reason the proposal works is that it's built from the ideation workshop transcript. So the proposal ends up mirroring the prospect's exact language about the problem, the outcomes that they want, and the constraints that they mentioned.
07:35So this way, it doesn't sound like a generic agency proposal, but literally like we were paying attention during the workshop. I hope that makes sense. Right?
07:41Once that is done, you get all of the slides done before you end up sitting down or I ended up sitting down this Sunday. I already have a proposal that reads like I spent at least half a day on it, and Gamma's key study template carried the whole thing, in my opinion.
07:55Now there is a quick mention that I need to make before we move to the next workflow. As you've probably already seen, not everything that I'm showing you is something I trigger by hand, and that's intentional. There are actually three kinds of workflows in here.
08:07Some run on schedule, like my community call every two weeks. I'm gonna come back to that, or any other scheduled task. In that case, Claude pulls the data, drops the deck, and it's predictable and recurring.
08:17But we also have some that run on events, like a recording dropping in Fathom after a Calendly meeting end. The recording itself fires a routine that checks what the call was, updates the pipeline, and decides whether something needs to be built. And then all the rest are manual, launch concepts, trainings, visual identity work.
08:32I'm gonna show you in a moment. Those have to wait for judgment because they depend on what's actually happening that specific week for me. The system can handle predictable and the event driven, so I can spend my brain power on anything that's situational, and that's the design principle behind everything.
08:47It looks simple. It took a lot to build all of this, by the way. The next thing on the week, we're opening Skill Studios location here in Switzerland in a few weeks, and that means that the team there need to be trained on our client onboarding SOP before they can take their first client.
09:01This one has to be manual because it's a one time deployment, not something that we're gonna do on repeat. The operations project has the current onboarding documentation, our automation scenarios, our team roles. So Claude can pull the live scenarios from Notion at runtime so the training reflects what actually builds today, not what was built six months ago, and in the meantime, has drifted.
09:22And then all I need to do is give the command. I need to say, build the client onboarding SOP training deck for the Scale Studios team. That's it.
09:30And then Gamma's training format can do the heavy lifting on the layout. Step by step, role by role, decision points highlighted. I just need to bring the SOP content.
09:38Right? And then a few minutes later, we have the deck for the team that they will need to use as the foundation of their first month. Next up is my live community call.
09:48So if you're new around here, every two weeks, we have what we call a hive call in my school community. It's where the members and I get together on a call, and we work through whatever is blocking them on their business. And that means that we need a deck for the call that reflects what actually happened to the community over the last two weeks.
10:04This is the scheduled automation example. Okay? This is recurring.
10:07It's predictable. There is no judgment call requires to get it started. But, obviously, I need to make the judgment call in terms of what goes in there.
10:15Okay? So every other Friday morning, a scheduled task ends up firing. So Claude pulls the top engagement posts from school.
10:22It identifies the top member questions. It names the engagement winner of the round and then drafts the prep document and the deck. By the time that I open the command center on Sunday, it's all there.
10:31But my role is to review, to read what Claude pulled, to tweak the agenda based on what I actually wanna talk about that time around, and then finalize the deck. And honestly, Gamma's flexibility really shines here because the deck can have mixed media. It can have community stats, member highlights, teaching content, a live q and a slot, all in one cohesive deck, and only a few minutes on Sunday it takes to review, and I'm done.
10:52Now workflow number five. Okay. So then we have the content for our Founders Hive.
10:58That is our paid school community. And for that, we are building a Claude course, and I need to work on a new module every week. Now this week's module is on Claude projects, which means that I need a module deck that fits the rest of the course visually and is in my voice.
11:13This one has to be manual. Right? I trigger it from the course's editorial calendar in the command center when the next module is due.
11:19Now the project has the full course curriculum loaded, the audience profile for our founders community, prior modules as reference, as well as our brand kit. And all I need to do is give the command to build the module deck for plot projects, section three of the course, for example, and that's it. And then Gamma stays consistent with our Hive brand kit, the same colors, the same fonts, the same layout, same grammar across every module.
11:43That consistency is honestly what makes a course actually feel like a course and not a folder of random slides, and it only takes a few minutes. And now the last thing on the week, and the one where I honestly think Gamma is going to blow your mind away just like it did with me. As I said, we are launching the Scale Studios location here in Switzerland in a few weeks.
12:01And before we tell the world about it, we need a visual concept. Right? We need a mood board that captures the aesthetic, the energy, the brand world that I wanted this location to live in.
12:09And that means that workflow six is not gonna be a slide deck. It's gonna be a mood board. Again, a manual one because it's a launch decision.
12:16The project has the brand guidelines loaded, prior mood boards as reference, and a few aesthetic descriptions that I wanted to anchor, like editorial and architectural and modern Swiss. And then all I need is to give the command to build the Scale Studio's launch mood board in an editorial, architectural, modern Swiss style with our brand palette as the anchor.
12:34And look at that. That is not a slide. That is a fully visual editorial concept with typography, color blocks, imagery, white space, brand cues.
12:44It's the kind of thing that a brand designer would probably have charged me thousands for, and it would have taken two or three weeks. But Gamma built this in a few minutes from a paragraph of intent. Now I'll be honest with you.
12:55I had a brand concept that I wanted to build last year, and I asked a designer for a proposal, but the proposal came back two weeks later. And by the time I got the price and the timeline, honestly, the launch idea had cooled off, and I'd already moved on. But that's not happening with this project, and it won't happen again.
13:10So that's the hour. A command center took a few minutes, and then the six workflows, the other 50 or 55. A launch sales deck, a client proposal already drafted before ended up sitting down, a team training, a community call deck, a course module, and a launch mood board.
13:24I mean, that's great. But here's what you actually just watched. It was not about the decks.
13:28It was actually more so about what becomes possible when a founder no longer treats prep work like a business expense or a time expense and chooses to look at it as leverage, as a point of leverage for their entire week, something that they invest in and not something that is taxing them. Because, honestly, when prep only costs one hour, .
13:51You can send the sponsor or the sales pitch that you were avoiding. You can run two launches in a quarter instead of one. You can prep for the meeting that scared you instead of winging it.
14:00The week is no longer something that happens to you, but something that you build towards. And by now, you know how to do it. And hopefully, now you know why I don't recommend you start a Monday morning by opening your inbox.
14:11Right? Now if you wanna learn how to do this for yourself, I am dropping the course in the founders community like I said earlier. The link is here as well as in the description down below.
14:21And also, if you wanna learn how to create your own skills, that video is coming next, so make sure you are subscribed. You can check over there. Alright.
14:27If you made it all the way to here, thank you so so much for watching. Like this video. If you did, make sure you're subscribed and share this with anyone in your circle of friends or family or coworkers who you think needs to be able to leverage AI, specifically Claude, to be able to manage their week and not the the week and their schedule.
14:44Manage them. Until next time, I suggest you go ahead and watch this video over here, and I'll see you soon. Bye.
The Hook
The bait, then the rug-pull.
The bet is made in the first ten seconds: there are two kinds of founders, and by the time you finish watching, you will never start a Monday by opening your inbox again. What follows is a live walkthrough of the 1-hour Sunday ritual -- command center, six workflows, six deliverables -- that makes the promise plausible.
Named ideas worth stealing.
01:15acronym
RPM -- Result, Purpose, Massive Action
- Result -- the specific outcome you are committed to by end of week
- Purpose -- why it matters to the business or yourself
- Massive Action -- only the moves large enough to produce the result
Tony Robbins planning model replacing task lists with outcome-first thinking. Tasks that do not serve a committed result are cut before the week starts.
Steal forAny weekly review or Sunday planning session; reframes the ritual from task capture to outcome commitment
08:52model
Three Workflow Types
- Scheduled -- time-based, predictable, recurring
- Event-driven -- fires on a system trigger
- Manual -- judgment-required, situational
Classification system for deciding which AI workflows to automate vs. keep human. Automate anything predictable; reserve human decision-making for anything situational.
Steal forMapping any automation portfolio -- identifies which processes to fully automate vs. which need human decision gates
How they asked for the click.
VERBAL ASK
14:15product
“Now if you wanna learn how to do this for yourself, I am dropping the course in the founders community like I said earlier. The link is here as well as in the description down below.”
Soft ask after the thesis reframe. Community and course bundled into same CTA; subscribe ask follows immediately.
MENTIONED ON CAMERA
FROM THE DESCRIPTION
PRIMARY CTAWhere the creator wants you to go next.
OTHER LINKSAlso linked in the description.
- 👉 Build or grow an AI powered business ↗
- ⭐ Google AI Prompt Essentials Course ↗
- ⭐ Google Data Analytics Certificate ↗
- ⭐ Google Digital Marketing Certificate ↗
- ⭐ Google IT Support Certificate ↗
- ⭐ Google Project Management Certificate ↗
- ⭐ Google UX Design Certificate ↗
- ⭐ Google Ads for Beginners ↗
- ⭐ Introduction to Generative AI ↗
- ⭐ Google Cybersecurity Certificate ↗
- ⭐ Google Advanced Data Analytics Certificate ↗
- ⭐ Google IT Automation with Python Certificate ↗
- ⭐ Google Business Intelligence Certificate ↗
- ⭐ Google Crash Course on Python ↗
Visual structure at a glance.
