Use Gmail with an AI Browser for Prospect Research

If you use Gmail and you regularly need to research a prospect, the bottleneck is usually the same: Gmail 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 Gmail 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 Gmail is one of the inputs. It names the Gmail 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 Gmail needs to contribute to the workflow.

What signals prospect research actually needs

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

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

What Strawberry can do inside Gmail

Strawberry can read entire threads, follow attachments, search by query, and draft replies that match a prior writing style.

Gmail surfaces Strawberry uses for this workflow: unread threads, labels, drafts, search operators, attachments.

How Strawberry runs prospect research with Gmail

1. Strawberry opens the Gmail unread threads that contains the relevant context.
2. The companion pulls related context from Gmail (labels, history, attached files) where it exists.
3. For the parts Gmail 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 Gmail or your system of record.

Example Strawberry prompt

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

Read this Gmail unread threads and any linked context.
Then run a full prospect research workflow on it. Use the browser to fill any gaps not in Gmail.
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 Gmail for this, and where to use a different tool

Gmail is strong for this workflow because Strawberry can read entire threads, follow attachments, search by query, and draft replies that match a prior writing style.

Where Gmail falls short Gmail rate-limits search-heavy queries; large inbox scans need pagination; sending requires explicit human approval to avoid spam risk.

Consider also a CRM for relationship history beyond a single thread.

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 Gmail to Strawberry

Gmail OAuth is a Strawberry native integration; no separate scopes setup needed once connected. 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.

When Gmail + Strawberry is NOT the right fit for prospect research

Skip this setup if any of the following is true:

• You don't actually need Gmail signals. If everything you need lives on the public web, drop the Gmail step and let Strawberry run on URLs alone - it's faster.
• Gmail rate-limits search-heavy queries will block the speed gain.
• The buyer (sales rep, founder, or account executive) doesn't own the decision. If the brief gets handed to someone who'll redo the research, the audit-trail-in-Strawberry advantage is wasted.

3 mistakes that kill this workflow

1. Researching prospects who don't match ICP - the brief is wasted. Gmail is one input. Strawberry's edge is combining it with everything else. Stop at Gmail-only signals and you'd have been faster with native Gmail reports.
2. Generic talking points ("impressive growth") that don't reference any real signal. Pre-check Gmail for a recent touch before Strawberry acts on the output. A duplicate hit burns the relationship.
3. Copying public bio text instead of synthesising fit. Strawberry is built so a human reviews before any external action. Skipping that review to save time is how you ship a wrong fact to a real person.

Honest tradeoff vs alternatives

You could research a prospect inside Gmail alone using its native features, or with a dedicated prospect research tool. Gmail alone gives you tighter data fidelity but misses every signal that lives off-platform. A specialised prospect research tool gives you better dashboards but its scope ends where its integrations end, and most of the real signal still lives on the open web.

Strawberry can read entire threads, follow attachments, search by query, and draft replies that match a prior writing style. That's where the Strawberry + Gmail combination earns its keep. The price you pay: an agent run takes 30-90 seconds; a native Gmail action loads in 2. For a one-off question you already know the answer to, use Gmail directly. For an output you'll redo every week or every account, route it through Strawberry as a saved routine so the synthesis happens once and re-runs automatically.

What a real output looks like

• 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