WEBVTT 00:00:00.000 --> 00:00:04.360 Have you ever felt just utterly drowned, like 00:00:04.360 --> 00:00:08.720 amidst this flood of AI tools? Oh, yeah. You're 00:00:08.720 --> 00:00:11.539 probably paying for, I don't know, 10 different 00:00:11.539 --> 00:00:14.380 subscriptions, but maybe actively using half. 00:00:14.439 --> 00:00:18.320 Right. If that. And every single week, it feels 00:00:18.320 --> 00:00:21.820 like there's some new game -changing tool. Everyone 00:00:21.820 --> 00:00:24.500 insists you must try it. The pressure's real. 00:00:24.760 --> 00:00:26.839 And it leads you down one of two paths, right? 00:00:27.260 --> 00:00:30.000 You either become this like AI tool hoarder. 00:00:30.120 --> 00:00:32.740 Chuckle softly, yeah. Gotta catch them all. Or 00:00:32.740 --> 00:00:34.600 you just boycott everything. Just say, nope, 00:00:34.820 --> 00:00:37.320 too much. And both ways, honestly, they cost 00:00:37.320 --> 00:00:40.979 you time, money, and you miss out on real opportunities. 00:00:41.280 --> 00:00:43.640 Exactly. So welcome to the deep dive. Today we're 00:00:43.640 --> 00:00:45.539 going to cut through that noise, navigate what 00:00:45.539 --> 00:00:48.259 we're calling the AI storm. Okay. Our mission. 00:00:48.380 --> 00:00:50.939 It's to give you a solid decision framework, 00:00:51.420 --> 00:00:54.200 a proven one. Good. We need that. Yeah. So you 00:00:54.200 --> 00:00:56.399 can filter out the hype, find tools that actually 00:00:56.399 --> 00:00:58.979 deliver value, and know when to test, when it's 00:00:58.979 --> 00:01:00.700 worth buying, or maybe even when you should build 00:01:00.700 --> 00:01:03.039 something yourself. Build it yourself. We're 00:01:03.039 --> 00:01:05.500 going to walk through a six -phase journey from 00:01:05.500 --> 00:01:08.560 spotting genuine innovation all the way to figuring 00:01:08.560 --> 00:01:10.280 out if a tool's actually gonna stick around. 00:01:10.420 --> 00:01:12.379 Let's jump in. Okay, let's unpack this first 00:01:12.379 --> 00:01:18.019 bit. The AI tool ecosystem. It's genuinely overwhelming 00:01:18.019 --> 00:01:20.980 right now. It really is. Thousands of apps. Thousands. 00:01:21.180 --> 00:01:24.079 Covering every category you can imagine. Design, 00:01:24.900 --> 00:01:27.799 AI browsers, coding assistants. Everything. And 00:01:27.799 --> 00:01:30.459 then there's this other layer, this AI tribalism 00:01:30.459 --> 00:01:33.420 thing. Oh, yeah. The kids. People picking sides. 00:01:34.269 --> 00:01:37.730 fiercely defending chat GPT over Claude or this 00:01:37.730 --> 00:01:39.450 code editor versus that one. They get pretty 00:01:39.450 --> 00:01:42.329 intense. It creates these like unnecessary ideological 00:01:42.329 --> 00:01:45.709 wars that honestly help nobody. And when we say 00:01:45.709 --> 00:01:48.849 AI tribalism, we just mean that really strong, 00:01:49.269 --> 00:01:52.709 sometimes kind of irrational loyalty to one specific 00:01:52.709 --> 00:01:56.329 model or tool. It just divides people unhelpfully. 00:01:56.590 --> 00:01:58.469 And what's fascinating, I think, is that the 00:01:58.469 --> 00:02:00.629 real problem isn't which side you pick in those 00:02:00.629 --> 00:02:03.209 debates. Right. It's the lack of a good mental 00:02:03.209 --> 00:02:05.349 framework. A way to assess if you actually need 00:02:05.349 --> 00:02:07.189 that tool in your life, in your work. Without 00:02:07.189 --> 00:02:09.550 that framework. You just get swayed, right, by 00:02:09.550 --> 00:02:11.729 the big headlines, the articles thrown around, 00:02:12.110 --> 00:02:14.469 breakthrough and game changers, like confetti. 00:02:14.550 --> 00:02:18.319 Happens all the time. And you end up... confused, 00:02:19.000 --> 00:02:21.259 probably overwhelmed, and definitely poor from 00:02:21.259 --> 00:02:24.039 all those subscriptions. So this framework, it's 00:02:24.039 --> 00:02:26.599 like your compass. It moves you from just reacting 00:02:26.599 --> 00:02:29.759 to whatever's hot this week to being an active 00:02:29.759 --> 00:02:32.860 strategic chooser, picking what actually works 00:02:32.860 --> 00:02:34.819 for you. Okay, so when we're trying to cut through 00:02:34.819 --> 00:02:36.879 all that noise, that feeling of being overwhelmed, 00:02:37.560 --> 00:02:40.759 why is having this framework really so crucial 00:02:40.759 --> 00:02:43.509 for us? It helps you choose strategically. You 00:02:43.509 --> 00:02:46.530 avoid the hype, the overload, and yeah, the unnecessary 00:02:46.530 --> 00:02:49.889 costs. Got it. Strategic choice. Okay, so phase 00:02:49.889 --> 00:02:51.669 one. This is where it gets really interesting, 00:02:51.689 --> 00:02:53.449 I think. Yeah, the initial filter. The initial 00:02:53.449 --> 00:02:56.330 filter. Before you even spend like five minutes 00:02:56.330 --> 00:02:58.289 signing up for a free trial, the question is, 00:02:58.889 --> 00:03:02.669 does this tool introduce any form of step change? 00:03:02.840 --> 00:03:05.259 for the specific work I'm trying to do. Key phrase 00:03:05.259 --> 00:03:07.379 there, step change. And we're not talking about 00:03:07.379 --> 00:03:10.259 just a tiny five or 10 % improvement. It needs 00:03:10.259 --> 00:03:13.319 to be a real qualitative leap forward. Exactly, 00:03:13.479 --> 00:03:16.060 a fundamental shift. And we've kind of broken 00:03:16.060 --> 00:03:18.439 this down into four types of step changes to 00:03:18.439 --> 00:03:22.259 look for. First one, new capabilities unlocked. 00:03:22.900 --> 00:03:25.379 These are tools that let you do things that were, 00:03:25.379 --> 00:03:29.199 well, basically impossible before or needed super 00:03:29.199 --> 00:03:32.539 specialized skills. Like what? Okay, think about 00:03:32.539 --> 00:03:35.180 a small startup, maybe just one person. making 00:03:35.180 --> 00:03:38.599 a decent product, intro video. Used to need a 00:03:38.599 --> 00:03:41.300 script writer, an actor, camera person, editor, 00:03:41.500 --> 00:03:44.300 a whole team. Right, expensive. Totally. Now, 00:03:44.599 --> 00:03:48.300 tools like Synthesia or HayGen. One person can 00:03:48.300 --> 00:03:50.740 create a video with an AI avatar speaking any 00:03:50.740 --> 00:03:52.719 language just from a text script that's not just 00:03:52.719 --> 00:03:55.539 faster, it's democratizing video production. 00:03:55.580 --> 00:03:59.280 Wow. Or imagine an interior designer. Using generative 00:03:59.280 --> 00:04:01.539 AI like Mid Journey, they can whip up dozens 00:04:01.539 --> 00:04:03.400 of different room concepts in minutes that used 00:04:03.400 --> 00:04:05.979 to take days. of sketching or 3D modeling, it 00:04:05.979 --> 00:04:07.759 really levels the playing field. That's a huge 00:04:07.759 --> 00:04:09.659 difference. It's not just productivity, it's 00:04:09.659 --> 00:04:11.919 access. Access is a great word for it. OK, second 00:04:11.919 --> 00:04:14.659 type, 10x improvements. These tools aren't just 00:04:14.659 --> 00:04:16.540 a little better, they are exponentially better. 00:04:16.819 --> 00:04:20.120 Think 10x cost savings, maybe in token efficiency, 00:04:20.240 --> 00:04:22.399 that's like how much processing power it uses, 00:04:22.579 --> 00:04:25.600 or just raw speed. OK, give me an example. Imagine 00:04:25.600 --> 00:04:28.660 a data analytics team. Normally, they spend maybe 00:04:28.660 --> 00:04:32.240 a week processing, cleaning, visualizing a big 00:04:32.240 --> 00:04:35.579 data set. Standard stuff. Right. A new AI tool 00:04:35.579 --> 00:04:38.339 lets them just ask in plain English, like, show 00:04:38.339 --> 00:04:41.339 me sales trends for product X and Q3 by region, 00:04:41.600 --> 00:04:43.860 and bam, they get a full chart in minutes. Oh. 00:04:44.439 --> 00:04:47.079 Imagine that kind of speed for complex data, 00:04:47.300 --> 00:04:49.240 getting insights in moments instead of days. 00:04:49.879 --> 00:04:52.500 Exactly. That's the 10x. Or another example, 00:04:52.660 --> 00:04:55.500 these new language models. Some have huge context 00:04:55.500 --> 00:04:58.100 windows now. You can upload an entire book, maybe 00:04:58.100 --> 00:05:00.540 a whole code repository, and analyze it all at 00:05:00.540 --> 00:05:03.600 once. That's easily a 10x jump over having to 00:05:03.600 --> 00:05:05.759 chop everything up into tiny bits. That's a massive 00:05:05.759 --> 00:05:08.680 change for research for coding. But wait, with 00:05:08.680 --> 00:05:10.819 those huge context windows, does that bring new 00:05:10.819 --> 00:05:14.220 problems like more chance of the AI hallucinating 00:05:14.220 --> 00:05:16.220 or making stuff up? Or maybe people just dump 00:05:16.220 --> 00:05:18.220 everything in without thinking critically. That's 00:05:18.220 --> 00:05:20.519 a really crucial point. And it highlights that 00:05:20.519 --> 00:05:22.899 even with these super powerful tools, you know, 00:05:23.019 --> 00:05:25.459 human oversight, still absolutely essential. 00:05:25.600 --> 00:05:27.620 Right. It empowers you, but it doesn't replace 00:05:27.620 --> 00:05:31.500 critical thinking. OK, third type, category creation. 00:05:31.959 --> 00:05:34.379 These are the pioneers. Tools that carve out 00:05:34.379 --> 00:05:37.300 entirely new markets. What? Well, think about 00:05:37.300 --> 00:05:41.579 vibe coding. Before, say, 2024, that wasn't really 00:05:41.579 --> 00:05:43.939 a thing. The idea you could just type a description 00:05:43.939 --> 00:05:45.879 and get a working app in like five minutes. Yeah, 00:05:45.980 --> 00:05:48.079 seemed like science fiction. Right. Tools that 00:05:48.079 --> 00:05:50.160 first cracked that. They created a whole new 00:05:50.160 --> 00:05:53.300 profitable category. Or think about autonomous 00:05:53.300 --> 00:05:57.480 AI agents like AutoGPT. That created a new space 00:05:57.480 --> 00:06:00.680 for AI that can actually plan and execute complex 00:06:00.680 --> 00:06:03.139 tasks on its own. OK, new categories. What's 00:06:03.139 --> 00:06:05.300 the last one? The fourth is paradigm shifts. 00:06:05.899 --> 00:06:08.379 These tools fundamentally change who can do certain 00:06:08.379 --> 00:06:11.500 tasks. They democratize skills, maybe even whole 00:06:11.500 --> 00:06:14.110 industries. Ah. So like the vibe coding example 00:06:14.110 --> 00:06:17.389 again. Exactly. Suddenly, a plumber, a welder, 00:06:17.610 --> 00:06:19.509 anyone without a coding background can build 00:06:19.509 --> 00:06:22.050 simple apps just by talking or typing. That's 00:06:22.050 --> 00:06:24.329 a total paradigm shift in who gets to create 00:06:24.329 --> 00:06:27.689 software. That's powerful. Or AI music generation, 00:06:28.529 --> 00:06:31.370 platforms that let literally anyone create professional 00:06:31.370 --> 00:06:33.730 sounding background tracks for videos without 00:06:33.730 --> 00:06:37.189 knowing a lick of music theory. Huge shift. OK. 00:06:37.870 --> 00:06:40.879 So. If a tool doesn't clearly fit into one of 00:06:40.879 --> 00:06:44.959 those four boxes, new capabilities, 10x improvement, 00:06:45.639 --> 00:06:47.980 category creation, or a paradigm shift, then 00:06:47.980 --> 00:06:50.040 it's probably just an incremental improvement. 00:06:50.339 --> 00:06:53.740 Nice to have, maybe, but probably not worth disrupting 00:06:53.740 --> 00:06:55.860 your whole workflow for. That's your first filter. 00:06:56.259 --> 00:06:58.720 You're gonna go. Precisely. If it's not a real 00:06:58.720 --> 00:07:00.579 leap, maybe just put it aside for now. Okay, 00:07:00.579 --> 00:07:02.600 so let's say a tool does pass that step change 00:07:02.600 --> 00:07:05.399 filter. It feels like a real leap. Now we hit 00:07:05.399 --> 00:07:08.699 that classic question. Do I dole it myself? Or 00:07:08.699 --> 00:07:10.680 do I just buy the subscription? The build versus 00:07:10.680 --> 00:07:13.360 buy dilemma. Yep. And this assessment seems to 00:07:13.360 --> 00:07:15.959 boil down to three core questions. You mentioned 00:07:15.959 --> 00:07:19.379 secret sauce earlier. What makes a tool genuinely 00:07:19.379 --> 00:07:22.680 hard to copy? Then, can I actually build it? 00:07:22.750 --> 00:07:25.029 And finally, could the big guys just swallow 00:07:25.029 --> 00:07:27.129 it whole? Exactly. Let's tackle the first one. 00:07:27.170 --> 00:07:29.730 Can I build this myself? And building today doesn't 00:07:29.730 --> 00:07:31.850 always mean writing thousands of lines of code 00:07:31.850 --> 00:07:34.730 from scratch. You've got these amazing automation 00:07:34.730 --> 00:07:38.329 tools like NEN or Make. Think of them like visual 00:07:38.329 --> 00:07:40.790 builders, drag and drop style, connecting different 00:07:40.790 --> 00:07:43.250 apps. They even have text to workflow features 00:07:43.250 --> 00:07:45.470 now. So you can just describe the workflow. Yeah. 00:07:45.790 --> 00:07:48.209 You can often sketch out a basic workflow in 00:07:48.209 --> 00:07:50.790 maybe an hour or two. You could even hook that 00:07:50.790 --> 00:07:54.139 up to a simple front end you vibe -coded with 00:07:54.139 --> 00:07:56.959 natural language. Hmm. But is it different that 00:07:56.959 --> 00:07:59.160 simple? I mean... Well, okay, full disclosure. 00:07:59.560 --> 00:08:02.300 I still wrestle with prompt drift myself sometimes, 00:08:02.500 --> 00:08:05.120 where the AI's output just kind of degrades or 00:08:05.120 --> 00:08:07.000 changes over time, even if you didn't change 00:08:07.000 --> 00:08:08.800 the prompt. Chuckles. Yeah, that's frustrating. 00:08:08.939 --> 00:08:11.180 It really is. And it is tempting to build when 00:08:11.180 --> 00:08:13.939 you see something cool that works, but you absolutely 00:08:13.939 --> 00:08:16.220 have to consider the hidden costs of building. 00:08:16.379 --> 00:08:18.959 Like what? Well, the time, obviously, and the 00:08:18.959 --> 00:08:20.699 opportunity cost. What else could you be doing? 00:08:21.060 --> 00:08:23.680 Plus perfecting it, debugging, maintaining it. 00:08:23.800 --> 00:08:26.180 And APIs change, right? Things break. Constantly. 00:08:26.360 --> 00:08:29.019 Ongoing maintenance is huge. And then can you 00:08:28.910 --> 00:08:31.110 your home -built solution actually scale if you 00:08:31.110 --> 00:08:34.470 needed to, those costs add up fast. OK, so the 00:08:34.470 --> 00:08:37.230 hidden costs are real. Don't underestimate them. 00:08:37.309 --> 00:08:39.370 Definitely not. Then the second question, do 00:08:39.370 --> 00:08:42.809 they have a secret sauce? This is all about competitive 00:08:42.809 --> 00:08:45.909 advantage, an economic moat, basically, something 00:08:45.909 --> 00:08:48.269 that makes their product really hard for anyone 00:08:48.269 --> 00:08:50.830 else, including you, to replicate perfectly. 00:08:51.470 --> 00:08:53.070 We'll dig into what counts as sauce in a sec. 00:08:53.190 --> 00:08:56.320 OK, the moat. And the third question. Can the 00:08:56.320 --> 00:08:58.580 big players replicate this? You gotta think. 00:08:59.460 --> 00:09:03.200 Could Google, Microsoft, OpenAI, one of the giants? 00:09:03.500 --> 00:09:05.639 Could they just build this feature themselves, 00:09:05.799 --> 00:09:07.379 especially the reputable companies, the ones 00:09:07.379 --> 00:09:08.860 you know are probably going to be around in a 00:09:08.860 --> 00:09:11.059 year? That's a scary thought for a startup. It 00:09:11.059 --> 00:09:13.799 is. Classic example. A couple years back, white 00:09:13.799 --> 00:09:17.360 -labeled custom GPTs felt revolutionary. Right. 00:09:17.360 --> 00:09:20.039 Everyone wanted one. Now, you can practically 00:09:20.039 --> 00:09:22.480 vibe code that whole experience yourself, the 00:09:22.480 --> 00:09:23.980 front end, and maybe add payments, hook it to 00:09:23.980 --> 00:09:26.860 a back end, relatively easily. Wow. And worse, 00:09:27.279 --> 00:09:30.639 if that kind of tool gets popular enough, ChatGDT 00:09:30.639 --> 00:09:33.049 might just build it in as a native feature. Poof. 00:09:33.529 --> 00:09:36.850 This vendor risk is real. Big platform updates 00:09:36.850 --> 00:09:40.409 from OpenAI, Google, whoever can literally make 00:09:40.409 --> 00:09:43.610 hundreds of startups obsolete overnight. Imagine 00:09:43.610 --> 00:09:46.590 your whole team relying on a tool and it just 00:09:46.590 --> 00:09:48.450 vanishes or gets kneecapped. That's a massive 00:09:48.450 --> 00:09:51.009 business risk. This is a stark warning. So when 00:09:51.009 --> 00:09:53.129 we're looking at a tool, we're asking, can I 00:09:53.129 --> 00:09:55.350 realistically build it considering the hidden 00:09:55.350 --> 00:09:57.529 costs? Is there something truly unique, some 00:09:57.529 --> 00:10:00.289 secret sauce? And could a tech giant just crush 00:10:00.289 --> 00:10:03.149 it? Exactly. Can you replicate it easily? Do 00:10:03.149 --> 00:10:04.909 they have a real secret sauce? And what's that 00:10:04.909 --> 00:10:07.250 big tech replication risk? Those are the key 00:10:07.250 --> 00:10:08.929 build versus buy questions. All right. Let's 00:10:08.929 --> 00:10:11.690 dive deep now into what really counts as secret 00:10:11.690 --> 00:10:14.289 sauce. That durable barrier, like you said, not 00:10:14.289 --> 00:10:17.210 just a slick interface. What makes a tool genuinely 00:10:17.210 --> 00:10:20.129 hard to copy? What are those maybe subtle signs 00:10:20.129 --> 00:10:22.450 you've learned to look for? Yeah. Good question. 00:10:22.570 --> 00:10:24.409 Because secret sauce isn't just one thing. It 00:10:24.409 --> 00:10:28.389 comes in several flavors. First up. complex workflow 00:10:28.389 --> 00:10:30.769 orchestration. Okay, what's that mean? Some companies 00:10:30.769 --> 00:10:33.529 are just exceptionally good at managing really 00:10:33.529 --> 00:10:35.730 intricate, sophisticated workflows behind the 00:10:35.730 --> 00:10:38.970 scenes. Think about Gamma, the AI presentation 00:10:38.970 --> 00:10:42.149 tool. I've seen that. You could theoretically 00:10:42.149 --> 00:10:44.450 try to build something similar yourself, connect 00:10:44.450 --> 00:10:47.809 APIs, but replicating how they handle element 00:10:47.809 --> 00:10:51.289 positioning, manage latency, choose design layouts, 00:10:51.690 --> 00:10:53.909 deal with fonts, all those details, it would 00:10:53.909 --> 00:10:56.750 take so much time to reverse engineer compared 00:10:56.750 --> 00:10:59.440 to just paying for it. So it's the fine -tuning 00:10:59.440 --> 00:11:02.019 the edge cases. Exactly. It's not just connecting 00:11:02.019 --> 00:11:05.000 A to B. It's optimizing for a million little 00:11:05.000 --> 00:11:07.759 things, anticipating errors, ensuring speed, 00:11:07.960 --> 00:11:10.620 making thousands of micro decisions. That kind 00:11:10.620 --> 00:11:13.519 of deep orchestration, that's a secret sauce 00:11:13.519 --> 00:11:16.259 that's almost impossible to copy quickly. Okay, 00:11:16.279 --> 00:11:18.259 so that invisible complexity is one type of sauce. 00:11:18.580 --> 00:11:21.440 Yeah. What else? Second, security infrastructure. 00:11:21.759 --> 00:11:24.559 If a tool handles sensitive tasks securely, that's 00:11:24.559 --> 00:11:27.960 huge. Building robust security yourself, especially 00:11:27.960 --> 00:11:30.860 if you need things like SOC2 or GDPR compliance 00:11:30.860 --> 00:11:33.279 for customer data, that's a massive undertaking. 00:11:33.519 --> 00:11:35.840 Yeah, saves huge amounts of time, cost, and headaches. 00:11:36.299 --> 00:11:37.940 Totally. Peace of mind is part of the value. 00:11:38.240 --> 00:11:40.580 Third, and this is a really strong one, proprietary 00:11:40.580 --> 00:11:43.240 data. Ah, data they own that nobody else has. 00:11:43.820 --> 00:11:46.919 Precisely. If a company has spent years collecting, 00:11:47.080 --> 00:11:50.279 cleaning, and refining a unique data set, models 00:11:50.279 --> 00:11:52.899 trained on that data have an inherent edge. You 00:11:52.899 --> 00:11:54.639 just can't replicate it if you don't have the 00:11:54.639 --> 00:11:56.700 ingredients. Makes perfect sense. Like a chef 00:11:56.700 --> 00:12:00.419 with a secret, irreplaceable spice blend. Exactly 00:12:00.419 --> 00:12:04.240 like that. Fourth, network effects. This is when 00:12:04.240 --> 00:12:05.879 a product gets more valuable the more people 00:12:05.879 --> 00:12:08.480 use it. Like social media, kind of. Yeah, or 00:12:08.480 --> 00:12:10.960 think of a collaborative AI design tool. It's 00:12:10.960 --> 00:12:12.799 way more useful if your whole team is on it, 00:12:12.799 --> 00:12:15.620 right? That naturally attracts more users, which 00:12:15.620 --> 00:12:18.240 makes it even more valuable. Creating this positive 00:12:18.240 --> 00:12:20.639 feedback loop, that's a strong moat. OK, got 00:12:20.639 --> 00:12:23.580 it. Network effects. What's next? Fifth, sometimes 00:12:23.580 --> 00:12:25.600 it's just elegant implementation. The product 00:12:25.600 --> 00:12:29.299 is just so smooth, so intuitive. Maybe it makes 00:12:29.299 --> 00:12:31.460 team sharing incredibly easy. It just works. 00:12:31.620 --> 00:12:35.240 So good UX is a boat. Exceptional UX, yeah. It's 00:12:35.240 --> 00:12:37.539 a moat, because achieving that level of simplicity 00:12:37.539 --> 00:12:40.440 and usability requires deep user understanding 00:12:40.440 --> 00:12:42.759 and literally thousands of hours of refinement. 00:12:42.960 --> 00:12:45.679 It's harder than it looks. True. OK, one more. 00:12:45.919 --> 00:12:48.279 Last one, and it's crucial, economies of scale. 00:12:48.879 --> 00:12:51.860 Does the company have access to, like, bulk discounts 00:12:51.860 --> 00:12:55.279 on using the big AI models? Cheaper API calls. 00:12:55.600 --> 00:12:58.860 Exactly. Big players negotiate much cheaper rates 00:12:58.860 --> 00:13:02.179 for using Claude, Gemini, GPT -4, whatever. They 00:13:02.179 --> 00:13:04.799 can pass those savings on to you, making their 00:13:04.799 --> 00:13:06.940 service way cheaper than if you tried to run 00:13:06.940 --> 00:13:09.279 the same number of queries yourself. Ah, OK. 00:13:09.279 --> 00:13:11.860 Or, related to that, maybe they're acting as 00:13:11.860 --> 00:13:14.559 a loss leader. They might be winning to lose 00:13:14.559 --> 00:13:17.000 money on the AI costs, at least initially, just 00:13:17.000 --> 00:13:19.080 to get you hooked and build a big user base. 00:13:19.240 --> 00:13:21.879 So they're subsidizing your usage. Right. That 00:13:21.879 --> 00:13:23.980 scale gives them a huge financial advantage. 00:13:24.139 --> 00:13:27.100 So quick gut check, then. Sure. If a tool has 00:13:27.100 --> 00:13:31.019 basically no real sauce, no complex workflows, 00:13:31.440 --> 00:13:34.179 no unique data, weak security, no network effects, 00:13:34.500 --> 00:13:37.700 clunky UX, and no obvious scale advantage. That's 00:13:37.700 --> 00:13:39.700 a pretty strong signal to probably skip it. It's 00:13:39.700 --> 00:13:41.860 likely easily replaceable. OK. That brings us 00:13:41.860 --> 00:13:43.639 back to that question, can I build this myself 00:13:43.639 --> 00:13:46.200 and into phase four, which you call the Vibe 00:13:46.200 --> 00:13:48.620 code test. Yeah. This is about testing the realistic 00:13:48.620 --> 00:13:51.100 possibility of you replicating it. So the question 00:13:51.100 --> 00:13:53.960 here is, If I used a vibe code in front -end, 00:13:54.100 --> 00:13:57.620 could I replicate, say, 80 % of this tool's core 00:13:57.620 --> 00:13:59.720 function using something like SuperBase for the 00:13:59.720 --> 00:14:03.559 back -end and maybe N8n or make for the workflow 00:14:03.559 --> 00:14:05.860 automation? Exactly. Let's walk through a scenario. 00:14:06.360 --> 00:14:09.039 Say you find a new sauce tool. Its whole job 00:14:09.039 --> 00:14:11.379 is generating social media posts from a blog 00:14:11.379 --> 00:14:14.039 post URL you give it. OK. Simple enough concept. 00:14:14.220 --> 00:14:16.299 Right. Could you replicate the core of that? 00:14:16.480 --> 00:14:18.779 Well, for the front -end, maybe use card that's 00:14:18.779 --> 00:14:21.519 a super simple one -page website builder or some 00:14:21.519 --> 00:14:24.179 basic framework. Just needs a box for the URL 00:14:24.179 --> 00:14:26.940 and a button. Okay, doable. For the backend logic. 00:14:27.149 --> 00:14:29.450 A super base edge function, think of that as 00:14:29.450 --> 00:14:31.429 just a quick bit of code that runs super fast 00:14:31.429 --> 00:14:33.450 when the button's clicked, could trigger the 00:14:33.450 --> 00:14:36.330 process. Trigger what, exactly? An N8N workflow. 00:14:36.610 --> 00:14:39.190 That workflow would, one, grab the content from 00:14:39.190 --> 00:14:41.830 the blog post URL, two, send that content to 00:14:41.830 --> 00:14:44.769 the chat GPT or Claude API with a specific prompt, 00:14:45.110 --> 00:14:47.509 like, summarize this, then generate three Twitter 00:14:47.509 --> 00:14:49.490 posts, one LinkedIn post, one Facebook post, 00:14:49.590 --> 00:14:52.090 three, get the results back from the AI, and 00:14:52.090 --> 00:14:54.860 four, display them on your simple web page. when 00:14:54.860 --> 00:14:57.019 you break it down like that? If you can easily 00:14:57.019 --> 00:14:59.759 map out those basic steps, front -end, back -end, 00:14:59.919 --> 00:15:02.299 trigger, workflow, logic, then yeah, maybe building 00:15:02.299 --> 00:15:05.480 it yourself is feasible. At least the core, 80%. 00:15:05.480 --> 00:15:08.500 But, and this is a big but, we keep coming back 00:15:08.500 --> 00:15:11.299 to, always remember the economics. Crucial point. 00:15:11.519 --> 00:15:14.720 Always. Like your example. If generating, say, 00:15:14.820 --> 00:15:18.049 100 ,000 images yourself, using an API directly 00:15:18.049 --> 00:15:20.710 would cost you maybe $50 ,000. Yeah, easily. 00:15:20.970 --> 00:15:23.309 Inference costs add up. But some platform offers 00:15:23.309 --> 00:15:26.210 that same capability for $24 a month because 00:15:26.210 --> 00:15:28.190 they have massive economies of scale. They've 00:15:28.190 --> 00:15:30.669 negotiated bulk rates. Math is pretty clear there, 00:15:30.669 --> 00:15:33.529 isn't it? You buy. Definitely buy. So, yeah, 00:15:33.529 --> 00:15:35.769 the decision point here is really if a tool is 00:15:35.769 --> 00:15:38.370 too complex for you to realistically build and 00:15:38.370 --> 00:15:40.649 you don't get significant economies of scale 00:15:40.649 --> 00:15:43.429 advantages by doing it yourself, then it almost 00:15:43.429 --> 00:15:46.129 always makes more sense to just buy versus build. 00:15:46.269 --> 00:15:48.470 OK, so to quickly gauge if we could realistically 00:15:48.470 --> 00:15:51.870 DIY an AI tool, it's about mapping its key parts, 00:15:52.110 --> 00:15:54.830 front -end, back -end workflow, using those common 00:15:54.830 --> 00:15:57.389 accessible automation tools. Exactly. Can you 00:15:57.389 --> 00:15:59.570 easily map its front -end, back -end, and workflow 00:15:59.570 --> 00:16:01.809 using common automation tools? That's the vibe 00:16:01.809 --> 00:16:05.470 code test. Got it. OK, moving on to phase five, 00:16:05.769 --> 00:16:09.129 the momentum test. This feels important. A great 00:16:09.129 --> 00:16:11.769 tool today could be totally useless tomorrow 00:16:11.769 --> 00:16:15.789 if the company behind it just Absolutely. Abandonware 00:16:15.789 --> 00:16:18.450 is a real risk. You need to assess the provider's 00:16:18.450 --> 00:16:21.149 vitality. Are they still moving forward? Are 00:16:21.149 --> 00:16:23.570 they alive? How do we do that? What are the signals? 00:16:23.690 --> 00:16:26.470 We look for key momentum signals. First off, 00:16:26.789 --> 00:16:29.830 shipping velocity. Pretty simple. Are they consistently 00:16:29.830 --> 00:16:33.169 releasing new features, fixing bugs, making improvements? 00:16:33.309 --> 00:16:35.149 Where do you look for that? Check their company 00:16:35.149 --> 00:16:37.529 blog, their Discord server if they have one, 00:16:37.690 --> 00:16:40.450 their official changelog. A green flag is seeing 00:16:40.450 --> 00:16:43.889 updates weekly or maybe bi -weekly. A clear public 00:16:43.889 --> 00:16:47.009 roadmap is also a great sign. Loveable, that 00:16:47.009 --> 00:16:50.169 AI tool, is a great case study here. Their consistent 00:16:50.169 --> 00:16:52.970 weekly shipping really put them on the map and 00:16:52.970 --> 00:16:54.950 built trust. And the red flag. Products that 00:16:54.950 --> 00:16:57.350 get built once, launched with a splash, and then 00:16:57.350 --> 00:17:00.730 crickets. Silence. A blog that hasn't been updated 00:17:00.730 --> 00:17:03.190 in six months, that's a very bad sign. Yeah, 00:17:03.190 --> 00:17:05.210 that's a clear indicator they're losing steam 00:17:05.210 --> 00:17:07.190 or maybe ran out of funding. You don't want to 00:17:07.190 --> 00:17:09.859 invest your time learning that tool. Precisely. 00:17:10.059 --> 00:17:14.819 Signal number two, free tier generosity. How 00:17:14.819 --> 00:17:17.740 much can you actually test for free before you 00:17:17.740 --> 00:17:20.140 have to pay? How does that tell you about momentum? 00:17:21.119 --> 00:17:24.220 Well, really generous free tiers, like maybe 00:17:24.220 --> 00:17:27.940 unlimited access to expensive models for a trial 00:17:27.940 --> 00:17:30.500 period often indicates solid financial backing 00:17:30.500 --> 00:17:33.440 and confidence in their product. Ah, they believe 00:17:33.440 --> 00:17:35.519 you'll see the value and convert. Exactly. They're 00:17:35.519 --> 00:17:38.000 not afraid to let you kick the tires thoroughly. 00:17:38.359 --> 00:17:40.880 A red flag, on the other hand, is a super limited 00:17:40.880 --> 00:17:42.839 free tier. Maybe you only get one or two uses. 00:17:43.339 --> 00:17:45.039 That could suggest their operating costs are 00:17:45.039 --> 00:17:46.420 really high, or maybe they're just trying to 00:17:46.420 --> 00:17:48.460 force a quick purchase after maybe one or two 00:17:48.460 --> 00:17:50.700 good initial results that might not actually 00:17:50.700 --> 00:17:53.059 hold up in real world use. OK, so a generous 00:17:53.059 --> 00:17:55.400 free tier is actually a sign of strength and 00:17:55.400 --> 00:17:57.880 confidence, not desperation. Interesting. It 00:17:57.880 --> 00:18:01.539 often is, yeah. Third signal, platform play clarity. 00:18:01.799 --> 00:18:04.640 does the tool seem to have a clear, coherent 00:18:04.640 --> 00:18:07.740 strategy, a vision for what it's trying to become? 00:18:08.000 --> 00:18:10.460 What do you mean by platform play? Like, take 00:18:10.460 --> 00:18:12.420 Vi coding tools. Their goal is pretty clear. 00:18:12.920 --> 00:18:15.579 Help people go from zero to a working app using 00:18:15.579 --> 00:18:19.200 prompts. Every new feature should kind of reinforce 00:18:19.200 --> 00:18:22.430 that core mission. That's a green flag, a clear 00:18:22.430 --> 00:18:24.930 vision. And the red flag here? Companies that 00:18:24.930 --> 00:18:27.609 seem to be constantly pivoting, chasing the latest 00:18:27.609 --> 00:18:30.029 trend, changing their identity every few months. 00:18:30.569 --> 00:18:33.029 That signals instability in their product roadmap. 00:18:33.710 --> 00:18:35.849 You don't want to build your workflow on a tool 00:18:35.849 --> 00:18:38.170 from a company that... doesn't seem to know where 00:18:38.170 --> 00:18:41.490 it's going, lacks staying power. Right. Unpredictable. 00:18:41.630 --> 00:18:44.210 OK. What's the last momentum signal? Finally, 00:18:44.230 --> 00:18:47.809 we have the Lindy effect. It's this idea that 00:18:47.809 --> 00:18:50.589 for non -perishable things like technology or 00:18:50.589 --> 00:18:53.789 ideas, their future life expectancy is proportional 00:18:53.789 --> 00:18:55.970 to their current age. So the longer something's 00:18:55.970 --> 00:18:58.210 been around. The more likely it is to keep being 00:18:58.210 --> 00:19:00.869 around. It's survived trials, adapted. Think 00:19:00.869 --> 00:19:02.950 about businesses. First year companies have a 00:19:02.950 --> 00:19:05.630 super high failure rate, right? Maybe 90%. Yes, 00:19:05.650 --> 00:19:08.509 brutal. Apply that same thinking to these AI 00:19:08.509 --> 00:19:11.309 tools. A tool that just launched two months ago 00:19:11.309 --> 00:19:13.869 carries a significantly higher risk of disappearing 00:19:13.869 --> 00:19:16.170 within the next year compared to one that's already 00:19:16.170 --> 00:19:19.309 been around, growing, adapting for two or three 00:19:19.309 --> 00:19:22.029 years. Age implies some resilience. That's a 00:19:22.029 --> 00:19:24.410 really good historical lens to apply, even to 00:19:24.410 --> 00:19:26.890 brand new tech. Yeah. Okay, so stepping back 00:19:26.890 --> 00:19:29.910 from just the cool features, what are the key 00:19:29.910 --> 00:19:33.789 signals for a tool's long -term viability that 00:19:33.789 --> 00:19:36.970 it won't just vanish next year? Check for consistent 00:19:36.970 --> 00:19:39.589 updates, look at the generosity of their free 00:19:39.589 --> 00:19:42.410 tier, assess if they have a clear vision, and 00:19:42.410 --> 00:19:46.009 consider its age, the Lindy effect. Got it. Now 00:19:46.009 --> 00:19:49.349 for our final phase, phase six, the depth ladder. 00:19:50.250 --> 00:19:52.410 This is about specialists versus generalists. 00:19:52.490 --> 00:19:54.849 Right. Is this tool trying to be a Swiss Army 00:19:54.849 --> 00:19:57.309 knife or is it a specialized scalpel? And you're 00:19:57.309 --> 00:19:59.549 saying the generalist tools, the Swiss Army knives, 00:19:59.789 --> 00:20:02.109 need more scrutiny. because they can end up being 00:20:02.109 --> 00:20:05.029 a jack -of -all -trades, master of none. Exactly. 00:20:05.329 --> 00:20:07.430 Your analogy is perfect. A Swiss Army knife is 00:20:07.430 --> 00:20:09.289 handy for lots of little things, but if you need 00:20:09.289 --> 00:20:11.109 heart surgery, you want the specialized scalpel, 00:20:11.210 --> 00:20:13.289 right? Yeah. So we assess this by thinking about 00:20:13.289 --> 00:20:17.359 the level of usage. First, casual use. Think 00:20:17.359 --> 00:20:19.680 students, maybe content creators doing simple 00:20:19.680 --> 00:20:22.819 stuff. Office workers needing quick tasks, summarizing 00:20:22.819 --> 00:20:25.420 meeting notes, drafting emails, generating simple 00:20:25.420 --> 00:20:28.299 images. Everyday AI tasks. Great! For this level, 00:20:28.720 --> 00:20:31.500 the big, broad, all -in -one tools like the free 00:20:31.500 --> 00:20:34.640 versions of ChatGPT or Gemini are often totally 00:20:34.640 --> 00:20:37.240 sufficient. They're designed for that wide utility. 00:20:37.640 --> 00:20:39.500 They handle the basics well. Okay, what's the 00:20:39.500 --> 00:20:42.099 next level? Professional use. Now we're talking 00:20:42.099 --> 00:20:44.579 developers, marketers running campaigns, designers, 00:20:44.799 --> 00:20:47.059 data analysts doing serious work. Their needs 00:20:47.059 --> 00:20:49.940 are deeper. building applications, automating 00:20:49.940 --> 00:20:52.740 complex marketing funnels, analyzing large complex 00:20:52.740 --> 00:20:55.500 data sets. So more specialized needs. Exactly. 00:20:55.740 --> 00:20:57.519 And for this level, you generally want to opt 00:20:57.519 --> 00:21:00.180 for well -funded focused tools, companies like 00:21:00.180 --> 00:21:03.400 Lovable, Bolt, Replet. They have substantial 00:21:03.400 --> 00:21:06.220 backing, clear focus areas. You probably want 00:21:06.220 --> 00:21:08.619 to avoid betting your critical workflows on Tool 00:21:08.619 --> 00:21:10.740 X that looks cool but just launched three months 00:21:10.740 --> 00:21:13.940 ago and has totally unknown survival odds. Right. 00:21:13.940 --> 00:21:16.019 Reliability matters more here. And the top level, 00:21:16.220 --> 00:21:19.519 expert level. This is for AI researchers, machine 00:21:19.519 --> 00:21:22.579 learning engineers, cybersecurity specialists. 00:21:23.240 --> 00:21:26.319 Their needs are highly specialized. Fine -tuning 00:21:26.319 --> 00:21:29.460 models, auditing source code for subtle vulnerabilities, 00:21:30.059 --> 00:21:32.099 working to minimize hallucinations in really 00:21:32.099 --> 00:21:35.240 complex AI systems. Very specific, deep work. 00:21:35.519 --> 00:21:38.160 Extremely. For these folks, specialized tools 00:21:38.160 --> 00:21:41.740 are key. like Cursor, which is designed specifically 00:21:41.740 --> 00:21:44.559 for developers doing AI -assisted coding. It 00:21:44.559 --> 00:21:46.700 focuses intensely on things like code review 00:21:46.700 --> 00:21:49.400 quality, security audits, generating correct, 00:21:49.500 --> 00:21:52.519 efficient code. The deep focus, funding, and 00:21:52.519 --> 00:21:54.339 active community around these tools give you 00:21:54.339 --> 00:21:56.000 confidence that the time you invest learning 00:21:56.000 --> 00:21:58.220 them won't be wasted because the tool disappears 00:21:58.220 --> 00:22:01.079 or pivots drastically. So the core idea here 00:22:01.079 --> 00:22:03.779 is to bet on tools you genuinely believe will 00:22:03.779 --> 00:22:06.140 still exist in, say, 6 to 12 months, or at least 00:22:06.140 --> 00:22:08.559 have the funding and focus to adapt as the technology 00:22:08.430 --> 00:22:10.670 technology itself makes huge leaps. It's about 00:22:10.670 --> 00:22:13.130 durability and focus matching your needs. Exactly. 00:22:13.230 --> 00:22:15.690 Match the depth of the tool to the depth of your 00:22:15.690 --> 00:22:17.390 need. So when we're faced with all these options, 00:22:17.710 --> 00:22:19.690 how do we make that choice between a broad general 00:22:19.690 --> 00:22:22.690 AI tool and one that's super specialized? Match 00:22:22.690 --> 00:22:25.910 the tool's depth and focus to your specific usage 00:22:25.910 --> 00:22:29.609 level. Are you a casual, professional, or expert 00:22:29.609 --> 00:22:33.130 user for that particular task? Okay, let's bring 00:22:33.130 --> 00:22:35.710 all six of those phases together now. We've gone 00:22:35.710 --> 00:22:37.849 through the filters, the tests. Let's create 00:22:37.849 --> 00:22:39.829 an actionable decision matrix for everyone listening. 00:22:39.970 --> 00:22:42.910 This is the complete framework in action. Right, 00:22:42.970 --> 00:22:45.009 let's summarize it. Here's when you should adopt 00:22:45.009 --> 00:22:47.329 a tool. This is when all of these things are 00:22:47.329 --> 00:22:51.190 true. First, true secret sauce exists. Real competitive 00:22:51.190 --> 00:22:53.849 advantages, not just a pretty wrapper on an API. 00:22:54.650 --> 00:22:56.890 Second, it has a scale advantage. You see those 00:22:56.890 --> 00:22:59.089 economies of scale, good shipping velocity, clear 00:22:59.089 --> 00:23:01.470 customer focus basically. It passes that momentum 00:23:01.470 --> 00:23:04.829 test. Third, there's a depth match. The tools 00:23:04.829 --> 00:23:07.009 capabilities actually match the level of depth 00:23:07.009 --> 00:23:09.289 you require for your work. Casual, professional, 00:23:09.369 --> 00:23:12.549 or expert. Right. And fourth, the economics favor 00:23:12.549 --> 00:23:15.079 you. It's significantly more cost -effective 00:23:15.079 --> 00:23:17.579 for you to use their service than to try and 00:23:17.579 --> 00:23:19.920 build and maintain it yourself. If all four are 00:23:19.920 --> 00:23:22.980 true, adopt. All four. Got it. When should we 00:23:22.980 --> 00:23:25.180 build instead? Okay, you should build instead 00:23:25.180 --> 00:23:27.990 if... One, it's actually pretty easy to replicate 00:23:27.990 --> 00:23:30.349 and you need deep customization that the off 00:23:30.349 --> 00:23:33.210 -the -shelf tool doesn't offer. Two, if this 00:23:33.210 --> 00:23:35.210 function is absolutely core to your business 00:23:35.210 --> 00:23:37.329 operations, you don't want to rely on a third 00:23:37.329 --> 00:23:39.890 party for that. Makes sense. Control. Three, 00:23:40.049 --> 00:23:42.490 if the long -term cost of you building and maintaining 00:23:42.490 --> 00:23:44.710 it seems reasonable for the value it provides. 00:23:45.230 --> 00:23:47.730 And four, if you want complete control and ownership 00:23:47.730 --> 00:23:50.869 over the data and the process itself. Okay, build 00:23:50.869 --> 00:23:53.250 for customization, core function, reasonable 00:23:53.250 --> 00:23:56.980 cost, and control. And finally, when do we just 00:23:56.980 --> 00:23:59.569 ignore a tool? Hit the back button. You ignore 00:23:59.569 --> 00:24:02.670 it if. It's just another wrapper with no unique 00:24:02.670 --> 00:24:05.269 value add. If it has no real moat, no competitive 00:24:05.269 --> 00:24:07.349 advantage you can identify. If it has an unclear 00:24:07.349 --> 00:24:09.710 platform strategy or seems to be pivoting all 00:24:09.710 --> 00:24:12.589 the time. Red flags from the momentum test. Exactly. 00:24:12.910 --> 00:24:15.190 Also, if the free tier is super stingy without 00:24:15.190 --> 00:24:17.710 a good justification. And finally, if it's a 00:24:17.710 --> 00:24:19.430 brand new company with a high risk of disappearing 00:24:19.430 --> 00:24:21.769 basically, if it fails, the Lindy effect test 00:24:21.769 --> 00:24:25.589 hard. Too new, too risky. That's incredibly clear. 00:24:26.269 --> 00:24:30.019 Adopt. build, or ignore based on those criteria. 00:24:30.640 --> 00:24:32.339 And I want to just add a quick wrapper warning 00:24:32.339 --> 00:24:34.119 here because it ties right into this framework. 00:24:34.779 --> 00:24:37.599 Be really careful with those big aggregator platforms 00:24:37.599 --> 00:24:40.240 like future tools or similar sites. You scroll 00:24:40.240 --> 00:24:43.759 through and there are just endless lists of companies 00:24:43.759 --> 00:24:46.440 you've never heard of. So many. And a lot of 00:24:46.440 --> 00:24:48.579 them are just those quickly vibe coded applications 00:24:48.579 --> 00:24:51.440 built on top of an API. They look slick, but 00:24:51.440 --> 00:24:53.960 they have no moat, no sauce, and they will disappear. 00:24:54.160 --> 00:24:56.259 Many of them will, yeah. So in this landscape 00:24:56.259 --> 00:24:58.480 that changes so fast, being disciplined with 00:24:58.480 --> 00:25:00.359 this framework, it's more important than ever. 00:25:00.700 --> 00:25:03.420 It's about seeing past the packaging to the actual 00:25:03.420 --> 00:25:05.460 value. That's a critical filter. Absolutely. 00:25:05.660 --> 00:25:09.500 Discernment is key. So boiling it all down, what's 00:25:09.500 --> 00:25:11.740 the ultimate takeaway? How do we make a confident 00:25:11.740 --> 00:25:14.579 decision on an AI tool? Systematically apply 00:25:14.579 --> 00:25:17.420 the framework. look for real value, look for 00:25:17.420 --> 00:25:19.500 sustainability, and make sure the economics make 00:25:19.500 --> 00:25:21.460 sense for you. Okay, let's just quickly recap 00:25:21.460 --> 00:25:23.980 the big idea from today then. The explosion of 00:25:23.980 --> 00:25:27.000 AI tools. It presents amazing opportunities, 00:25:27.039 --> 00:25:30.619 but also some significant traps. Both sides of 00:25:30.619 --> 00:25:33.839 the coin. The goal isn't to become an AI tool 00:25:33.839 --> 00:25:36.920 hoarder. collecting digital dust. And it's definitely 00:25:36.920 --> 00:25:40.059 not to get bogged down in those tribal wars over 00:25:40.059 --> 00:25:42.839 which model is best. Right. It's about building 00:25:42.839 --> 00:25:47.079 your own personal AI ecosystem, one that efficiently 00:25:47.079 --> 00:25:50.019 and cost effectively serve your specific needs. 00:25:50.299 --> 00:25:52.700 Your needs. That's the focus. So focus on tools 00:25:52.700 --> 00:25:55.200 that have real competitive advantages. That's 00:25:55.200 --> 00:25:58.039 secret sauce. Look for clear signs of staying 00:25:58.039 --> 00:26:00.920 power that momentum and make sure the economics 00:26:01.150 --> 00:26:04.670 truly favor you over trying to DIY everything. 00:26:05.069 --> 00:26:07.750 Well said. And maybe start applying this framework 00:26:07.750 --> 00:26:10.369 today before you click subscribe on that next 00:26:10.369 --> 00:26:13.250 email promising a game -changing tool. Good advice. 00:26:13.769 --> 00:26:16.069 Your time, your money, and honestly your sanity 00:26:16.069 --> 00:26:17.690 will probably thank you for putting in that little 00:26:17.690 --> 00:26:20.049 bit of discipline upfront. Definitely. And maybe 00:26:20.049 --> 00:26:22.720 a provocative thought to leave you with. In this 00:26:22.720 --> 00:26:24.920 landscape that's shifting under our feet constantly, 00:26:25.200 --> 00:26:27.480 how will you make sure that the AI toolkit you 00:26:27.480 --> 00:26:30.740 carefully build today remains an asset and doesn't 00:26:30.740 --> 00:26:34.039 become a liability, say, a year from now? Hmm. 00:26:34.559 --> 00:26:36.319 Something to think about. Thank you for joining 00:26:36.319 --> 00:26:39.400 us on this deep dive into navigating the AI toolstorm. 00:26:39.579 --> 00:26:42.299 Yeah, thanks for tuning in. Until next time, 00:26:42.500 --> 00:26:43.259 Okiero Music.