How Recruiters Use AI Browsers for Lead List Building

This guide is for recruiters who run lead list building. It explains how an AI browser like Strawberry runs the workflow given the tools a recruiter actually uses every day, what the output should look like, and where the workflow fits in the recruiter's week.

Why this matters for recruiters

A recruiter spends time on this: source, screen, and close hires across multiple roles, often without a dedicated sourcer or coordinator. The pain that makes lead list building feel slow is real: sourcing eats the day; screen calls compete with intake; coordination of interviews falls on the recruiter. The reason an AI browser helps is that recruiters already use multiple surfaces (LinkedIn (Recruiter when licensed), Greenhouse or Ashby or Teamtailor, Gmail, Google Sheets, Notion) to do this work, and the browser is the only tool that can read across all of them and produce a finished output.

What success looks like

The goal of lead list building is to produce a clean, enriched, dedup'd list of N contacts who match ICP and have at least one buying signal. For a recruiter, success metric is concrete: bounce rate below 5%, dedup rate above 95%, and at least 30% of leads with a fresh signal. A finished lead list building run should look like this: a shortlist of 10-30 candidates with role-specific personalised openers, fit notes, and contact links.

Signals lead list building needs

The workflow needs these signals: ICP criteria (industry, size, geo, stack); title match including variants (Head of, VP, Director of); verified email pattern; phone number (when reachable from source). For a recruiter the practical question is which signals come from the tools already in the stack (LinkedIn (Recruiter when licensed), Greenhouse or Ashby or Teamtailor, Gmail, Google Sheets, Notion) versus what the browser has to fetch. Strawberry reads the in-stack tools through native integrations and uses the browser for the rest (LinkedIn, news, company websites, search). The recruiter stays in one surface.

Paste-ready Strawberry prompt

I'm a recruiter. Run lead list building for me using LinkedIn (Recruiter when licensed), Greenhouse or Ashby or Teamtailor, Gmail and the browser, then save the draft.

What a finished lead list building output looks like

Concrete example, not a placeholder:

• Goal: 75 Head of Growth contacts at Series A-B SaaS in DACH
• Sources: a CRM-clean filter, a ZoomInfo/Apollo enriched pull, and a LinkedIn sweep with manual review
• Output: Google Sheet 'DACH-growth-2026-W23' with columns name, title, company, work email, LinkedIn URL, signal (hiring or funding), source notes

When this works, and when it does not

This workflow is right for recruiters when the work is repeatable and crosses multiple tools. It is wrong when spray-and-pray DMs that mention nothing specific about the candidate. In that case, the recruiter should keep doing the work manually until the pattern is clear enough to automate.

Three mistakes to avoid

• Guessing email patterns and getting bounced
• Including duplicates because the source mixes work and personal emails
• Padding the list with leads who don't match ICP just to hit a count target

Caveats

Strawberry holds back on sending email, updating CRM records, or changing shared systems until a human approves the action. Treat the agent as a fast first-draft author, not an autopilot.