When should you use it?
- You run cold email at volume and segment lists by hand
- Bounce rates are hurting deliverability
- You have more warm follow-ups than time to research them
Not for: Small total markets where dropping catch-all addresses removes too many good leads; Sending without unsubscribe handling and local legal compliance
What do you need, and what do you get?
You need
- A broad company export from your list tool
- Your ICP written as yes or no rules
- An email verifier and a way to look up MX records
You get
- Companies labeled fit or not with a reason
- Leads grouped by email provider
- A verified-only send list and drafted follow-ups
How does it work, step by step?
- Export broad, filter narrowPull a wide company list, then have a script read each website and label it against your ICP.
- Pull contacts for fits onlyLoad only the companies marked as a fit back into the list tool and fetch contacts for those.
- Group by email providerLook up each domain's MX record and match sending inboxes to recipients on the same provider.
- Verify strictlyKeep only addresses that pass every check; drop unknown and catch-all results if your market is big enough.
- Research warm follow-upsFor leads who showed interest then went quiet, draft follow-ups that reference their company, and proofread before sending.
The prompt
Our own prompt, inspired by u/rasmusnilselid on r/coldemail and written to work in Claude Code, Claude and ChatGPT. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Here is a company's website text: {site_text}. Our ICP rules: {icp_rules}. Answer FIT or NOT FIT, then one sentence citing the evidence on the page. If the page has too little information, answer UNSURE. Do not guess industry or size from the company name alone.
Inspired by u/rasmusnilselid on r/coldemail: Claude Code for Cold Email. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- The author notes dropping catch-alls only works with a large market; you lose real leads.
- Website-based ICP labels can be wrong for sites with little text; spot-check a sample.
Our take
This is practical list engineering rather than AI copywriting, and that's why it works. The biggest gains in cold email usually come from who you send to and whether the message lands in the inbox, and three of his four tips are about exactly that. Labeling companies from their own website is a cheap, scalable way to segment that most list tools don't offer, and building it as a small script with a coding agent means you own the rules. The MX grouping is a clever deliverability idea; test it on your own data rather than assuming the lift. Strict verification is the kind of tradeoff that should be a conscious decision: you trade reach for sender reputation. For follow-ups, keep the human proofread he describes. Account research makes a message relevant, but one wrong fact makes it obviously automated. Respect opt-outs and the email rules in each country you send to, and keep sending volumes per inbox modest.
Where the time goes back: Segmentation and list hygiene that used to be manual run as scripts, and warm follow-ups arrive researched.
FAQ
Why match email providers?
Does he write follow-ups himself?
Source and credit
Inspired by u/rasmusnilselid on r/coldemail. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Claude Code for Cold Email
- Creator
- u/rasmusnilselid on r/coldemail
- Published on
- Original date
- May 13, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.