Use ZoomInfo with an AI Browser for Prospect Research

Run prospect research in Strawberry using ZoomInfo as one of the inputs. Specific surfaces, example prompt, real output, and tradeoffs vs alternatives.

Diagram of Strawberry AI browser workflow using ZoomInfo for prospect research

If you use ZoomInfo and you regularly need to research a prospect, the bottleneck is usually the same: ZoomInfo holds part of the context, but prospect research also needs signals that live outside it - on the public web, in LinkedIn, in news, in other connected apps. Strawberry is built to combine the ZoomInfo context with the rest of the browser, and run the full workflow as a companion you can re-trigger every week.

This page describes specifically how Strawberry handles prospect research when ZoomInfo is one of the inputs. It names the ZoomInfo surfaces involved, the signals the workflow actually needs, an example prompt you can paste, and what a good output looks like.

The job a sales rep, founder, or account executive is trying to do

The goal of prospect research is to decide whether a prospect is worth a calendar slot and prepare a personalised first touch. The success metric is concrete: first reply rate above 8% and a meeting booked in under 14 days from first touch. That definition matters because it shapes what ZoomInfo needs to contribute to the workflow.

What signals prospect research actually needs

For each signal below, here is whether ZoomInfo can contribute directly or whether Strawberry has to find it via the browser:

  • Role tenure and seniority on LinkedIn - ZoomInfo stores or surfaces this directly. Strawberry reads it through the connected integration.
  • Recent funding rounds or M&A activity - ZoomInfo stores or surfaces this directly. Strawberry reads it through the connected integration.
  • Headcount growth or layoffs in the last 6 months - ZoomInfo does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Tech stack and procurement signals - ZoomInfo does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Recent content the prospect has published or commented on - ZoomInfo does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Open job postings that reveal team priorities - ZoomInfo does not contain this directly. Strawberry uses the browser plus public sources to fetch it.

What Strawberry can do inside ZoomInfo

Strawberry can run ZoomInfo searches by company size + intent topic, pull org charts to find decision makers, and combine with public web research for account-based outreach.

ZoomInfo surfaces Strawberry uses for this workflow: contacts, companies, intent topics, Scoops, org charts.

How Strawberry runs prospect research with ZoomInfo

  1. Strawberry opens the ZoomInfo contacts that contains the relevant context.
  2. The companion pulls related context from ZoomInfo (companies, history, attached files) where it exists.
  3. For the parts ZoomInfo does not store, Strawberry uses the browser - web search, LinkedIn, news, the prospect's website.
  4. Strawberry synthesises the output in the shape this workflow needs: A one-page brief.
  5. A human reviews before any external action (send, update, post). Then the approved output is saved back to ZoomInfo or your system of record.

Example Strawberry prompt

Paste this in a new Strawberry chat with ZoomInfo connected. Adjust the specifics to your actual ICP, role, or topic.

Read this ZoomInfo contacts and any linked context.
Then run a full prospect research workflow on it. Use the browser to fill any gaps not in ZoomInfo.
Return the output in the shape we use for prospect research: A one-page brief: name, role, company, ICP fit (yes/no with reason), top 3 talking points, suggested first message, 1-2 source links.
Do not send anything externally. Save the draft to me to review.

What a good prospect research output looks like

Here is what a finished output for prospect research should look like in practice. The specifics will change for your use case, but the shape should look similar:

  • Anna Lindqvist - VP Marketing, Voi Technology
  • ICP fit: yes (Series D scooter co, EU expansion, 1500 employees)
  • Talking point 1: hired 4 paid-acquisition managers in last 90 days - clear shift toward performance marketing
  • Talking point 2: spoke at SuperVenture last month on scooter unit economics
  • Talking point 3: company just announced Germany pull-out - retention focus is likely a priority
  • Suggested first message: short, references the SuperVenture talk, asks one specific question, no calendar link

Why ZoomInfo for this, and where to use a different tool

ZoomInfo is strong for this workflow because Strawberry can run ZoomInfo searches by company size + intent topic, pull org charts to find decision makers, and combine with public web research for account-based outreach.

Where ZoomInfo falls short ZoomInfo Intent topics must match exact strings - use lookup('intent-topics') first; rate limits hit at 5+ parallel calls.

Consider also a CRM (HubSpot, Salesforce, Pipedrive) once the prospect enters pipeline.

Common mistakes when running prospect research

  • Researching prospects who don't match ICP - the brief is wasted
  • Generic talking points ("impressive growth") that don't reference any real signal
  • Copying public bio text instead of synthesising fit

Connecting ZoomInfo to Strawberry

ZoomInfo MCP OAuth - sandbox active; production pending InfoSec review. Once connected, the companion can read the surfaces above without re-authenticating, and any write action still requires explicit human approval the first time the workflow runs.

Caveats

Do not let any AI agent send emails, update CRM records, or change shared systems without a clear approval step. Strawberry is strongest when the workflow combines browser context with connected-app context and a human review for sensitive actions.

How ZoomInfo + Strawberry runs prospect research

1 ZoomInfo

Read

Open the relevant ZoomInfo contacts; pull related context.

2 Browser

Augment

Use the browser, LinkedIn, news, and other connected apps for signals outside the CRM/tool.

3 Output

Compose

Synthesise into the prospect research shape: A one-page brief.

4 Human

Approve

Human reviews before any external action; approved output is saved back.

FAQ - ZoomInfo + AI browser for prospect research

Can Strawberry do prospect research entirely inside ZoomInfo?

No, and that is the point. prospect research needs signals ZoomInfo does not store - public web, LinkedIn, news, other apps. Strawberry combines ZoomInfo with the browser, which is where the real value comes from.

Does ZoomInfo need to be the primary CRM or system of record?

Not necessarily. ZoomInfo can be one input among several. Strawberry can read it as context even if your primary system of record is somewhere else.

What permissions do I need on ZoomInfo?

Read access to the surfaces you want Strawberry to use (contacts, companies, intent topics). Write permissions are only needed if you want Strawberry to update ZoomInfo after a human approves the change. ZoomInfo MCP OAuth - sandbox active; production pending InfoSec review.

What is the realistic success metric for prospect research?

first reply rate above 8% and a meeting booked in under 14 days from first touch - that is the target Strawberry helps you hit, not the only thing it measures.

What is the biggest mistake to avoid?

Researching prospects who don't match ICP - the brief is wasted.