Use Google Drive with an AI Browser for Client Reporting

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

The job a agency owner, account manager, founder serving clients is trying to do

The goal of client reporting is to produce a clean, on-brand recap of what was done, what worked, and what is next for a client. The success metric is concrete: report turnaround under 1 day, client approval without major revision. That definition matters because it shapes what Google Drive needs to contribute to the workflow.

What signals client reporting actually needs

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

Campaign or activity data from connected ad/analytics tools - Google Drive does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
Agreed KPIs and last-period comparison - Google Drive does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
Qualitative wins or losses - Google Drive does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
Next-period plan - Google Drive does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
Open questions for the client - Google Drive does not contain this directly. Strawberry uses the browser plus public sources to fetch it.

What Strawberry can do inside Google Drive

Strawberry can find files by query, open Docs/Sheets/Slides in-context, and read content for follow-up actions.

Google Drive surfaces Strawberry uses for this workflow: folders, shared drives, permissions, doc/sheet/slide files, search.

How Strawberry runs client reporting with Google Drive

Strawberry opens the Google Drive folders that contains the relevant context.
The companion pulls related context from Google Drive (shared drives, history, attached files) where it exists.
For the parts Google Drive does not store, Strawberry uses the browser - web search, LinkedIn, news, the prospect's website.
Strawberry synthesises the output in the shape this workflow needs: A PDF or Google Doc structured by section.
A human reviews before any external action (send, update, post). Then the approved output is saved back to Google Drive or your system of record.

Example Strawberry prompt

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

Read this Google Drive folders and any linked context.
Then run a full client reporting workflow on it. Use the browser to fill any gaps not in Google Drive.
Return the output in the shape we use for client reporting: A PDF or Google Doc structured by section: summary, KPI table, highlights, plan, asks.
Do not send anything externally. Save the draft to me to review.

What a good client reporting output looks like

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

Client: Sparbanken Skåne - May 2026
KPIs: CPC -12%, CTR +0.4pt, total leads +18%
Highlights: new creative angle on retention won 60% of impressions
Plan for June: scale the winning creative, test a second segment
Asks: confirm copy review SLA for new creative

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

Google Drive is strong for this workflow because Strawberry can find files by query, open Docs/Sheets/Slides in-context, and read content for follow-up actions.

Where Google Drive falls short PDFs without text layer need OCR; binary files (.psd, .zip, .ai) can't be read directly.

Consider also a structured CRM or Sheet for tracking actions.

Common mistakes when running client reporting

Report is mostly screenshots of dashboards with no synthesis
Missing the comparison vs last period so the client can't tell if things are working
No 'what we're doing about it' section for bad KPI movements

Connecting Google Drive to Strawberry

Drive scope is included when you connect Google Workspace. 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.

How Google Drive + Strawberry runs client reporting

1 Google Drive

Read

Open the relevant Google Drive folders; pull related context.

2 Browser

Augment

Use the browser, LinkedIn, news, and other connected apps for signals outside the CRM/tool.

3 Output

Compose

Synthesise into the client reporting shape: A PDF or Google Doc structured by section.

4 Human

Approve

Human reviews before any external action; approved output is saved back.

FAQ - Google Drive + AI browser for client reporting

Can Strawberry do client reporting entirely inside Google Drive?

No, and that is the point. client reporting needs signals Google Drive does not store - public web, LinkedIn, news, other apps. Strawberry combines Google Drive with the browser, which is where the real value comes from.

Does Google Drive need to be the primary CRM or system of record?

Not necessarily. Google Drive can be one input among several. Strawberry can read it as context even if your primary system of record is somewhere else.

What permissions do I need on Google Drive?

Read access to the surfaces you want Strawberry to use (folders, shared drives, permissions). Write permissions are only needed if you want Strawberry to update Google Drive after a human approves the change. Drive scope is included when you connect Google Workspace.

What is the realistic success metric for client reporting?

report turnaround under 1 day, client approval without major revision - that is the target Strawberry helps you hit, not the only thing it measures.

