How Business Development Teams Use AI Browsers for Meeting Prep

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

Why this matters for business development teams

A business development lead spends time on this: build pipeline through outbound, partnerships, and channel motions before the AE team takes over. The pain that makes meeting prep feel slow is real: lead lists go stale fast; messaging fatigue is real; partner outreach competes with direct outbound. The reason an AI browser helps is that business development teams already use multiple surfaces (LinkedIn, Apollo or ZoomInfo, a CRM, Gmail, 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 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 business development lead, 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 verified lead list with signals, a sequence draft, or a partner shortlist with fit thesis per partner.

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 business development lead the practical question is which signals come from the tools already in the stack (LinkedIn, Apollo or ZoomInfo, a CRM, Gmail, 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 business development lead stays in one surface.

Paste-ready Strawberry prompt

I'm a business development lead. Run meeting prep for me using LinkedIn, Apollo or ZoomInfo, 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 business development teams when the work is repeatable and crosses multiple tools. It is wrong when lists with high bounce rate or messaging that does not earn a reply. In that case, the business development lead 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.