When should you use it?
- You do cold outreach and personalization is the bottleneck
- You can build a multi-step automation
- You want research at scale, not mass spam
Not for: Blasting generic mail to huge purchased lists; Claiming the sender hand-researched each lead when they did not
What do you need, and what do you get?
You need
- A source of leads with email and website
- A workflow tool and an LLM
- A sending tool and verified addresses
You get
- Several pages of each lead's site, summarized
- A couple of personal openers per lead
- A spreadsheet ready to load into sending
How does it work, step by step?
- Filter to usable leadsKeep only leads that have both a contact address and a site.
- Read the whole siteHave the workflow pull multiple pages, not just the homepage.
- Summarize each pageLet the LLM condense what the company does and cares about.
- Draft personal openersGenerate a couple of openers grounded in what the site actually says.
- Verify and spread sendingCheck every address and send across inboxes with small, niche lists.
The prompt
Our own prompt, inspired by James Presbitero and written to work in n8n and Custom agent. Values in lime are placeholders.
Build a cold-outreach research workflow: take a list of leads, keep only those that have both a contact address and a site, and for each one read several pages of that site. Summarize what the company does and what it seems to care about, then draft two or three personal openers grounded only in what the pages actually say, no invented praise. Output a spreadsheet with the lead, the summary and the openers. Flag any lead where the site gave too little to personalize.
Inspired by James Presbitero: AI Cold Email System: What It Really Takes in 2026. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Big databases and huge volumes drop reply rates; the author favors small, niche lists.
- Reading the whole site helps, but pretending a human did the research is the part to avoid.
Our take
James Presbitero's write-up is valuable for its honesty about what viral outreach tutorials leave out. Grounding each opener in pages the system actually read is far better than generated flattery, and filtering to leads with both an address and a website removes the people you could never personalize for anyway. He is also openly uneasy about outreach that pretends to be handwritten, which is a fair concern worth keeping in mind. Practical rules from the piece hold up. Keep lists small and specific to a niche, since relevance matters more than volume. Verify every address before sending, because bounces damage your sending domain's reputation quickly. Spread sending across days rather than blasting, and warm up any new domain. The opener must reflect something true and specific from the site; if the summary is thin, skip the personal line rather than inventing one. Follow anti-spam law where you operate, such as CAN-SPAM or GDPR, with a real address and an easy opt-out, and read each draft before it goes out under your name.
Where the time goes back: Personalized research that would take minutes per lead by hand runs at list scale, so outreach feels human without the manual reading.
FAQ
What does the automation personalize from?
Does volume win?
Source and credit
Inspired by James Presbitero. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- AI Cold Email System: What It Really Takes in 2026
- Creator
- James Presbitero
- Published on
- unpromptable.substack.com (Substack)
- Original date
- Oct 15, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- n8n
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
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 24, 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.