8 Workflows That Turn Claude Code Into a Cold Email Machine

8 Workflows That Turn Claude Code Into a Cold Email Machine

Most teams are still doing this manually.

Buying domains by hand. Setting up DNS by hand. Writing sequences by hand. Checking warmup dashboards by hand. Routing replies by hand.

That is six tools, twelve tabs, and a full day gone. Every time you launch a campaign.

The Eight Workflows

1. Domain, DNS and mailbox provisioning via API. Buy domains, set SPF, DKIM and DMARC records, create mailboxes. All of it is API-addressable, and none of it needs a registrar dashboard.

2. Warmup health monitoring with auto-quarantine. Watch per-inbox reputation continuously and pull unhealthy mailboxes out of rotation automatically. Without this, one degraded domain quietly drags down the whole pool and you notice weeks later.

3. Waterfall enrichment across Apollo, Hunter.io and Prospeo. Stop at the first verified result rather than querying every provider for every contact.

4. ICP scoring with Firecrawl website research. Crawl the company site and score fit before spending on contact data. This is the cheapest place in the entire pipeline to disqualify an account.

5. Research-backed personalised first lines at scale. Generate openers from what the crawler found rather than from a merge field.

6. Full campaign builds from ICP definition to send. Go from a definition to a loaded, scheduled campaign without assembling it in a sequencer interface.

7. Reply classification with CRM routing and Slack alerts. Sort every response and get qualified ones in front of a human in minutes.

8. Signal-driven micro-campaigns that auto-launch. When a buying signal fires, a small tightly targeted campaign goes out immediately instead of waiting for the next batch.

The Setup

Four things, in order:

• Install MCP servers for the tools you use (Smartlead, Apollo, Firecrawl, Slack)
• Define your ICP in a project config file so every workflow shares the same definition
• Build reusable skills for each workflow rather than re-prompting each time
• Schedule agents for the monitoring jobs that need to run without you

The ICP definition being centralised matters more than it sounds. When scoring, personalisation, and campaign building all read from one file, changing your targeting is a single edit rather than a hunt through eight prompts.

The Result That Actually Matters

15 to 20 targeted micro-campaigns per month instead of 2 or 3 big blasts.

That is the real change, and it is worth being precise about why it helps.

Big blasts force a compromise. To justify the setup effort, the list has to be large, which means the targeting has to be loose, which means the message has to be generic. Every step follows from the cost of launching.

When launching costs almost nothing, you can run a campaign to 200 companies that all did the same specific thing last week. The list is small, the targeting is tight, and the message can reference something real. That combination is what produces reply rates that look nothing like the benchmark.

What Gets Harder

Two things, and they are worth planning for.

Monitoring becomes your job. A person running campaigns manually notices when something looks wrong. An automated pipeline running twenty micro-campaigns does not volunteer that enrichment has been returning nulls since Tuesday. Build the health checks before you build the volume.

Deliverability risk scales with automation. The system will happily send at a volume that damages your domains if you let it. Auto-quarantine, gradual ramping, and hard volume ceilings are not optional features here, they are what makes the rest safe to run.

Where To Start

Workflow 7, reply handling, before anything else.

It is the highest-value automation in the list, it touches nothing that can damage your sending reputation, and it fixes the failure that costs teams the most: a positive reply sitting unread while the prospect's interest cools.

Then build backwards up the pipeline.

One terminal. Full pipeline. No dashboards.

The Eight Workflows, Ranked By Where To Start

Frequently Asked Questions

Why start with reply handling rather than sending?

It is the highest-value automation on the list, it touches nothing that can damage your domains, and it fixes the failure that costs teams the most: a positive reply sitting unread while the prospect's interest cools. Build backwards up the pipeline from there.

Why are micro-campaigns better than large batches?

Big blasts force a compromise. To justify the setup effort, the list has to be large, so the targeting has to be loose, so the message has to be generic. When launching costs almost nothing, you can email 200 companies that all did the same specific thing last week.

What is the biggest risk of automating cold email?

The system will happily send at a volume that damages your domains. Auto-quarantine, gradual ramping, and hard volume ceilings are not optional features here, they are what makes the rest safe to run at all.

Do I need MCP servers for this?

They help substantially where they exist, because they remove the integration you would otherwise write and maintain. Where a vendor has no MCP server, the agent writes against the raw API instead, which works but puts maintenance back on you.

What does the ICP file actually do?

It centralises your targeting definition so scoring, personalisation, and campaign building all read from one place. Changing your targeting becomes a single edit rather than a hunt through eight separate prompts, which is what keeps the workflows consistent as they multiply.

We build AI-native pipeline systems and you pay per qualified meeting, not a retainer. No paying for activity. You only pay when we book you a qualified sales meeting. See if you qualify.