Valdeir Lima · August 2026 · 8 min read

The outbound guide to Claude Code — from someone who runs it daily

Most guides about AI outbound are written by people selling you a tool. This one is different: I run my entire outbound operation on Claude Code, every day, on my own infrastructure. This is what the system looks like, what broke while I built it, and what I would build first if I were starting today.

Why Claude Code instead of fifteen subscriptions

The standard GTM stack in 2026 looks like this: a data tool, an enrichment tool, a sequencer, a deliverability tool, a CRM, and five point tools duct-taping the gaps. Somewhere between $500 and $1,000 a month, and none of them talk to each other properly.

Here is the thing I learned the hard way: the tools were never the moat. Claude can write any workflow in minutes. Knowing which workflow your pipeline actually needs — that is the skill. Once you accept that, the terminal becomes your GTM platform. Claude Code reads documentation, writes the integration, runs it, and fixes it when it breaks. My monthly tooling cost is close to zero. My constraint is judgment, not budget.

The architecture: five stages, zero manual steps

My outbound engine runs end to end without me touching it. The shape is simple:

1. Sourcing. Custom scrapers pull prospects matching my ICP — B2B SaaS founders and growth leaders. I published eleven data actors on Apify for this. You do not need eleven; you need one good source and a clear definition of who you are looking for.

2. Enrichment. Every prospect gets enriched before anything else happens: role, company, headline, recent activity. I use a waterfall pattern — try the first source, fall back to the second, then a scraper as the last step. Enrichment quality decides personalization quality. Garbage in, generic out.

3. Qualification. An LLM pass scores each prospect against my ICP and disqualifies the wrong fits before a single message is written. This is the step almost everyone skips, and it is why most automated outreach feels like spam. Volume without qualification is just noise with better grammar.

4. Personalized messaging. Claude writes each message from the enriched profile — a specific observation about the person, one genuine question. There is a hook I use that outperforms everything else: the message says openly that it was written and sent by an AI system I built, and that if their outbound is still manual, I can build them the same. The cold message IS the demo.

5. Sending and follow-ups. n8n orchestrates the sending with human-like pacing: daily caps, random delays, follow-up sequences that back off when someone replies. The daemon respects limits because a banned account has a reply rate of zero.

What broke — the parts the tool ads never mention

Deliverability and account limits. My first campaign barely fired. Not because the logic was wrong, but because pacing, caps, and warm-up matter more than clever code. If you automate LinkedIn or email, spend your first week on limits, not on message copy.

Silent failures. The worst bug in autonomous systems is the one that fails quietly. My engine once had a scheduling jitter that blew past a timeout and killed five out of six runs. Nothing errored loudly. I only caught it because I check the database, not the dashboard. Build observability before you build volume.

The AI that invented things. Early on, my content system published a post claiming I was at an event in London. I was not. That incident taught me the most important rule of agentic GTM: every outward-facing artifact gets a human approval gate. My engine now emails me drafts and waits. Autonomy for the plumbing, approval for the words.

What I would build first (if I were you)

Not the full engine. One narrow motion, end to end:

1. Define your ICP in one sentence. If you cannot, stop here — no tool fixes this.
2. Source 100 prospects that match it. One source is enough.
3. Enrich them with a simple waterfall.
4. Have Claude qualify them and write one genuinely personal opener each.
5. Send 5 a day, by hand if you must, and read every reply.

Reading replies is where the actual learning lives. The system can scale later; the judgment cannot be skipped.

The honest conclusion

Claude Code turned outbound from a stack of subscriptions into a system I own. But the technology is the smaller half. The bigger half is the same as it always was: knowing who you serve, saying something true, and following up like a professional. The AI just removes the excuse that you did not have time.