How Partnership Managers Use AI Browsers for Lead List Building

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

Why this matters for partnership managers

A partnership manager spends time on this: find, evaluate, and close partnerships that move revenue or product without acquiring the partner directly. The pain that makes lead list building feel slow is real: research happens before every conversation; pipeline lives in scattered docs and emails; tracking what is open is manual. The reason an AI browser helps is that partnership managers already use multiple surfaces (LinkedIn, Gmail, Notion or Coda for trackers, Calendly, a CRM) 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 partnership manager, 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 fit brief per partner: audience overlap, proposed shape, first ask, executive sponsor.

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 partnership manager the practical question is which signals come from the tools already in the stack (LinkedIn, Gmail, Notion or Coda for trackers, Calendly, a CRM) 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 partnership manager stays in one surface.

Paste-ready Strawberry prompt

I'm a partnership manager. Run lead list building for me using LinkedIn, Gmail, Notion or Coda for trackers 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 partnership managers when the work is repeatable and crosses multiple tools. It is wrong when treating every integration as a partnership when it is just a checkbox. In that case, the partnership manager 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.