Leveraging AI
Dive into the world of artificial intelligence with 'Leveraging AI,' a podcast tailored for forward-thinking business professionals. Each episode brings insightful discussions on how AI can ethically transform business practices, offering practical solutions to day-to-day business challenges.
Join our host Isar Meitis (4 time CEO), and expert guests as they turn AI's complexities into actionable insights, and explore its ethical implications in the business world. Whether you are an AI novice or a seasoned professional, 'Leveraging AI' equips you with the knowledge and tools to harness AI's power responsibly and effectively. Tune in weekly for inspiring conversations and real-world applications. Subscribe now and unlock the potential of AI in your business.
Leveraging AI
250 | The No-Code Way to Use Claude Code For Creating AI agents for Business with Tim Cakir
📢 Want to thrive in 2026?
Join the next AI Business Transformation cohort kicking off January 20th, 2026.
🎯 Practical, not theoretical. Tailored for business professionals. - https://multiplai.ai/ai-course/
Learn more about Advance Course (Master the Art of End-to-End AI Automation): https://multiplai.ai/advance-course/
Claude Code sounds intimidating. It has the word “code” in it, after all. But what if we told you it’s one of the most powerful (and shockingly accessible) ways to create AI agents that automate entire business workflows, without knowing how to code.
Join us for a live, step-by-step masterclass with Tim Cakir — AI trainer, YouTuber, and the kind of guy who casually manages 50+ agents to run his operations. You’ll learn how he uses Claude Code to automate content creation, training, sales prep, and more.
We’ll break it down from the beginning: what Claude Code is, how it works, how to set it up, and how to build agents using skills. All using real-world examples that businesspeople (not developers) can use immediately.
About Leveraging AI
- The Ultimate AI Course for Business People: https://multiplai.ai/ai-course/
- YouTube Full Episodes: https://www.youtube.com/@Multiplai_AI/
- Connect with Isar Meitis: https://www.linkedin.com/in/isarmeitis/
- Join our Live Sessions, AI Hangouts and newsletter: https://services.multiplai.ai/events
If you’ve enjoyed or benefited from some of the insights of this episode, leave us a five-star review on your favorite podcast platform, and let us know what you learned, found helpful, or liked most about this show!
Hello and welcome to another live episode of the Leveraging AI Podcast, the podcast that shares practical, ethical ways to leverage AI to improve efficiency, grow your business, and advance your career. This is Isar Metis, your host, and we have an incredible episode for you today. Now, everybody, literally, everybody is talking about building agents and how they're gonna change the world and so on, but the reality is very few people actually. Build agents and even fewer people build agents that actually do something meaningful in their businesses day in and day out. Our guest today, team Ecker, has built over a hundred agents that work in his company regularly and do different functions in his business. And through this process, he became so familiar with what's good and not good that even fired more than 50 of the agents that he initially created. So he's been evolving this for a while now, to make this episode even more interesting, we are going to talk not only about how to build the agents and show exactly how to do this. But we're also gonna look at it with a very interesting platform, which is Claude Code. Now, from an adoption perspective, everybody knows Chacha piti. Some people know Gemini because they get it through their, uh, Google membership, but a lot less people are actually using Claude, which I personally really, really like. And out of that small people that uses Claude, a much smaller percentage uses Claude Code. And the vast majority of people who use Claude Code are coders. But the reality is there are huge benefits that you can gain by using Claude Code. Not coding, and this is not exactly what we're gonna look at today, is how to use cloud code not coding because I don't know how to code and I'm still gaining a lot of benefits from it. Now, the reason most people don't do it yet is because either they don't know that it exists or it has code in the name and people assume that's the only thing it is good for, which is not the case. And this is one of the reasons I'm really excited about this episode, because you're gonna learn a new tool that most of you probably do not know, and you're gonna learn how powerful it is and what can you do with it without writing code Now. The other reason a lot of people are not using Cloud code is because until not too long ago, you had to go through a weird install, which we're gonna show you how to do in order to get it to actually up and running. But the reality is, as of about a month ago, and Tim, correct me if I'm wrong afterwards, uh, you can now run cloud code on the web, which means you don't have to install anything. There's still benefits of installing it, uh, but you don't even have to do that anymore. So in today's episode, we're going to explain to you the benefits of Running Cloud Code and how to use it to create incredible agents that actually do functions in your business and provide value. Now, our amazing guest, Tim, brings. And really huge variety of experiences that makes it highly relevant for our episode today. He held top leadership positions, including CEO and COO in many different companies, which means he understands how a business actually runs and what it takes to run an effective business. But he was also a professor in two separate university, which means he's really good and passionate about teaching, and he's currently the chief AI officer and the founder of AI Operator, which is a company that helps businesses in implement AI in an effective way. So this combination makes him literally the perfect person to teach us about cloud code and how to create agents not being a technical person. So you don't need any coding or technical skills to do this, and that makes me very, very excited. So Tim, welcome
Tim Cakir:to leveraging ai. Well, thank you so much for the kind introduction. It's an absolute pleasure to be here, sir. Thanks.
Isar Meitis:Uh, you know, you and I spoke several different times. I, I'm a big fan of your, uh, YouTube channel. Uh, we're probably gonna talk about that in the end where people can find you, but you're, you're really a magician when it comes to doing these kind of things, but let's really start at the more higher level. Mm-hmm. What the hell is cloud code and why do people need to care about it?
Tim Cakir:Yeah. I think that, uh, there is one issue about cloud code is that they called it cloud code. Yeah, yeah. I think it's better than
Isar Meitis:GPT. At least it has a name that means something.
Tim Cakir:Yeah. Yeah. It is just the code. I mean, CLO is, is great, but is is, they call it CLO code and then everybody, like I tell'em, I'm like, how have you tried CLO code? And they're like, I don't code. I'm like, well, you're missing out. Or maybe it's good for me'cause I use it and not others do. But no, I like to share, I want everybody to use it. I want everybody to get the productivity gains and the efficiency and the incredible. I guess you call it magic, I call it just obsession about, uh, obsession about AI and what it can do. Um, and so cloud code, uh, was basically a, a way to interact with the cloud models in the CLI in the command line interface, which is the terminal in a computer. And that's very scary, right? And because there is no ui, there's no user interface or the user interface just text, it's a dark screen. It looks scary, right? It looks absolutely terrifying. I even sometimes I open, I'm like, oh shit, am I working here again? Like I just work 90% of my time now on the terminal, you know? And it's like, it's so funny, like we've done such UI designs and so on, right? And then now we're going back like to using the terminal. Yeah. Uh, so code code is really an incredible. Let's call a product to, um, to tap into, uh, large language models that are Biro. So code Opus 4.5 being the la the latest one. Um, and what's, why is it so powerful? Because it runs on your terminal. It can create files, folders, it can run scripts, and it can really control everything on your computer, right? Yep. From including browser to the applications to the settings of your computer itself. And because of that, it takes the, you know, a level higher in, in, in, um, in control and efficiency and being able to achieve things than a chat GPT, right? The chat, GPT is great. You have to connect things, you know, you, you click on connectors, clo itself, you click on connectors, but with cloud code, it's in your computer. It's, it's, it's literally everything that you have in, in your computer that you can run. Um, and, uh. In a nutshell, it looks scary. It sounds scary because of the code, if you don't code, but what I've realized with Cloud code is that it's right now the most powerful product for building systems, business, operational, running systems. Um, and, and, and, and I'm, I'm still mind blown, you know, when I speak about it, I'm like, what the f is it? You know, it's just like, it's still incredible what we're living and it's just, you know, the beginning of December, um, and quote code is, is is just mind blowing. Absolutely.
Isar Meitis:Amazing. So, so let's really show people, first of all, how it looks like, and then we can start diving into examples of how you are using it to create these systems and processes. Uh, and again, people Yes, I, I agree with everything Tim said. Like, what is the terminal? How do we even get to it? And it's really simple. You both on Mac and in pc, it's, there's a button that takes you there and, and you can, and you can have the terminal. Uh, and as it, as Tim said, it looks like we're back in 1985. It's like a dos prompt, kind of like environment. Uh. But it works. And it is extremely powerful. And for those of you who're like, oh my God, I don't want it to mess with my computer. Uh, you do as long as it's controlled. And one of the amazing things in Claude models in general, and specifically Claude 4.5, is that it's code adherence, which is a professional term to saying it does what you fucking tell it to do versus, uh, kind of does what you want it to do. It, it, it is very good at that. So it's only going to do what you tell it to do, and it is not going to do anything. You do not tell it to do. So the fear of like, oh my God, this thing can take over my computer. In theory, if you tell it to you and you define exactly what you want, it will. But if you tell it to do one, two, and three, create this file, copy the information from here, bring it there, activate this thing, and send this message, then that's the only thing it is going to do.
Tim Cakir:Yeah. And I think that it has really good, um, security settings. Uh, you can set the settings so that you can decide on what it can do without asking you each time. Um, and it's also incredible at really asking you when it's necessary and when it doesn't have enough information, it's like, Hey, I'm about to do this, but I'm not sure, like, you know, what do you think about this plan? And you're like, oh, okay, I like the plan. Go execute the plan, or let's change the plan. Right. The planning mode of it is just, it's just mind blowing
Isar Meitis:in, in general, I find Claude to be the most collaborative model out of all of them. That really makes you feel that it's a consultant and not just an execution arm of your dreams. And that makes Claude like an amazing partner for anything. This as well.
Tim Cakir:Yeah. I think that in, you know, if we talk about models very quickly before I show things, you know, I use Claude, um. 4.5 opus, uh, the most at the moment. Um, but if I'm doing a business strategic task, like planning, you know, Q1 2026 for my business, I will still switch to GPT 5.1 Pro. Right. Which it's only on the pro people. Uh, so not the plaster 20 bucks, but the 200 bucks. Yeah. And people tell me, oh, I have the pro. I'm like, no, no, no. You don't have the, the pro how much you pay 20. Yeah. Well, you don't have the pro. Uh, so GBD 5.1 Pro is just incredibly amazing at business, business logic, business strategy, and so on. Um, but everything else now, I'm, I'm definitely a Cloud 4.5 Opus fan. Um, and it's, you know, uh, if you pay for Cloud Max at 20 x, which is$200 a month, you don't hit the limits. Uh, and I run that on my cloud code. So just FYI for everybody. Be careful, you know, I'm gonna show you things now, if you run it on the API, the cost can go up very, very quickly. Yeah. So you do wanna be on a subscription package, on a Max Cloud max plan, a 10 x or a 20 x plan.
Isar Meitis:Okay. So let's dive right in. Yeah. Let's see how this thing looks like, how to set it up and how to create magic with it.
Tim Cakir:Awesome. Let me share my screen. Uh, can we see my screen? Yeah. Yes. Awesome. So, so this is why I said it's scary, isn't it? It's just, it's it's just a black box, right? Uh, so let, let's
Isar Meitis:take, let's take a step back. Yeah. How do you get this thing? Yeah. How do you open terminal on your computer? Yeah. So for people who don't know what it is and
Tim Cakir:Absolutely. So I run a version of the terminal called I term two. It's an application that you can download. Um, you can run the normal terminal. The normal terminal doesn't have some of the little gadgets. I mean, you know, now you see these as cool gadgets'cause you can see, you know, uh, the GPU and, and, and what it's doing. But on the normal terminal you don't see much. So it's a little bit cooler than just the terminal itself. There's also another option that I was into for a bill bit called Ghostie with doublet ghostie, uh, which was also a terminal tool, which is really good. But you know, you just go on your spotlight in your search spotlight if you're on a Mac or in a Windows, uh, you know, to your search and you go right terminal. Right? And if you want a little bit of better experience, I would suggest I term two, uh, is a great little app. Yeah.
Isar Meitis:Cool. Yeah. Yeah. I, I will say one more thing, not to confuse people, but I would say anyway, if you are using any of the vibe coding tools, whether it is Replicate or mm-hmm. Lovable or whatever, uh, there's a terminal version in there that you can run as well, and it has slightly better user interface than this thing, but overall, it does the same stuff. So if, if you're starting with nothing, then just running the terminal in the computer could be your easiest starting point.
Tim Cakir:Yeah, I mean I think that the difference there is, uh, I think we, we spoke about this when we first met, but you know, I was saying that yes, in the Rept terminal you can run CLO code. Yeah. Uh, I think you tried it since, didn't you? Six minutes
Isar Meitis:after we close the call. I already had it running. Yeah. It's one of the best
Tim Cakir:hacks people don't realize is that you can open up Repla and not pay too much for rep tokens and only set up your environment and then run the terminal quote coding the terminal and inside Repla and then you can see the preview, which is great. But you know, there we're really talking about coding and building a product. Yeah. That you wanna be in that folder and you wanna be in that repository. But here, what I really love. Is that I'm on my computer. Yeah. So the first thing that I did when code Code came, um, and I was like, oh, what's this crazy stuff? Right? I was like, Hmm, okay. And it was a couple of sleepless nights as usual when anything new come, uh, it's a sleepless nights, you know, I, I love it. Um, and the first thing was like, oh, okay, it can do files, folders in my computer. And it was years that I've been wanting to tidy up, you know, my desktop documents and, and all that kind of stuff. And I just said, Hey, can you gimme a strategy? And I was like, great, can you implement that? And it changed names of files and images and videos and put them in folders and it just kind of start cleaning out my computer. I was like, I. Oh, crap. This is, this is very good. You know, I want, I've been wanting to do that for 10 years or so, and I never did it. And, you know, I just piled shit on top of shit. And then it, it was, it was putting all the PDFs somewhere, naming them, reading them, telling me what they are and really creating different folders for me. I was like, wow, this is, this is really like, we're starting to see real agentic, agentic support assistant, whatever you wanna call it on my computer. Um, so here's, here's the terminal, right? I term two. I term two, running my terminal inside my terminal. And it's, it's a, it's a black box. It's a black screen. Lemme see if I can make this a tiny bit bigger for people maybe. Yeah. Uh, so it's just a, a black box. Um, and then you have to install code, code on your computer. That's very easy. You can actually go on, on, on, on Chrome or in a, in a browser and write code, code installation. It's a, it's a very small snippet of, of some, some words and some, some kind of codes that you just input here and you let it run and it installs it, it asks you to log in. Right. So I'm not gonna do that'cause I've already done that. It's very easy. It's, it's this five minute process. Um, and then what I'm gonna do now is I'm just gonna tease you a little bit and then I'm gonna show you what I've built and then we'll go into, into how to build what I've built and, and, and this type of things, if that's okay with you, ISAR.
Isar Meitis:That's awesome. Sounds like a great plan.
Tim Cakir:So, so what I'm gonna do is I'm just gonna launch Claude by saying clo. So I'm just gonna say, Claude, and I'm gonna enter, and as we can see right away, I get the question asked if I trust this, uh, folder, right? Because, uh, Claude code may read, write, or execute files contained in this directory. This can post security risks. So only use files, hooks and bash comments from trusted sources, meaning prompt injection. As we, as we know, if this was some files and folders that I didn't know, and then there, there was some, some kind of hacker trying to get my information, it could kind of do that. But it's my computer. I know it's clean. You know, I, I've, uh, I've been working on my computer for, for really long, um, even if I change computers, iClouds, you know, so, so I know what's in my computer, so I'm gonna accept yes, proceed, right? And then that's it. We get this little, this, this little, you know, uh, I love it, this little thing, you know. And here we go. This is closed, closed code is ready, and I have Claude on opposite 4.5 with a closed max plan, right? As I was mentioning, you don't wanna be on the API, you're gonna pay a shit ton of money if you do that. Uh, and then I'm on my user. I'm in the. I'm in my whole computer. I'm not even in a folder, but what you could also do which I'll show later, you can run it in a specific folder. Right. So I do run it in very specific folders. Like I have a sales folder, I have an onboarding folder, I have a customs folder, and I run it in different places. And what's great about this is that I can open up multiple tabs and I can run four or five Claude at the same time. And it's like, oh. So I had an assistant, and now I have multiple assistants, and each can run multiple agents and each can have different skills, Claude skills. It, it just gets a bit meta. Like, it's like I run orchestrators that run other ones and they run each other. And it's just'cause like what? And you know, I was reading about hyper productivity and it's scary because it's, it's quite exhaustive. It's like, oh my God. Like I have to, I have to babysit all these agents. You know? So, so I think it's, it's tough. It's not easy to get to the usage that I am, but I'll show some simple tricks for everybody to, to start getting there because this is the world that we're really living in. But in 2026, I do believe that this is going to be one of the most powerful things is to build systems. That can run without you. Right? And you wake up in the morning, this is my dream. I wake up in the morning, which I'm kind of doing a little bit of that, but I wanna wake up at 9:00 AM not, you know, I wanna be on my desk at 9:00 AM I've dropped my kids to school. I'm at 9:00 AM uh, in my desk. I open it and I have, I've done all of this stuff. Um, bless you. I've, I have all of this stuff. I've done all of this stuff. These are things I was a bit unsure, you know, I wanna ask you some questions. Great. What is, what did it do? I it did all the follow ups, it sent the proposals. It's, you know, it's, it's created some, uh, contracts for some clients and so on. And then it has some clarification questions. Like, Hey, I wasn't sure about this. You know, like, can you check that email? Can you check that document? And you check it and then you say, okay, you know, glad you didn't send this because here's some feedback, right? And then you give that feedback. But then that feedback the next day, I don't want it to ask similar feedback because it knows it. So I wanted to learn, and I want it to be iterative learning, right? Like, so that it keeps, it keeps learning every time I give it feedback. So I kind of build something like that. I'll show in a second as well, but this is the world we're gonna live in, guys, and you know, it's just gonna wake up throughout your whole sleep and you went to school, dropped the kids and stuff, you came back, you've had multiple agents, you know, 50, a hundred agents actually doing work for you, right? This is definitely happening. Like I can show you in a second, you know, um, it's just that I still dream of a little bit more, more proactivity from these agents, right? Yeah. I still have to run them. I can schedule them, but the, the more proactive is coming. I know that because we saw that with chat, PT Pulse, right? On the ProPlan we have something called Cha PT Pulse, which every morning it gives me like some incredible things about me, about my search history, about my day, about my calendar, and it kind of is proactive, right? So, so I think we're gonna get this proactive right now is very reactive. So I have Claude. Claude ready. It just, it's scary because you dunno what to do. It's, it's asking you like, it's waiting for me. It's like, okay, well I'm waiting for you. What are we gonna do? Right? So let's say what, what we're gonna do is we're gonna go and we're gonna launch, let's, let's launch a guide about Claude code. How about that? Right? So I'm gonna write a 10 page guide about Claude code, right? And I wanna write, I wanna write this. So what I'm gonna do is actually, I, I would kind of go to the folder where I have content and guides, but I'm not gonna do that. And what I'm gonna do, hopefully this is gonna work. I'm gonna talk to it.'cause I, I talk a lot to, to these things now and I don't type, so I'm just gonna, I'm just gonna talk to it quickly. Uh, go to my, uh, guides folder, uh, inside, uh, my content folder in AR operator and run my uh, guide system. And let's write a guide, um, about cloud code, how, uh, how cloud code with Opus 4.5 and the cloud max plan. And how cloud code people think it's for coding, but it's not. You can run business operations and you can do a lot of things and so on. You know, do a proper research and make sure to run all the agents and, and to run the actual, uh, guide system workflow, right? So you still kind of have to babysit a little bit and you have to tell it like, make sure to run my workflow, right? Make sure to find the agents, you know,'cause if not it, it still wants to please you and is gonna go and do it on its own thing. But I already have a system for this. So what I'm gonna do now, I'm doing shift tab. As you can see, something is changing on the bottom left and. Edits own so that it is kind of, it accepts like you automatically accept some stuff. I'm gonna take it to plan mode, right? Because I don't want it to go and actually start doing things. I want it to plan first. It gets very powerful when we put things in plan mode, right? So this gonna take quite a bit. And
Isar Meitis:again, to switch to plan mode, you just used, uh, shift tab. Yeah. Yeah. So just use a, a keyboard shortcut. There's no, again, like anything fancy to do that you just switch the mode that it's gonna operate in.
Tim Cakir:Yeah. Shift tab. Shift tab. And then you get to plan mode. You see, uh, it is green on the bottom left. It has like this, this kind of pose button. Is it a pose button? So it's, it's more like, Hey, I'm not gonna take actions, you know, I'm just gonna plan, you know, I'm not gonna go change anything. Uh, and what we can see, you know, we can open up this whole thinking with control O, which gets really big. Um, you know, and it looks scary. This is where exactly it starts looking scary because like, oh, okay, what is this? Actually it's not that scary.'cause this is just like, oh, it's finding folder, right? It's going to my documents and my documents is found my AR paid folder, right? My company name folder. And then there it found the content folder and then it opened that up and then it's looking at certain things and so on, right? And as you can see, I just asked something, but it wrote its own it. It wrote its own prompt. Find the AR paper project on the system, look for a folder or project called AR paper or similar. We didn't find a content folder and a guide sub folder, look for any guide system and so on, right? So it kind of gave itself some task and I was like, okay, this is what I'm gonna do. And then it keeps thinking, I'm gonna close this'cause it can look a bit scary and let's go to the normal look. Right? So that's like the detailed look of seeing what's inside these 360 lines, these 376 lines. What is it doing inside these? You just go control, oh, it gets even more scary than what it is. So you close it, you're like, oh my God, lemme not see that. Right. You know? But it's good. I do recommend, you know, when you get comfortable, I do recommend to read these things and you know, it might, yeah. If,
Isar Meitis:if you wanna understand what the model is doing behind the scenes, and by the way, it's the same thing in like all the regular tools. Like if you're in Chachi PT or a Clot or Gemini, it says thinking. I'm like, okay, what are you thinking about? If you click on the thinking Blinking thing, it's gonna show you exactly what it's doing. And then the, the benefit of that is you understand how the model works and how it thinks, and that usually makes you a better prompter because you know the steps that it's going to do and you can guide it just like Tim did now. Like, oh, go look for this folder. Go look for these agents. Why is he doing that? Because he looked previously and said, okay. It's kind of like struggling with that. If I tell it what to do, it will know what to do. So it, looking at this actually gives you a better understanding of how the models work and then you can be a better prompter because you can know how to guide it.
Tim Cakir:Yeah, absolutely. And I don't, it's not just about being a better prompter, it's about this thing that we see in the news, isn't it? It's like, it's saying that's humanity's getting dumber. Right? They're getting dumber and kids are getting dumber because they let Chachi BT do all the work and they just get the output and then they go with it. Uh, but the second you open the reasoning, the thinking, right? The thinking I always say, because it's the reasoning and you open that up and you start reading it. And in every model that you're using, if you can read that, you get smarter. Yeah. You get absolutely smarter. I see things that these things are thinking or like reasoning and I'm like, whoa, I didn't think about that. Or Let me, let me bring more information. Lemme bring more context. Right. It becomes really an, uh, a partner, you know? Yep. And not just like, God, do this work for me. And then I, and I, yeah, it's okay. Let me go. No. It's like, oh, well we work through things together and I'm learning and the next time I know how it's gonna kind of think and how it's gonna reason. And I start understanding different models. It's, yeah, it's very geeky, but yeah, I am obsessed about all this stuff. So, so, uh, as you can see on the bottom, what happened, this is quite a new ui, uh, user interface kind of feature is, you know, it did 1, 2, 3, 4 things like project type, audience use cases, pricing focus, these like a tabs, and then I can submit and it's great. It's asking me clarification questions now, right? So, so, okay. Do I wanna standalone deliverable, like top level folder, like AI safety startup pack, which I, I've already built that before. So it's like a, do you want a complete package for distribution or do you wanna research the guide pipeline? Right. Do you want just a, just a, a quick guide about quote code? Or do you want something for distribution? I, I potentially want a standalone deliverable, right? So I'm gonna click that. So I entered that. So, so basically we tick that, so you can also tick things if you wanna see'em, you can do a space bar, which I've already done, so no. But here, who is the primary target audience for this quote? Code guide, right? Business operators, I think, uh, entrepreneurs. Founders. Yeah. I think I would go, I'm gonna go for entrepreneurs and founders, right? Because those are the people that I kind of, I kind of talk to, so I'm gonna go, yeah. Entrepreneur, founders. What specific business operations or use cases should be emphasized beyond coding? Right here? I would potentially spend a bit more time, right? And tell it to the things, but I, I'm just gonna do something quickly. I'm just gonna tell it so that it kind of finds my systems. Make sure to go read my systems. I have a, uh, this guide system, which is about content creation. I have a sales system, which is about, you know, running a CRM and so on and, and how to sell in my company. I have a onboarding system. After I close the deal, how do I onboard a client? And then I have a training system. How do I train people and create the training program, the custom training program for our 12 week AI first mindset training program, review all of that. And then as a bonus, because, um, I'm on a very important, uh, call right now. Also, can you highlight, um, the system building system? Oh, thanks. Alright, so I kind of said that'cause I, I wanted to go and, and check these things, right? So for those
Isar Meitis:of you who are not watching the screen and just listening the way this looks like, again, think about the poorest user interface you can imagine. So dos level, so there's just this little, there's different rows and you can pick from them by scrolling to them with a keyboard and selecting them. Uh, or you can go to the bottom one, which is just like a. Open line and type whatever you want to type. What Tim is doing is what I'm doing as well. We're voice typing everything just because it's a lot faster. It requires a decent level of talking skills, but not much because these tools are pretty good at understanding what you want. Even if you didn't structure it as well as Tim, uh, it you get much better at this. The fact that Tim has a YouTube channel and I have a podcast makes it a lot easier to say what we want in the first time around in an organized way. Uh, but you will figure it out as well, and it just significantly faster than typing. And to be fair, I find that I express myself a lot more, uh, with more details and color when I speak versus when I type. And so that's another benefit because then the AI gets more context. But now that you've done this, let's see what the system does.
Tim Cakir:Yeah, absolutely. I just wanna add something to that is because I'm still kind of practicing the, speaking to the machines instead of typing to the machines. Because guys like every, you know, guys and girls and everybody, you know, like get ready because we are going to speak to the machines more by voice. You know, the, the new open AI product hardware is gonna come, is definitely not gonna have a screen, right? So we understood that. So, so it's not gonna have a keyboard. We're gonna speak to these things and you're gonna have a robot in your house, you're gonna speak to it. Like these things aren't gonna happen. So I think it's a great time now to practice speaking to these things. Um, so I'm still not very good at explaining what I want and sometimes I go, but it's okay.'cause it understands and it's some, somehow it cleans it up, you know? And I think by practicing I'm getting better at it.
Isar Meitis:Yeah.
Tim Cakir:So I'm gonna accept what I just said there. I'm gonna be like, okay, yeah, this, this is, this is the good stuff. And then it said, uh, pricing. Should the guide focus specifically on Cloud max? No. All right. Uh, all tier comparison, right? So we went all tier comparison. I'm gonna submit all this information. So I've submitted all this information. It asks, you know, what was the four clarification questions? We answered them. Um, and now four or five, right? And it's now going to do the work, right? Uh, and you'll see the minutes it's spending and the tokens that it's spending. But I'm not paying per token. I have a, I have a subscription plan. Um, and you know, if you're listening and not watching, it kind of gives you its plan. So it's exploring the operator systems because I told it, go look at my systems. You know, about the guide, the sales, the onboarding, the training, my system, building system, which is the brand new one, uh, I just done last weekend and I'm still working on it. And it was like I was building so many systems. I decided to build a system that builds systems like I was like.
Isar Meitis:It's kinda like, kinda like the Claude skill that builds Claude
Tim Cakir:skills, right? It's the same type of concept. Yeah, exactly. I took that approach. I was like, you know what, why am I keep designing, you know, these systems? I should have a system that asks me question and goes and designs the system from the first four or five systems I've already done. Right? And, and I just finished that and, you know, I'm still working on it, but I finished kind of the first draft and I'm like, oh, this is getting meta, this is getting cool. I even tag, I think tropic on, on one of my LinkedIn posts. They didn't come, but I was like, guys, you gotta see this. You know, it's like I'm taking a bit next level now. Yeah. Um, so, so what it does, it gives you the tasks and it has four tasks here. It's gonna explore, then it's gonna design the guide structure, then it's gonna write final plan for quote, quote guide, and then it's gonna execute the guide workflow with all agents. Right. So even before going to my guide creation, uh, system, it's going to do these three tasks, which is the explore, the design, and the write the final plan for the quote quote guide, which is great because this is not AI slop, this is exactly what I do. These are my systems and this is my context. And so the guide is gonna be about exactly what I do. And people are like, oh yeah, but you got AI to do your guide. I'm like, yeah, well, AI looks at my context, asks me questions, and is gonna ask me more questions. And I build these systems for the last, I don't know, couple months or whatever. Right? It's definitely very, very custom content to the context of, of Tim, the AR operator and my systems.
Isar Meitis:Let me ask you a pause, you and ask you a question. You are sending it to all these resources, like your systems and your agents. Yeah. Uh, can you talk a little bit more about what these are? Yeah. Like what are these systems and what are the agents that it's actually using? Uh, because that's a big part of this Yeah. This secret sauce, right? It's like the clot itself is actually using these additional resources in order to do the thing that it's doing.
Tim Cakir:Yeah. Yeah. So, I mean, this is a perfect timing. I just wanted to launch this because it's gonna take, you know, a few minutes anyways, and I, I'll, I'll change my, uh, screen share. I think you can see my browser now, right? Yep. So I had closed code open for you guys. You know, you just go to clo clo.com product cloud codes, you can find it. This is like the kind of, uh, the kind of codes, uh, that you have to, um, put it in the terminal to, to, to download it. And then, you know, you can learn a little bit about it. It might be scary, but here's the plans that I was mentioning and so on, uh, which is cool. Um, and now before we get into those systems, now on cloud itself, you actually do have here code, right? So if you click on code now here, it opens another tab, which is code code, but it runs on the cloud. Right. Uh, uh, it can run on an environment that you give, actually can start now running inside your also system, uh, and your GitHub re repository, which is another tool where, uh, we put code in. So this is quite newish. So we know that what's happening is that they've realized that the usage of cloud code and now they're like, okay, well let's offer it on a browser. Let's start offering in different things. So there is gonna be a product that is gonna be better in UI and it's not gonna be the terminal. So you're not gonna have to be scared, but I believe that the biggest power still is in that terminal. So, so, you know, I'm still there. Um, so because you asked that question and I had prepared this, of course, ISAR, uh, so this is my, I never doubted you, Tim. So I prepared this quick thing with cloud, with cloud code. I said, Hey, you know, can you build something that shows my systems. And it is like, oh yeah, of course I can build you a whole thing and then build me a whole beautiful thing that I'm gonna talk about. So, AR operator systems architecture overview, right? So all of this, that what you're gonna see runs in my computer in folders, right? They have agents, they have uh, skills, they have cps model context protocols, they have all these things, but it all runs in my computer, right? Um, so this is my new meta system, which I'm very proud of myself, like I'm proud of myself. Finally, like I'm taking a whole December, like almost on just focusing on this, right? So we've closed all our cohorts, uh, Q1, uh, clients are ready. I have a few more training, uh, to finish before Christmas, but I'm like focused. I told my team and my guys, I'm focusing on systems, you know,'cause it's just like. It's gonna help me scale in 2026, you know, so I build a system builder. So this system builder is quite simple. It's the meta system that builds the systems. It has five core agents, it has an orchestrator, a questionnaire, a matcher, a generator, a validator, which we'll look into it. There's five simple agents. You know, the orchestrator actually does the whole work. The questionnaire comes and asks question to the human, which is me, to make sure that it doesn't kind of create its own, uh, thing, but it's, it's from my brains and stuff like that. And then it matches things like, um, I created blueprints from the existing systems that are like templates, blueprints, and it matches the new system. That I need to a blueprint and it says, oh, you already have this type of blueprint so that I go even faster. And then it generates the whole system and then it validates it. So these are five core agents that work on these. And then there is like these little factories, right? So I have an agent factory, I have a skill factory, a closed skill factory, a folder factory that has to create the foldering system. I have a, a workflow factory that creates the whole workflow, that has a different agent so that it knows how to run. I have a script factory so that anything that it needs to be code, right? So that it's deterministic and not non-deterministic. Because as we know, uh, large language models are non-deterministic. And that's why you don't get the a hundred percent each. Uh, same time, uh, same, um, each time the same input, the same output, sorry. And that's the problem that we're all facing with large language models. But you can fix that by running scripts and scripts that are already defined and, uh, the deterministic. And then I have one that creates all the read me files, which is. Files that explains the, the things, right? And then a, a one, uh, a factory for schemas, right? Building schemas of, of different things. CPS codes and stuff like that, right? So, and then this is the blueprints that I was saying there called the archetypes here. Uh, you know, which is one is a pipeline, one is a journey, one is a production, one is a program. So the pipeline is my sales pipeline. So I made that a blueprint. The journey, uh, the journey is the onboarding, is the onboarding one. Uh, the production is the, um, content one, the guide one, right? And the program is my trainings program. And for, for archetypes, um, I think it's, it's quite good because, you know. Most things are gonna be like kind of a pipeline or kind of a journey, kind of a production kind of program. If something doesn't match, I might create a fifth one, you know? But these are my blueprints at the moment, and I have, you know, a three phase process. Discovery is about 20, 30 minutes. And then, so it's not this, you know, people think, oh, I'm gonna build an agent. It's gonna be, you know, and if you do that, you're gonna get crap agents because you just build something that is very generic. But I spend, I spend hours on building these systems and then people are like, yeah, but you spend so many hours. Yeah. But I spent 15 hours building that training system, or maybe now about 30 hours that I've spent. And it's, you know, I've served about, you know, about was it 250,$300,000 of clients with that system? You know? And it's like, it's okay. I'll spend the, the 30. Yeah.
Isar Meitis:Yeah. The, the ROI is very obvious. I have, I have a couple of questions. Yeah. Just diving a layer deeper to get people to understand what it is so we understand it has. Uh, agents and it has factories.
Tim Cakir:Yep.
Isar Meitis:Can you walk us through what is an agent and how you built it and what is a factory and how you built it? I think prototypes are pretty obvious, and I think the phases of production are pretty obvious. Uh, I think the things that people are scratching their heads and like, okay, how did you create this, uh, yeah. Organization or questionnaire or, or matching agents. Uh, and where, what did you create them with? How did you create them and where do they live now that you've created them?
Tim Cakir:Yeah. Yeah. Um, just before that, maybe I'll, I'll just finish off on the system. Yeah, sure. And then we will dive deep, because, because I absolutely wanna show you that, but I want people to understand that, you know, in, in the front end, in a nutshell, in an overview, it's much simpler than, you know, then we might understand because I, I think it's, it is quite simple. At the end, you're gonna see, in a second you're gonna be like, oh my God. He, he, he just made it sound so cool. And it's simple things. They are simple things, you know, it's processes, SOPs, and then job descriptions. You know, it's like I create processes and all these processes go into a system and that system, like, who's gonna run the system? Well, I need 10 people. And those 10 people are agents and each agent has a job description. Yeah. It's that simple. You know, like, I mean, it sounds simple when I say it like that, but. So my sales system, same thing. You know, it's about sales and then, you know, you can see where things live. I'm gonna show you the backend in a second. My onboarding system, you know, and, and then, you know, I know how to do these things and it knows it's a 14 day engagement journey. The onboarding, my training's a 12 week, it has three phases. It's all mapped out. The guide system that we're just running, it's, you know, five to 10 page guides, two to three case studies, five LinkedIn posts, three email templates. It's gonna do all of this about that guide that we ask about quote code. Um, and this is only seven agents running this thing. Uh, it was about 36 agents yesterday, and I, I, I kind of optimized this and I fired, you know, 29 of them again, you know, uh, because I added a lot of new ones, I added these ones, I added these five core agents, and, and then I was like, you know what? This is all my systems are much simpler and efficient, and this was. Kind of cumbersome. It, it had 30, I don't know what, and, and they were like, it was a bit too much. And I, I was getting 40 page guides, which were, were very good, but maybe it was, it was overkill, you know? Yeah. So I that, yeah. Um, and then, you know, I built that guide system that can build guide systems. You know, this was one of my most exciting thing, but I'm gonna show you now, um, the backend. Right? Um, alright, so let's go in the backend again. Uh, but this time, if you don't mind, I'm gonna open, I'm gonna open a visual studio code. So I'm gonna open an IDE, right? So, uh, where people code again, right. But I'm not gonna code. Yeah. Right. And why I'm gonna open this is because you can read files a little bit easier, right? Um, you know, and, and I want, I want us to read some files. So I, I went into my.cloud folder, right? This is a folder that is in my computer. And inside this folder I have all my cloud code things, right. So I have, you know, I have my guide system that we just talked about, right? And I have all the agents here. So you were asking about the agent. So let's, let's get the first agent that we actually running in the backend right now. Right? Which is the, the, the guide orchestrator. Right? So I just opened this up. I'll close this to make it a bit cleaner for us and maybe, let me see if I can make this a little bit bigger. Yeah. So this is, this is an agent. And, and people are like, what? This is how, how, how does an agent supposed to look like anyways? Nobody knows, right? Um, nobody knows. So, yeah, so I think it looks like this, you know, it, it has a name, it's a guide orchestrator. It has a description. It's a meta agent that orchestrates guide creation with five phases and seven agents. Creates focused five to 10 page guides. No fluff, never creates content directly launches specialized agents. So this agent's job is to be the orchestrator. It has some tools, right? It has some tools like task Read the Globe. Like these are different, uh, tools, uh, that you can have in your terminal. So they can kind of, you know, create tasks, can read stuff, you can find stuff, you can search for stuff and all that. And then this, actually, this one runs on sonnet. So Opus decided that Sunnet was more than enough for this, right? Uh, and in some, you might see that I have Haiku. Haiku is, is a good fast model by, uh, Tropic again. Um, and, um,
Isar Meitis:yeah, again, for those of you who don't know, uh, every time Op, uh, philanthropic comes up with, with a new model, so now it's 4.5, they are eventually, they, they don't always come with them at the same time, but eventually they have three models. Haiku is the smallest, cheapest, fastest one. Then there's Sonnet, which is the middle one, which is the one they always released first. And then there's Opus, which Opus 4.5 was just released last week, uh, which is their biggest, more capable mm-hmm. Uh, and also most expensive, uh, model to run. But because team is running on a prepaid plan, he doesn't care how much it costs, because as long as you don't run to your end of your allowance, then you are fine. And then you can run Opus as much as you want.
Tim Cakir:That's exactly it. That's exactly it. And you know, sometimes I go to these agents folder that I'm like, oh, okay, let me switch this to Opus, or things like that. But, but Opus helped me. Opus 4.5 helped me, especially or not in the guide system, sorry, in the latest system I built. Opus 4.5 helped me in this one, I think it was Opus 4.1 that helped me, or it was SUNNET 4.5 when I did this, you know, and it decided that was Sonet. I'm fine with it. The output is great. Yeah. So, and then as you can see, it has a little bit about the description, what it's supposed to do, as we said. So this, by the way, this is quite important, um, because this is like the tag, the metadata about this agent, right? You know, if you just, uh, if an a, if a model has to read something, it will just read this to understand if it needs to use it or not. Sadly, these gets loaded in the context window, but with closed skills, which is a new feature, you can have skills like this and you have this metadata that it doesn't read anything else. It just reads this and it knows that, oh, okay, I need to use this skill. Let me go read the other stuff so it loads. I'll, I'll
Isar Meitis:pause you. I'll pause you for one minute. Uh,'cause I don't want to jump into cloud scale. I probably need to record a whole episode about cloud scale because it's, yeah. Invite
Tim Cakir:me again. Yeah,
Isar Meitis:yeah, yeah, yeah. But, but I be aware of what you wish for. But, but Claude skills are, think about every automation you've built, basic automations like a custom GPT. But think about packaging it in a way that it knows how to call it just when it needs it. So you don't need to go and copy the files and send it to your custom GPT Uh, Claude Code says, oh, this requires this kind of data analysis. I have a skill that knows how to do it. And for me, as an example, I have one that knows how to query my podcast if I wanna know something. When did I talk about this thing in my podcast? Uh, it knows how to do that, which otherwise it, it wouldn't. Uh, or it has one that does things based on my, uh, brand guidelines, or it has one that does very specific data analysis for me. And like Tim said, the, the important thing here is instead of. Blocking your context window, which means it's consuming part of the memory you can use in order to do the actual ask. You wanna do. It does not unless it is actually required. And then it goes and opens, looks, basically opens the book, reads what it needs to do, and then does what the book tells it to do. So these are cloud scales and it's very, very powerful and the fact that you can run them inside of anything Claude, including cloud code is, is really, really cool.
Tim Cakir:Absolutely. Absolutely. And I think that this is still the beginning, but you know, we do have the problem of the context window, right. The memory that I can remember. Yeah. It's very small still, you know, and, and you know, Gemini is doing 1 million, uh, tokens and, and you know, uh, we do have, uh, cloud models that are 1 million, but they're not served to everybody. Uh, you know, uh, but we're supposed to get, hopefully, bigger contact windows very soon. We
Isar Meitis:have about 14 minutes, so let's, uh, let's go. I will shut up.
Tim Cakir:Yeah. No, no, no. I love, I love I love it. And we'll give value, we'll give value very quickly now, so, so this is an agent, right? Uh, it has some principles, you know, these are forbidden. Don't not write content yourself, you know, and, and we don't get the pink elephant in the room problem anymore, right?'cause prompt adherence, you know, if you say, don't do that, it doesn't do it. But before, if you said, you know, don't do that, it's like, oh, I'm gonna go do that. You, she's like, oh, he
Isar Meitis:talked about it. He probably wants
Tim Cakir:you to do, but it's, it's, it's like my four and a half year old daughter, you know, you tell her not to do it, she'll do it, you know? But I think that AI now, like large language models that are now maybe 7, 8, 7 years old, maybe not, you know, they, they act a little bit more like they know that they'll get in trouble if they do it, so they don't do it. Yeah. You know, a little bit better. And so this agent also is aware of the other agents, right? Because it's the orchestrator. It's like, Hey, these are your buddies that you're gonna come in and then you're gonna use these buddies, you know, the guide, researcher, the guide, the outline, and so on. And then it has a phase, it has a total time. Yeah, it has a whole thing that is like, it's like a process, right? It's like a, yeah.
Isar Meitis:So again, to make it simple for people who are not looking at the screen, the, it's simple English, like there's no magic. No. And it's just describing in a well structured way that I'm sure you used AI to help you structure to explain what this agent needs to do, how to do it, and what it shouldn't do. That's basically what it is.
Tim Cakir:Just in plain English. Like, like a job description. Like you're hiring someone. Yeah, you're gonna give'em a job description. You're gonna tell'em, Hey, what you can do, but you can't do, what are the tools that you have access? Here's the logins, right? This is your job. Go do your job. Right. Uh, so this is the same thing, and I, and I recommend everybody. Um, you know, when you're getting agents and so on, write a job description, you know, like onboard your job, your agents, you know, give them the same quality that you would give to a good team member that you've hired for a lot of money. Right? Um, that's important because that's, that's what sets you for success. Um, and, and then it has, you know, the actions and so SOP, right? So a standard operating procedure, it knows exactly how to create a project structure, discrete folders. It has, you know, it tells it what to say when it's done. And some decision trees, some quality focus and some things that it should remember, right? This is an agent Question. Question about
Isar Meitis:this. Yeah. Just to verify, I assume you have a, either a Claude skill or something like that, that helps you write these in a well
Tim Cakir:structured way. Yeah, so it, it's not even skills in most of the things in writing, it's, my agents do a really good job because I'm breaking things into different, uh, agents. So I don't have one agent that will outline and write the whole thing. Right? Yeah. I have an agent that will do the research, will write it to a context file. Then the next agent that is gonna create the outline will look at the, uh, output of the researcher agent, right? And then it's gonna create his own context saying, Hey, like I looked at that. Here's the outline that I think, and then the next agent is gonna take that outline. That's that outline that is, yeah. So the instructions
Isar Meitis:don't get too complicated and too cumbersome because something very
Tim Cakir:much more specific and focused. You know, one is a good writer and then the writer I will say, this is how I write. Here's some examples. Right? And then I'm not eating up on the context window neither. And by another question, because
Isar Meitis:we're in a. Id. Mm-hmm. If you wanna reference a file, so I said, this is how I write. You wanna give it three examples? Where do these example live? Or you just give it a link to your folder inside your computer?
Tim Cakir:Yeah. So in, in, in a lot of cases, I do have, uh, the path name to the file Yeah. Where it is, because it knows in the computer. Uh, but if, if you also wanna put an example, you could put another file and say, here's the file. Uh, but also, uh, you can, you can kind of embed it inside here. You could say, here is my tone. You know, you could kind of put a section. Yeah, here are the words I like to use. Here are the words I like. Yeah, yeah. Understood. You can kind of do that.
Isar Meitis:No, but I was thinking more of, let's say you create one that's writing proposals and you want to give it examples of two of your winning proposals, then you'll put a file to give it a pass to the file. Yeah. Got it. Okay. Exactly.
Tim Cakir:Yep. Um, so, so this is an agent at the end of the day, and let's just go back, uh, a stage, you know, so this is an agent inside my guide system. As you saw, there's a bunch of other agents, like this is the enhancer, right? This is the one that is gonna write some case studies and examples for the guide, right? Uh, and is gonna ask a bunch of questions. So this is the guide system, it's, it lives here, has agents, uh, has some other things like a knowledge base, as you were saying. So, you know, here's my program, here's my company training program. Here's our blueprint, here's the company methodology, here's my style guide. Actually, as you can see, there's a Tim Checker style guide. There's a Tim Checker writing style, right? And it knows, because in the agent you can say, Hey, I do have some style guides. Go read those, you know? Uh, so you're keeping this in a knowledge base. So the guide system has a knowledge base. It has a memory as well, right. So it writes in the memory, it has some schema, which is empty at the moment, has some templates, you know. Uh, so workflow is state templates and project metadata template. So to write those things and so on. Each time the same, these are, these are adjacent files, right? Uh, and has, you know, here's, you should have the year, month date, the topic, and so on. So it kind of gives very small kind of template structure. Yeah. Structure. Yeah, that's a good word to put it. Thank you very much. Uh, and at the end of the day, the, the more important thing here is the workflow, right? So I showed you kind of, you know, the, the beautiful thing earlier, but at the end of the day, this, it's the five phase workflow using the seven agents, right? So this is why, if you remember when I spoke, I said make sure to use my guide creation workflow.
Isar Meitis:Yeah. Because
Tim Cakir:then it does, it reads this first it says, oh, okay, well I have this, or I have an agent that I'm gonna first work with, right? And then it's guide researcher, and it's the orchestrator that works with it. Okay? Then I, it works with the outline, then it works with the right, but then the polish, then the market, then the enhancement, right? So this is basically
Isar Meitis:the handshake agreement between the different agents, right? That's what makes the content move from one agent to the other. Is this workflow.
Tim Cakir:Yes. Because it knows this step. I'm gonna work with this guy. Yeah. The step two, I'm gonna do this, but I do something very, uh, different than a lot of people. And I think people really love that on my LinkedIn. And the other day I showed is I don't let an agent as, as we were just saying earlier, I don't let an agent speak to the next agent because the only speak
Isar Meitis:to the orchestrator,
Tim Cakir:they only speak to the orchestrator, but they also only write files to context files. Right. Because the output, it would be too much, and then the context window would go, but because it writes it to a context file, and then the next agent, instead of looking at thing, it just picks up that context file that was written from the previous agents. Yeah, yeah, yeah. Right. And I'm able to keep much better, uh, again, in
Isar Meitis:I I we're short on time, but I wanna explain what you said because it's important. The context window is your limiting factor, right? This is the amount of data that can go in and out, out of a single conversation.
Tim Cakir:And it gets worse. And it gets worse, right? Yeah. And if, if you take.
Isar Meitis:Yeah, let's say now it's the fifth agent and he wants to know what happened in the first four steps and has to read everything that happened in each one of previous agents. It's basically gonna run out of memory before it can do the thing that it needs to do. And what Tim is doing, it's having, the only thing that gets transferred is basically the output versus the entire thing, and this is what he's calling context files obviously go, Hey, here's what I created. This is all you need to know. Like you don't need to know how he created it, what the data that is. You don't need to know any of that. Yeah,
Tim Cakir:just read this. Here's what I created.
Isar Meitis:Use this as your entry point to do your task, which saves a lot of space and efficiency and tokens and a lot. There's a lot of other reasons why this is a good idea.
Tim Cakir:Brilliant. Exactly. Yeah. So that's a little hack that I've been doing. So that's basically one system, you know, it has, it has a master workflow, it has agents, it has some memory, it has different things, it has templates. And this runs in this folder, right? And I have a bunch of these, you know, I have a memory system, which this, this is basically every agent and every time I run quote code, this is something new that I, because I read the article a few weeks ago and I was like, oh my God, I need systems that get better because I can't just keep, you know, working on my system. But instead, if I get feedback, this memory system takes memory, takes things and saying, oh, Tim said this, Tim, you know, gave me feedback on here. And then I'm building this memory system because then the next, uh, phase it's looks at the memory system and takes the learnings and does the learnings, right? Yeah. And, and it kind of updates the agents as well as we go along, right? Yeah. And so, yeah, so every system, as you can see, has same agents bin schemas skills, you know, uh, and so on, right? So, so they all kind of work on the same thing. All my systems, you know, have similar, similar things, and the agents are, are just there. Um, it's, you know, it, it's simple. I say, yeah. So
Isar Meitis:I, I wanna, I wanna really summarize this and then, and then let people know where they can find you and follow you and work with you. But at the end of the day, we went from, I know I want to do something. Mm-hmm. To breaking this down to, okay, if I had to hire people to do this, what would I do? I will hire a person that will be their manager because I need five people and I don't want to manage them. Yeah. And then I will need a person that does this, a person that does this, a person does this, and then you literally go in and explain what each and every one of them does. Just like Tim said, it's a job description. A very detailed job description, because it's gotta follow that. Exactly. It's not gonna take any initiatives. Uh, so you gotta tell it exactly what it needs to do. As Tim said, the smaller you make it, the better, because then it's very specific and then hand it off to the next agent and it's not gonna get confused with what it needs to do. And then create the plan of how does the handshake work once you're done, who do you hand this over to? And then when you run the process, you ask quote unquote, the process to use this plan and then use the agents in order to complete the task. And then what happens is. Then the magic happens, right? Because when then you give it a task, it already has all these job descriptions and all the handshake functions on how to go from step one to step two, to step three, to step four. So if you think about every process in your company, you can mimic this. If you can clearly describe what each of the steps are and how the steps lead from one another, uh, which makes it so powerful and brilliant because you can apply this to literally anything in your business, and it's all 100% of it. Simple English. There's nothing here that you cannot do without writing any. Code. Yep. Tim, this was nothing short of incredible. I think what you built is mind blowing, but as you said, it's also very simple and I know that people are gonna listen to this first, like, okay, we, we lost you in 30 minutes in. Listen to this again, and you'll see that there's nothing here that is rocket science. It's literally simple English, explaining what you want. That will happen and breaking it and structure it in a very well-defined way. If
Tim Cakir:I can add something. I think it's about, yeah, yeah, a hundred percent. It's about zooming out. I was, you know, since, since chat g pt, you know, which has been three years and four days came out, I was very zoomed in and I was kind of, you know, doing all these things, prompts and so on. And then I realized if we zoom out, I, and then we start looking at this, as you said, it's much simpler as just a business with processes, a bunch of process, system job descriptions, and put'em in there and then you'll give them tools. The model context protocol, MCP that I mentioned are like APIs. Imagine it's like a login. You know, I can give it an MCP to HubSpot to my CRM and it can update my HubSpot. It can do these things. And it's like getting a salesperson. I hire a salesperson, I'm like, here's your HubSpot login. So it's the same idea. It is just we, I think, overcomplicate things, but when we simplify things again, and AI is an incredible colleague now, uh, for you to, to build these systems, you just have to very much think about. What do I do, right? Yeah. What does this team member do? How do we do what we do? You know, what do we do? Right? Because if you actually start asking these questions and you can write them down, the AI will help you build it anyways. You know, you don't have to, you know, you don't have to be a rocket scientist.
Isar Meitis:Amazing. Tim, if people wanna follow you, work with you, learn from you, hire you, what are the best ways to do that?
Tim Cakir:Yeah, I think that's the best way is LinkedIn. You know, Tim, check here. Uh, T-I-M-C-A-K-I-R is LinkedIn or my email tim@arbeta.com. Um, you know, we do have, um. Uh, training programs. We build stuff for people and so on. But we usually work with companies of at least 50 people. So we work with, with kind of mid, you know, SMBs, uh, nothing under 30 or so people. Um, because that's where we really get, get, see, return on investment. Right. Just FYI, for everybody listening. Um, uh, and my YouTube, yeah, my YouTube is a, is a new project. I mean, it's been a year, it's been something where, how I'm sharing what I'm sharing today. I share everything that I know, every failure, everything I, I fix, I try. You know, and then from there you'll find from my LinkedIn, you'll find newsletter. There's a lot of free content I put there. It's our, I wanna, I wanna teach everybody for free, but I have some clients so that they can pay, so that I can kind of also share things for free for everybody. Yes, same thing. Same thing that
Isar Meitis:I do. Gender is absolutely amazing. You are absolutely brilliant. I appreciate everything that you're doing and what you're sharing and sharing with us today. Thank you so much, and thanks everybody who joined us live, uh, and, and was in this, uh, in the backend and listening to what we're doing. And obviously if you're listening to this after the fact, come and join us in this live so we can ask questions as well. Uh, thanks again.
Tim Cakir:Thank you very much. Thank you for having me.