How Agency Owners Use AI Browsers for Meeting Prep

This guide is for agency owners who run meeting prep. It explains how an AI browser like Strawberry runs the workflow given the tools a agency owner actually uses every day, what the output should look like, and where the workflow fits in the agency owner's week.

Why this matters for agency owners

A agency owner spends time on this: win new clients, retain existing ones, and produce billable work across multiple accounts with a small team. The pain that makes meeting prep feel slow is real: client reporting and pitch decks consume the senior team's time; juniors cannot produce them at quality. The reason an AI browser helps is that agency owners already use multiple surfaces (Slack, Google Workspace, a CRM, HubSpot or Notion for client tracking, Looker Studio or sheets for reporting) 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 meeting prep is to produce a one-page brief for each upcoming meeting so the person walks in informed and time isn't wasted. For a agency owner, success metric is concrete: subjective - the meeting feels productive; objective - notes/next-step ratio is high. A finished meeting prep run should look like this: a draft client report, a pitch deck section, or a research brief that is 80 percent there and only needs minor polish.

Signals meeting prep needs

The workflow needs these signals: attendee LinkedIn snapshots (role, tenure, mutuals); company recent news (funding, hires, product); last touchpoint in the CRM; any open opportunities or support cases. For a agency owner the practical question is which signals come from the tools already in the stack (Slack, Google Workspace, a CRM, HubSpot or Notion for client tracking, Looker Studio or sheets for reporting) 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 agency owner stays in one surface.

Paste-ready Strawberry prompt

I'm a agency owner. Run meeting prep for me using Slack, Google Workspace, a CRM and the browser, then save the draft.

What a finished meeting prep output looks like

Concrete example, not a placeholder:

• Meeting: 14:00 Thursday with Anna Lindqvist (VP Marketing, Voi) and Erik Nilsson (Head of Growth)
• Last touch: warm intro from Marcus on May 14, no reply since
• Company news: Germany pullout announced May 28; hired 4 paid acquisition managers in Q1
• Suggested agenda: 1) Their take on Germany decision, 2) Where retention sits in 2026 priorities, 3) Show 90-sec demo of win-back loop
• Three questions: How is the team structured post-pullout? What's the budget cycle? Who owns retention KPIs?

When this works, and when it does not

This workflow is right for agency owners when the work is repeatable and crosses multiple tools. It is wrong when any output the agency cannot defend to the client without a human review pass. In that case, the agency owner should keep doing the work manually until the pattern is clear enough to automate.

Three mistakes to avoid

• Generic bios instead of role-specific context
• Missing the most recent news that the prospect would expect you to know
• No link back to the prior conversation thread

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.

When this is NOT a fit for agency owners

Skip this workflow when any output the agency cannot defend to the client without a human review pass. agency owners should keep doing the work manually until the pattern is clear enough to automate, otherwise you ship a generic meeting prep brief that hurts trust.

Three mistakes to avoid

• Generic bios instead of role-specific context.
• Missing the most recent news that the prospect would expect you to know.
• No link back to the prior conversation thread.

Honest tradeoff

Strawberry will not invent missing signals. If the public web does not have headcount data or the CRM is empty, the draft will say "unknown" rather than guess. That is the right behaviour - the workflow is faster, not magic. The win for agency owners is that the first draft is 80% there and the remaining 20% is judgement, not data plumbing. A good run looks like: a draft client report, a pitch deck section, or a research brief that is 80 percent there and only needs minor polish.

What a finished output looks like

• Meeting: 14:00 Thursday with Anna Lindqvist (VP Marketing, Voi) and Erik Nilsson (Head of Growth)
• Last touch: warm intro from Marcus on May 14, no reply since
• Company news: Germany pullout announced May 28; hired 4 paid acquisition managers in Q1
• Suggested agenda: 1) Their take on Germany decision, 2) Where retention sits in 2026 priorities, 3) Show 90-sec demo of win-back loop
• Three questions: How is the team structured post-pullout? What's the budget cycle? Who owns retention KPIs?