How to research leads in Claude
Source review · Checked . Based on the linked documentation and tool definitions. Examples are illustrative unless a run receipt is provided. Editorial standards
To research leads in Claude, connect ToolRouter and use Lead Finder to discover companies or people, then keep every contact as a candidate with its source fields. Finding a name is not the same as verifying an email. None of these skills send email, LinkedIn messages, or CRM writes. Outreach stays a step you take yourself after you review the evidence.
This rewrite is source-reviewed against the Lead Finder skills and the provider pages linked below. It is not a live enrichment run. The prompt is illustrative. Use the list only for a purpose you are allowed to pursue, and follow applicable privacy and marketing rules before you contact anyone.
Connect, then pick the discovery skill
Follow Connect Claude and enable ToolRouter in the conversation. Confirm Lead Finder is in the catalog Claude loaded.
The skills below are paid. Successful calls are billed at max($0.01, provider cost); failed paid calls do not charge. See Billing and pricing. Optional Hunter, LeadMagic, Prospeo, or Exa keys change which email sources run; they do not change the “review before use” rule.
| Job | Skill | What comes back |
|---|---|---|
| Companies matching a description | find_companies | Name, URL, description, plus structured fields when the provider supplies them |
| People matching a description | find_people | Title, profile url, text excerpt, highlights — not a verified mailbox |
| Lookalikes from one URL | find_similar | Similar pages; one seed URL per call |
| Criteria-checked list with contact fields | prospect | Name, position, company, location, url, email, phone, linkedin_url when returned |
| One known person | enrich_person | Profile fields plus email_candidates |
| Published addresses on a domain | domain_emails | Email, name, position, confidence when available |
| Recent openings | search_hiring_signals | Job rows with observation time, coverage, and a data-use notice |
Exa People Search documents a people index of 1B+ public professional profiles, refreshed weekly. That is Exa's coverage claim for the people category. Treat each ToolRouter row as one provider observation, not a complete directory of every worker at the company.
Evidence fields to keep
find_people is discovery. Contact candidates appear when you enrich or prospect.
enrich_person accepts a LinkedIn (or other) url, or name plus company. Alongside person.email it returns email_candidates. Each candidate carries:
| Field | Use it for |
|---|---|
source | Which lookup produced the address (exa, prospeo, hunter, leadmagic, github, exa-scrape) |
email | The candidate string |
on_expected_domain | Whether it sits on the company domain you passed |
meta.status | Provider status when supplied (Hunter and Prospeo) |
meta.hunter_score | Hunter 0–100 when that source ran |
meta.source_url | Page the address was scraped from (Exa scrape) |
meta.verified_by | Named upstream check when present |
Hunter's Email Verifier API documents status and a deliverability score. A high score is still a provider label. Keep it in the sheet; do not convert it into “safe to mail.”
prospect can AI-check each result against up to five criteria you pass. That check is still a model pass over provider data. Export url, role, company, and any email together so you can reopen the source.
search_hiring_signals is a recency signal (title, optional region and company domain, posted_within in days). Its response includes data_use_notice and coverage. It is not a licence to message applicants.
Build a working table with at least: name, role, company, profile or company URL, email candidate, source, on_expected_domain, status/score, and observed date. Leave blanks blank. Then decide, outside the tool, whether you will contact anyone.
Connect your assistant, then try the task described in this guide.
Illustrative prompt
Use ToolRouter Lead Finder.
1. Call find_people with query "Heads of Product at B2B analytics companies in the UK" and numResults 10.
2. For the first five profile URLs, call enrich_person.
3. Return a table: name, position, company, url, email, email_candidates
(source, email, on_expected_domain, meta.status, meta.hunter_score, meta.source_url).
4. If found is false, keep the row and say so.
Do not send messages. Do not invent an email when candidates are empty.If you are starting from public listing pages instead of a people query, scrape those pages first with How to scrape a website to CSV in Claude, then enrich the domains you kept. Open Lead Finder after you connect at toolrouter.com/connect.
*Source-reviewed 13 September 2026 against the Lead Finder skill contract, Exa People Search, and Hunter Email Verifier docs linked above. Not a live enrichment session and not a send.*
