I spent the last 4 months designing AI automation systems for my company as someone who had never touched coding before, and here is what worked for me
I spent the last 4 months designing AI automation systems for my company as someone who had never touched coding before, and here is what worked for me

I spent the last 4 months designing AI automation systems for my company as someone who had never touched coding before, and here is what worked for me

This is all based on my experience. I’ve spent over 6 months in total working on AI setups alone for my business, and most of the work was focused on automating some of the tasks that used to be very time-consuming. About 2 months were wasted trying multiple setups before I discovered Claude Code and started actually building systems that work.

Discovering Claude Code

As you can imagine, this was THE moment for me. Months of moving from one model to another, months of trying to integrate the basic paid versions of ChatGPT, DeepSeek, and Claude into my workflow. Experimenting with those custom AI agents (and actually paying about $100 for a subscription for one of these), with barely any success.

ChatGPT/Claude projects looked cool in theory, but had no permanent memory outside the chats. I couldn’t teach them to perform anything beyond the simplest tasks, and giving them perms to actually edit my sheets/docs; learn and improve was pain in the ass. Each upgrade meant me having to make yet another doc (or edit the existing one) in the project’s memory, and it never really meant too much progress. Then a client of mine showed me Claude Code, a system I wrongfully ignored because I’m not a developer and felt like I couldn’t make any use of it. Boy was I wrong.

Honeymoon Period

Since I discovered Claude Code, my free time got deleted, I gained 5 kilos, and I have been glued to my PC more than during my most hardcore gaming days. It truly felt insane at first, the thing built a full app for me in a single day, I just described what I wanted. Then it optimized it, helped me build the structure, did everything, and even designed it. I was like “Fuck, AI’s gonna replace us all” and I mean this as no joke. For literal weeks, I was lying in bed at night thinking how my agency, my life’s work gonna crumble before my own eyes because AI can now do some insane stuff and I’ll have to pivot into tourism or something as far from AI as possible.

This period was truly amazing because I never realized how quickly time can pass when you do something you love - building and inventing. I don’t know the number of “AI-powered tools” I planned to do and the times I felt like this is the opportunity for me to become a billionaire. Until I slowly realized one hard truth.

AI is amazing, but it’s not all-powerful

As I started actually using the tools I’ve built and actually putting them into practice with my employees, issues were emerging one after another. A bug here, an issue there, then a random loop that eats all my API credits. I would usually just be like “Okay, let’s go again”, but as I continued, it was more obvious that AI can make the big-picture stuff in moments, but the actual, fine-tuned, working systems? For that, you’ll need weeks. I’m not a developer, so I don’t know how to better put this, but it felt like the AI built a house, and from the outside, it looked totally normal. Then you start digging into the walls and foundations and actually using the house, and you realize most planks are rotten, the bricks are layered unevenly, the foundation has holes in it, and every time you try to do an actual walk to the kitchen and back (a full workflow), multiple things break. Not knowing how to write a single line of code didn’t help here at all, so I tried using AI to actually do full-checks and fix the issues. It worked, to a certain extent - in a way that it gets off rails, I put it back, then it drives to the next spot (task), falls off rails again, and the process repeats.

This actually taught me a ton and brought me back to my philosophy roots and the 80/20 rule. AI can do 80% of the work really fast and really well, but the remaining 20% needed to make the entire system actually work in practice takes weeks.

The middle ground, the reality

I quickly realized one thing - AI automation is amazing as a support system, but for actual, quality work, you need people. No AI brain can replace a human one, and no AI tool can do what a quality employee can. I never even thought about “replacing my team with AI” because I honestly don’t give two shits about making more money over ruining loyal people’s lives, but still, I was happy to know the limits of the AI.

Back on the topic, I actually tested multiple workflows at this stage - a single agent with all the knowledge vs multiple specialized agents. Claude Code vs Codex vs OpenClaw-like tools. Each of the workflows had its own advantages and shortcomings, that I’ll try to summarize here:

  • Single agents (Claude Code and Codex) work amazing for strategy, high-level tasks. The more knowledge they have in their md files the better, but you have to be careful because of the active memory limitations. The architecture alone cannot support too much knowledge, and if you try to use one agent for, let’s say, digging, evaluating, reaching out, and quality-checking LinkedIn leads, it won’t work that well. However, a single agent with a ton of knowledge about the grand plan to oversee the process and qualify leads, and then specialized, minor agents with very well-defined skills for digging and writing outreach messages will work well. Separate tasks fall into the specialized agent’s hands and they actually do an amazing job with a clear set of rules/instructions.
  • Multiple agents work well, but they have their risks too. If you overspecialize and have each agent have knowledge about only their job, consider only their job, you will get a system that looks like a chain where every link was made individually by a different smelter, and none of them knows about the other links, or even less the entire chain. The quality of the entire workflow just won’t be there.

My solution was a mix of both - larger, single agents with all the knowledge for ideating/strategy tasks and smaller, minor agent with a narrow, specific set of specialized skills for the execution of specific tasks. This resulted with the best quality, I’d say almost 70%-80% of what a human can produce.

However, the next issue I faced was: Inconsistency

AI ALWAYS pigeonholes into certain pre-defined, approved workflows, and you can’t really deviate from that too much. If you teach it how to write a LinkedIn outreach message, and then reiterate time after time until it learns a good pattern, that pattern will be almost all it does. Won’t be an issue at first and you’ll be like “damn this is fucking amazing”, but then 4 weeks in you’ll see that every new campaign somehow sounds very close to the old ones. If it tries a new approach, it will usually fail miserably, but if you teach it that new pattern now - that will be all it does. That’s why we all see the same spammy LinkedIn posts, Reddit posts, Reddit comments, LinkedIn outreach messages, emails. They all sound the same, and if you really spend enough time analyzing this, you’ll be able to catch AI by a single flow or a single construction it uses. It’s just not smart enough yet to really have variety, and while the quality starts at 70%-80% as I mentioned before, it relatively quickly drops down to below 60% - as soon as you need to change the pattern because the old one was overused.

