When should you use it?
- You do your own outbound for a small business
- You want research and drafts done, but sending kept manual
- You already use Claude Code with mail and Sheets access
Not for: Sending at volume from a personal inbox; Lists where you can't verify addresses
What do you need, and what do you get?
You need
- A description of target businesses and location
- Claude Code with Google Sheets and inbox access
- An email verification service
You get
- A sheet with business, email, location and key points
- One personalized draft per prospect
- A verified send list
How does it work, step by step?
- Describe the targetsSay what kinds of businesses, where, and what makes one a good fit.
- Research and logHave the agent find businesses and record email, location and two or three relevant facts in the sheet.
- Verify addressesRun the emails through a verifier before drafting; drop failures.
- Draft in the inboxCreate a personalized draft per prospect using the logged facts.
- Review and send yourselfRead each draft and send at a modest daily pace.
The prompt
Our own prompt, inspired by u/ranger0004 on r/AiAutomations and written to work in Claude. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Find {count} {business_type} businesses in {location} that fit: {fit_rules}. For each, add a row to {sheet} with name, website, public contact email, location, and three facts relevant to {offer}, each with its source URL. Skip any business without a public email. Then create an email draft in my inbox for each verified address: under 120 words, one specific reference to their business, a clear question. Don't send anything.
Inspired by u/ranger0004 on r/AiAutomations: How I automated my Cold Email Outreach with Claude Code. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Sending outreach from a personal Gmail risks your main address; use a separate domain and inbox.
- Unverified addresses raise bounce rates and hurt deliverability.
Our take
This is a sensible, small-scale version of agent-assisted outbound: the agent does the slow research and drafting, and the person keeps control of sending. The two problems he names are the right ones to fix before scaling. Sending cold email from a personal Gmail ties your main address's reputation to campaign results; set up a separate domain and inbox, warm it up, and keep volumes modest. Verification is cheaper than lost deliverability, so budget for it or check addresses with a pay-as-you-go service. Keep the sheet as the source of truth, with a column for where each fact came from, so you can correct mistakes and avoid emailing the same business twice. Personalization should reference something specific and accurate about the business; one wrong detail reads as automated. Add an unsubscribe line and follow your local email rules. Once replies come in, log outcomes in the same sheet so you learn which kinds of businesses respond.
Where the time goes back: Prospect research and first drafts arrive ready; the human step is reading and clicking send.
FAQ
Does Claude send the emails?
What was he stuck on?
Source and credit
Inspired by u/ranger0004 on r/AiAutomations. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How I automated my Cold Email Outreach with Claude Code
- Creator
- u/ranger0004 on r/AiAutomations
- Published on
- Original date
- Oct 23, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- 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.