When should you use it?
- Lead lists are full of weak fits
- You can state your ideal customer clearly
- You want reasons, not just scores
Not for: Scraping personal data at scale; Sales teams without anyone to review edge cases
What do you need, and what do you get?
You need
- Your target-customer definition in writing
- Public sources of candidate companies
- A sheet or CRM to receive rows
You get
- Scored leads with fit and confidence
- A one-line reason for each
- An edge-case queue
How does it work, step by step?
- Define the profileWrite down size, industry, signals and disqualifiers.
- Filter earlyDrop obvious misfits before spending research effort.
- Research each candidateLook at each firm's site and news for supporting evidence.
- Score with light rulesUse a simple qualification checklist rather than a heavy sales method.
- Export with reasonsSend rows with the evidence attached; route uncertain ones to a person.
The prompt
Our own prompt, inspired by Nimesh Kulkarni and written to work in Custom agent. Values in lime are placeholders.
Using this ideal customer profile: [ICP], find candidate companies from [sources]. Discard obvious misfits first. For each remaining company, read its site and public news, then score fit from 1 to 5 and confidence from low to high, with one sentence of evidence and a link. Put uncertain cases in a separate list. Output rows for [CRM fields]. Do not contact anyone.
Inspired by Nimesh Kulkarni: How I Built a Hermes Agent for Lead Generation That Finds and Qualifies Better Prospects. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Numbers with no explanation are hard to trust or act on.
- Public signals go stale; date your research.
Our take
Nimesh Kulkarni's Hermes flow is sensible and modest, which is what lead generation needs. Collecting candidates from public sources, filtering early against an ideal customer profile, researching each company, scoring fit and confidence with light rules, sending edge cases to a person and exporting CRM rows with reasons attached aims for fewer, better leads rather than a bigger pile. The insistence on a reason for every score is the habit to copy, because a number without evidence is useless in a sales meeting. Keep the profile document under version control and review it monthly against which leads actually converted, so the score stays honest. Prefer company-level research over personal profiling, and respect privacy and spam rules where you sell. Never let the agent send outreach; export and review first. Cap how many new rows enter the CRM per day until quality is proven. Drop sources that consistently produce low scores rather than scoring more junk.
Where the time goes back: Reps stop wading through junk lists and start with prospects whose fit is already explained.
FAQ
Does it send outreach?
Why not one big prompt?
Source and credit
Inspired by Nimesh Kulkarni. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How I Built a Hermes Agent for Lead Generation That Finds and Qualifies Better Prospects
- Creator
- Nimesh Kulkarni
- Published on
- DEV Community (dev.to)
- Original date
- May 20, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- 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 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.