WEBVTT 00:00:00.000 --> 00:00:01.800 You know, I was just thinking about how much 00:00:01.800 --> 00:00:04.860 the idea of free has changed, especially with 00:00:04.860 --> 00:00:08.220 software for like a decade. Free just meant a 00:00:08.220 --> 00:00:11.359 demo that's useless until you pay. Oh yeah. The 00:00:11.359 --> 00:00:13.220 freemium trap. It was a trap. Exactly. You get 00:00:13.220 --> 00:00:16.320 one tiny feature and then boom, a paywall. Right. 00:00:16.500 --> 00:00:18.679 But if you look at where we are now, what is 00:00:18.679 --> 00:00:22.539 it? January 23rd, 2026, that whole playbook is 00:00:22.539 --> 00:00:25.519 kind of dead. The game has totally changed. Companies 00:00:25.519 --> 00:00:27.679 aren't just competing on price anymore. They're 00:00:27.679 --> 00:00:30.379 terrified of losing adoption. So they're competing 00:00:30.379 --> 00:00:32.960 for your habit. Exactly. So they have to give 00:00:32.960 --> 00:00:34.859 away the whole engine, really, just to get you 00:00:34.859 --> 00:00:38.340 in the door. So the free tools in 2026, they 00:00:38.340 --> 00:00:40.520 aren't demos. No, they're full blown products, 00:00:40.619 --> 00:00:43.280 high leverage products. Which brings us to today. 00:00:43.399 --> 00:00:46.200 We are going to unpack a guide to the 15 best 00:00:46.200 --> 00:00:49.060 free AI tools out there right now. But I want 00:00:49.060 --> 00:00:51.219 to be clear. My goal here isn't to just give 00:00:51.219 --> 00:00:53.259 you a list of bookmarks you'll never open again. 00:00:53.520 --> 00:00:55.520 I really want to figure out how these things 00:00:55.520 --> 00:00:58.060 can actually change the way we work. Right. It's 00:00:58.060 --> 00:01:00.380 about moving from just you know, collecting shiny 00:01:00.380 --> 00:01:03.259 objects to actually building leverage. So we're 00:01:03.259 --> 00:01:05.980 going to look at automation, creative assistants, 00:01:06.280 --> 00:01:08.200 and what I like to call research brains. And 00:01:08.200 --> 00:01:10.260 then we'll wrap up with a framework for how you 00:01:10.260 --> 00:01:12.260 can pick the right ones without just getting 00:01:12.260 --> 00:01:14.340 overwhelmed. OK, let's start with the giant in 00:01:14.340 --> 00:01:17.739 the room, Google. For years, Google Workspace 00:01:17.739 --> 00:01:21.560 was just there. It's a utility. But now they've 00:01:21.560 --> 00:01:23.700 rolled out this thing called Google Workspace 00:01:23.700 --> 00:01:26.299 Studio. This is a big deal. Because it takes 00:01:26.299 --> 00:01:28.219 the automation that we used to need other tools 00:01:28.219 --> 00:01:32.120 for, like Zapier or Makely, and it bakes it right 00:01:32.120 --> 00:01:34.760 into the ecosystem using Gemini. OK, give me 00:01:34.760 --> 00:01:36.659 a real example. Because when I hear automation, 00:01:36.900 --> 00:01:38.900 I still imagine spending three hours configuring 00:01:38.900 --> 00:01:41.879 something to save me, like three seconds. Fair 00:01:41.879 --> 00:01:44.319 enough. OK, so picture this. You get a really 00:01:44.319 --> 00:01:46.280 chaotic email from a client. Happens all the 00:01:46.280 --> 00:01:48.340 time. Right. It's got three different attachments, 00:01:48.780 --> 00:01:51.939 a messy list of demands. In the old world, you're 00:01:51.939 --> 00:01:54.310 copy -pasting that into Slack. You're downloading 00:01:54.310 --> 00:01:57.129 files to drive, opening a sheet. The add -in 00:01:57.129 --> 00:02:00.530 tax. The busy work. That's it. With Workspace 00:02:00.530 --> 00:02:03.170 Studio, you just use a starter, which is basically 00:02:03.170 --> 00:02:05.450 a trigger. You tell it in plain English. When 00:02:05.450 --> 00:02:07.730 I get an email from this client, extract the 00:02:07.730 --> 00:02:10.669 due date to this sheet, save the PDFs to this 00:02:10.669 --> 00:02:13.610 drive folder, and draft me a confirmation reply. 00:02:13.750 --> 00:02:16.150 And it just does it natively? Natively. No setup. 00:02:16.150 --> 00:02:19.830 That is compelling. But I have to ask, does staying 00:02:19.830 --> 00:02:24.699 entirely inside Google's ecosystem Doesn't that 00:02:24.699 --> 00:02:27.180 limit you? Aren't we just locking ourselves deeper 00:02:27.180 --> 00:02:29.379 into their world? Oh, you absolutely are. That's 00:02:29.379 --> 00:02:31.539 the trade -off. OK. It trades that flexibility 00:02:31.539 --> 00:02:35.199 for speed and trust. It just works. Got it. OK. 00:02:35.300 --> 00:02:37.860 Let's pivot to the creative side. There's a tool 00:02:37.860 --> 00:02:40.360 here called Pamelli. It comes out of Google Labs 00:02:40.360 --> 00:02:43.300 focused on social campaigns. Yeah, this one solves 00:02:43.300 --> 00:02:46.479 the disjointed asset problem. What's that? You 00:02:46.479 --> 00:02:48.919 ask an AI for an image, you get one style. You 00:02:48.919 --> 00:02:50.460 ask it for a tweet, you get a completely different 00:02:50.460 --> 00:02:54.520 tone. Pamelli actually scans. your website URL 00:02:54.520 --> 00:02:57.280 that pulls your brand colors, your fonts, your 00:02:57.280 --> 00:02:59.300 voice. So it builds a style guide for itself 00:02:59.300 --> 00:03:01.620 before it even starts creating. Exactly. And 00:03:01.620 --> 00:03:04.180 then it generates a full campaign. Not just here's 00:03:04.180 --> 00:03:07.439 a post, but here's the launch strategy, the visuals, 00:03:07.860 --> 00:03:11.080 the copy, all aligned. My skepticism here is 00:03:11.080 --> 00:03:13.719 always around the quality. We've all seen AR 00:03:13.719 --> 00:03:17.189 art that just looks like. generic mush so is 00:03:17.189 --> 00:03:19.930 the value here the quality of the art or is it 00:03:19.930 --> 00:03:22.349 just the consistency of the brand it's about 00:03:22.349 --> 00:03:24.909 consistency it's about generating campaigns not 00:03:24.909 --> 00:03:27.770 just single posts for a founder with no design 00:03:27.770 --> 00:03:30.219 team This is a lifesaver. It's the good enough 00:03:30.219 --> 00:03:33.439 revolution. Speaking of getting things done, 00:03:33.919 --> 00:03:37.020 writing. I have to admit, even now in 2026, I 00:03:37.020 --> 00:03:39.840 still get blank page syndrome. I just stare at 00:03:39.840 --> 00:03:42.199 that blinking cursor and the friction of just 00:03:42.199 --> 00:03:45.199 typing. It slows down my actual thinking. That 00:03:45.199 --> 00:03:47.360 is precisely what Whisper Flow is built to solve. 00:03:47.539 --> 00:03:49.159 It's a voice to text tool, but it's not like 00:03:49.159 --> 00:03:51.620 the old ones where you had to speak. And then 00:03:51.620 --> 00:03:53.939 hope it gets the punctuation right. Whisper flow 00:03:53.939 --> 00:03:56.099 is aggressive. It cleans up your filler words 00:03:56.099 --> 00:03:58.460 in real time. You can stumble. You can rephrase 00:03:58.460 --> 00:04:01.500 a sentence, say, a dozen times. And on the screen, 00:04:01.539 --> 00:04:03.960 it just appears as clean prose. See, that's where 00:04:03.960 --> 00:04:07.400 I get torn. Because part of me thinks the struggle 00:04:07.400 --> 00:04:12.159 of typing, pausing to find the right word, that's 00:04:12.159 --> 00:04:14.860 where the good thinking happens. So if we remove 00:04:14.860 --> 00:04:17.439 the friction of typing, does that actually change 00:04:17.439 --> 00:04:20.850 what we say? I think it does. But for the better. 00:04:21.069 --> 00:04:23.370 It captures the speed of thought directly. That's 00:04:23.370 --> 00:04:25.230 interesting. So it separates the generating from 00:04:25.230 --> 00:04:27.990 the editing. Exactly. Okay. I can see that. Let's 00:04:27.990 --> 00:04:30.610 move to research. We've all drowned in PDFs, 00:04:30.629 --> 00:04:33.850 right? You download 20 papers, open 40 tabs, 00:04:33.889 --> 00:04:36.610 and then you just stare. The collector's fallacy. 00:04:37.170 --> 00:04:40.310 You feel productive, but you're not. Yes. So 00:04:40.310 --> 00:04:43.129 notebook LM is pitched as an AI research brain. 00:04:43.589 --> 00:04:45.730 How is this different from just uploading a PDF 00:04:45.730 --> 00:04:48.449 to, you know, any other chatbot? The key word 00:04:48.449 --> 00:04:50.949 is grounding. When you put your sources, your 00:04:50.949 --> 00:04:53.550 PDFs, your notes, your docs into Notebook LM, 00:04:53.769 --> 00:04:56.329 it creates a closed system. You aren't asking 00:04:56.329 --> 00:04:58.610 the entire internet. You're asking your personal 00:04:58.610 --> 00:05:00.790 library. So if I ask it a question, it won't 00:05:00.790 --> 00:05:02.990 just make something up it saw on Reddit. No, 00:05:02.990 --> 00:05:05.389 it stays grounded strictly in the provided sources. 00:05:05.470 --> 00:05:08.649 It'll give you citations from your own documents. 00:05:09.009 --> 00:05:12.350 So it transforms scattered files into a single 00:05:12.350 --> 00:05:15.290 queryable intelligence. That's a perfect way 00:05:15.290 --> 00:05:18.089 to put it. It turns isolated documents into a 00:05:18.089 --> 00:05:20.160 connected brain. That feels like a fundamental 00:05:20.160 --> 00:05:26.540 shift from just searching to synthesizing. OK, 00:05:26.560 --> 00:05:28.459 let's talk meetings. There's a tool here called 00:05:28.459 --> 00:05:31.379 Granola. Great name. It is. But we have a million 00:05:31.379 --> 00:05:33.879 AI meeting bots. What makes Granola different? 00:05:34.139 --> 00:05:36.160 Well, most bots just give you a transcript, maybe 00:05:36.160 --> 00:05:39.399 a summary. Granola focuses on structure. It uses 00:05:39.399 --> 00:05:41.879 these things called recipes. So if you're in 00:05:41.879 --> 00:05:44.759 a client check -in, you pick that recipe. It 00:05:44.759 --> 00:05:47.220 knows to listen for things like, what did we 00:05:47.220 --> 00:05:49.279 promise? What's the deadline? Who's responsible? 00:05:49.500 --> 00:05:51.800 So it filters the whole conversation based on 00:05:51.800 --> 00:05:54.040 the purpose of the meeting. Precisely. And then 00:05:54.040 --> 00:05:55.980 it can draft the follow -up email automatically. 00:05:56.100 --> 00:05:58.360 So is the goal here to record the meeting or 00:05:58.360 --> 00:06:01.019 is it to trigger the next action? Oh, it's purely 00:06:01.019 --> 00:06:02.779 about triggering the next action, effectively. 00:06:03.079 --> 00:06:05.480 I like that. Records are useless. Actions matter. 00:06:05.600 --> 00:06:08.500 Right. OK, this next one. Hits close to home. 00:06:09.000 --> 00:06:11.639 Task paralysis. When the to -do list is so big, 00:06:11.699 --> 00:06:15.720 you just nap. Goblin tools. This is a cult favorite, 00:06:16.019 --> 00:06:19.019 and for good reason. It's designed for neurodivergent 00:06:19.019 --> 00:06:22.120 users, but honestly, it's for everyone. You type 00:06:22.120 --> 00:06:25.480 in a huge, scary task like, plan the company 00:06:25.480 --> 00:06:28.120 offsite. Which is terrifying. It is. You hit 00:06:28.120 --> 00:06:30.519 one button, and it breaks it down into research 00:06:30.519 --> 00:06:33.339 venues, set budget, email the team. And you can 00:06:33.339 --> 00:06:35.699 keep clicking to break those down into even smaller, 00:06:35.920 --> 00:06:38.759 less scary steps. Why is breaking a task down 00:06:38.759 --> 00:06:41.139 so often harder than actually doing the task 00:06:41.139 --> 00:06:44.439 itself? Because we get stuck on the how. This 00:06:44.439 --> 00:06:47.060 just solves that. It takes the burden of executive 00:06:47.060 --> 00:06:49.540 function off your plate. It outsources executive 00:06:49.540 --> 00:06:52.779 function. That's a really kind use of AI. Okay, 00:06:53.000 --> 00:06:54.680 sometimes text isn't the answer. We've got a 00:06:54.680 --> 00:06:58.139 few visual tools here. First, mymap .ai. This 00:06:58.139 --> 00:06:59.759 one's for your logic brain. You can just dump 00:06:59.759 --> 00:07:02.120 a paragraph of text, maybe a complex process, 00:07:02.379 --> 00:07:04.540 and it turns it into a flow chart or a mind map. 00:07:04.720 --> 00:07:06.439 And the goal here isn't to make it look pretty, 00:07:06.519 --> 00:07:09.160 right? No, it's all functional. It's for spotting 00:07:09.160 --> 00:07:11.339 the holes in your logic. When you see a process 00:07:11.339 --> 00:07:13.860 visually, you instantly see where the dead ends 00:07:13.860 --> 00:07:17.300 are. So does seeing an idea visually expose flaws 00:07:17.300 --> 00:07:20.319 that text hides? Definitely. It instantly highlights 00:07:20.319 --> 00:07:23.160 gaps in your logic. OK, so my map is for logic. 00:07:23.579 --> 00:07:26.980 What about explaining things? This list mentions 00:07:26.980 --> 00:07:30.949 napkin AI. Napkin is like a translator. It takes 00:07:30.949 --> 00:07:34.069 dense text bullet points, paragraphs, and turns 00:07:34.069 --> 00:07:36.649 it into those clean sort of hand -drawn style 00:07:36.649 --> 00:07:38.930 diagrams you see in presentations. So I don't 00:07:38.930 --> 00:07:41.569 need design skills to stop using giant walls 00:07:41.569 --> 00:07:44.370 of text in my slides. Exactly. It just lowers 00:07:44.370 --> 00:07:47.170 the barrier to communicating visually. So is 00:07:47.170 --> 00:07:50.009 this basically a translator between, like, writers 00:07:50.009 --> 00:07:52.529 and visual learners? Precisely. It makes dense 00:07:52.529 --> 00:07:55.069 text instantly scannable. Okay, and then there's 00:07:55.069 --> 00:07:59.740 senal draw AI. This one seems messier. By design. 00:07:59.899 --> 00:08:01.639 Yeah, it's an infinite canvas. It's for that 00:08:01.639 --> 00:08:03.879 really early, messy thinking. You can scribble 00:08:03.879 --> 00:08:06.180 a stick figure in a box, and the AI will clean 00:08:06.180 --> 00:08:08.540 it up into a diagram, or you can draw a rough 00:08:08.540 --> 00:08:10.600 wire frame for a website, and it'll actually 00:08:10.600 --> 00:08:12.500 write the code for it. It really feels like this 00:08:12.500 --> 00:08:14.720 is for the napkin sketch phase of an idea. Yeah, 00:08:14.740 --> 00:08:17.199 that's exactly it. It's very low stakes. So does 00:08:17.199 --> 00:08:20.079 a messy interface actually encourage freer thinking 00:08:20.079 --> 00:08:22.779 than a really rigid one? I think so. Yes, it 00:08:22.779 --> 00:08:24.939 lowers the stakes for just starting an idea. 00:08:25.310 --> 00:08:27.250 Okay, I want to jump to something much more technical 00:08:27.250 --> 00:08:30.069 now. N8n. This is listed as the heavy hitter. 00:08:30.269 --> 00:08:33.070 Yeah, N8n's a beast. It's an open source automation 00:08:33.070 --> 00:08:35.909 platform. So think of it like Zapier, but you 00:08:35.909 --> 00:08:38.450 host it yourself. You host it yourself? That 00:08:38.450 --> 00:08:40.230 sounds like a lot of work. Why would I do that 00:08:40.230 --> 00:08:42.350 instead of just paying for a cloud tool? Two 00:08:42.350 --> 00:08:45.539 reasons. Privacy and power. If you're dealing 00:08:45.539 --> 00:08:47.500 with sensitive data, maybe you don't want to 00:08:47.500 --> 00:08:49.720 send it through some third -party server. With 00:08:49.720 --> 00:08:53.159 N8n, it stays on your machine. And because it's 00:08:53.159 --> 00:08:56.120 open source, you can build these incredibly complex 00:08:56.120 --> 00:08:59.139 multi -step AI agents that would cost you a fortune 00:08:59.139 --> 00:09:02.559 on a paid plan. So is the steep learning curve 00:09:02.559 --> 00:09:04.740 just the price you pay for having total control? 00:09:04.940 --> 00:09:08.220 Yes. You trade ease of use for limitless power. 00:09:08.779 --> 00:09:11.169 For the right person, that's an easy trade. Let's 00:09:11.169 --> 00:09:12.950 talk models. We have this problem now where we 00:09:12.950 --> 00:09:15.870 don't know which AI is smartest this week. Chathub 00:09:15.870 --> 00:09:17.809 seems to deal with that. It does. It's a browser 00:09:17.809 --> 00:09:20.370 extension, and it lets you run the same prompt 00:09:20.370 --> 00:09:24.409 through GPT -4 and Claude and Llama all at the 00:09:24.409 --> 00:09:26.269 same time, side by side. That seems like more 00:09:26.269 --> 00:09:28.970 than just a novelty. Oh, it's a huge reality 00:09:28.970 --> 00:09:31.529 check. You start to see that these models have 00:09:31.529 --> 00:09:35.049 distinct personalities. One might be really concise. 00:09:35.250 --> 00:09:36.950 Another might be a bit moralizing. Another might 00:09:36.950 --> 00:09:39.370 just make things up. So does comparing models 00:09:39.370 --> 00:09:41.809 reveal that AI has distinct personalities? It 00:09:41.809 --> 00:09:44.450 reveals their unique reasoning styles and biases 00:09:44.450 --> 00:09:47.299 instantly. Yeah. And if you want to build with 00:09:47.299 --> 00:09:50.120 these models, the list has OpenRouter. OpenRouter 00:09:50.120 --> 00:09:53.460 is basically a unified plug. So instead of managing 00:09:53.460 --> 00:09:56.539 10 different subscriptions and API keys, you 00:09:56.539 --> 00:09:59.220 just use OpenRouter to access everything. It's 00:09:59.220 --> 00:10:03.340 the ultimate try before you buy for anyone building 00:10:03.340 --> 00:10:06.600 with AI. So it's the gateway to testing everything 00:10:06.600 --> 00:10:08.759 without commitment. Exactly. OK, we're getting 00:10:08.759 --> 00:10:10.740 near the end, but we have to talk about how we 00:10:10.740 --> 00:10:13.440 consume information. Podcasts, obviously. They're 00:10:13.440 --> 00:10:16.320 great, but they're linear. They take time. Snipt 00:10:16.320 --> 00:10:19.159 is trying to change that. Snipt solves what I 00:10:19.159 --> 00:10:21.559 call drive time amnesia. You know, when you're 00:10:21.559 --> 00:10:23.259 driving, you hear some life changing insight 00:10:23.259 --> 00:10:25.620 on a podcast. And by the time you park, it's 00:10:25.620 --> 00:10:29.029 just gone every single day. Every day. Snipt 00:10:29.029 --> 00:10:31.610 uses AI to transcribe and summarize the show, 00:10:31.850 --> 00:10:34.389 but the killer feature is the SNIP. You just 00:10:34.389 --> 00:10:36.470 tap your headphones, and it saves the last minute 00:10:36.470 --> 00:10:38.809 of audio, transcribes it, and syncs it to your 00:10:38.809 --> 00:10:40.889 notes app. So you're turning passive listening 00:10:40.889 --> 00:10:43.970 into, like, active library building. It just 00:10:43.970 --> 00:10:46.669 respects your time. But are we listening to enjoy 00:10:46.669 --> 00:10:48.649 the journey, or are we just trying to extract 00:10:48.649 --> 00:10:51.129 data? I think SNIP lets you do both. You can 00:10:51.129 --> 00:10:53.230 enjoy the flow, but capture the data when you 00:10:53.230 --> 00:10:57.600 need to. And finally, search. Perplexity AI. 00:10:58.519 --> 00:11:00.120 I feel like this one has had the biggest impact 00:11:00.120 --> 00:11:02.580 on my own workflow this past year. It's the death 00:11:02.580 --> 00:11:05.700 of the 10 blue links. We used to Google something, 00:11:05.799 --> 00:11:08.240 click five different links, dodge all the ads, 00:11:08.399 --> 00:11:10.220 and try to piece together and answer ourselves. 00:11:10.840 --> 00:11:14.340 Perplexity just answers. Whoa. But the danger 00:11:14.340 --> 00:11:16.779 there is trust, right? If it just gives me an 00:11:16.779 --> 00:11:18.559 answer, how do I know it's not just making it 00:11:18.559 --> 00:11:20.639 up? And that's why the citations are the whole 00:11:20.639 --> 00:11:23.399 product. It shows you its work. It footnotes 00:11:23.399 --> 00:11:27.259 every single claim. In 2026, trust is the scarcest 00:11:27.259 --> 00:11:30.019 resource there is online. So is the citation 00:11:30.019 --> 00:11:32.600 the most important feature for trust in 2026? 00:11:33.159 --> 00:11:36.139 Without citations, AI answers are just confident 00:11:36.139 --> 00:11:38.799 guesses. Confident guesses. That is a terrifying 00:11:38.799 --> 00:11:41.879 thought. We also, we skipped over Headline Studio 00:11:41.879 --> 00:11:43.799 real quick. That's just a simple feedback loop 00:11:43.799 --> 00:11:45.860 for titles, right? Yeah, simple utility just 00:11:45.860 --> 00:11:47.340 scores your headlines so you're not publishing 00:11:47.340 --> 00:11:50.279 into a void. Simple but effective. Okay, so we 00:11:50.279 --> 00:11:52.799 just walked through 15 different tools, and I 00:11:52.799 --> 00:11:55.519 can almost feel the anxiety coming from the listener, 00:11:55.580 --> 00:11:57.700 like, do I need to download all of these? Get 00:11:57.700 --> 00:11:59.700 a new account for everything. Please, please 00:11:59.700 --> 00:12:02.220 do not do that. That is the tool overload trap. 00:12:02.559 --> 00:12:04.980 The more tools you have, the more time you spend 00:12:04.980 --> 00:12:07.100 maintaining them. So what's the framework? How 00:12:07.100 --> 00:12:09.200 do we actually filter this down? I like to think 00:12:09.200 --> 00:12:12.919 in four buckets. You have creation, thinking, 00:12:13.519 --> 00:12:16.980 automation, and learning. And you are allowed 00:12:16.980 --> 00:12:21.190 one primary tool for each bucket. Just one. Just 00:12:21.190 --> 00:12:24.029 one. If you have TotalDraw and MyMap and Napkin 00:12:24.029 --> 00:12:26.710 AI, you're not working. You're just playing with 00:12:26.710 --> 00:12:29.169 toys. Pick one that actually fits how your brain 00:12:29.169 --> 00:12:31.190 works. And for automation. You choose your level 00:12:31.190 --> 00:12:34.070 of pain. If you want something easy, go with 00:12:34.070 --> 00:12:36.610 Google Workspace Studio. If you want total power 00:12:36.610 --> 00:12:40.970 and privacy, go with N8n. But don't try to use 00:12:40.970 --> 00:12:43.669 both. So is the discipline of just saying no 00:12:43.669 --> 00:12:46.409 to new tools, is that the real productivity hack 00:12:46.409 --> 00:12:48.730 here? Eliminating tool clutter is the ultimate 00:12:48.730 --> 00:12:51.120 efficiency upgrade. It really is. That feels 00:12:51.120 --> 00:12:54.360 like the big idea. The critical insight for 2026 00:12:54.360 --> 00:12:56.899 isn't just that these tools are free. It's that 00:12:56.899 --> 00:12:59.259 they only matter if they remove friction. Right. 00:12:59.480 --> 00:13:01.879 Leverage is the goal. If you're spending your 00:13:01.879 --> 00:13:05.179 time managing your AI tools, you've already lost. 00:13:05.759 --> 00:13:08.440 The AI should be managing the work for you. So 00:13:08.440 --> 00:13:10.200 here's the challenge for you listening right 00:13:10.200 --> 00:13:13.220 now. We covered a lot of ground. Pick one, just 00:13:13.220 --> 00:13:16.000 one tool from this list, and then tie it to one 00:13:16.000 --> 00:13:18.379 specific recurring task. that you absolutely 00:13:18.379 --> 00:13:20.500 hate doing. Maybe it's that blank page. Maybe 00:13:20.500 --> 00:13:23.039 it's the meeting follow -up emails. And just 00:13:23.039 --> 00:13:25.440 master that one workflow. Yeah. Use the tool 00:13:25.440 --> 00:13:27.399 until it disappears, until it becomes second 00:13:27.399 --> 00:13:30.120 nature. Then and only then, maybe consider adding 00:13:30.120 --> 00:13:32.000 another one. I think that's the healthiest way 00:13:32.000 --> 00:13:34.659 to approach this. Because if the tools are free 00:13:34.659 --> 00:13:37.159 and the capabilities are basically infinite, 00:13:37.840 --> 00:13:40.879 then the only limit left is your ability to clearly 00:13:40.879 --> 00:13:43.159 define the problem you want to solve. That's 00:13:43.159 --> 00:13:45.059 the new scale. Thanks for diving in with us. 00:13:45.100 --> 00:13:46.000 We'll see you in the next one.