When we say Claude Code replaced our outbound stack, we mean it replaced the layer that connected everything. Data providers, sending platforms and the CRM are still there. What went away was the manual coordination between them, plus a set of point tools whose only job was moving data from one place to another.
We rebuilt our pipeline around Claude Code because the old setup had a familiar shape. Each tool did its job well, but a person had to decide what happened next, export a file, clean it and load it somewhere else. Every campaign depended on that person having time. The rebuild moved those decisions into written rules and the handoffs into code that Claude Code runs.
The seven stages we run
Every campaign goes through the same sequence. Each stage has a narrow job and a clear output that the next stage reads.
1. Detect signals
We watch for hiring, funding and technology changes. Each signal is tagged by strength, and only signals that point to buying intent move forward. A news mention that does not change what an account needs stays out of the pipeline. Our guide to signal-based outbound covers how to decide which events count.
2. Score against the ICP
Claude Code reads our ICP rules from a file and scores each account on fit and signal. This is where most noise is removed, before anyone spends money on data or writes a word of copy. If your ICP is not written down in a form a machine can apply, start with how to define an ICP for outbound.
3. Find decision-makers
The contact search is built from the ICP rather than from a generic title list. We pull key roles only, usually one to three buyers per account. More contacts per account rarely means more conversations. It usually means more people ignoring the same message.
4. Enrich across providers
Contacts run through three providers in a fixed waterfall order. The waterfall fills emails, LinkedIn profiles and firmographics, and the clean result is written back into the working table. One provider rarely covers a whole list, so the order and the fallback rules matter more than any single source.
5. Generate personalized copy
Copy generation reads our offer and past wins from files. The angle comes from the signal and the role. The tone comes from our best-performing templates. The model is not inventing a pitch from nothing. It is applying frameworks we have already tested.
6. Push to campaign
Contacts and copy sync to the sending platform, sequences are set, and the CRM is updated as part of the same run. Nobody has to remember to log the campaign afterwards.
7. Analyze and improve
Replies and meetings are tracked, wins are written back into the record, and templates are updated from real results. This is the stage most teams skip, and it is the one that makes the next campaign better than the last. It relies on clean outbound attribution.
What was actually replaced
Replaced
- Manual exports and imports between tools
- Spreadsheet steps used to clean and merge data
- Copy written from scratch for every campaign
- After-the-fact CRM logging
- Point tools that only existed to connect other tools
Still in place
- Data providers for contacts and firmographics
- A sending platform with proper deliverability setup
- The CRM as the system of record
- Human review of ICP rules, copy frameworks and results
Framing this as "the stack is gone" misses the point. Data still has to come from somewhere, and emails still have to be sent from infrastructure that protects your domains. The change is that one orchestrator now holds the sequence and the rules, instead of a person holding them in their head.
Claude Code, Clay or n8n?
We still use different tools for different jobs. As a rough guide from our own work:
| Tool | Where it fits best |
|---|---|
| Claude Code | Multi-step work that needs judgment and context: scoring against written rules, writing copy from frameworks, analyzing replies, and running the whole pipeline end to end |
| Clay | Table-based enrichment and research where a person wants to see and adjust rows, and where many data providers are already connected |
| n8n | Fixed, scheduled or event-driven automations that should run the same way every time without a person starting them |
The choice depends on who needs to operate the workflow and how often it changes. A stable webhook that updates the CRM belongs in a scheduled automation. A campaign that needs new scoring logic every month is easier to run from Claude Code with the rules in files. For the setup side, see building outbound agents in Claude Code.
What we would tell a team starting now
- Write the rules before the code. ICP, tiering and copy frameworks should exist as files a person can read and edit.
- Rebuild one campaign first. Take a play you already run manually and move it into the pipeline. Compare the output with what the team would have done.
- Keep a review step. An orchestrated pipeline can launch a bad list quickly. Check the scored list and a sample of copy before anything sends.
- Close the loop early. The analysis stage is what turns a faster process into a better one. Build it in from the first campaign.
Conclusion
The shift is less about one tool and more about where the logic lives. When the rules, the sequence and the learning sit in one place that a model can read and run, the tools around it become simpler to swap and easier to trust. If you want to see where that would change your own outbound, book a GTM Engine Review. Jan covers the same pipeline from the client side in Claude Code for outbound.