# How to Actually Automate Your Company w/ Claude (Seriously)

Channel: Nick Saraev
Video: https://www.youtube.com/watch?v=rvkjS3YoVio
Duration: 8 min
Language: English
Words: 1880
Transcript page: https://viewrankai.com/tools/youtube-transcript/rvkjS3YoVio

---

[0:00] So, I gave Claude code access to a business of mine that does around a million dollars a year and I asked it to automate everything and uh it actually did a really good job. And this isn't a clickbait or one of those like hype beast videos where I just talk about how it's automated my whole life and everything's amazing. Um I've tried this many, many times over the course of the last 4 years with different models all the way back to GPT-3.5 Turbo and I'm usually quite disappointed. Uh but we've now reached the point where you can do this. And so, in this video I'm going to

[0:25] run you through a very simple standardized process that you guys can use to automate most of your knowledge work as well. The first thing you need to do is you need to audit your work. Uh this took me around a week and it involved me asking Opus 5.5 on Max thinking, by the way, to build a tracking tool that took a screenshot of what I was working on every 5 seconds or so throughout the day. So, about 12 times a minute. Uh that's a lot of screenshots. So, you have to have it compress it down to a minimum legible size and then tell you something about

[0:50] what you are looking at, what you were working on, and so on and so forth. So, I stored all the stuff in a database. I additionally asked Claude to ask me a bunch of questions throughout the day, about 10 or 15 of them. Um um these are usually simple ones like, "Hey, what are you working on? Why are you working on this? Why did you do that? What systems do you need in order to make this happen?" And the whole idea here is you can tell Claude what you're working on, but oftentimes you don't even fully know all of the context required to make a decision. So, it's far more effective to

[1:16] show it. Now, this took me around a full session's worth of usage. Um I had to upgrade my plan, so you guys will probably have to do that as well if you want to do it on Max thinking, which I'd recommend. Um but assuming that you do, you will actually get a very, very in-depth breakdown of everything that you do. And after that I had a big list of literally all of the deliverables and processes that I personally involved myself with in my agency. Um in my case, it was things like scraping lead lists using Apollo.io or LinkedIn Sales Navigator. It was enriching and verifying emails. It was writing cold

[1:44] email copy and sequences. It was buying and then warming up domains and then sending accounts. Replying to cold email responses. Booking calls. Checking new bookings. Running discovery calls. Sales calls. Proposals. Obviously, there are a lot of things that go into running an agency, so I'm going to spare you all of that, but it is quite the list. The key thing is here, after you have the list, just feed that into a new Claude instance, and then say, "Hey, here's

[2:09] everything that I do on a daily basis. My goal is automating the vast majority of my non-customer facing work. Can you help me build systems for each of these to automate as much as possible?" And if you don't have enough context on any of this stuff, just ask me. And then it'll ask you. And then all you need to do is just voice transcribe your answers to it. So I just use a a simple voice transcription tool. You can dump it all out in probably about an hour or so, and then it will have all of the context that it needs in order to do the

[2:32] automation. So for each of these tasks, then you need to create what are called evals. An eval is a test that repeatedly, over many, many times, records how well an AI model performs a specific task given a specific prompt. It'll then average the results. Uh you need this cuz sometimes AI models will do really, really well in isolation, other times it'll do a really, really poor thing or or outcome on the same job. Uh so in my case, um for every task that I gave it, everything that I've just mentioned, I had it do it 10 times, and then I looked at those 10 outputs, and I scored them myself. If the score

[3:02] was less than approximately an eight out of 10, you know, sometimes I was fine with a little bit less uh certain or accurate score, but most times it was about eight out of 10 or 80%. I just asked Claude, "Hey, how can we improve the system to increase the score according to my goals? Hey, I've noticed that, you know, a lot of the outputs look like this, and I actually want them to look like that." Um so we just looped over and over and over again until it successively improved the skills and the systems that it used to produce the outputs. And then I got all of them,

[3:29] approximately all of them, to seven out of 10 or eight out of 10 or above. Um that was probably the most time-intensive aspect of this whole process. The screenshots and stuff took me no additional time cuz it's just monitoring my work and looking over my shoulder, but this was all like active time where I was actually like, "Hey, this is wrong. We need to fix this. Hey, that's wrong. We need to fix that." Um often times I also had to give it a bunch of templates or assets. So I had to give it a bunch of like high-performing cold email copy examples, for instance. I had to give it

