Claude Code Converted Me (I'm Not a Developer)

Key Takeaways

Floodcode has converted me. Yes, it finally happened and I am using it basically all day every day to do most of my work now. After how many months have you been telling me to use this for Gil? Like more than 6 months, yeah. More than 6 months. Well, for context Gil is like the early adopter of the early adopters. Like he's the first person to use most things and despite him yeah, telling me to use this for so long, I don't always pay attention to everything he says. But as a non early adopter myself, I think you know, we've hit that second wave now and you're seeing kind of normal business people start to use this more. Why exactly is that Gil? Because the models got so good that the gain in productivity is undeniable at this point and that if you're using it all day most day, you decided this is essentially better than what you were doing before and you're still doing it now. So you've you've you've either would have found value or you would have gone back to your old ways, right? I think it's obvious 4.5. It's really obvious 4.5 that was kind of like that jump in capabilities and it made Claude Code more than just a coding thing. Yeah, and I think you've mentioned this before but because it's called Claude Code, every non-technical non-developer person thinks oh, that's not for me. I shouldn't use it. And you know, in the beginning those fears are almost feel justified in a way because it looks like a tool for developers. >> It sometimes feels like a tool for developers. Yeah, yeah, but it's like it's it's it's difficult. There's a kind of like mental hurdle. I switched from PC to Mac a couple years ago and I felt like a complete idiot, like a beginner trying to do just basic stuff again. And like it's it's not a nice feeling. And it's like there's something similar in using a tool like VS Code with Claude Code. And we'll show you how to use this later on. How the video. >> though? Like, do you feel like you would go back? Do you think you're going to stick to it? Do you think like >> Yeah, I mean, like it's This is how I work now. That's the thing. We put everyone do this. Every single person doing any kind of knowledge work, any kind of marketing, online marketing, running an online business, uh you know, if you use a computer for work, you should be using this. Okay. >> Um and I think this is the year when everyone who is using it will start to get ahead by leaps and bounds from everyone who is not. It's like when computers came along or the internet came along and people who started using that early on just destroyed everyone that was doing, you know, calculations by hand. Yep. I agree. I think by the end of this year, if you haven't started using this tool, it's like I see I see that. It's like a lot of people now we talk to, for example, they've Everyone has used ChatGPT. It's not You have no edge using a chatbot. Like, everyone is using a chatbot. If you want an edge, you need to jump out of the chatbot into these tools. And if you It's It's This is the point of this adaptability that we always talk about. It's like, you know, you have to adjust with the market, etc. That's the adjustment. Like, if you're not making the adjustment, you're [ __ ] It's like I think uh I will say it's difficult to know which adjustments to make because there have been plenty of tools come along >> though. It's You but this is like the market really is Yeah, solidifying around Claude code specifically, but you know, Next tool, I think. There are other ways of Yeah, there are So, let's just give some context here. Claude code is not the same as Claude. Claude being the the desktop or the app But Claude code is inside the the app, actually. So, it's like if you really want to go that way, it's like you actually have You have it inside the app now, but it's not as powerful. It's getting there. It's getting better. If I show my app now, for example, you'll see that this is the chat. And I'll tell you why I sent a hi to Claude in a minute. Uh all the time. Then you have this code auxin which is kind of an in-between between Claude code and the chat and you have Claude code here that allows you to work like for example you see I have this thing. And uh and you can do some stuff there like now they brought slash command you can see it's actually buggy like it doesn't even work anymore. So the point is that you could do some of it but this version is the shittiest version of Claude code and that's not how you should use it. Uh essentially what it is it let me correct me if I'm wrong here but it's like a very high thinking reasoning um model. The same model. So so okay. >> [laughter] >> It's the same model as the chat. The the only difference is it can use a terminal and a terminal is the gateway to do anything on your computer like actually every time you click on an icon on your desktop what happens really is there's a terminal command in the background that executes and does and opens the app you wanted to open. Like So all all Claude all Claude code is is uh Opus or whichever model you select. With a terminal. >> access with like root access to your computer. And then smart enough to use it properly and to know what to do like it knows all the commands by hand etc. so it knows what to do. And that's the That's it. But but like for example when I'm using Claude code and we'll show you some things we've built with it and what you can do just a second but like when I'm using it it often kind of thinks to itself back and forth and goes through like you know 5 10 15 something like 20 minutes before it finishes something. Yeah. But when I'm using like the Claude desktop app with the same model it's not like it might take like 30 seconds a minute or something but it's faster. So still the same model. The difference is when you run Claude code it has access to a file system. So now when you run it you have a lot of essentially knowledge and context scattered across files inside your system. So you have you know a brief summary of what the company does you have like a description of like a how what makes a good podcast episode, you have all these kind of documentation that it has access to. It has access to tools as well, so it can call, you know, Notion, it can call Google Drive, it can call all that. And so, it's utilizing the context it has. When you're in the chat, it only has the past discussion that is automatically sent, and it has the search tool. >> That's not strictly true. If you're in a project, it has all the context of the >> Sure, but it's kind of loaded as you send your message. Yeah, you but you still have like MCPs, you The The point is like when you send a message in a chatbot, it gets basically all the context at once. When you load flow code, it has no context, and it has to pick where it's going to go get context. So, it uses search, and it's like, "Oh, is there a document about the podcast? He's talking about podcast." It's going to run a search. That's going to be a line that says, "I'm searching for documents about the podcast." So, "Oh, I found three documents. Let me read them." But to come back to the point where, I guess I I I misspoke when I say it uses the same model, but like it's fundamentally there is something like there's some extra like code that it will like >> agentic. Uh like, you know, when people say agentic, etc., like it basically that's what it means. It means using tools to build its own context. Instead of you building the context in a chatbot, it just figures out figures it out. It figures out what it has access to. And it's like, "Oh, I need more information to do this task. Let me spend some time gathering information." And that's why you'll see it kind of go for a while and be like, "Oh, let me search that. Oh, I read this in this document. Maybe I should also search for that. He mentioned that, etc." And so, it has none of that in your chatbot. Um what it has is it has If you have a project, sure, it has the document, but kind of like loads them in the first prompt. It just destroys your context window and just loads all of it in the prompt. Whereas, it doesn't do that in flow code. It will go and read it if it thinks it needs it. Uh and that means it takes extra time. Fine. Fine. So, let's talk about some practical examples of this. So, last week, uh on Friday morning, I built a dashboard, and yeah, whoopsie do. Um Can we see it? Yeah. What does this dashboard do? So, last week I built this dashboard using Cloud Code uh and it connects to our Stripe API and pulls in all of the sales. It actually connects to two Stripe APIs cuz we had two accounts over the last 6 months. And it pulls in all our sales data. It breaks it down by plan. Um it works out all our fees, our processing costs, our taxes, our VAT costs. I'll get into that in a second. So, do you have a map as well? A map of where our members are. >> Who Who drew that map? >> [laughter] >> Cloud Cloud Code did. Okay. We've got kind of like uh breakdowns of like where our revenue comes from, member counts, subscribers, churn, um things like that. Cool. And you know, very very simple. Like you you make a you ask it to make a dashboard um showing you basic information and it can do that. Okay, fine. It's not >> did you take? And it's not crazy complicated, but So, I I spent three or four hours Okay. doing this, but 90% of that like I had a working dashboard in 10 minutes, I think. After I had to iron out a couple bugs. I spent most of the time working on two things. First is I wanted to get a clear picture of all our processing fees to understand how much it we're being charged. And second, I wanted to get a clear picture of our VAT because we collect VAT just like a sales tax and for some European customers and it's very complex who who has to get charged and how much they get charged. Um but it figured out all of that and it figured out how much we needed to be setting aside to pay our next VAT bills. So, there was no like surprise, "Oh, you have to pay $10,000 tomorrow." How did you do this before? Like before you built this I didn't. I I guessed it because it was like it's really difficult to calculate. So >> So that's the unlock. >> have like, yeah, I would have like floating funds of money just in case we had a big bill come in. So were you keeping more money aside and being less flexible with your money before? >> less less of that was being invested or spent in the business or whatever. Whereas now, I know this is our position. Like I know on the 20th of April, we owe this amount and on the 7th of May, we owe this amount. And when that's paid, I can simply uh check that it's paid and it'll reduce the amount owed. >> you restart your server? Yeah, it does. >> Okay. Okay. Cool. Uh this is fantastic. Like it really really helpful. The other thing it did, um and I know you're mocking me for the map. [laughter] So we do like a weekly group coaching call with our plus and max members. And you know, the time zone for that, you can see right here, most of our customers are in Europe or North America. Um so we optimize for, you know, a time zone that will work for both those folks. Occasionally, we have people in Asia or sometimes even Australia ask us about it. And I think twice in the last few weeks, we've had someone say, you know, "Oh, do you have anyone else in Australia or anyone else in Singapore or Asia um on there as well?" And now, I can just pull this up and say, "Well, yeah, we do. We have three in Australia or we have three folks in Singapore or one in Thailand, one in Hong Kong." And you know, they can see they can show you in the map. And that that was like a 5-minute job to do that. Uh but it's like a very niche thing. It's a very niche thing that's like it it's hardly ever going to be come up and you would never like hire a developer, pay a developer to do that. But the fact that it's so abundant and cheap to code anything these days means you can do all these little annoying niggly things that you wish you could do but couldn't justify it previously cuz of the cost, right? >> Do you understand the tech behind it? Like do you know what it's built on, for example? I don't have a clue. Yeah, it's built on Next.js, for example. Like it the little N at the bottom and the local host 3000 gives it away, but essentially Claude could figure it out for you, right? Do you need to know what it's built >> No, no, no, I'm just asking. It's interesting because it's like some people want to know. Like it's like how much do I need to know to create something like this? And and it's like apparently not a lot because you don't need to know. So, when I started building the dashboard, it mapped out this oh, you know, I'll look for some hosting and I'll do this. I was like, no, no, no, I don't need to do any of that. Just fire up on my local machine when I need to access it. And then it's like, all right, okay, cool. I'll do the quick and dirty approach. Here here you go. Yeah. And it it was like pulling I saw there was some Tailwind CSS at some point in there, but again, I don't particularly know exactly what that does. Um, but it used it and So, you put it in plan mode. You put it in plan mode. You told it what you wanted and then you said go and then you got 90% of these. Yep. Yeah. So, that's powerful. And it's like you can connect your So, for example, I don't have the dashboard yet, but like I have a skill that connects to analytics, etc. Like if a lot of the apps that we use, they have data. I think the main problem with small businesses is we don't use that data um, for knowledge, for example. So, one thing that I realized, for example, doing something similar with Claude code is I pulled like our email ISP uh, data into Claude code and then we used to email the podcasts. And I was like, oh, look at this look at the broadcast and just tell me what you what's interesting. Literally, it's just like go go figure it out. And he figured out that basically almost nobody clicked on the links for the podcast. And so, we stopped knowing it because of that. And so, that's the point. We have all that data and we were making mistakes, but because we had no time or even sometimes not the skill to essentially put it together and or it wouldn't be worth the time. Like it wasn't very important. But now, you can connect your APIs to these things either through dashboard or through a skill and we'll talk about skills in a bit on the show. And you can have Claude be your data analyst and translate that data into actions. For example, the action was stop emailing the podcast. People don't click on it. But when you email back short videos loom style, you get like 20 times more clicks. So like do that. Great. Like and I love that it translates all these complicated data in all these complicated software into just [ __ ] do this, which is essentially my job. Like my job when I create processes is basically that. It's like just [ __ ] do this. People love that. And Claude is awesome at this. And so now I'm like obsessed with collecting as much data as we can everywhere everything and then plug it into LLMs and have it figure out what's the best course of action based on the data basically. And you know, you can even have it So for example, like with this dashboard stuff, right? We're pulling information from one source, which is Stripe, very well documented API. It's like it's very easy for it to get everything it needs. But you know, in future when we expand this to look at like our sales funnel, we might want to look at you know, how our YouTube videos are doing or how you know, our marketing performance is and we might have to go to like different places to get the data and there's not necessarily an API for it. But you can go indirectly through something like Appify to get social media metric data if you want to pull that. >> If you do links and if you do GTM on your links like GTM parameters, which I've done I've plugged analytics into it as well. It's like awesome. Like I think you know, for when Google Analytics 4 came out, everyone was like this this sucks. I don't know how to use it. I don't know what it means. So but you don't need to anymore. You just use AI to interpret it for you. That's actually a skill that's coming out into accelerator really soon. It's one of the ones on my list. It's like literally just plug your analytics API, put your GTM on your links, like set up your conversion tracking. By the way, also helped me fix conversion tracking cuz I had the code of the website and I had I had analytics. It was like oh, you have this newsletter thing but conversion's not tracking. Like do you want me to do it? >> [laughter] >> And it just went and edited the website, set up conversion tracking, I pushed the code, boom, done. conversion tracking was done. And now I can analyze what's happening. Can we talk just very briefly about skills? Because I'm sure there's at least one person who heard that and doesn't understand what you mean by a skill and think it's more like a traditional, you know, >> Yeah, skill issue. a skill issue or knowledge issue. It's not a skill issue. >> But Um It's a It's like Let me try and explain this cuz I'm very newbie at this. A skill is a file and sometimes a set of files uh in markdown format, so it's like a text file, which explains how to do something. And one of the benefits of having it in this way is you can say like, "Okay, here's step one, do this. Step two, do this. Step three, do this." as a business process. It will remember how to do that. So, whenever you ask AI to do that thing, it will do it for you. But, within that file, you can also say, you know, like access, use this MCP to pull the data from Notion or use this this script to edit the image or whatever it might be. So, it's really just like an SOP but for AI. There's a bit more to it. Um I think the the thing with skills is like, okay, so these are basically pre-written prompts that you break down into chunks and an AI can open the chunk it needs. Like you make one main file that's like, "Here's the workflow." and then you can have have different like sub SOPs basically that explain the sub process. And sometimes it's a conditional thing. It's like, "If this happens, then do this. If then go read that document. If not, don't do this. Give it a try." >> So, essentially what you're saying is like the skill file, the skill.md file is like, "Here are the five steps." and just like, you know, a few lines about each one. Yeah. Yeah, and it needs to be short because it's optimized for minimal context. So, it's not like overflowing your context with the entire It's a progressive disclosure, basically. >> doesn't need to to access it at that point. When it does, it'll go and access the more detailed file about how to do step one or step two. >> There's still more to skills. There's That's the one part, but the other part is it can contain uh scripts, Python scripts. And so, it's very useful for like Like MCPs are good, but they're very token hungry. Like you need to kind of load all the tool definitions, and the model needs to operate it. So, let's say you want to extract 10,000 keywords, and then you can only extract 100 keywords per API call, for example. Like you need to do 100 API calls. That would destroy your context window and you run out of context on cloud. You can make a Python script that will do these API calls for you and save everything into a file. And it just runs outside. It's just like a piece of software that runs, and then the model just has to press the button to run it, basically. Maybe just put a variable which is like the main keyword or whatever you want. It will just run. And the point is that you can essentially get more done outside of the limit of the token windows of these LLMs through that. So, for example, an example of a skill that we used that has a script is the thumbnail one. So, it's like if you see the thumbnail for this podcast, probably created by that. It basically creates the background with Nano Banana, and then it overlays one of our photos on top and edits it onto it. And to edit it onto it is a Python script. It's not the LLM doing some magic or whatever. It just has a script that uses. I can just grab a photo and say, "I want it at this position on top of this image." And then essentially just plays with the X and Y of where the image is and moves it around. Um and so, that's a script. And so, that's the power. It's like you can combine these MCPs, these SOPs basically, and traditional programming for deterministic outcomes. And that's unlocks the I I want to add something here because, you know, when you start talking about traditional programming for deterministic outputs, like I think there's probably a few non-technical people out there who are thinking like that just went over my head. What the hell is he talking about? Okay. I want to like explain a few much more simple business use cases why this is relevant. Um There's two things. One is you can share these processes, these skills with other people. So, Gale, you created the newsletter skill file, showcasing newsletter skill. You shared it with me. I then used it to create a newsletter. Mhm. Great. But, when in doing so, I also wanted to edit the output slightly, so it was, you know, a little bit better, a little bit more to what I was trying to achieve. So, afterwards, I asked it to update the skill file to reflect the different direction I I took it in. And so, it went and it updated itself. It updated its its own skill file. It rewrote the process in here to add more information about what it could see as the difference between the output is and was in the skill file. And that is like really a key improvement versus using, you know, a project in Claude or ChatGPT to do it because I don't know what about you, but I would spend a long time making like really good system prompt and really good set of context files. I'd then run it a bunch of times and after a few weeks, what I was outputting would be quite a bit different and I would and I was like, "Oh, I've got to go and like spend all that time to update the system prompt again and it's it's a hassle." But now you just say, "Update your system prompt with or update the skill file based on that the output I got." You're going to employ it. You you essentially fix it with them and then they learn from that experience. It's it's very similar. That's the problem with projects. It's like they kind of stuck and then you have to re-download the files, go edit some text file. Like, [ __ ] that. I don't want that. And quite often you just settle, right? It's like it's kind of like 90% and you're like, "Oh, I just have to tweak it at the end, etc." And you just it's not worth the effort to re-download to slightly tweak it and it still won't be perfect. But, if you just say, "Look at everything that I gave you as feedback and what propose some edits to the system prompt, for example." Then, that's low effort after running a scale, basically. And that's kind of the point. It's like I tell people, "The first time you run it, it will be 70% as good, just the same as like a project." But, the point is like you will run it and it won't be good. And then, you tell it, "No, change this, change that, edit this, edit that." And you tell it, "Okay, now fix your instructions." And next time, it will be 80%. And you do that again, and it will be 85%. And it's kind of like diminishing return, right? As you go, it's not like it ever goes to 100%. Um but, you get to a point where every output requires less time, which means that frees up more time for more things. And you end up essentially leveraging your time more and more because the AI takes more burden away, you know? Which is exactly how it should work with an employee, right? You know, you you have to invest all this time when they start to train them up and share your process and like how you like to do things. And then, probably the first time they do it, it's not great. And you know, it needs quite a bit of feedback. But then, the next time, it is slightly less feedback and then slightly less and slightly less. And then, eventually, they can more or less do it themselves without too much hand-holding from you. And that's that's exactly what AI has replicated. Yeah, and that's the thing. It's like you're basically creating digital employees, or rather, kind of like specialized freelancers that know how to do one task well when you create a scale. It keeps improving. I would say it's like it's not too far It's not as proactive as an employee would be. Like, it's not going to spontaneously tell you how to make it better or look at your competitors if you don't tell it or whatever. Uh which I think eventually will come. Um but, in terms of like improvement rate, it's not so far off from working with junior people on these kind of marketing tasks, at least. >> It's like it's not even working with junior people. Like, it's it's cuz in a way, some of the things that capabilities do is like it's very, very senior. But, it's more like uh I mean, it's exactly what it is. It's like working with a robot that has no common sense. Like it's very smart. It has access to all the data on the internet. It's relentless. It works 24/7. Um but like it really does lack some basic common sense sometimes. Um so you have to steer it a little bit. Yeah. Yeah. It's like I don't think it's going to replace you but like you know, I was talking to team from Ahrefs. Uh and he's like you know, Dmitry who is the CEO of Ahrefs like forces us all of us to use cloud code and do this. It's like it's mandatory at this point and create skills etc. It's like everyone it's like you need to do this this year. Like if you don't do this this year, you're like the boomer who didn't know how to use a computer that arrived in an office in the 2000s basically. That's about the same. Yeah. They will like as painful as it probably is for all the non-technical folks uh in that company at the moment, they will be thanking them thanking their CEO so much in a year's time for that. Because yeah, this is this really is the future. Yeah. You have it. It's it's non-negotiable. And it's like let me ask you. I mean you didn't really write newsletters before but like how long do you think it would take you to write a newsletter now? Like how long does it take you versus how long would it have taken you if you did it without Even with the chatbot. Let's say a chatbot. If I would even with the chatbot like an hour or so to do it back and forth like to really really get it down. Like I'd probably go get a few examples of ones that we've done before. Maybe like a few examples of some newsletters from folks that I know do good newsletters. Um brain dump a bunch of my thoughts in there. You know, get a shitty version and then do like three rounds of feedback to it and then eventually I get that, take it and copy paste it and you have to upload it into Bento and send it. Whereas now You didn't explain that part actually. You didn't What What does it do exactly? Well, yeah. Whereas now uh with a skill file is like here is the transcript of the video which is based on Go and write the newsletter. And if there is any kind of direction I want to give, I can give it, but it's so good it usually doesn't need it. So, it will sometimes ask some clarifying questions. I may get the opportunity to steer it if I want to, and then it will create it. I can edit it within Claude code in the text file there. I save it, I tell it it's ready to go, and then it actually goes and connects into Bento and uploads it as a draft. It doesn't send it. I will never let it send it cuz that's like could go ter- ter- ter- >> doesn't let you anyway. Like it built it on purpose so that it can't go crazy. Bento, by the way, not sponsored at all. It's an email tool very similar to sort of active campaign except it's kind of like an indie tool and it's it's very like AI native. So, like they have one of the most robust MCPs of out of all of these email tools out there. And it's just it just works very well with this stuff. So, if you want to Claude code to go upload your draft email in into it, like it it knows exactly what to do. It gets all the fields correct. It's ready to go, basically. So, all I would do at that point is just send myself a preview, check it, check the links cuz, you know, I've made that mistake before, not putting links in there, and then send it and it's press send in inside Bento and it's it's good. There's actually one thing in this code that you don't I don't know if you even understood it does that because I built it. But, the point is in through the Bento SP you can upload images. So, when we have like a thumbnail or something like that, actually the image needs to be hosted somewhere else. So, within this code I built a sub process that is uploading images. It's connecting to our Cloud Flare. It uploads images to Cloud Flare, gets a URL back when it's uploaded it, and then when it generates the HTML for the email it puts the essentially the image uh directly inside the HTML, which seamlessly adds the image to the email. And that's the kind of like sub workflows that you can build within these skills. You will understand if there's an image or not. I will just figure it out basically. And that reminds me cuz there's a I have a complaint about this. Uh so >> Okay, go ahead. I don't know if it's Bento or if it's like the deliverability thing, but it suggests that images should be or the whole email should be below 100 kilobytes. That's a bit hardcore, yeah. images which are bigger than that, it's not so good. So, it's almost like you would want a image compression process in there. You don't even need like a third-party service to do that. You just tell Cloud Code to compress the image and it will like do it for you to do it, but It's not that simple. >> is that it's simple to No, no, no. It's not. No, no, hold on. Hold on. Hold on. Wait, wait. It's simple to compress the image in Cloud Code. I think what you're saying is to do that as a skill is not so simple. No, that's not what I'm saying. What I'm saying is the reason Bento tells you you need the images below 100 kilobytes is because for mobile specifically, people who are on like 3G It's not images below 100 kilobytes. Mhm. Is the whole image below >> finished that, but the it doesn't matter. Text, text, no space. Um the point is that um Cloudflare detects the size of the viewport. So, if it's easier on your phone, it will actually serve a smaller image automatically through the service that we use. But Bento, when it tests, it tests through desktop resolution, um which is allowed to have bigger images than than that. Um so, the point is Bento is actually not very smart in the way it detects these things, but in reality, Cloudflare fixes a lot of that stuff for you by compressing the image automatically and also serving the right size for the right viewport. Um so, it's like Yeah. It's not >> So, so you you you chose to ignore it basically cuz it's not necessary. I I'm I'm not saying we pass it all the time. It's like if the image is really big, sure, but It does come off like you know, if you have a 4 megabyte image, it's like seems a little over the top. >> It's a bit much, but like I mean, you can just ask Cloud Code. You can be like, "Hey, before you update the upload the image, uh just compress the image." And it's like honestly, you just tell it that, it will just install the Python library, update the scale, and then next time you run it, it will just do it. Just test it before so the image doesn't look like [ __ ] but that's it. Yeah. Um, that's the beauty of it. It's like, you had that the time it took you to explain this to me, you probably could have edited the scale, right? It's like And that's the point as well. It's I think that's quite important. That's an important distinction because it means you don't need to go back to me when you need things like that done anymore. You can literally just tell the chatbot and it does it. And I think that's an unlock that a lot of people don't have yet. Like, I even see it with questions and like accelerator etc. Like, I would say it's less and less, but 20 to 30% of questions and like, just ask Claude. Like, it's like just just tell the bot because it will actually solve it for you even if you don't understand the tech behind it the same way you did not understand the tech behind the dashboard. It's fine. It will translate your non-technical language into technical stuff and specs and do it for you. And we are that level of abstraction now for at least simple things. Like, you're not going to build a full SaaS in one prompt, but simple marketing workflows like that, easy, honestly. Reminds me of I saw this video years ago. It was talking about electricity generation and how they saw this future of like abundant electricity. And if you were just able to imagine a world where generation was so cheap, um, what uh, benefits that would bring and what problems that would what new problems I would face. And then the problem stopped being like, how do we make energy or electricity? Uh, and and the problem became how do we transfer it around or transmit it, move it. And so it just creates this whole different perspective of the world. I think we're we have a similar situation like that with with coding and almost like work to an extent. Whereas it's so cheap and so fast and so easy for anyone to build anything these days that utilizing existing code or existing processes >> It doesn't matter, right? You built a a V1 of this dashboard. It was much more simple, but it worked. And I was like, "Ah, do we need to like, you know >> You pass it to me. I'm like, "No." >> [laughter] >> Put this on GitHub and share it and da da da. And you're like, "Dude, just [ __ ] rebuild it." And I was like, "All right, fine." But I think also >> out of working version in 10 minutes. Like, that was it 90% of what that did. So. But I think also it's quite interesting because it means that you because you're not a developer, historically you've solved most of your problems without code. And you kind of trained at looking for a solution or SaaS or something like that, something that you can use off the shelf that will do 80% of what you want and then you kind of have a shitty system to make up the last 20%. Or some manual work to >> to change your head around that. You can code. Everyone can code now, at least personal tools that you run locally. There's really little risk if you don't apply it on the internet. And you can solve your problems with code now. Uh even if you understand none of it. Provided you just learn the tool. Which, how long did it take you to kind of like feel comfortable using Cloud Code from the day you opened it to like, it's okay. Like, I don't Well, it was probably about three or four weeks, but that's not of usage. That of That's like a total time. I was probably in those three or four weeks used it like four days or something. Um Mhm. And it was really one when I spent a whole morning, like three hours, messing around with this dashboard and then starting to like build out context files and things like that for other work that I had really like, "All right, this is my new thing now." And what As soon as I had that mental shift from like, "All right, I'm going to stop using all these projects I have in the Cloud Desktop app um or in Gemini Gems and just rebuild everything uh basically anytime I came up with a task that I needed to do, Yeah, I've got I've got I I would migrate it over to Cloud Code. And then, you know, that was Friday. It's Tuesday and like most of the stuff I use it's on here now. Yeah. Yeah. Okay. I can if you want I can show you one of the skills I just built recently cuz I think people need to see more use cases. So let's do that. So actually what I'm going to do is I'm first going to share a Chrome tab for Marketing Pros. So Marketing Pros are recruiting company we work with in South Africa. They recruit marketing professionals. It's cheaper than the US and people are pretty good. That's like the high-level thing. And the thing is like one thing that they need to do right now is they need to run some ads. Like people who go on their website if they saw ads they would get more leads basically. That's simple. Everyone should do that. We've never lost money doing that. Um >> You're you're talking about retargeting ads like Yeah. I mean it's not really called retargeting anymore because it's not pure retargeting like it all broadens a bit. But the idea is like yeah, people who interact with their brand on social as well, that kind of stuff. So this is my VS Code. Looks very similar to yours. Chatbot on the right. Whatever content in the middle. Files on the left, right? It's like pretty simple. And so I have this skill called Meta Ads Meta Campaign, sorry. And you can see literally I started this the thing by saying slash Meta Campaign and I just gave Marketing Pros. And the thing is like it's quite hard to come up with a good angles for ad campaigns, right? So like how do I catch people? How do I stop the scroll etc. And how do I make it like interesting and fun while still selling my product? And so I built that skill that basically I will create a folder which you see here Marketing Pros as the run. And it kind of like scraped the site to understand what they do. It also you know, we talked about scripts. It has this script that basically scraped their CSS. So it gets their colors for example. So you see it got all the colors. It also if I actually go in research you will see that it actually downloaded their logo for example. It's just that's what you do a Python script for for example on the skill. And again, I don't know how it works. I just told code code make a script that does that, right? So anyway, we use it. By the way, their logo is way too big on their site. I discovered that right after I wrote it. Anyway, it made a brief and it was like, "Oh, they're basically a staffing company in South Africa." Does it look good? My input is looks good. Um then after that it makes itself a little to-do list. I interview me on the uh on this. So, actually you can't really see the questions but it's like, you know, who is your primary buyer? Have you run ads before? Do you have stuff that worked? What is you know, what does um what's your best customer success best testimonial like ask me a bunch of questions basically. And based on that it basically writes a whole actually has some notes here. You can see it just it writes this file basically uh based on all my answers. And then after that >> It's creating its own context file there basically. >> Exactly. We're building context but it's painless for me. It's just like a question thing and I just click the right answer or I type something. Uh I don't have to think too much. I just give the URL and I just pick some answers. Then it has an agent that basically role plays as the customer. So, it actually spawns a sub agent and it's like, "Hey, you uh a struggling agency owner trying to grow your agency and you want uh like you you have clients, you have demand and then you don't have people to execute and then you have you hire people and the clients quit and then you have too much too much staff and not enough etc. Like, what are your problems etc." It basically does all that brainstorming slash role playing. And the other one is a market research agent that goes and read Reddit and stuff like that and see what people complain about basically. And you can see like it it this is the prompt that it gives to the agent. This is the prompt it gives to the market research. Like, you know, search for like Reddit, search for all of that etc. And it just comes back with a customer profile. So, it's just, you know, "I can't hire fast enough to keep up with client demand and the people I can't find either cost too much or burn me." Like, you know what I mean. You know what I mean. So, again, it builds context that way. It builds context also based on the research. So, you can see it writes a whole research. Talks about Upwork, talks about Fiverr, talks about the problem with the offshore, uh talks about good marketing talent being hard to find, all of that context, right? Um then after that, it just actually run a bunch of extra searches cuz it decided to do that. Uh and it makes a strategy. And again, I didn't give much so far, right? I answered a few questions. And uh I just run. After that, it basically run these and came up with a campaign plan. So, you can see for example, like I gave it a budget, etc. It came up with angles, uh which is burned by offshore {slash} Upwork, marketing only South Africa advantage, and three X your capacity for half the cost, basically. And kind of high-level things. And presented that to me. And my feedback was also You see, I'm typing a lot on these things. I I yes, let's go. And then essentially, then it brainstorm each ad set and how it's going to do things. So, you can see it picked some templates. So, in my skill, actually, I have uh if I go in assets, I have these templates that I curated manually. So, for example, the Apple Note one. And so, it it does look at these and it just like knows which template it can use. So, in this case, for example, we have the before after, right? So, if you go in before after, you check the examples, you can see like it has examples of ads that you can use from that. And so, it it basically comes up with the ads and it's like, "Do you like this? Is this good enough?" I'm like, "Yep, looks good. Create them." So far, I wrote about 20 words, right? Then, what it does is it uses the Nano Banana API through a Python script again. And what's really good is because it can also upload in the prompt the actual uploads the logo, it does all of that, etc. And essentially, it generates the whole ad campaign for you without doing anything. So, it generates the copy first. So, for example, not VAs, marketers. Actually, the other one I think was a bit better if I check the copy. Yeah, done with Upwork roulette. I thought that one was really good, actually. Um and the point is it has like three versions of the copy, like short, medium, long that you can test, link descriptions, and CTAs. And you can see it basically generated ads. Like for example, this one is really cool. Uh like a text message one where people go back and forth, "I I hired this agency, etc." You can see some kind of like whiteboard one freelancers I hired this year ghosted bad work missed deadline. South African marketers I hired all still here marketingpro.co. These are pretty good. I tried that one before and South Africa was different marketing pros. Um the point is yeah, literally everything is generated on its own and you can see I have a lot of these copies. This one is actually >> look great. I mean if you're listening to the audio version of this like they look good. Like they look like a any other ad you would see in your uh Facebook stream. >> I would say so and the thing as well is like when it runs let's say you don't like an output. I think at some point it generated an ad and it was there was a typo. Yeah, you can see there oh there's a minor text glitch. And so there was a text glitch on this one I think. And uh it regenerated it. So it's like oh there was a glitch. And it's like boom I regenerated it it's fixed now. Uh and that's it. It just it it looks at it and it's smart basically. But yeah, you can see this before after try try risk free. Uh I had the listical one and I had the quotes for example. I mean these are decent ads basically. And the point is yeah, that's the kind of stuff you can do with this skill. And how long would it take you to generate all of that especially because it's all cut down in ad sets with all different copies to test and the creatives in the right folders and you can just go to meta and upload these and it's ready basically. So it's like that's the power of the skills and that's why we tell people like if you don't do this now uh you're [ __ ] because I can make five campaigns when you make one or seven or something. Uh and when it's running I can do something else. And uh and so like I'm I'm more likely to test I'm more likely to run more things and to find a winner than you are if you do this manually basically. Even if my graphics are like 10% less good than the ones you may have. Uh and it's also I don't know like there's like 12 images times 40 cents. So it's like yeah, it's not very expensive basically. Yeah, I mean super impressive. Like uh you know, if you asked an agency hey design me some some ads like they would probably follow a similar process to what you've done there in terms of interviewing you, asking you questions, and like you know, okay, like a pro designer might come up with a few better things, but >> better, but not perfect yeah, it's not that good. >> It's like yeah, it's like it's not even 80/20, it's like it's the 90/10 kind of thing. Like it's way good enough for any business that's not running ads to have this their first campaign. Or if your strategy is I want to deploy, you know, dozens of new ads every day to test, then this is a way to do that quickly at scale. And if you have ideas, you can also put them in the prompt, right? Initially I put zero, like I put nothing. But if you have a special landing page, a special promo, a special thing, etc., you can put that and that's going to influence the whole process. It's going to cascade all the way down to the creative. So it's like that's so powerful, you could run it 100 times. You could be like, "Hey, like let's brainstorm like 20 angles for 20 campaigns." And then you run each one one by one and create all your ad sets that way. And then you'll have like a lot a lot a lot of stuff to test. And I did not even connect uh competitor scraping into this. I had it initially, then it became too complicated. Because if my whole context is used actually in this one run, so this was uh this was already pretty intense, but I think it's good enough already to be honest. >> So what does it cost to generate those ads in terms of your uh usage or, you know, Nano Banana API? Around $5 for this. How many ads? Like I mean, you can see there's 12 creatives. Okay. Um so 12 creatives are around $5. 40, 50 cents each, something like that. >> Yeah, around that. Um and I mean, I'm pretty sure like there's going to be some kind of uh image model that's going to come soon that will be equally good and you know, a quarter of the price. So the And but like, you know, you're spending money on ads, like does $5 really matter? Like isn't it better to spend some money? >> [laughter] >> It's weird cuz it's like we have this discussion internally. Cuz like, "Oh, should should should I I'm going to spend $100 $100 to the $200 plan?" And it's like it's because you're spending it on you know, let's put it in the software group even if it's like an AI model or API credit. It you know, we're a little bit more cautious of it, whereas you wouldn't even think about oh, I need to spend $100 to pay a designer to do something. Like it's it's just that's what you would pay. Yeah. >> Um so, it's almost like there's a mental shift needs to happen there as well. Yeah, but I mean you can see these are real outputs that you could really run and it's like these skills are available uh should be available in AI Accelerator uh at the time at which we release this podcast and I just shot the video for it. Yeah. Let let let's actually try and talk about that for just a sec. Um so, the AI Accelerator is our course/community where we talk about how to build all these things, how to use it. We give you all these skills that we've created um inside there that you can go and use that today, I believe as this is going out. Um there's, you know, we're uploading multiple of these skills every single week into the accelerator at the moment. We do weekly group coaching calls there with other business owners. It's a good way to connect with just anyone else who's running a business, who's implementing AI in their company and, you know, some folks bring their team in there as well. You know, there's a lot of uh debate at the moment, you know, AI traffic is a good example there about like how do you get your team excited and using AI? Well, you know, we hopefully will help give them some structure to be able to do that as well if you wanted to do that. >> Yeah. If you're interested, um it's the only thing we do, only thing we sell. This episode's not sponsored. Head on over to authorityhacker.com/aiaccelerator and you can find all the details there. Yeah. So, I mean going back to the topic of skills, that's really kind of the hot topic right now. And it's really kind of powerful like you talked about sharing and stuff. You can actually upload these skills to GitHub and then you can connect these skills into Cloud Co-work. So, let's say you have staff that really is like I can't do the terminal. Like some people would be like that. They would be like uh you know, some It's some person with like uh glasses with a chain around their neck. Uh no, it would be like I can't do this. Um well, the actually these skills are usable inside the Claude chatbot and Cwork. And so, if you actually build them, they don't all run perfectly, but we had some members that have been using them directly inside there and skipping the VS code and terminal setup. And for the other teams, I it's you know, I do think most people should learn, but I understand the constraints as well. And so, there's a way to build some kind of like essentially company level you used to make SOPs for humans to read and do. Now, basically everyone's a manager and is managing agents and is managing their own library of SOPs for their responsibilities to be done. And then it's just uh it's just their job to maintain that, basically. That's the that's working in 2026. Yeah, I mean, instead of that being in your brain, it's now just in a skill file. Well, it was supposed to be in an SOP before, but let's be honest, most people didn't do it. Um so so, it's like I do have one one thing to ask [clears throat] here though, cuz we talked about Cwork, which is the new feature, something between Claude and Claude Code, uh which is in the Claude desktop app at the moment. It's basically a dumbed-down version of Claude Code that they're trying to make more accessible um for non-developers, for knowledge workers. Isn't there an argument that people should just wait a few months till that like develops and becomes more robust and not to worry about the terminal and, you know, Claude Code? I think Claude Code will always be the edge. Like the same way as like you can do these things in Claude Code, but not necessarily in Cwork today, there will be something that you can do in Claude Code in 6 months that you can't do in Cwork. And it's like if you want that competitive advantage, if you want to actually be able to do more than most people right now, then it makes sense, because it's not that difficult. It's really just a chatbot in a terminal. Yeah. Um it's like the ratio of effort to reward It still incredible. It's one of the best things that you can learn right now. One of the best things you can spend 2 hours on. And you do actually have a course inside the accelerator which teaches you how to do this. But even if you don't want to buy our stuff like you can go on YouTube and like there are people who have like videos explaining how to do some of this stuff. So like it's like we really believe that this is like a key thing that everybody listening to this needs to know needs to do this year. Yeah. So it's like yeah, you could wait 6 months and get the same capabilities of the expensive models in the cheap ones. Like Gemini 3 Flash. It's about as smart as the best models a year ago. Um maybe even better. But the reality is if I put you on Gemini 3 Flash for your day-to-day work, you're going to be like I want Opies back. Um and then you'll want it because it just unlocked so many things for you. Same thing's going to happen and that thing is not going to change. It's just going to keep moving the goal post and everything's going to evolve and you'll be able to one-shot your dashboard instead of spending 2 hours on it by the time Co-work can do what you can do in Clo Code today. Mhm. So up to you, but I think that the productivity gain is so big that the people who are not willing to go to the edge are going to lose out anyway. The same way as like people who stay on chatbots. You'll just like slide like you might as well just stay on the chatbot. And I think that you know, when we were in the SEO industry like we we talked for so long about how big companies and big sites have such an advantage over small one-person companies or small small sites. It feels like this is almost like a great equalizer in a sense, right? You know, small medium companies who are using this technology effectively are a are are going to be able to outcompete not just catch up with but outcompete bigger companies who are going to be obviously much slower to implement this across their larger teams and get everyone on board and using it correctly. And they're going to be worried about more safety, security, governance stuff Whereas a small business can that you'll be able to be a lot more nimble. I think it depends. Like for example, at Meta, Instagram, right? I was watching some videos from like product managers at Instagram. Product managers at Instagram, they had to kind of like, you know, essentially make a proposal, make a presentation for a new feature, etc. Now they are forced to vibe code it. No developer involved. They vibe code it in a test environment. And then they present the feature built. And then it's like if it's good enough, then it's passed to the dev team who vibe codes it properly. >> [laughter] >> Um and then that's how it works. And so like that's not how every company works, but big companies are jumping onto this fast already. I feel like if you're a Meta and you know, you have the best of the best people who are paid the big bucks. Like you know, you can issue a top-down command. Like everybody has to do this or else. Yeah. And you know, you have smart people around you. They'll get on board. There might be a bit of resistance, but you can get it working. But They're all excited. think of like the average company. Not like full of rockstars. Like you know, with 20,000 people trying to make that happen. Like it's going to be harder. Yeah, this we see we see it with some people we consulted with. For example, like the engineering engines are resisting and so on. Yeah. I mean, the guy who built flood bot, right? He just got acquired by Open AI. Supposedly for [ __ ] ton of money. Single guy. Like alone building and it you know, according to his stats from the guys from Codex, he uses more than like entire teams. Uh he uses more tokens than like entire teams sometimes. And so yeah, there's an opportunity. It's just like it's so funny because I know a lot of people who still listen to us that they're still kind of think in terms of SEO, etc. But the edge is not there anymore. Like SEO is a is a mature uh declining market. And um and the edge is there. The edge is like, how do I build stuff? How do I do things faster? How do I do good marketing? Like these ad campaigns that I showed you for example. Um using these tools with a minimal drop in quality, but a massive improvement in productivity. And and the value of these things is still pretty high because most people can't do it. That's the thing. You're kind of fighting against the curve of people who also adopt these these tools, and you want to be ahead to create value. And that's what the edge is. Um and and that's why Yeah, and if you're a marketer, that's that's what you need to do. I see I see tons of CEOs of agencies and so on now that like, "Oh, if you're a big ClickFlow user, etc., we want to hire you. Like, send us your CV, etc." They're they're desperate for it. I'm telling you, yeah, if you went to Ahrefs and you told them that you're you're marketer and a big ClickFlow user, your chances of being hired will probably be pretty high if they're hiring, for example. Um so, yeah. Great. I think we'll leave it there. Any final words of wisdom? No, just just [ __ ] do it. Like, it's last last chance. Last last call right now. Uh by the end of this year, if you haven't done it, you're officially a boomer. And uh and we can't help you anymore. No, I'm kidding. We can, but you know. We are going to be around this year to help you for free on this podcast. And we're going to be covering this in a lot of detail. We'll have more dedicated episodes to it, how to set it up, how to optimize it, you know, all that kind of stuff. But, you know, if you want to get in there right now, then head on over to authorityhacker.com/aiaccelerator, and you can get all our stuff in there. It's currently live. Thanks for listening. Um I know this is a little bit rambly and less structured than a >> podcast, yeah. >> usual episode, but um we we really just do feel it's so important that people have to take note of it now. This is not an early adopters thing anymore. This is a an everyone thing. Um and now is the time. So, thank you for listening. If you have any thoughts on this, please head over to our YouTube channel and leave a comment. We do read them all. Um drop us a like, subscribe while you're there as well. That really really really helps us out in the YouTube algorithm, so we appreciate everybody who's done that. And uh we'll see you next week for another episode.