Christian says a Slack agent named Hermes builds his client lists

Christian says his team built an AI agent called Hermes that now builds the lists for almost all of their clients. Anyone on the team messages it in Slack, and it sources, enriches, validates and researches every account. He attached a figure to it, "Hermes + cold outbound = $70M+ in pipeline", which is his own claim with no breakdown of sends, clients or time period behind it.

Christian

@coldemailchris

X

Hermes + cold outbound = $70M+ in pipeline

The post is a pointer to a longer writeup rather than a spec you could rebuild from. He lists what the article covers. What Hermes is connected to. A request walked through start to finish. How to phrase a request so it works. The lists he says Clay cannot build. Account research on autopilot. And where Claude Code takes over from the agent.

What is actually verifiable here

Not much beyond the shape of the system. There is no reply rate, no list size, no error rate on the validation step, and no detail on which data providers sit behind the sourcing. The claim that Clay cannot build certain lists is asserted in the thread, not demonstrated. Treat the $70M as a marketing number until someone shows the campaigns underneath it.

The interesting part for anyone sending is the interface choice. The unit of work is a Slack message from whoever needs a list, not a table someone has to learn to operate. That removes the usual bottleneck where one person on the team knows the enrichment tool and everyone else queues behind them. Whether the output is any good is a separate question and the post does not answer it.

The Claude Code handoff is the other thread worth watching. Christian is not the only operator putting agent tooling between the list and the sequence. Illingworth has argued the same stack can replace Apollo, Clay and Instantly outright, and Lieben has published the APIs that make it run. Christian's version keeps the agent in Slack and reaches for Claude Code only at the point where the agent stops.

For people sending, a chat-driven list builder changes who can request a list, not whether the list converts. The deliverability and targeting problems sit downstream of this and Hermes does not touch them.