288 | My entire Claude setup for creating AI teams that run my businesses

SECURE YOUR SPOT FOR THE:
MULTI-AGENT ORCHESTRATION AI COURSE: https://multiplai.ai/multi-agent-orchestration-course/

What if your business could run before you even start your day?

That’s not a futuristic promise—it’s already happening. Imagine waking up to client proposals written, content created, and opportunities queued up… all without touching your keyboard.

In this episode, you’ll learn how shifting from “using AI tools” to building AI teams can unlock massive growth, efficiency, and entirely new revenue streams—without scaling headcount.

Instead of chatting with AI, start designing systems where AI works for you. This episode breaks down the exact infrastructure, mindset, and real-world use cases to help you get there.

In this session, you'll discover:

• The critical mindset shift: from AI as a tool to AI as a workforce
• How to structure AI agents, orchestrators, and workflows like a real company
• The concept of “evergreen documents” and why they solve AI memory limitations
• How to build a shared AI-human workspace that eliminates copy-paste chaos
• The architecture behind multi-agent systems (agents, skills, plugins, orchestrators)
• A real AI content engine that increased LinkedIn impressions by 147%
• How to automate proposal generation directly from client calls
• The system behind a fully automated AI news research and production pipeline
• Why “the moat isn’t the model”—and how to stay flexible across AI tools
• How to keep control with human-in-the-loop checkpoints

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!

Transcript

GMT20260427-134703_Recording_avo_1280x720 0:00

