Speaker A
Right now, most businesses are still paying people to do work that AI could finish in seconds. And the ones who figured that out months ago, they're quietly pulling ahead of everyone still doing it by hand. So, this video is
Learn how to run your entire business using Claude Code with no coding required, leveraging AI workers to automate tasks and scale efficiently.
Ask about this video. Answers come from its transcript only — with the timestamp, so you can check them.
Generated from the transcript and can be wrong — check the timestamp.
Key Takeaways
- Claude Code enables running a business with AI workers without any coding knowledge.
- Using a flat-rate subscription plan is more cost-effective than pay-per-use API keys for business automation.
- A centralized memory file allows AI to retain business context and improve over time.
- Teams benefit from shared AI playbooks for consistent and scalable operations.
- Integration with existing tools and scheduled automation makes AI practical for real-world business tasks.
What the video covers
- Most businesses still pay humans for tasks AI can complete instantly, causing them to fall behind.
- Claude Code is a no-code AI automation tool that runs your business by managing tasks through AI workers.
- The tool integrates with your existing business tools like email, documents, and files.
- Setup is simple via IDE extensions like Cursor, VS Code, or terminal, with a recommended paid Claude subscription for cost efficiency.
- Claude Code uses a memory file (claude.md) to store business rules and context, onboarding AI like a new team member.
- You can maintain both global business rules and project-specific notes to customize AI behavior.
- Teams can collaborate using shared playbooks, ensuring consistent workflows and easy onboarding.
- AI workers can handle scheduled tasks, multiple simultaneous jobs, and integrate with real tools for practical business operations.
- The video provides a free guide with templates and prompts to help viewers implement the system.
- Anthropic, the company behind Claude, uses this system internally across departments like legal and marketing.
Chapters
- 00:00Introduction to AI automation and Claude Code
- 01:30Concept of AI workers and business integration
- 03:04Setting up Claude Code with Cursor IDE
- 04:31Signing in and subscription plans overview
- 05:48Using the memory file to onboard AI like a team member
- 07:18Collaborative team workflows and shared playbooks
- 08:55Running multiple jobs and scheduling automation
- 10:16Cost considerations and real-world use cases
- 12:36Summary and free guide resources
Full Transcript — Download SRT & Markdown
Speaker A
about cloud code. And it's probably not what you think. Now, most people hear the name and picture a tool for some programmers, something that they will never touch. And they are wrong. And that one assumption, it is literally
Speaker A
costing them hundreds of thousands if not millions of dollars. I run my entire business on it. And I've never written a single line of code. This was never even about coding. It's about having a team of AI workers that actually are able to
Speaker A
do work for you instead of just talking about it. And this scales. Zapier, the automation company, they now run more of these AI workers inside of their businesses than they have employees.
Speaker A
Claude, they use AI for 99% of what they do to enhance their product and even marketing. So, here's the plan. I'm going to walk you through the exact setup that I used inside of my business and for our clients and every piece that
Speaker A
matters for a business just like yours and nothing that you don't need. But with that being said, just using a normal AI chat through your browser, it has three problems that make it completely useless for running real work. However, this setup, it fixes all
Speaker A
three of those. And by the end of this video, you will know exactly how it works, how to set it up, and how to get your whole team using it. Now, just a quick intro if you don't know me
Speaker A
already. My name is Nick. I've spent the last couple of years implementing AI systems inside of real businesses and teaching thousands of entrepreneurs how to sell AI effectively. But enough said, let's dive into it. So before we actually touch anything, let me just
Speaker A
reframe what this thing even is because this one shift is going to be what makes the rest click for you. Now the simplest way to be thinking about this is we're just going to have one place that is
Speaker A
holding everything about your business plus a team of AI workers that can actually do the tasks and use your real tools. So you're not going to be just chatting with it. You are literally handing it entire jobs. So here's the
Speaker A
whole idea in just one picture. So this is going to be you inside of the middle.
Speaker A
You are going to be the operator right now. On one side, this is going to be your AI team right here. On the other side, this is just going to be all of your real tools. So, this can consist of
Speaker A
different things like your email, any of your documents, any of your files, and you just sit in the middle and you are directing it, right? It's not just me saying this because the company that actually makes this, Anthropic, they have
Speaker A
said that their own teams outside of engineering run real work on this as well. So just to name a few different departments, their legal team, they built a working prototype of a phone system. Their marketing team, they've spun up hundreds of different ad
Speaker A
variations, the different go-to-market systems, people who have just never written code or understood anything about computer science. They're building real tools just by describing in plain English what they want. So that's going to be the entire shift. It's not a
Speaker A
smarter search box or anything like that. It's just a place to run your business with a team. But now let's just set it up and it's actually much easier than you might expect. So jumping into the setup. This is actually the part
Speaker A
that most people are scared of and it's honestly incredibly easy. So you've actually got a few different ways that you can be running this. So there's going to be the terminal. Then there's going to be a desktop application. And
Speaker A
you can also just run it right inside of the editors that people already use like VS Code. So all of these are they're called IDEs. So VS Code, Cursor, Anti-gravity, it's the same cloud code underneath. You just pick your door. Now
Speaker A
me, I often use Cursor. It's free and it just feels very normal to me. Not some like scary black terminal window. So that's the one I'm going to be setting up here. So first you just go ahead and
Speaker A
download Cursor and just grab it off of their site. It's completely free and you install it just like any normal application. And then from there you just simply open it up. Now over on the left there's going to be an extensions
Speaker A
button. So you click that, you search for Cloud Code and you hit install. It's that simple. That is the whole thing. It drops right into the editor for you.
Speaker A
Next up it'll just ask you to sign in. And one quick tip here that actually saves you money is you can sign in with a paid Claude subscription, not with an API key. And this is what you would 100%
Speaker A
want to be using instead. Because with the subscription, you're going to be paying just one flat price and you stop thinking about it. With the API key, you have to be paying per use, which means that you're basically just watching a
Speaker A
meter the whole time. So for running a business, flat and predictable wins every single time. It's what I and my team use. Now, just to cover the plans real quick, Claude Code is actually included on the pro plan, which is about
Speaker A
$20 a month, and that's where I would start almost everybody. Now, above that, there's going to be max at $100 and a bigger one at $200 for people who live inside it all day who are using it more.
Speaker A
So, this is what my team and I use. And as you might expect, the free plan doesn't include cloud code. So, pro, it's your entry point for this and what I recommend for you. And that's the whole setup. Editor extension, you sign in,
Speaker A
and you're ready. That's it. And by the way, real quick, if you do want to follow along, I'm going to be putting a free guide inside of my school community with the exact doc and the templates, all the prompts that I'm about to show
Speaker A
you. So, you can just copy the whole thing. It's very easy. It's free. Link will be down below in the description.
Speaker A
We have plenty of other guides and resources that we do not post on our YouTube channel inside of there, too.
Speaker A
We've got about 20,000 members, so make sure to check that out if you're interested. But, let's get back to it.
Speaker A
So, the first real piece, and honestly, the most important one, this is the memory. Now, this is what makes literally everything else work. So there's going to be a file called claude.md. Now the easiest way to be thinking about this is this is just
Speaker A
where your business effectively lives. So it's just a plain text file where you write down everything about how you operate and Claude, it reads it automatically at the start of every single conversation. So instead of just reexplaining who you are every time, you
Speaker A
just write it once. So who you serve, how you talk, any of your prices, any of your rules, the way that you like things done and from then on it just knows. So you can save anything important into the
Speaker A
file by hand and it also just quietly picks up the little corrections that you make as you go on. So instead of just resetting to zero every single morning, it keeps getting more like you. And the way that I describe it is you're just
Speaker A
onboarding it once like a new hire instead of just reexplaining the job every single day. Now here's mine. So this is the real one for my agency. You can see it's not just code. It's actually just plain English. So here's
Speaker A
who we work with. Here is our tone of voice. Here's the stuff that we never do and things you have to be cautious of.
Speaker A
None of this is technical. It just reads like a note that you would write for a new team member. Now, one thing worth knowing is that you can have one of these at the top level for your whole
Speaker A
business and you can have smaller ones inside of specific projects. So, your main rules, they apply everywhere and then you have a specific client or projects can have its own extra notes on top of them. That's how I use it. So,
Speaker A
big rules, they're going to be going at the top. Your specific notes where they actually
Speaker A
this file automatically. So you don't even have to start from a completely blank page. So that is the memory. Now let's give it some skills. So a skill, it's just a saved playbook. It's an SOP.
Speaker A
It's the way you teach Claude to do a specific job in your way and how your business actually operates and how they go about those processes and just doing it once. So it does the same way every time after that. So if you've ever
Speaker A
written an SOP, just a standard operating procedure, so a specific way doing a task, that is just exactly what this is, except Claude actually follows it step by step. Now the magic with this is you don't even have to dig it up and
Speaker A
run it. So Claude notices when a job matches just one of your skills and it pulls it up on its own. So when I say something like draft a proposal, it goes off. It finds and sees that I have a
Speaker A
skill for that and it follows my exact steps. So I can either just in plain English call it like that or I can just get it a little bit more specific and say you know like slashdraft proposal if
Speaker A
I've created it with that name. Now a couple of things that make these really good is they only load when they are actually needed. So they don't slow everything down inherently and you can also share them across your teams or
Speaker A
collaboratively. So this means that your whole team can be running the exact same playbook instead of everybody doing it their own way. So when we are working with a team we make sure that everybody's going to get access to the
Speaker A
same things. Of course, if they're across different departments, then they're not going to need access to some things. But this is how we build this for operations. So, this is just a stack of skills that I've built up for my own
Speaker A
business. Now, every one of these, it's just a job that I was doing over and over again. I wrote it down once so that Quad can just handle it the same exact way every single time. Saved me hundreds
Speaker A
of hours, probably every single month, I would say. Now, let me just open one so you can actually see what's inside and notice how simple it actually is. So, let's go. It's really just three different things. What the job is, when
Speaker A
Claude should be using it, and then the steps. Now, this one is my email reply skill. So, the steps are just how I want my emails to be sounding, how short to be keeping them, what to always include,
Speaker A
and what never to touch without checking with me first. So, that's the whole thing. So, now when I ask for a reply, it comes back actually sounding like me and not just some generic robot every time, right? So, that's the idea. We
Speaker A
want it to be in our own language and mimic our behaviors or our patterns and our speech. So ultimately, skills are just how you bottle the way that you work or how your business operates. Now, what if you want to package up a whole
Speaker A
bunch of these and hand them to your team in just one go? Well, that's the next piece. So this next one, it's a big deal if you've got a team. And this is the plugins. So a plugin, it's basically
Speaker A
just a box where you take a bunch of your skills, your workers, your connections, your rules, and you bundle them all into just one package. And then anyone in your team can actually install that whole package in simply just one
Speaker A
command and instantly have the exact same setup as you do. So think about what that solves. So normally getting a new team member set up the right way, it might take forever for you. With this, you hand them just one box, they install
Speaker A
it, and they're running your whole system on day one. So you get the same playbooks, you get the same standards, you get the same everything. And there's actually marketplaces for these. It's kind of like an app store. So, there's
Speaker A
an official one from Enthropic, there's a community one, and you can also host a private one just for your own company.
Speaker A
So, you can grab ready-made ones, or you can just build your own, and you can keep it internal. So, look at this. You don't have to build every one of these yourself. There are loads of these ready-made packs out there right now for
Speaker A
all kinds of different work. Like, Enthropic built a whole one just for small businesses, like the everyday finance and sales and admin jobs already done for you. Now, I actually made a full video breaking that down already.
Speaker A
So, I'll link it if you want the full deep dive, but that's just one of them.
Speaker A
So, you could browse what's out there, pull the ones that you want, and what is most applicable to you in your business and your departments and jobs and processes, and they just drop straight into your cloud code setup. Now, the
Speaker A
reason that I am putting this right after the skills is that it's the natural next step. So, first you write your playbooks, and then you box them up so your whole company runs off the same box. And that's just a plug-in. Now,
Speaker A
let's talk about the workers themselves. Okay. Now, this is the one that makes the whole AI team idea real. So, this is sub agents. Now, sub agent, this is just one AI worker that you've given a specific job and a specific set of
Speaker A
instructions. So, the idea is you write it once and after that when the work just comes up, Claude hands the job to that worker on its own. So, you don't have to go call it specifically. So, here is how I picture it. And this is
Speaker A
the diagram and the document, but that's you at the top. And under you, these are your departments. So, a proposals worker, we have a content worker, we have an operations worker, we even have a research worker. So, each one is just
Speaker A
a specialist that only knows its job and it does it incredibly well. So, we're not creating just one ultimate sub agent where it has access to how to do everything because in that case, we're going to experience context bloat and
Speaker A
just feed it too much information. It's going to get confused. It's going to hallucinate and just give you wrong answers. It's inevitable. So, that's why we split it off into different specialized sub aents. Now, there's two particular things that actually makes
Speaker A
this powerful. To actually expound on that a little bit further, each worker, it just keeps its own separate memory, so they don't trip up over each other or clog up the main conversation. And because they're actually separate, several of them can work at the same
Speaker A
time. So, you're not doing every task one by one anymore. You're running departments at the same time, all synchronously. Now, these are my actual departments sitting right here. So, each one's a worker that I have set up for a
Speaker A
specific part of a business. And a worker, it's just a file. So, let me just open one up to give you an example.
Speaker A
So, at the top, it just says its name and a brief short description of what it does. And that description is what Claude uses to decide when to send it to work. And then below that, this is just
Speaker A
the instructions. And that's the whole worker. Now, one thing worth saying, and it comes straight from Enthropic's own guidance, don't go overboard building 20 workers on day one. You want to just be starting with one, and then from there,
Speaker A
you can just add a specialist only when you've actually got work that is separate enough to need its own lane.
Speaker A
until verbatim. They say a team of one good worker beats a mess of 10 that you've never tuned. And I completely agree with that statement. So with that being said, that is your department. And next is what happens when you actually
Speaker A
just let them all run at once. All right, so this point you've got a few workers and now you get to do the thing that actually feels like running a company, which is running them in parallel. So here's the picture. You
Speaker A
hand out the work. One worker is maybe drafting the proposal. Another is going to be pulling the research. Another one is going to be running the follow-up.
Speaker A
And they're all running and going at the same time. and then the results come back and get pulled together. So that is the operator seat. So we have a few different things moving at once with you pointing the way. So there's actually a
Speaker A
newer version of this where you can just ask Claude to coordinate a whole group of workers on a bigger job where they're going to be sharing a task list and past work between all of each other. So it's
Speaker A
genuinely impressive when you see a big job just get chopped up and handled all at once. But I'm going to be straight with you here because this is exactly where people get oversold. this bigger team stuff. It's still early. It's still
Speaker A
a preview and it burns through a lot more usage. So, the person who created Claude Code said it very plainly that these teams use a lot of tokens. So, save it when a job is actually genuinely big and worth it, not just because it
Speaker A
looks cool or it's idealistic. So, that's how the team scales, but none of this is going to be mattering if it cannot touch your actual tools. So, let's connect it to your real business.
Speaker A
So, so far everything has been inside of Cloud Code. But to actually run a business, it needs to reach inside of the tools that you are already using. So things like your emails, your documents, your files, your customer records, and
Speaker A
your CRM. That is what this piece does. So it's got a technical name and it's just called MCP, model context protocol.
Speaker A
But the idea with it is dead simple. So let me explain that. So you just think of this as one universal plug. So on its own, Claude can talk about your email, but it can't open it. So this is where
Speaker A
you connect the plug and now it can actually read your email. It can draft replies. It can pull a file. It can update a record. So the picture with this is cloud code is in the middle and your real tools they're plugged in
Speaker A
around it. So we have Gmail, Google Drive, Slack, notion, your accounting, maybe your meeting notes. Each one it becomes something that your team can actually use. So this is what mine looks like and these are the tools that I've
Speaker A
actually plugged in. And once they're actually connected, I can just say something very simple like pull the notes from yesterday's call and then turn them into a draft and it just does it completely end to end across two
Speaker A
different tools. I have used this so many times and it's one of the highest leverage things that I've ever done is pulling every single call that I've had.
Speaker A
I've had probably about 500 calls over the past three years inside of my AI business on sales calls and meetings with any of my students and just finding like what the most important things are.
Speaker A
So like what is the top niche of businesses that we've spoken to? What are the top problems? So being able to literally pull from hundreds of meetings and getting all of the data from all of that. Granted, something like that would
Speaker A
be and has been about an hour task and it takes quite a while, but you can just get an idea of what you can be using it for inside of your business or whatever you are doing. So, this is literally
Speaker A
where everybody's saying, you know, you can run your company with AI stops becoming a slogan and it starts getting very real because now one instruction can move through several different of your tools all at once. Now, just two
Speaker A
things to keep in mind here though. One, more is not better here. So you can plug in the two, three, four tools that you actually live in the most. And I would just stop there. Now, if you keep piling
Speaker A
on too many tools, it gets pretty noisy. And you'll notice that sometimes your tokens are going to get eaten up a little bit more. But number two, stick to the official well-maintained connections. So Enthropic, they are very clear that they do not personally vet
Speaker A
every third party connector out there. So just use the trusted ones, not some random thing that you found. I would keep it a little bit safer with this.
Speaker A
But that being said, your team now has hands. Next, let's make sure that you just stay in control of what it is actually doing. So, here's the question that everybody has at this point, and it's a pretty fair one. If this thing
Speaker A
can get into my files and my email and actually do stuff, how do I stop it from doing something that I didn't want it to do? There's three simple things that you can do to keep you in control and
Speaker A
prevent anything detrimental. So, first is plan mode. So, this one's for any of the bigger jobs. So, say you ask it to clean up a messy folder just full of client files or just go sort through your whole inbox. Now, you don't want it
Speaker A
to just dive in and move a 100 things around. So, this is where you turn on planning mode and instead of touching anything, it stops. It writes out exactly what it is planning to do first.
Speaker A
And in this case, you just read it over. If the plan looks right, you can hit go.
Speaker A
You can approve it or you can suggest edits because if it doesn't do anything or if it doesn't create a plan that you do not like, you just tell it what you want it to change. Nothing happens until
Speaker A
you are happy with it. Number two is permissions. So out of the box, it's actually very careful where it'll look at the things on its own, but the second that it wants to actually change a file or send something out, it stops and it
Speaker A
asks you first. So you can see right here, it is asking me. You can let it do that one thing or you can just tell it to, you know, trust it and let it run.
Speaker A
But either way, you are going to be the one deciding. Now, one thing that I typically do inside of mine is I just skip permissions and often just let it go haywire and do whatever it wants because 99% of the time, it's not going
Speaker A
to be doing anything detrimental. But in this case, if you are, you know, having to adhere to compliancy or different security concerns, then you will want it to be a little bit more cautious and not just allow it to skip the permissions.
Speaker A
Now, number three is the undo. So, there's a rewind button right here that takes you back a step if something does go wrong. So, you're never going to be stuck with a mess. So, hypothetically, if we had messed up right here and we
Speaker A
don't want to commit with this or if we just have to like revert what we just did, we could just go back. It's that simple. Now, getting into the actual point of all of this. So the goal it
Speaker A
isn't to just hand your whole business to a robot and walk away. It's to put a capable team in front of you with you checking the stuff that really matters.
Speaker A
So for anything important, money going out or something getting sent to a client, you still should be signing off.
Speaker A
You should still be having that human in the loop. And that's not a limitation.
Speaker A
That's just how you run this properly. So that is the control piece. So now let's make it run without you babysitting it every single second. So so far at this point, you were still the one kicking everything off. But this
Speaker A
next piece, it's about making the routine stuff happen on its own. So, first, this is going to be the hooks.
Speaker A
Now, a hook, this is just going to be a rule that runs by itself when something happens. So, every time a worker actually finishes a draft, it's automatically going to get checked before it ever reaches me. So, you set
Speaker A
that up once and then from then on, it just happens every time without you thinking about it or having to provide any additional instructions to make that happen. Now, number two is your own commands. Now, these are just going to
Speaker A
be your shortcuts for the stuff that you do over and over again. And so it's almost like a skill. And I've actually got a whole bunch of them set up now.
Speaker A
And each one's it's just a little job that I run quite often. And I just saved it so I can fire it off by name. So you can see like this command right here.
Speaker A
Like instead of typing out the same long request every single time, I just type the command in one word and the whole thing kicks off. It's just like a shortcut on your phone or on your computer. Number three, one of the most
Speaker A
important pieces is the schedules. So instead of you kicking off a job every time, like you set it to run on a timer.
Speaker A
So, for example, every morning at 8 in the morning, just go build my competitor brief and it's done before I sit down.
Speaker A
So, there's two actual versions of this and the difference matters where one runs right on your own computer. So, this is going to be able to save your files and there's no extra setup, but it only goes while your computer is on and
Speaker A
the application is actually open. Now, the other one, it runs up in the cloud.
Speaker A
So even when your laptop is shut off and that one's definitely more handsoff, but it's a more technical setup where your work has to be sitting in an online code repository like GitHub or using Claude's new feature or platform called managed
Speaker A
agents. So if you're just starting out, the one on your computer, it's going to be the easier way in. But I do have other videos on how to set that up. So if you're interested, go make sure to
Speaker A
check that out. But that right there, that's the shift from a tool that you use to a system that runs completely without you. So all of the boring repeating parts of your week, the reports, the weekly check-ins, the
Speaker A
roundups, like those can just happen on their own and you only have to step in when something needs you. So that effectively is automation and it's not even chained to your desk anymore. But that said, I do want to cover one last
Speaker A
thing and it's going to be more about where this is all heading. So with this, like you can send a job off to just run in the background and just carry on with something else completely different. And there's actually a dashboard that pulls
Speaker A
all of this together. So you can see like this shows me every job that is running, which ones are finished, which ones are just waiting on me. So I could have three or four different things going at just once and just glance in on
Speaker A
them, like checking in on a team. And the newest one, it's actually called computer use. It's still pretty rough, but Claude can actually take over your screen and click through an application for you for the tools that do not plug
Speaker A
in any other way. Now, none of this is day one stuff. I just want you to see that it keeps going beyond this. It's not just stuck on your desk. And there's so many features and so much that you
Speaker A
can be exploring to ultimately increase leverage inside of your business. And another quick thing so that you're not actually confused out there is going to be a separate application from Enthropic called Co-work. And this is just built for non-coding work. So it is very good,
Speaker A
but it's its own thing. So everything I'm showing you today, this is quad code. And I just want you to know the difference so you don't go in circles here. But okay, I've shown you the whole system. Now this is the part where it
Speaker A
actually falls short because that matters just as much, right? So, this isn't just simply going to be a magic button that runs your whole company while you sleep. And Thropic themselves, they ran an experiment on exactly that.
Speaker A
They actually called it Project Vend, where they just had Claude run a little shop on its own for about a month or so, and it lost money. It gave things away.
Speaker A
It got confused on its pricing. And the honest lesson from Enthropic's own writeup is that this is all fantastic at specific well-defined jobs and it's not ready to be left fully alone as a general manager which is exactly how I'm
Speaker A
telling you to be using this. I have real jobs with specific defined functions where you are going to be reviewing all of the important ones, all the important things. Now, two more quick things. First is going to be the
Speaker A
cost because the AI workers, they actually do do very much, but they use more under the hood than a quick chat is going to. And most of the heavier plans bill by usage. So there was actually a recent story about a big company rolling
Speaker A
this out wide and getting surprised by the bill. It was about over a million dollars or something insane. And it's not because it was broken, but because they didn't watch the usage. So the move is very simple. Just start small. Keep
Speaker A
an eye on it. Just understand what is happening and scale what's clearly worth it for you. Number two is garbage in, garbage out. So if your files are just complete mess and your notes are chaos, your team's output will be a mess, too.
Speaker A
So, the businesses that actually win with this, they're going to be the ones who feed it clean, organized information, and they're prompting it correctly. So, just do a little tidy up of your stuff. It's going to be paying
Speaker A
off very much for you. And the golden rule on all of this is just pick one workflow, get it working really well three times in a row, and then you could expand from there. So, the people who actually just try to automate everything
Speaker A
at once, they often give up. Things don't work. Their team doesn't actually use it and they just, you know, go back to manually doing things and complaining that AI doesn't work. We see it time and time again. But the people who nail one
Speaker A
thing first, they're the ones who actually end up running their whole operation on it and start, you know, scaling practically. So that is the honest picture with all this, but here's what actually changes for you when this is in place. So when all of this is
Speaker A
actually set up, the real change isn't just that you get a faster tool is that your job changes. You stop being the person just grinding through the tasks and you become the person directing the work and checking the output. It's that
Speaker A
simple. So you're moving from doing to deciding. And that's the whole point of running a team. You just happen to have built this one out of files and instructions instead of hiring for every single seat of every process that you
Speaker A
need. And none of this is wishful thinking. Like Enthropic, they put out real numbers on their own company. A huge share of their work now runs directly through Claude just using AI.
Speaker A
And they measured a real jump in how much their people get done, including their engineers shipping a lot more every single day. Now, an accounting and consulting giant PWC said they took a process that used to take 10 weeks down
Speaker A
to 10 days. a support company, Intercom. They built an AI agent on this that resolves the majority of customer questions all on its own. And one last thing, this isn't going to be replacing the thinking. It's just taking the busy
Speaker A
work off your plate. So, you've got room to actually run the business and focus on higher revenue generating tasks. So, you just stop being the bottleneck for every little nuanced monotonous task.
Speaker A
So, that's the whole thing. You give it a memory so it knows your business. You then write the playbook so it works in your way. You set up all of the workers so it has a team and you just plug in
Speaker A
your real tools who are going to actually do the work for you. And with that, you're going to be staying in control of the parts that truly matter.
Speaker A
So none of this is about coding. It's just about building yourself a small team that handles the work that you've already been drowning in so you can get back to the parts that only you can do or if you want to get out of the
Speaker A
business and you know focus on time with your family or whatever else it may be.
Speaker A
So if you do want to actually build this, I put the whole thing in a free guide in our community. the document from this video, the example playbooks, the worker files, literally all of it.
Speaker A
It's ready to copy. It's free. The link will be down below in the description.
Speaker A
And if you'd rather not build it yourself, if you'd rather just we just set this up for your team and hand it over. That's literally what we do inside of my agency. There's a link for that down below in the description. You can
Speaker A
book a free AI strategy call with my team. We'll show you how we can increase leverage and your bottom line this year.
Speaker A
So either way, you've got the full picture. Now, pick the one piece that would save you the most time this week and start there. But that being said, thank you guys for watching and I'll see you in the next
Topics:Claude CodeAI automationno codebusiness automationAI workersAnthropicCursor IDEAI business toolsautomation setupentrepreneur AI
