I Automated My Prospecting With Claude Code: The Real Budget (and What Broke)

Automating with Claude Code isn't about hooking a chatbot up to your inbox and hoping for the best. It's about building, step by step, a chain that reads, decides, acts and reports back, on a budget you can cost out to the euro. I tested the approach on real prospecting work, with the same building blocks I show my small-business clients: Claude Code to write and execute, an MCP protocol to connect the tools, and an orchestrator to tie it all together.

The result is neither the magic promised in YouTube videos nor the Rube Goldberg machine IT directors fear. It's a system that works, has a specific monthly cost, and broke once. Here's how I built it, what it cost, and what I'd do differently.

Why prospecting and reporting eat a solo business owner's time

A small-business owner handling prospecting alone rarely loses time on one big task. They lose it on ten small ones: following up with a forgotten prospect, rebuilding a quote from scratch, compiling a weekly report by hand. A freelancer based in Mauritius describes exactly this pattern on r/FrenchTech: "prospects I kept forgetting to follow up with, quotes rebuilt from scratch every time, accounting I kept putting off." None of it is serious on its own, but stacked together it swallows a full day every week.

Why can't a small business just use ChatGPT?

A standard chatbot answers a question but touches nothing in your systems. A video from the AI Master channel draws a useful distinction between three levels of AI use: basic conversation (ask a question, get an answer), content generation (ask for a script or a draft, but validate every step by hand), and agency-style work, where you hand over a complete objective and the agent figures out how to reach it on its own. Most users stay stuck at the first level without even knowing the third exists.

That shift to the third level is what changes the economics. A solo developer wearing six hats (dev, SEO, sysadmin, accountant, support, follow-ups) recounts on r/developpeurs turning each of those hats into a Claude Code "skill", eventually accumulating around sixty of them. The real trap, in their view, isn't writing the skills: it's organising them without blowing up the context budget on every session.

How I built the automation, step by step

The first step isn't technical: it's mapping the tasks that repeat every week without varying. In a solo agency, that's typically prospecting, invoicing and client reporting. Those are the three blocks I automated first, in that exact order, because each one depends on the previous one for its data.

Claude Code acts as the execution layer: it generates the scripts, reads the documents, and runs commands in the terminal, in French or English depending on how you speak to it. MCP (Model Context Protocol) then connects Claude to the real tools: local files, databases, spreadsheets, inboxes. Without MCP, Claude stays an assistant that describes what ought to be done. With MCP, it does it. A user on r/ZoneIA sums up the difference: with MCP, "Claude can read and edit my project files without me leaving the terminal", for an estimated 30 % time saving on repetitive tasks.

How does Claude Code's auto mode work?

Auto mode, introduced by Anthropic, cuts down interruptions by letting Claude chain several actions together without manual approval at each step. The key point, often misunderstood: Claude does not approve its own actions. A separate classifier, which sees neither the internal reasoning nor the generated responses, compares each action against the user's original intent. According to figures published by Anthropic, 97 % of permission requests get approved in normal use, which gives you a sense of how much friction is being avoided. The classifier blocks irreversible or destructive actions first, such as a force push to a main branch when only a local change was asked for.

Once Claude Code and MCP are in place, n8n (self-hosted) orchestrates everything: it triggers the scripts, passes data between tools, and handles the cases where several actions have to run in sequence without human input. Several solo founders report the same architecture on r/ZoneIA: Claude Code for code and long-form content, n8n for orchestration, and Composio to quickly connect APIs without hand-coding authentication.

At ai-first.fr, I've been training small businesses on this exact stack for months now. I sell that service, so my enthusiasm has a commercial edge to it, but it also comes from what I genuinely see working (and breaking) at my clients, not from a sales brochure.

What it actually costs, and what it returns

The numbers circulating on the forums are remarkably consistent with each other, which is what makes them credible. A freelancer in Mauritius puts their full stack (self-hosted Hetzner server, Claude subscription, n8n) at roughly 80 € a month, for an estimated 15 hours saved per week, concentrated on accounting, client follow-ups and content drafting. Another, on the same platform, quotes a similar cost (10 € of VPS plus around 20 € of Claude API for professional use) for 10 hours saved weekly and a threefold reduction in manual data-entry errors.

What does a Claude Code + n8n stack really cost per month?

The table below compiles the cost lines reported by the users cited above, set against a standard SaaS alternative (Zapier plus a typical CRM subscription) for equivalent use.

On ai-first.fr, I see the same pattern on the audience side: the article covering the Claude Code tutorial in French is still my best-ranking page, at an average position of 8.0 for the query "tuto claude code" over the last thirty days. The volume is modest, but it confirms that demand for the concrete stuff (cost, steps, limits) far outstrips demand for visionary talk about AI.

According to McKinsey's projections on the future of work, a significant share of repetitive administrative tasks remains automatable in the medium term across most support functions, which lines up exactly with what these solo founders report about their prospecting and invoicing.

