Richard Illingworth
Every Cold Email Daily story that cites Richard Illingworth (@RCIllingworth), newest first. 27 stories since September 2026.
On X: Founder @ https://t.co/QzwI5sf7yC | #1 GWS and MS365 Inbox Provider | Cold Email Infrastructure That Lands You Clients 👉 CODE “INBOXFIRST” FOR 15% OFF
- Illingworth says a client went 68 days without inbox checks
The vendor's own numbers on automated inbox monitoring, including 12,817 blocked dead addresses.
- Illingworth puts a lifespan cost on every extra daily send
His fix when a campaign needs more volume is more inboxes, not a higher daily number.
- Illingworth, half of 10M emails came from dead inboxes
One agency's biggest account sent 76% of its email from inboxes that are gone, and human replies fell to 0.03 per 100.
- Illingworth, rebuild a domain 3 times before buying a new one
The domain-level version of his lifespan play, built on a book of 570,000+ inboxes he says his team has set up.
- Illingworth posts the subdomain rules behind 60 inboxes per domain
A root that never sends, 20 branches maximum, and a warning that none of it pays off at 30 inboxes.
Know what is landing before you burn another domain
One email a day. Under three minutes. What the operators found out yesterday.
- Illingworth says 60 inboxes need $10 of domains, not $200
He says he tested the belief that subdomains on one root all burn together and found no deliverability difference.
- Illingworth says a reply rate drop rarely needs new domains
His checklist reads drift at domain level, tests with a bland email, then rebuilds accounts in a new Google admin panel to pick up a different IP.
- Illingworth says parallel warmup doubled his inbox lifespan
One operator's replacement cycle, with 10 cold and 20 warmup emails a day per inbox and no placement test attached.
- Illingworth claims 250 contacts enriched in 30 minutes
Eric Nowoslawski says the same job should take under 15 minutes with the Clay CLI and asked to see the table.
- Illingworth posts the six sending rules behind his agency
Twenty sends per inbox, three inboxes per domain, 14 days of warmup and a 70% health score before anything goes out.
- Lieben and Illingworth both post Claude Code cold email builds
Two rebuildable workflows, no send numbers attached to either one.
- Illingworth says subdomains held across 1.8M sends
A client ran 5,000 Google accounts on 10 subdomains per root, and Illingworth says the root never sent a single cold email.
- Illingworth says 3 in 4 first replies land in hour one
He argues a silent inbox at hour 24 points at the list, not the subject line.
- Berman and Illingworth both ditch the compliment opener
Two operators arrive at the same verdict on scraped personalization from opposite directions, and neither published the test data.
- Illingworth says parallel enrichment cut a 12-hour Clay job to 30 minutes
The number is his own, on his own list, and the tool he is replacing is the one he sells an alternative to.
- Ingram says AI lets B2B teams automate mediocrity
Two operators argue in the same week that the automation-first move is the wrong one, from different sides of the market.
- Illingworth and Shields put replies upstream of copy
Two senders spent the week arguing that inbox placement is arithmetic, not writing.
- Illingworth says a seven-source list beats Apollo alone
He names Google Maps, Apify, Sales Navigator and four more tools, and claims the same list performs 3 to 4x better.
- Illingworth gives away an infrastructure spec for 10,000 sends a day
A free blueprint with a sizing formula, a four week warmup schedule and a bounce rate target, and no reply numbers behind it.
- Christian splits cold email sends by MX record
One enrichment column, two campaigns, and a reply rate that finally means something.
- Lieben puts a Claude Code campaign at 15 minutes
Michel Lieben times a one-prompt run on the Forbes AI 50, and Richard Illingworth says the same rebuild cut a week of manual work to an afternoon.
- Illingworth says campaigns held with almost no warmup
One operator, no send volumes posted, and he says he is still testing.
- Illingworth adds QC pass and segment cuts to Claude Code stack
Two steps past the version he published last week, with a caveat about inboxes attached.
- Illingworth says config rebuild took a client 0.9% to 23% replies
One operator's before and after, with the copy and the list held constant.
- Illingworth says one $10 domain can carry 60 inboxes
The spec sits behind a comment gate, and the same operator lists 10 inboxes on one domain as a spam cause.
- Lieben maps 28 APIs for cold email inside Claude Code
The connection order runs from hiring signal to verified address to an Instantly campaign you switch on yourself.
- Illingworth says Apollo-only lists run 50-65% valid
One operator's build order for lists, plus the bounce thresholds he uses to decide when to stop sending.
Get the next one by email
Cold email and outbound, read daily so you do not have to. The campaigns, the reply rates, the deliverability findings and the copy that ran, from operators who send at real volume. No revenue flexes, no course launches.