[3:53] a bunch of examples of like qualified lists, high-quality proposals, like, you know, you're going to have to do a little bit of legwork here. But then for all of the systems that score over a certain amount, you can actually institutionalize these as skills. And the reason why it's so important to institutionalize these as skills is because if you get on something like a Claude Teams plan, um you can then share these skills with other people in your organization, even non-technical people, okay, that don't necessarily need to use Claude code in order to get value out of this. They could use simpler tools like Claude Co-work, Claude Chat. By the way,

[4:20] something that will save you a lot of time when you do this is not actually just improving one tiny little part of the skill and then retesting the uh Edal Suite 110. I'd actually recommend you batch three or four tests and run them all simultaneously because um that way you'll parallelize the changes that Claude is making to the skills. And so this saves me a lot of time. If I had to go one at a time, it'd probably take me

[4:40] like a week as opposed to a day. Finally, for every skill that I now had, I simply asked Claude, "Does it make sense to schedule this to run autonomously without me?" Um some skills, like preparing a draft to all of my clients, which I do every morning, and it's a simple draft that just explains, "Hey, you know, here's what I'm working on, here's what I did yesterday, uh here's some blockers that I have." Those are basically completely automatable. You just, you know, give it a check through before sending and then press enter. But other ones, like maybe um building a a deliverable of some kind, building a system, um writing a

[5:10] cold email campaign from start to finish, you don't actually want to schedule these automatically because they do still require, you know, at least human oversight or human in the loop. And so these skills I run um when I need to, essentially. But yeah, you schedule all of the things that you can schedule, and then at the end you literally just have a short list of tasks, like in my case, about five or six tasks that I do on a daily basis for the agency. Uh the other, you know, 80 or 90 are completely automated. And yeah, at the end of this process, I literally ended up automating virtually

[5:37] everything in the business that could run without me. And that's an important distinction. All I now have to do in this business, to be honest, is just show up to calls and then talk about the systems I want to create. Which, you know, some people don't like doing, of course. But, for me, this is actually the part that gives me the most value, the most joy. It's connecting with people, figuring out their bottlenecks, which, by the way, you can you can consult Claude on, as well. But, actually chatting with people and like really figuring out what the heck's going on, and then using my own human

[6:03] knowledge to proactively suggest, uh you know, solutions based off my experience and case studies. I cannot tell you, as somebody that has has had to do so much software engineering in the past, so much useless AB testing, uh dragging and dropping of modules, how freeing all of this is. I genuinely feel like for one of the first times in my life that I am operating at, uh essentially, maximum productivity. I don't really know how much further you can go after this process. I'm sure technology will continue to surprise me. But, yeah, I'm definitely feeling the AGI. And if you guys run through this process top to

[6:33] bottom, just like I did, you you will, as well. So, if you want the same process that I talked about in this video, completely free, you can head over to Maker Zero. That's the second link in the description, and just copy over a detailed prompt that will walk you through building this whole thing. I would highly recommend you use the most

[6:47] frontier model you can on Max Thinking. Because this is such an upstream planning style skill, everything downstream of it uh will essentially be impacted. And so, it makes the most sense to use the most capable model for the task. And that's even if you burn out of usage, you might just have to wait a little while, and then, you know, run when your session uh resets. Um aside from that, if you guys want to grow a business doing this exact thing, check out the first link in the description. That's Maker School. That's my 90-day accountability program, where I'll guarantee you you get a customer in 90 days, or I'll give you your money

[7:15] back for any AI automation or AI consulting service, kind of like what we just talked about today. Um feel free to take a look inside. Um thank you guys very much for supporting the channel, as you always have. And I'm looking forward to catching all y'all in the next video. See you.

---

About this transcript
Read from YouTube's own caption track and laid out by ViewRank AI (https://viewrankai.com).
ViewRank AI finds the videos already beating a creator's own average on Instagram, TikTok and YouTube Shorts, transcribes them from the audio itself in more than 60 languages, and turns what worked into new ideas and scripts.
Free transcript tools, no account needed: https://viewrankai.com/tools
How to read any video this way: https://viewrankai.com/llms.txt