What is the biggest mistake to avoid?

Report is mostly screenshots of dashboards with no synthesis.

Run client reporting in 10 minutes with Strawberry and Google Drive

Open Google Drive

Connect Google Drive so Strawberry can read folders, shared drives, permissions, doc/sheet/slide files, search and combine them with the rest of the brief. Pin the specific records or views you want to start from so the agent does not drift.
Tell Strawberry the brief

Drop the prompt below. Replace the placeholder with the actual agency owner, account manager, founder serving clients target - one name, one URL, or one Google Drive reference is enough. Keep the goal explicit: produce a clean, on-brand recap of what was done, what worked, and what is next for a client
Let it gather signals

Strawberry pulls campaign or activity data from connected ad/analytics tools and agreed KPIs and last-period comparison, then layers public web sources in parallel. You should see citations next to each fact - that is the audit trail. Watch the Google Drive side: PDFs without text layer need OCR; binary files (.psd, .zip, .ai) can't be read directly
Review before write-back

Output lands in the shape you asked for: A PDF or Google Doc structured by section: summary, KPI table, highlights, plan, asks. Read it once. Fix anything off. The success metric is report turnaround under 1 day, client approval without major revision - if the draft does not hit that bar, send it back with a one-line correction.
Save it as a routine

If you will produce a client report this again next week, click Save as routine. Pick a cadence (daily, weekly, on-trigger). Strawberry re-runs the whole flow on schedule and pings you when the new output is ready.

Paste-ready prompt for client reporting with Google Drive

You are helping me produce a client report client reporting. Use Google Drive as one input and the public web for the rest.

Target: [paste one agency owner, account manager, founder serving clients target here - a Google Drive reference, a name + company, or a URL]

Goal: produce a clean, on-brand recap of what was done, what worked, and what is next for a client

Signals to gather:
- campaign or activity data from connected ad/analytics tools
- agreed KPIs and last-period comparison
- qualitative wins or losses
- next-period plan
- open questions for the client

Output shape: A PDF or Google Doc structured by section: summary, KPI table, highlights, plan, asks

Rules:
- Cite every fact with a link or a Google Drive reference. If you cannot find a signal, say so explicitly rather than guessing.
- Do not invent specifics. Use real, dated signals from the last 90 days where possible.
- If a fact would change the outcome and is missing, pause and ask me before writing the final output.

When the output is ready, surface it in this chat. Do not write back to Google Drive or send anything externally until I approve.

Paste this into Strawberry's chat field. Replace the target placeholder before running.

When Google Drive + Strawberry is the right combo for client reporting

Google Drive is the file system where team documents, decks, and reports live. Strawberry can find files by query, open Docs/Sheets/Slides in-context, and read content for follow-up actions. For client reporting specifically, that means the agent already has folders, shared drives, permissions, doc/sheet/slide files, search as starting context - you do not need to brief it from scratch.

When it is NOT a fit

You need a single number, not a synthesised brief. A SQL query against your warehouse is faster.
The decision is happening in the next 60 seconds. The agent is fast but it is not instant; for hard real-time use, do it manually.
The Google Drive data you would feed in is stale or wrong. Garbage in, confident garbage out.

Three mistakes to avoid

report is mostly screenshots of dashboards with no synthesis
missing the comparison vs last period so the client can't tell if things are working
no 'what we're doing about it' section for bad KPI movements

Honest tradeoff

PDFs without text layer need OCR; binary files (.psd, .zip, .ai) can't be read directly. If you are running this at scale (10+ briefs per day), batch the inputs and let Strawberry process them as a routine instead of one-by-one prompts - cheaper per brief and the output stays consistent.

What a real output looks like

Client: Sparbanken Skåne - May 2026,KPIs: CPC -12%, CTR +0.4pt, total leads +18%,Highlights: new creative angle on retention won 60% of impressions,Plan for June: scale the winning creative, test a second segment,Asks: confirm copy review SLA for new creative