The inspiration for this episode is the fact that when I woke up this morning while I was drinking my coffee, I already had two podcast guest pitches ready to go. I had six AI. News articles summarized in my AI news application. I had six LinkedIn posts, including their suggested images, ready for me and Joyce to review. I had a client proposal together with an email to the customer as a draft in my outbox, and I had five potential YouTube shorts ready to go for me to review or for my team to review, to get posted in addition, all based on my previous full podcast, all of that and a few other things before I did a thing on my own. This is the power of having multiple agents, teams of agents working for you, not you commanding them, but you setting them up and they're working for you across multiple aspects of the business. And this is the inspiration for this episode. Hello and welcome to 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 Isar Metis, your host, and I've got a really exciting episode for you today that I wanted to do for a while. If you've been listening to this podcast in this past quarter, since the beginning of this year, or the end of last one, you know that I've been diving very deep into developing and deploying and using multi-agent orchestration solutions, or if you want, in simple terms, complete armies of AI employees across different teams. Across my two and a half different businesses that are basically running more and more things in the businesses. It allows me to do magical things. It allows me to grow in a speed I couldn't even imagine possible. And that's all. While having only myself and my incredible assistance to working in all of these businesses combined, not completely true, at least on the operational side, it's us. On my software company, I actually have a software team, and on my half company that I'm sharing, I have a partnership with another company that actually has human employees as well, but. The vast majority of the work that happens that I'm involved with doesn't happen by me, actually happens through these AI employees teams of AI employees that actually do the day-to-day work more and more of it. And it's not just about efficiencies in doing stuff that I could have done. It's actually doing a lot of things that either I don't even have a clue how to do, or I know how to do it, but not effectively. Or I know how to do it, but I don't have the time to do it because I'm running two and half different businesses. Either way, it allows me to grow the business, go after new initiative, new revenue pipelines in different ways that were not possible to me. Before I had these teams of AI employees. What I'm going to show you today is how my cloud universe looks like, how I think, what are the systems that I'm using, what are the concepts behind the scenes, how does it all connect together? And some examples. So it'll help you make it more tangible and hopefully to follow that path and do the same thing. So with that in mind, I will share my screen and I will go through some slides and some sharing of actual Claude and other aspects that I'm working on, that will help you to understand how I'm thinking, and how you can hopefully do the same thing. Before I get started, I will say one thing. This episode is brought to you by the Multi-Agent Orchestration course. It's a course and workshops for companies in which I teach everything you're gonna see very briefly now, but over eight to 10 hours of going through every single tiny component here and delivering it in a way that enables people and entire companies to implement this as well and build. Teams of AI employees that can help you grow your businesses. We sold the first two cohorts of this in 10 days. We're now in the process of selling cohort number three. That third cohort starts on June 22nd, and it's selling out fast. So if you wanna learn within the next three months how to do the magic that I'm going to show you today, come and sign up for the course. Now, before this cohort sells out, I'm gonna keep on selling cohorts, but that means you have to wait basically now an entire quarter unless you join the one that is open right now. With that, let's dive into the actual flow and the concepts that I wanna share with you today. As I mentioned in the opening to this episode, when I woke up this morning, I had two podcast guest pitches ready to go. My. Team of AI news specialist has found and summarized six AI news articles and added them to my application that I use in order to create the news episode every weekend. I had six LinkedIn posts, including images ready to go for this coming week for the team to review. I had a client proposal perfectly written based on the conversation I had with them yesterday, including the email to the customer as a draft in my outbox with the proposal attached to it, with the relevant setup in my CRM to know that the proposal is sent and so on. And I had five options for YouTube shorts. The actual videos, not suggestions based on my previous episode that I deployed to YouTube. Many other things. All of that with before me doing a thing, and this is exactly what I want to show you today, is how to build these kind of things. This is the magical aspect of all of this. Now the trick is, which most people haven't done yet, is to go from a world in which you chat with AI to a world in which AI is your actual workforce. Now, it doesn't need to replace your human workforce. It is going to enhance, accelerate, and amplify your human workforce. In my case, it is just the two of us, Joyce and myself, and literally the rest of the work is done by ai and it's growing every single day because we're building both Joyce and myself, more and more agents and more and more teams of agents that are working every day. But you can do the same thing and amplify whatever aspect and whatever team in your company. So the first thing you need to do is a mindset shift. Instead of you telling the AI what to do, chatting with it, copying and pasting things into AI chats and trying to use this in your day-to-day flow, you need to change your mindset of going from AI is a chat partner to AI is employees, actual teams that can do actual work across almost every aspect of the company. And to be fair, across every digital aspect of the company. The second thing is you gotta stop thinking about AI as a tool. Again, something you use and think about it as workforce that uses tools in order to achieve different goals. And these tools that the AI can use is basically everything you use in the digital world. It is writing documents, it is doing research, it is summarizing, it is doing analysis of financial information and any other numerical information. It is writing proposals, et cetera, et cetera, et cetera. Every single thing that you and or your team do in the digital space, the AI can do while using similar tools to the tools you are using in order to achieve these goals. Now the real magic happens is instead of building a single agent that does one thing, is building multiple agents, each and every one of them specializes in something that is very, very specific, which makes it very good in that one thing. And it also makes it very efficient from the memory that it's using because it is focusing on that one thing and then having multiple of these work together to achieve different goals. I'm gonna show you several different examples of exactly how this works, but before we dive into from the concepts we talked about so far, to the practical actual things, I want to clarify the terminology to make sure we're all on the same page. Those of you who are watching the screen, watching this on YouTube or on Spotify, you can look at the screen. If not, I will explain everything that we're seeing. So what we're seeing is a little drawing of a company, and I'll explain the terminology in the AI agent space and how it connects to what happens in real life. So the first one is an employee and an employee is an agent. An agent replaces or represents an employee who can do different tasks in your company. As I mentioned before, when you build agents correctly, they focus on one thing, and if you want them to do several different things, build several different agents and then work with them together, as we're gonna discuss in a minute. The second thing is the SOP. The standard operating procedure is called a skill. A skill is something you teach the AI how to do, and as sophisticated as it sounds, it's literally a document. Everything we're going to talk about today, the whole magic of creating these really sophisticated, incredibly powerful automation tools and capabilities is all built around what's called markdown files or.md as the, type of file that you're going to see. But all it is is think about a very simple word document without all the fancy formatting. It's just a Word document that is written in a well structured way and a skill is basically the SOP, how to do something specific, how to do research, how to write a document, how to design a presentation, how to create graphics, how to do financial analysis, how to do that step versus the second step of the financial analysis. How to review an RFP, et cetera. Each and every one of these things can be a skill, and you can have more or less as many of those as you want in order to run your business, just like you do with real people. The next one is the workstation where work actually happens. And when work happens, it's more than just one skill. It is multiple things that needs to happen together, including different tools that you need to use in order for the person at the workstation to be able to do what they need to do. And that workstation in the AI space and in the cloud space is called plugins. So plugins are an aggregation of multiple skills and tools and commands and connectivities to other sources and things like that, which enable the work to be able to happen as a package. And that package, that plugin, can actually be shared with other people in your organization. And if you really want with people outside your organization as well, it's a package of everything that's needed in order to complete a specific kind of work. The next one, we have the manager, which is in the. AI terms is the orchestrator, and an orchestrator, as the name suggests, knows how to move data and tasks around across different agents, across different employees in the company, just like a real manager does. So you could build a sequential process or one agent triggers the next. That is helpful in some cases, but it is limiting the flexibility of the process. If you are creating agents that can do different things and you create an orchestrator that understands the broader goal and what needs to happen, he can be a lot more flexible with which agents to call in which section and scenarios in order to be more effective and more flexible in addressing different situations. So a orchestrator is basically a manager in the company that can hand work and get the output of the work, and then continue to the next step of the work with other agents slash other employees. The next component is the employee handbook. If you want, how the company operates, not a single SOP, and that is in the cloud universe is called claude.md, but the same exact concept exists in Chachi PT and exists in Open Claw and exist in any one of the other tools. It is the general definition of how you want to work with that specific environment and that can include things about you, things about how you communicate things to do and not to do guidelines. Guard rails, anything you want, that will be the way everything needs to work. Not just a specific task, not just a specific employee, but the rules that everybody must obey by needs to be in that environment. And that makes it extremely powerful because you can align your entire workforce to whatever structure, processes and so on that you want. The next thing is, in my image, is a badge that allows you entry to additional rooms, and that is in the. AI world and MCP an MCP server basically a way for ai and there's other ways to do this, but it's a way to allow AI access to other universes. It allows it access to your email system, it can give it access to your marketing platform, to your CRM, to your ERP to third party tools outside your environment. And MCP is just a very simple way to do that. You can also connect it through actual APIs. You can also connect it through CLI. There's. Other ways to do this, but MCP allows it to happen very, very quickly. And today with almost zero knowledge, you can connect your tools into a huge variety of MCP servers and allow your AI agents, workers orchestrators and so on, access to your universe of tech stack. The last component is a conveyor belt, what actually brings goods in and out. And for that I use N8N. N8N is an automation tool that is open source. That is complex to use, but I don't care because I don't actually use it. The AI is generating everything I need and creates dozens of these N8N processes, which then knows how to take data from different components in my tech stack and from the things that the AI generates and move them around in the most effective way. Connecting to literally anything you can imagine, including servers on Google Cloud or AWS, including databases in different systems, including my YouTube account, including LinkedIn, including anything else you can imagine. So quick summary. We have the employee that is an agent. We have the orchestrator, which is the manager. We have the SOP, which is a skill. We have the workstation that is a plugin. We have the employee handbook or the company rules, which is in the cloud universe, cloud md, which have cps, which is the badge that allows us access to other rooms with more information, more capabilities and tools and so on. And we have the conveyor belt that knows how to move goods in and out. That is N8N. So this is how my universe and any AI Agentic universe actually works. Now let's talk about my operating system. What is in my operating system and how does it actually work? So the idea here is that instead of just having these agents, there needs to be structure. There needs to be clear processes, there needs to be an environment for everything to work in the most effective way. And this is the biggest unlock. Once I understood that and started building infrastructure and building the underlying concepts, ideas, processes, protocols, which I'm going to share with you right now, this is when I was able to start unlocking significantly higher levels of growth and efficiencies. And again, these are two very separate things. The growth is doing things that drive revenue to the company. Efficiencies are things that are reducing cost to the company. Both are very important. I can tell you from myself and from doing this with multiple businesses, that growing the company drives significantly higher ROI than the savings you can get on the savings sides. Doing both obviously is very important because you gain on both sides. I will also tell you that it is very hard to get to the things that are driving revenue before you start working on efficiencies and understand what is possible. So how does that my infrastructure set up? The first thing is what I called the shared work environment. It's the environment in which I work together with the ai. You have to build a working environment in which you and the AI can have access to the same documents, to the same information, to the same outputs, so you don't have to copy and paste and go back and read and look for everything is structured in the same place. And the way this is happening is actually relatively simple. Everything these models do, as I mentioned before, is written down in markdown files, these documents. All you have to do is create a folder structure that will work for you that is identical across each and every one of the initiatives that you're running. For me, I have one mega folder that is called Cloud Desktop, and underneath that I have different universes for my different companies. And underneath that, for each and every one of them, I have the specific projects that I'm working on. And each project there is the same folder structure until a certain level, and then there's a different thing for every project because they require different things. Because of this way, everything I do lives in the same structure everywhere. I know where to go and look for it. I know where to add files when I want to add files, and the AI knows the same thing. So when I do something or the AI does something, it lives in a very clear folder structure, going back to SOPs and processes and best practices. And this way I can go back and forth between different tools without any problem. The cool thing about this is that in addition to the fact I don't have to explain anything to ai, I don't have to continue from where I left off without any clear passage by remembering myself and retyping the instructions. I can also navigate between Claude Cowork and Claude Code, and I will tell you something more interesting. I can navigate between Claude and Gemini and Chachi PT and Grok, and any platform that I want because that infrastructure that I created is completely blind to which model is running on top of it, which provides a lot of flexibility that we're gonna talk about it later in this episode. But the key thing here is the ability to. Create a folder structure that is the same across the board with the same type of files in each one, and we're gonna talk about what these files are in a minute that everything connects to. So let me show you a simple example, and I'll show you exactly how I work literally all the time. on my main screen, I have always these two things side by side on the right, I've got Claude Cowork on the left, I've got cloud code. In this particular case, Claude code is running inside of Cursor, but you can run it however you want inside your computer terminal. On other third party platforms. By the way, you can also run cloud code inside of the cloud desktop app, which we're going to talk about in a minute. But the reason I have it open on both sides is because there are things that I. Do include code, which is writing code, creating applications, and building more sophisticated stuff. And there is where I spend most of my time, which is Claude Cowork, which I have on the right side, but they're both looking at the same folder. So when I tell the left side, when I tell Claude code to work on a project, I don't need to tell it to what to work on because there are a set of documents that will tell it what to work on and when it finishes working, I don't have to tell Claude Cowork that we finished that step in the process because it knows, because they're looking at the same documents. So this is the magic of creating the right setup and infrastructure of your folder that shared space between you and multiple AI tools Very quickly on Cloud Cowork, if you haven't used it, on the top left corner you have three little buttons. One looks like a chat, which takes you to the regular cloud chat. The second one looks like these little check marks, uh, which is cloud cowork. And next to it there is like a little, code thing and that takes you to cloud code sessions. Again, I very rarely run cloud code inside of the desktop app. I actually run it on other applications such as Cursor or the terminal, but it doesn't really matter. You can run it in here as well. on the left side menu, it is very similar to what you know from regular chats. There is the ability to start a new task. There is projects, there's scheduled things, so you can schedule, sequential things. I will show you examples later on how that happens. As an example, my news summaries happen on a regular schedule. My dashboards get updated on a regular schedule. A lot of things happen on regular schedules. Then you have live artifacts where you can create things that connect to your live data and create dashboards and so on. You have dispatch, which allows you to connect to your phone. So a lot of the work that I'm doing actually happens on my phone. The way this works is as long as Cloud Cowork is up and running, you can open Cloud app on your phone, whether it's iOS or Android. Click on dispatch on the mobile and then tell it what you wanna work on, any of your projects. And it will actually trigger the desktop application to start working on things. So if you see down here I have multiple scheduled things, it actually not showing all of them, it's showing some of them. And then I have dispatch. And you can see on dispatch there's like 30 different things that just happened in the past few days. Because every time I have an idea, or every time I'm on the run and I need to check up on a process, I can do this from my phone and it will actually happen on my computer as long as it's open and it's running. And then underneath that, there's the actual conversations in the middle. You have the actual chat and everything that's going on. And on the right you have. On the top right, you have the progress. So the way you work with Claude Cowork or with any agentic system, is you give it goals and it will define the steps that it needs to do and include cowork. It actually shows you what it's doing and it's crossing out everything that it completed. It shows you what folders and context it is connected to and what tools it's using and stuff like that. So that's in general how Claude Cowork works. Now, back to the process. So we talked about having these. structured folders, but what are the files that we actually put in these folders and what we're actually doing to create this additional infrastructure? So the first thing that I have that I'm using all the time, every single morning, that's my starting point, is my portfolio dashboard. What the hell is my portfolio? Dashboard is the place that summarizes all the different projects that I'm working on across the board. How does it work? There are several different agents that goes to different aspects of my universe. They go to all my files, so all the MD files, all the different projects because it's, they're structured in the same way. It goes to my clickup, it goes to, my email and other places, and it looks to what is happening today, and it's creating a dashboard for me that allows me to decide what are the highest priorities for me today. Now if I'll show you how this looks like, looks like. So again, those of you're not seeing, I will describe what I'm seeing. There's a section at the top that is a very high level summary that shows me I have 31 active projects, 21 that needs my attention. Six up and running live. Basically 29 ideas in my backlog. five projects on hold, and 14 stale projects. And I've got a list of the stale projects. What are stale projects is projects I didn't touch for 14 days or more. Again, this is perfectly fine. There's priorities in a company, but that shows me kind of like things that I may have forgotten that want to go back into. It gives me my top action items that comes from the actual tasks in the actual projects. And we're gonna talk about how this works. But again, this pulls it from Clickup and from specific folders in my files, which I will show you in a minute. And then I've got the actual portfolio of projects themselves. I have the ones that are in discovery, the one that are in architecture, the ones that I'm building and working on right now, the ones that I'm testing and the one that I'm live, and the ones that are live. And on the bottom I have my backlog of ideas and I can see all of them in different categories. And on the very, very bottom I have the portfolio growth. Basically a bar chart that is showing me how many projects existed in every single day. And since the last week and a half or two weeks or so, it is also showing me whether they're in discovery or architecture or build or testing or live. And I can see how many projects I'm adding regularly and how. Much progress I'm making across each and every one of these statuses of the projects. Now these projects span across everything that I'm doing across the different companies that I'm running, and they work through financial analysis, creating accounting, purchase orders and invoices, uh, working with suppliers, answering emails, working on LinkedIn, doing marketing infrastructure projects, et cetera, et cetera, et cetera, across basically every aspect of the business. And I'm moving several of them in parallel every single day. So this is one thing that, that I wanted you to see. This is my dashboard. But how does all of this happen? What's actually happening behind the scenes to enable this incredible knowledge on every single aspect of everything that I'm doing and that is happening because I have these standard documents that I mentioned before. Inside of each and every one of the folders and each and every one of the projects, the first thing that I have is evergreen documents. When you use chat and you use chat, all of you regularly in a regular chat. Once you start a new chat, it doesn't know what happened in the chat before. Now all the ais now have quote unquote long-term memory, and they remember things about you, but they don't remember the granular details of everything you talked about in every single conversation. That doesn't make any sense. The problem with that is you run out of the context window if you're gonna do everything in a single chat forever, and then the AI goes cuckoo and starts forgetting stuff and start doing weird things, and you have no control on what it actually knows and it doesn't know. The solution is what I called evergreen documents, and these are documents that I built for the ai and the AI knows how to use it across the board and it explains what are we working on? What is the project, what are the steps? What did we do now? What did we do before? What was completed? What is not completed? What building blocks we're using? What third party tools we're connected to for this project? What are limitations that we are aware of? What are things we shouldn't do? All of this is defined in the Evergreen document and the document gets updated automatically by the AI all the time. The same document gets updated by Claude Code because in the general instructions that we talked about in the beginning, the company, employee handbook, it tells them to do so every. Thing that starts with reading the evergreen document. Every step that is made gets updated back into that document and therefore I have consistent memory for everything that I'm doing. And I can start a fresh new chat and tell it a project I wanna work on, and it will be able to tell me exactly what I need to work on, what was completed pre, previously, and what are the exact next steps to make this more practical from a task perspective, I actually broke this down into another set of documents, and that's the task registry. So in addition to the Evergreen document, there's a task registry. And the task registry is, as the name suggests, is just at least of tasks. It says, what do we need to do? What was completed? What's the status, who needs to do it? And that gets updated automatically, dynamically without me having to do anything. And that's why all these tools, and it doesn't matter which AI I drop on top of it, we'll know how to continue from any given point I'm in. So these two are two of the biggest tricks. And then there is the structure of each and every one of the projects. So in addition to knowing all this information, I wanna know how exactly the thing works. And the reason I got to this was I started building these automations and they started getting really complex. Those of you who are looking at the screen can see what I'm talking about right now. There are dozens of components in here. Some of them are agents, some of them are N8N processes, some of them are databases. By the way, I haven't built any of them. AI has built all of them. And this is what I'm teaching in the course is how to. Teach ai how to build all these things so it can build these incredible processes. But I started losing control. I did not understand what's connects to what and how the whole process works, which makes it harder for me to continue evolving it or to troubleshoot when things break. And so I created another skill that generates incredible flow charts, that shows me everything that's happening, how the actual process works in each and every one of these projects. Now, we'll dive more into this afterwards when I'm gonna show you examples of specific projects. But in general, what's happening now is in my dashboard, and I'll go back to it again so in my dashboard, for each and every one of the more developed projects, the one that are mature and are in testing or either live, it has a link to a flow chart. And if I click on the flow chart, it's actually gonna show me exactly how the thing works. And if I put the mouse over any of these components, it will tell me what it is and it will show me what are the inputs and outputs of each and every one of these steps so I can understand exactly how this works. so far we talked about a specific project. As I mentioned, each project has the flow chart. Each project has evergreen document and it has a task list. But I also want the system to learn across the board. I want the fact that I learned something in one project. Let's say on how to work with N8N. That happens in all my projects. I want the other projects to be aware of that as well. And so there's a higher level document called Lessons Learned that gets updated from all the agents across everything that they're doing, and they're all reading and writing too. So I'm creating an ever growing, improving organization of agents because everything they're learning across the board anywhere gets written to the bigger lessons learned, and that drives knowledge across the entire organization, which I wish it was that easy to do with humans as well. But it works incredibly well with AI agents. And then as I mentioned, there's the standing instructions, the broader instructions that tell everything how to work. That's that Claude MD document that describes how I work with ai. Underneath that, there are multiple levels and layers of additional MD documents, additional markdown files that explain how I communicate, what is my style, who am I working with, what type of clients do I work with, each and every one of these things, is a standalone document that the AI knows how to call just when it needs it. So it doesn't read all of that, because again, it will run out of context in the context window, but it has access to all of these at its fingertips, and it can pull information from each and every one of these things as it needs them. So that makes it an incredibly powerful operating system if you want, for everything that I'm doing. And it's completely independent from the models on top of it, which is very powerful. And we're gonna talk about this more in a minute. I wanna show you or share with you three of those 31 projects and how they're happening. Before I explain, what does the LinkedIn content machine do? Let me start with describing the problem. The problem is that in 2025, LinkedIn introduced a new algorithm that they called 360 Brew. What 360 Brew did is it trashed the engagement more or less across the board on LinkedIn. So I went to several different reliable sources including Social Insider, Hootsuite, sprout Social, LinkedIn Engineering, and looked for the information. So here's the findings. Overall, there's been a 50% decline in platform wide post views. There's been a 25% decline in engagement per post. Again, platform wide. There's been a 42% decrease in the rate in which followers gets added to people on LinkedIn. And all of that happened because of a change in the algorithm that LinkedIn themselves did in 2025. I was suffering from the same thing. I was making the same amount of effort, creating the same amount of poets, working very, very hard, trying to look for different tips and tricks, and yet I was growing significantly slower and getting significantly lower engagement. And then it hit me that there is a better way to do this. I can do this in a much more scientific way. Look what is working on LinkedIn by analyzing the top performers on LinkedIn. Figure out the strategies that they're using and apply it to my content. And this is exactly what I built with the AI content machine. And the results are these since the launch. Of the AI content machine, which again uses my content, it doesn't generate stuff on its own, but it applies best practices that it is testing and verifying on weekly basis. On LinkedIn, I've seen 147% growth in daily impression. That's almost two and a half x of the amount of impressions I saw before. I see a 37% increase on engagements per day, and my followers are increasing a 21% faster per day than it did before I launched this system. So while the overall average on LinkedIn is declining dramatically, I'm seeing a very nice growth. And again, I was seeing that decline before I deployed this. So how does this thing work? So with this, the easiest way to understand how the system works is actually to look at this really complex and scary flow chart that again, the AI generates explaining how it's doing and what it's doing. So the first thing it's doing is it has what I call the creator universe manager. It's actually continuously looking for the top. AI creators on LinkedIn. So these are the people who are in my niche in my industry, my competitors, and it's building a database of them, and it's tracking what they're doing every single day. What are they posting on? How long are their posts? Are they using video image or text? Are they writing on news or on tools, or what is the mix of the things they're sharing? How long are each lines in each and every one of the posts, et cetera, et cetera, et cetera, each and every one of the things that it does. And then there's a whole intelligence and data layer that uses this information to define what is going to be my strategy? What are the things that are working right now, and how to analyze my content based on these new ideas. It saves that information and it creates a strategy that then is being used in. Creating the plan for the following week. So you can see here that I have the weekly content orchestrator that works everything, more or less connected to everything around it. And then we have the content strategy generator that updates the strategy every time the universe of creators that it's tracking is doing something different. And then you can see that there's a strategy optimizer that keeps updating that all the time, and that generates a content calendar generator that generates the content calendar for the next week based on the new things it learned from looking at all these people, which means it has a scientific approach and an on demand currently relevant approach to how to post on LinkedIn. Now, those of you who are thinking, oh my God, I can do this for. YouTube, and I can do this for Facebook and I can do this for Instagram. The answer is absolutely yes, the same exact process. All I have to do is replace the type of people it's looking at and the platform, and it will do the same exact thing across the board, but then it goes and actually generates the content. How does it generate content? As I mentioned, it's not making stuff up. It is actually using my voice, my content, and that's obviously the magic behind all of this. How does it know my voice and my content? I have a podcast that has two episodes every single week. It can pull from with my voice and my content. I have the Friday AI Hangouts, which is my community of people who are just like you, who are in the business world that wants to know how to use AI effectively. We meet every Friday at 1:00 PM By the way, if you're interested, come and join us. It's an incredible, incredible group of people that is constantly sharing ideas and practical deployments of AI and learning from one another. Every Friday, 1:00 PM Eastern Time. But that's another piece of content that is available for you to look at. And every time I have an idea of something I wanna talk about something that frustrates me. A cool thing that I found. I just open my phone and I click on a button and I record a voice message that goes into this process and gets processed and becomes a post as well. So all these things, it's taking my actual voice, my experience, my background, all the knowledge that it has in the MD files, and it creates content that is me, but based on the best practices of the best performing people on LinkedIn, or like I said, on any platform. And then the final step, it actually delivers it. So it deploys it. I'll show you exactly how there's a human in the loop step, which we're gonna talk about in a minute. And it also learns. On its own. So it's looking at what is working for me that may not be exactly the same thing as for these top creators. And it is continuously updating the strategy that is happening in the very first step based on the results that we are achieving me. We meaning my assistant, myself, and the AI in our posting on LinkedIn. And I showed you before the results that it's generating. So this is project number one that I wanted to show you. Project number two is the proposal pipeline. I get approached. Several times a week by companies who want me to do workshops for them or people who want my consulting capabilities and so on and so forth. There is a Zoom call that's happening to meet with these people and learn what they need after they fill up an initial form. There might be some email exchange, back and forth between me and these prospects or existing clients who are looking for more stuff. And all of that triggers the generation of proposals, again, without me having to do anything other than verifying it in the end. So let's see how this looks like. So this is a much shorter pipeline, but it is still extremely effective. So let's see what's happening here. First of all, it is scanning my Google calendar. How does it have access to my Google Calendar, through the MCP we talked about before? So I have an MCP connector to my Google calendar, and it sees when these type of meetings happen. So either specific types of client meetings or specific kinds of meetings with prospects. Then it goes through N8N and pulls the actual summary of the meeting from Fathom. Fathom is an AI tool. There's many other tools like this who transcribes and summarizes everything that I do. It then evaluates whether based on the summary, the client or the prospect actually asked for a proposal or I suggested a quote. It doesn't have to be a verbatim. Please send me a proposal. It understands from the context, and if it is, it actually pulls the entire transcript and then it has a whole process with several different agents. Again, you can see six different agents here that actually will. Research about the client will learn exactly about their needs. We'll figure out how that that aligns with my offering. And then it will write and draft a proposal. And then he does three additional things. It will create a draft email in my Gmail account and will attach the proposal, it will upload it to the relevant place in my Google Drive, and it will update my CRM with that all without me having to do anything. So when I wake up in the morning, in my morning brief, I have a message saying, Hey, there's a new proposal ready for you to review. And here's the link to the proposal. Here's the link to the CRM, and here's a link to the email. The draft email that's already in your outbox ready for you to review. And if you like it, you just hit send and you're done. All of this happens basically 30 minutes after the meeting is over, and the reason for 30 minutes is if you can see in the trigger, it gets triggered by a Google Calendar invite and. We don't always actually finish on time. So it actually asks it to wait 30 minutes after the meeting is over to go and run this process, just to be sure that the meeting actually ended and it has access to the transcript. So this is another project we're gonna look at a third project, which is my AI weekly news. If you've been listening to this podcast for a while, you know there's two episodes a week, one like this where we go into tactical things and how to do things in ai, usually with really incredible guests that share how they do things in AI and the other every Saturday that shares AI news. How does that happen? I need to find news. I need to curate news. I need to filter news. I need to sort news. I need to summarize news. I need to do all these things, and there's an entire universe of agents and other processes that make that possible. Looking at the flow chart of that, you can see again, multiple steps. There's a step that starts with an input that starts either by me dropping in articles into a Slack channel or the things that it is researching on a schedule on its own. There's a very, very long list of N8N processes, and you can see there's probably 15 of them here that do multiple things as far as grabbing the article, analyzing the article, figuring out whether it's relevant or not relevant to you, my audience, and then based on the decision, sending it through a specific pipeline to get analyzed. And then eventually it gets deployed to an application, which is a web application That cloud code created based on my requirements that I keep on updating every single week that has all these articles where I can highlight and shift stuff around and decide on the sorting order, which it's recommends on its own, and then actually produce the. Podcast by allowing me to review this in the right order, with the right highlights, with the right focus. And it also produces the newsletter that tied to it that I know a lot of you read as well. So this pipeline does a lot of that work again while I sleep and I just have to verify, see the things, and obviously employ my judgment to what I think would be more interesting and less interesting. So like in the other places, you'll see a lot of collaboration between myself and the AI in that universe. Now, and this is actually a good segue to the really important fact that despite the fact there are. Dozens or maybe hundreds of agents working in orchestration, doing all these things. I'm still in control. The human you, the people who work for you with you are still in control. And the way I do this is I have human checkpoints for basically everything that I'm doing. As I mentioned before in the proposal, the proposal doesn't actually get sent. It gets placed in an email in my outbox as a draft for me to review. But there are much more granular things that I'm doing and the way I'm doing it, I'm actually doing it inside of Clickup. So those of you who don't know Clickup, Clickup is similar to, notion or Asana or Jira or monday.com, or microsoft Planner. It is a board or multiple boards in multiple panels in which I can define different tasks and define who's in charge of them and view the statuses of all of them and communicate about them and so on. So I work with all these AI agents in the same exact way. I work with human teams. I have a board for each type of process, and in that board, there are steps that are human for review and there are steps of actual work that the AI agents do. So in this particular case, we're looking at the A at the LinkedIn content production process that we discussed before, and you can see that there's planned posts that the AI created. You can see prompt reviews that I asked the AI to create a new prompt, and it created a new prompt for it. What do I mean by a new prompt? If we go into any of these posts, you will see that it has multiple components. It tells me which, It tells me which pillar of content it belongs to. It gives me a lot of information about it. It has the actual suggested post that again is based on my information. And you can see down here on the bottom, you can see where it comes from. So you can see it says, uh, which pillar of content? This is AI tools. You can see the overlap score. The overlap score basically tells it how aligned is the content that it found from my content, how aligned is it with the best practices and the things it found with the best performers on LinkedIn right now. But what you also will see, and this one is actually not a good example, so we'll look for another one, uh, that is actually already produced. What you'll also see is that on the bottom right there is a prompt in the chat suggesting what should be the image for that particular post that again, the AI decides based on its best practices and the strategy that they developed. Should it be a video which it can create on its own based on my original videos, or should it be a image or just text and so on. So it suggests that, and if I approve it and all I have to do by approving it is dragging it to ready for graphics, and then it goes and generates the graphics. And that might be a simple flow chart. This can be a photorealistic image, it can be whatever it thinks is the right thing. I can obviously give my comments. How do I give my comments? I actually write in the chat of the task just like I would do with a human and say, oh, I don't like this. I like that. Or I will just rewrite the prompt myself or edit the prompt and send it back and it will generate a new kind of graphics. So I work. In this board as if I had a team of an entire marketing team working on this, including designers, including researchers, including content writers, including stylists, including all of that. It's obviously connected in the backend to my brand guidelines to how I want to communicate to all the files that we talked about before. And then he knows how to do it. Down here as an example, you can see a voice note. This is one of those where I just had an idea and I clicked a button and I recorded and it does the same thing. It goes and creates a post based on me just speaking away, and you can see the transcript of what I was speaking. And you can see that he actually wrote an actual post based on that, that can go and be posted on LinkedIn. So here's the post itself, and you can see here that there were several different variations of the actual graphics because I sent it back and I didn't like it, and I wrote comments and then it went and fixed the graphics until I was happy with it. This human in the loop aspect of it is a critical, critical aspect of actually staying in control of what it is that you are trying to do. And so while the AI does the work, you still have full visibility to everything that it is doing. And now too, the critical aspect that I talked about before, you do not wanna be locked into either Claude or Cha Chie or Grok or whatever the next thing that's gonna show up or Gemini because of two reasons. One, redundancy. If tomorrow something happens to Cha Chie and it's down for three hours and you entire operation depends on it running, you are screwed because for three hours, your entire company doesn't work, or critical aspects of it don't work and three hours is not five minutes where you can recover from. That's a very long time to be down. So by having the ability to switch to a different model and everything still keeps on running, gives you that powerful redundancy. More or less, every single process that I built is built with redundancy on top of it. So it can switch to a different model and still ke keep on running. And the way it works if the process gets stuck and the API doesn't respond, it tries again if it tries a third time. If it doesn't work, it goes to its secondary model and keeps on running from there as if nothing happened. And then an hour later, we'll check again if the original process that is its first choice runs and it will check again another hour until it's back up. And then we'll switch back to the original model. So redundancy is one. The other one is improvements. These model keep coming up with new models. Every single time the new models get better, and in many cases cheaper as well. So you can get better results for less money. So why not do that if you build everything locked into one environment? You're stuck with that, and so that's another reason to build it the way I'm describing it here, because the actual model doesn't matter. I can switch it with very, very little effort and still have everything running because everything is in that file system, and everything is in those processes that I created, in the infrastructure I created. The bottom line is the moat isn't the model. People think, oh my God, you're doing so great because you're using Claude. No, I'm not doing so great because I'm using Claude. I'm doing so great because I built this entire system that I'm sharing with you right now that currently runs mostly Claude, by the way, not only like all the images as an example that you see in this presentation that Claude created, the presentation, the images are created by nano banana and Image 2.0 by OpenAI it. Generates images with both of them based on what it thinks will fit the slide. It looks up both of them. It suggests one, I get to pick the one I like, and that's how the process works. So even in this presentation that I'm using here, there are several different models in the background that are running to do different things while allowing me to make the final choice. That's what I wanted to share with you today. Quick recap and a quick reminder, if you wanna learn really how to do this, not of the. 40 minute overview, but rather how to do every single step and to get the actual prompts and to get the actual links to things, and to experiment and to learn how to build these kind of systems. Come and join the Multi-Agent Orchestration course. As I mentioned, the next session starts on June 22nd and it's selling fast. So if you want to join that, you need to act today. By the way, if you sign up between now and the end of April, which is just a few more days, when this episode goes out, you get$200 off. And the link to How to Sign Up is in the show notes, and the code for the$200 discount is on that page that is in the link in the show notes. So if you're interested, come and sign up today. The first two. Cohorts sold out in 10 days, and this one is already selling pretty well. So if you wanna join this would be a good time to join. I can tell you if this didn't tell you enough what you just saw in the past 40 minutes, it changes everything you know about how businesses run, about what you can do, about the level of efficiencies, about how much growth, about what kind of teams you can have, and so on. Limitless. That's all I can say. So if you wanna learn this, come and join us. And that's it for today. I hope this was eye-opening and educating at the same time. I was trying to reveal as much as I can in the time that I had. So if you don't want to join the course, at least it gives you ideas on where to go and what to do next on what kind of infrastructure you need. If you like this episode or this podcast in general, I would really appreciate if you do two things for me. One, go into your favorite platform, whether it's Apple Podcasts or Spotify, and give us a review. And the second one, which is a lot more important, is share this with other people who will benefit from this on your phone or wherever it is you're using this. There's a share button. Click on that button. Choose your favorite tools of communication, whether it's Email or Slack or WhatsApp or Telegram or just regular SMS messages, and send this podcast to people that you know can benefit from this so they can learn as well. They would appreciate it. I will appreciate it and you will feel good about doing the right thing. That's it for today. Have an awesome rest of your day and have a great rest of your week.