Transcription
There 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. The 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. I 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. And I'm going to show you the whole thing today so you can run your week and not let the week run you. I'm going to 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 15 minutes or so, you will never start a Monday by opening your inbox again. I 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. Are 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. The 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. It 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 result that you're committed to by the end of the week. And then you ask, "Why does that make any difference to you? What 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. When 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 in of something that you already decided was worth it.
Let 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. It'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. The results 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. Everything 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. The 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. It took quite a while to build all of this, but I want to show you everything, okay?
So, this week we are actually launching the Social Brand Accelerator. That 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, it's not a recurring task. I hope that makes sense, right? So, the project I open has everything that I need already loaded. The program positioning, the audience profile, my pricing tiers, prior winning sales decks as reference, and then three skills will fire when I run this. One that handles the offer architecture, one that holds my voice, and one that knows our presentation style and brand elements. And then Cloud 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 Cloud skills that I use, I'm going to 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.
So, what I do next is I type one sentence. I asked 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. The 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 connector. And 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 10 minutes. Honestly, I would send this to a business owner tonight. That presentation, like I said, was created in Gamma using the Claude 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. Now, 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 describe 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. You 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.
Now, let me give you a quick example of what it looks like to finalize a deck once 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. Let's say you want the slide to feel more editorial, and you want two columns instead of one. It's easy to do that. You 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 it. 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, you can change your heading, you can restructure a slide, and it feels less like editing slides and more like editing a single document, honestly. With 5 minutes of polish, you've got something that you would be really proud to send. Now, if you want to try Gamma, the link is going to 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. We 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. Now, 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, it'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. It 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. I 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. The 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. So, 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? Once that is done, you get all of the slides done before you end up sitting down or I ended up sitting down this [music] Sunday. I already have a proposal that reads like I spent at least half a day on it, and Gamma's case study template carried the whole thing, in my opinion.
Now, 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. Some run on schedule, like my community call every 2 weeks. I'm going to come back to that. Or any other scheduled task. In that case, Claude pulls the data, drafts the deck, and it's predictable and recurring. But, we also have some that run on events, like a recording dropping in Fathom after a Calendly meeting ends. 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 I'm going to 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 the predictable and the event-driven, so I can spend my brainpower on anything that's situational. And that's the design principle behind everything. It looks simple. It took a lot to build all of this, by the way.
The next thing on the week, we're opening a 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. This one has to be manual because it's a one-time deployment, not something that we're going to 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 built today, not what was built 6 months ago and in the meantime has drifted. And then, all I need to do is give the command. I need to say, "Build the client onboarding SOP training deck for the Skill Studios team." That's it. And 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, right? 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. So, if you're new around here, every 2 weeks we have what we call a hive hall 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 in the community over the last 2 weeks. [music] This is the scheduled automation example, okay? This is recurring, it's predictable, there is no judgment call required to get it started. But obviously, I need to make the judgment call in terms of what goes in there, okay? So, every other Friday morning, a scheduled task ends up firing. So, Claude pulls the top engagement posts from School, it 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. But my role is to review, to read what Claude pulled, to tweak the agenda based on what I actually want to 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&A slot, all in one cohesive deck. And only a few minutes on Sunday it takes to review and I'm done.
Now, workflow number five, okay? So, then we have the content for our Founders Hive, that 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. This one has to be manual, right? I trigger it from the courses editorial calendar in the command center when the next module is due. Now, the project has the full course curriculum loaded, the audience profile for our Founders community, prior modules is referenced, as well as our brand kit. And all I need to do is give the command to build the module deck for Claude 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. That consistency is honestly what makes a course actually feel like a course and not a folder of random slides. >> [music] >> 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're launching the Scale Studios location here in Switzerland in a few weeks. And 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 want in this location to live in. And that means that workflow six is not going to be a slide deck, it's going to be a mood board. Again, a manual one because it's a launch decision. The 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 commands to build the Scale Studios launch mood board in an editorial editorial, architectural, modern Swiss style with our brand palette as the anchor. And look at that. That is not a slide. That is a fully visual editorial concept with typography, color blocks, imagery, white space, brand cues. It'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, I 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.
So, 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 I ended up sitting down, a team training, a community call deck, a course module, and a launch mood board. I mean, that's great. But here's what you actually just watched. It was not about the decks. It was actually more so about what becomes possible when a founder no longer treats prep work like 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 1 hour, you don't ration what you ship. You 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. The 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, right?
Now, if you want to 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. And also, if you want to learn how to create your own skills, that video is coming next. So, make sure you are subscribed. You can check over there. All right, if 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 co-workers who you think needs to be able to leverage AI, specifically Claude, to be able to manage their week and not that the week and their schedule manage them. Until next time, I suggest you go ahead and watch this video over here and I'll see you soon. Bye.