Use Google Docs with an AI Browser for Meeting Prep

If you use Google Docs and you regularly need to prepare for a meeting, the bottleneck is usually the same: Google Docs holds part of the context, but meeting prep 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 Google Docs 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 meeting prep when Google Docs is one of the inputs. It names the Google Docs surfaces involved, the signals the workflow actually needs, an example prompt you can paste, and what a good output looks like.

The job a AE, founder, CSM, or anyone with a calendar full of calls is trying to do

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. The success metric is concrete: subjective - the meeting feels productive; objective - notes/next-step ratio is high. That definition matters because it shapes what Google Docs needs to contribute to the workflow.

What signals meeting prep actually needs

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

• Attendee LinkedIn snapshots (role, tenure, mutuals) - Google Docs does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Company recent news (funding, hires, product) - Google Docs does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Last touchpoint in the CRM - Google Docs does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Any open opportunities or support cases - Google Docs does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Agenda or context from the calendar event description - Google Docs does not contain this directly. Strawberry uses the browser plus public sources to fetch it.

What Strawberry can do inside Google Docs

Strawberry can draft new Docs from research or update existing Docs with structured outputs (briefs, recaps, reports).

Google Docs surfaces Strawberry uses for this workflow: headings, comments, suggesting mode, tables, linked Sheets/Slides.

How Strawberry runs meeting prep with Google Docs

1. Strawberry opens the Google Docs headings that contains the relevant context.
2. The companion pulls related context from Google Docs (comments, history, attached files) where it exists.
3. For the parts Google Docs 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 250-400 word brief.
5. A human reviews before any external action (send, update, post). Then the approved output is saved back to Google Docs or your system of record.

Example Strawberry prompt

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

Read this Google Docs headings and any linked context.
Then run a full meeting prep workflow on it. Use the browser to fill any gaps not in Google Docs.
Return the output in the shape we use for meeting prep: A 250-400 word brief: attendees, company snapshot, last touch, suggested agenda, 3 questions to ask.
Do not send anything externally. Save the draft to me to review.

What a good meeting prep output looks like

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

• 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?

Why Google Docs for this, and where to use a different tool

Google Docs is strong for this workflow because Strawberry can draft new Docs from research or update existing Docs with structured outputs (briefs, recaps, reports).

Where Google Docs falls short complex tables can lose formatting; comments are write-once and don't always trigger collaborator notifications.

Consider also a CRM for the relationship layer.

Common mistakes when running meeting prep

• 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

Connecting Google Docs to Strawberry

Bundled in Google OAuth scope. 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 Google Docs + Strawberry is NOT the right fit for meeting prep

Skip this setup if any of the following is true:

• You don't actually need Google Docs signals. If everything you need lives on the public web, drop the Google Docs step and let Strawberry run on URLs alone - it's faster.
• Complex tables can lose formatting will block the speed gain.
• The buyer (AE, founder, CSM, or anyone with a calendar full of calls) 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. Generic bios instead of role-specific context. Google Docs is one input. Strawberry's edge is combining it with everything else. Stop at Google Docs-only signals and you'd have been faster with native Google Docs reports.
2. Missing the most recent news that the prospect would expect you to know. Pre-check Google Docs for a recent touch before Strawberry acts on the output. A duplicate hit burns the relationship.
3. No link back to the prior conversation thread. 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 prepare for a meeting inside Google Docs alone using its native features, or with a dedicated meeting prep tool. Google Docs alone gives you tighter data fidelity but misses every signal that lives off-platform. A specialised meeting prep 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 draft new Docs from research or update existing Docs with structured outputs (briefs, recaps, reports). That's where the Strawberry + Google Docs combination earns its keep. The price you pay: an agent run takes 30-90 seconds; a native Google Docs action loads in 2. For a one-off question you already know the answer to, use Google Docs 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

• 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?