"The right question is never 'what can AI do?'. It's 'where is my business losing time?'. Until you've answered that, automating anything with Claude Code is pointless."

Vincent, September 2026

What broke (and what it taught me about auto mode)

No serious account of this stack claims it worked on the first try. The same user who puts their saving at 10 hours a week also describes their own failure: an automation workflow that sent duplicate invoices for three days, before they put a simple rule in place, test every new automation on a 10 % sample before running it in full production.

What happens when an agent gets it wrong?

That's exactly the job of the auto mode classifier mentioned above: it doesn't judge the quality of Claude's work, only whether the proposed action stays within the scope that was asked for. An engineer with thirty years of experience recounts on r/ClaudeAI halting all feature development for three days to build a full CI pipeline around GitHub Actions: each Claude Code session works in an isolated branch, a first pass of fast checks validates the code before it merges into the development branch, then a deeper inspection (database migrations, an automated run through a real browser) protects the production branch. Without that guardrail, they considered coordinating between sessions unmanageable past a certain level of complexity.

I see it with my small-business clients: the problem is almost never that Claude Code gets the substance wrong. It's that we give it too much latitude before checking the result on a small scope. Companies that use AI badly create noise and technical debt, not value, and an auto mode classifier is never a substitute for a first small-scale test.

Should you start now? My verdict after testing it

Yes, but not on everything at once. The approach that works, confirmed by every account cited here, fits in one sentence: start with a single measurable use case, run it for two weeks on a reduced sample, then expand. Automating prospecting before you've validated invoicing, or the other way round, reliably produces the same kind of incident described above.

The real budget sits between 80 and 100 € a month for a complete chain (Claude Code, MCP, self-hosted orchestrator), which is still lower than or comparable to a pile of standard SaaS tools, for a substantially broader automation scope. The headline promised two things: the cost can be quantified, and so can the first failure. Both are now down in black and white, which should be enough to decide whether it's worth it for your business.

If you want to dig into the technical build, my full assessment after six months with small-business clients covers the most common mistakes I fix during engagements, and the real-world test of automating client reports shows a case where the agent partly failed its mission. For the cloud orchestration side, without depending on a machine left switched on permanently, the GoLive Software blog covers the aspects closer to pure software engineering.

Frequently asked questions

Do you need to know how to code to automate with Claude Code?

No. Several of the accounts cited here come from people with no developer training, including one tinkerer who describes their own level as "not a software developer". Claude Code accepts instructions in natural language, in French as well as English, and generates the necessary code itself. The difficulty isn't the syntax, it's describing the task to be automated precisely.

What's the difference between Claude Code and a simple AI chatbot?

A chatbot answers a question without touching your actual tools. Claude Code, connected through MCP, reads and edits your files directly, runs commands and interacts with your applications (mail, spreadsheets, databases). That capacity to act, not the quality of the conversation, is what makes the difference in professional use.

Is Claude Code's auto mode dangerous for company data?

Auto mode reduces manual approval requests, but an independent classifier keeps checking each action against the user's original intent, with tighter controls on irreversible actions. The real risk users describe rarely comes from auto mode itself, but from a poorly tested workflow pushed straight into production without going through a reduced sample first.

How long does it take to build your first automation?

The accounts cited converge on a few days for a first limited use case (a prospect follow-up, a weekly report), and several weeks for a complete chain covering prospecting, invoicing and reporting. The single biggest accelerator is starting from one measurable use case rather than trying to automate everything at once.

Is n8n required to automate with Claude Code?

No, but it makes orchestration much easier as soon as you go beyond a single isolated script. Without an orchestrator, Claude Code can handle a one-off task very efficiently, but chaining several triggers together (a new lead, an invoice due date, a weekly report) quickly becomes hard to maintain without a tool built for that chaining.

Vidéos YouTube

• How auto mode works with Claude Code — Claude
• How to Build an AI Agent with Claude Code (Claude AI Agent Tutorial) — AI Master
• How I Fully Automated My Video Editing (Claude Code) — Jason Cooperson
• Diese KI erledigt deine komplette Arbeit (Claude Cowork) — Jonas Keil

Discussions Reddit

• Mon stack IA pour gérer ma micro-agence solo (Maurice) : 6 mois de terrain avec Claude, n8n et MCP — r/ZoneIA
• 6 mois avec Claude Code + MCP + n8n : mon stack IA pour gérer une agence digitale solo (île Maurice) — r/ZoneIA
• Freelance web solo : j'ai fini par bricoler une soixantaine de skills Claude Code autour de mon activité — r/developpeurs
• Depuis des mois je fais tourner mon activité avec un cerveau posé dans Claude, j'en ai fait un kit — r/FrenchTech
• If you're not already using a CI pipeline with your larger Claude Code projects, switch ASAP — r/ClaudeAI

Articles & ressources

• Claude Code : guide pratique pour automatiser vos workflows — flowt.fr