How Operations Managers Use AI Browsers for Prospect Research

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

Why this matters for operations managers

A operations manager spends time on this: keep the company running across systems - finance, vendors, payroll, contracts, ad-hoc projects nobody else owns. The pain that makes prospect research feel slow is real: every system is a different surface; ops admin lives at the bottom of every other team's to-do list. The reason an AI browser helps is that operations managers already use multiple surfaces (Google Sheets, QuickBooks or Xero, Slack, Notion, Calendly) 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 prospect research is to decide whether a prospect is worth a calendar slot and prepare a personalised first touch. For a operations manager, success metric is concrete: first reply rate above 8% and a meeting booked in under 14 days from first touch. A finished prospect research run should look like this: a weekly digest, a vendor brief, a budget variance note, or a process doc - all of it cross-system.

Signals prospect research needs

The workflow needs these signals: role tenure and seniority on LinkedIn; recent funding rounds or M&A activity; headcount growth or layoffs in the last 6 months; tech stack and procurement signals. For a operations manager the practical question is which signals come from the tools already in the stack (Google Sheets, QuickBooks or Xero, Slack, Notion, Calendly) 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 operations manager stays in one surface.

Paste-ready Strawberry prompt

I'm a operations manager. Run prospect research for me using Google Sheets, QuickBooks or Xero, Slack and the browser, then save the draft.

What a finished prospect research output looks like

Concrete example, not a placeholder:

• 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

When this works, and when it does not

This workflow is right for operations managers when the work is repeatable and crosses multiple tools. It is wrong when anything that requires the ops manager to become a domain expert in code, sales, or design. In that case, the operations manager should keep doing the work manually until the pattern is clear enough to automate.

Three mistakes to avoid

• 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

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.