My Setup

Now, I managed to battle this in a very specific way that works for me, and I can’t promise it will work outside my workflow because I don’t have a single clue of how it works in the backend.

Automating stuff like research and docs/sheets browsing was hard to do with Claude Code and Codex simply because I didn’t want to give it autopermissions on everything, and manually approving it meant no automation and having to stay there and click all the time. There could be a way to give it a specific range of autoperms just for internet research and docs/sheets browsing, but I didn’t want to mess with that so I looked for alternatives instead. OpenClaw looked veeeery enticing, and I’m actually looking into getting a Mac Mini just for that, but the supply of these is scarce in my region and they’re quite pricy. Instead, I found a substitution, MoClaw, and I’m using it right now because it hosts the entire thing on its own PC. This means that it can freely browse the internet and docs/sheets without requiring permissions and without putting my rig at any risk. Plus, it doesn’t expose my IP, nor can it overuse my APIs and get me banned or waste all my credits (happened once with Claude Code because I overused an API and now I’m super careful).

This might not be a plus for everyone, but as someone who doesn’t have a clue about software development and programming, I’d rather use a tool like MoClaw that’s safe and hosted on another PC than risk hosting OpenClaw on mine and getting some things destroyed, at least until I get a Mac Mini.

This agent is used strictly for search. I trained it to do research and digging, and the entire goal of this stage is to find whatever I’m looking for. One example is - when I do sales, the agent does all the digging and finds the best prospects based on the diagonal I’m selling to at that exact moment. I layered the info for each diagonal in a separate md file, and have several text files with instructions (diagonal-based, of course) that are booted whenever I need that. The way it works is - the agent does a deep search on the internet and goes through a predefined list of websites where I usually find my best prospects. Then it uses its knowledge stored in the md files and instructions to filter through the companies. Once that’s done, it does research on each individual company, finds out the unique selling points, and pushes all that info to a spreadsheet, together with the LinkedIn profiles of the CEOs.

This is where my strategists come into action. I’m currently using the Claude Code-based ones, but I also tried the Codex version, and they works pretty well too. One huge advantage of Codex is - with a monthly $20 or $25 sub (I forgot the price), you can do almost the same amount of work as with the Claude $100 sub. If you’re trying to save money, go for Codex right now, or even Deep Seek (haven’t tried myself, but a friend did and he told me it works pretty fine).

The strategist monitors the Google sheet, and as soon as MoClaw adds prospects and all the info needed to get a good angle on them, it pulls that data, uses the vast knowledge about my company, my work, my best examples, etc. and creates angles for each of the prospects. Keep in mind - I don’t use the strategist to do actual writing. It just leaves a template of how to reach to that individual subject, what selling point to use, and how to ultimately convert them. That template is distributed to the writers through a dashboard. The strategist can also create a short sales playbook in case I need something to reference during conversation, but this is done only for the highest level of prospects.

Then the SDR agents come in and write the messages (also Claude-based, but ChatGPT version works pretty well too, the style is just different). Their sole purpose is to write converting copy, and they have only a few skills - writing being the most important one - to make sure their focus stays razor sharp. Tried adding more knowledge to them, but it just dilutes the writing, so I decided to keep them concise and focused. They write each individual outreach sequence and save it to the sheet.

Possibly the most important layer here - Quality Assurance - and it happens in stages. Multiple agents check the messages to make sure the AI didn’t hallucinate, the angle used to approach them was actually on point, and the prospects are the actual people we’re targeting. Trust me when I tell you, it happened more than a few times that the AI hallucinated the angle, the prospect, or just did a bad job researching (this was especially the case before I moved to MoClaw for research because Claude would just make shit up to make it look like the job was done). ADD A QA LAYER!!!

Lastly, the LinkedIn list, together with the personalized messages with a unique angle for each prospect, is uploaded to Expandi to finish the circle. This stage takes some manual work, but it really does help because clicking on these people’s LI profiles, opening their company page, following it, liking their posts, and commenting (if there’s anything to comment on) would take so much time per prospect that I’d probably just give up and spam connection requests. To avoid that, I use Expandi and just automate all of this stuff.

Closing Thoughts

Now, my actual salesmen are monitoring all of this, making sure everything’s done correctly, and tracking the entire workflow. They are responding to messages and leading the conversations, but the bulk, hustle part of the job is now totally automated. I didn’t replace my guys with AI, I just built systems that helped them push their work to the next level and focus on things that actually matter - converting the prospects into paying clients.

This is one example of an (almost) fully automated workflow that I’ve designed. It works pretty well, the entire system is layered, and the success rate is actually pretty high. I can’t point at the exact thing making this system successful, but I can tell you that I have more clients than ever, definitely more than when I did all of this manually.

I’d gladly share the other systems here, but the length of this post has become quite alarming, so I’ll have to wrap it up here. If you have any questions or anything you’d like to know, please feel free to ask. I’d be more than happy to help!

EXTRA NOTE: Claude Code seems to officially be behind Codex now. I tried both setups today after coming back from a short vacation, and Codex is both sharper and much cheaper. If your entire setup isn't relying on Claude Code currently, I'd advise going with Codex. Plus the barrier of entry is much, much cheaper.

submitted by /u/RainbowFatDragon
[link] [comments]