Google Calendar AI Browser for Partnership Research

Diagram of Strawberry AI browser workflow using Google Calendar for partnership research

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

The job a founder, partnerships lead, BD is trying to do

The goal of partnership research is to decide if a partnership is worth pursuing and prepare a specific first conversation. The success metric is concrete: first meeting booked within 14 days, clear next step at the end of that meeting. That definition matters because it shapes what Google Calendar needs to contribute to the workflow.

What signals partnership research actually needs

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

Audience overlap (do their customers look like yours) - Google Calendar does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
Go-to-market motion (do they sell the way you'd want) - Google Calendar does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
History of co-marketing (do they ship with partners or not) - Google Calendar does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
Current ecosystem partners (where do you fit relative to them) - Google Calendar does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
Executive sponsor identification - Google Calendar does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
Any prior conversations with their team - Google Calendar does not contain this directly. Strawberry uses the browser plus public sources to fetch it.

What Strawberry can do inside Google Calendar

Strawberry can read next-7-days events, pull attendee LinkedIn profiles, and compile a prep brief before each meeting.

Google Calendar surfaces Strawberry uses for this workflow: upcoming events, attendees, meeting links, free/busy, recurring rules.

How Strawberry runs partnership research with Google Calendar

Strawberry opens the Google Calendar upcoming events that contains the relevant context.
The companion pulls related context from Google Calendar (attendees, history, attached files) where it exists.
For the parts Google Calendar 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 partnership brief.
A human reviews before any external action (send, update, post). Then the approved output is saved back to Google Calendar or your system of record.

Example Strawberry prompt

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

Read this Google Calendar upcoming events and any linked context.
Then run a full partnership research workflow on it. Use the browser to fill any gaps not in Google Calendar.
Return the output in the shape we use for partnership research: A partnership brief: fit thesis, audience overlap, proposed shape (integration, co-marketing, distribution), first ask.
Do not send anything externally. Save the draft to me to review.

What a good partnership research output looks like

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

Partner: Kime (GEO platform)
Fit thesis: their users (in-house marketers tracking AI-search visibility) need an AI browser to run the research workflows that produce the content Kime tracks
Audience overlap: 30-40% based on Kime's customer list (Saxo, Superb, THEMAGIC5)
Shape: mutual referral, 15% rev share, 18-month attribution
First ask: a 30-min product demo from each side, decide if MCP integration is worth building

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

Google Calendar is strong for this workflow because Strawberry can read next-7-days events, pull attendee LinkedIn profiles, and compile a prep brief before each meeting.

Where Google Calendar falls short Calendar permission scopes are split between read and write; cross-calendar visibility depends on org sharing settings.

Consider also a CRM for the relationship layer.

Common mistakes when running partnership research

Treating every integration as a partnership when it's just a checkbox
No clear thesis so the first meeting is a generic 'let's see how we can help each other'
Skipping audience overlap and pursuing partners whose users don't buy what you sell

Connecting Google Calendar to Strawberry

Google Calendar shares OAuth with Gmail in the Strawberry connection flow. 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 Calendar + Strawberry runs partnership research

1 Google Calendar

Read

Open the relevant Google Calendar upcoming events; 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 partnership research shape: A partnership brief.

4 Human

Approve

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

FAQ - Google Calendar + AI browser for partnership research

Can Strawberry do partnership research entirely inside Google Calendar?

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

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

Not necessarily. Google Calendar 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 Calendar?

Read access to the surfaces you want Strawberry to use (upcoming events, attendees, meeting links). Write permissions are only needed if you want Strawberry to update Google Calendar after a human approves the change. Google Calendar shares OAuth with Gmail in the Strawberry connection flow.

What is the realistic success metric for partnership research?

first meeting booked within 14 days, clear next step at the end of that meeting - that is the target Strawberry helps you hit, not the only thing it measures.

What is the biggest mistake to avoid?

Treating every integration as a partnership when it's just a checkbox.

Run partnership research in 10 minutes with Strawberry and Google Calendar

Open Google Calendar

Connect Google Calendar so Strawberry can read upcoming events, attendees, meeting links, free/busy, recurring rules, event description 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 founder, partnerships lead, BD target - one name, one URL, or one Google Calendar reference is enough. Keep the goal explicit: decide if a partnership is worth pursuing and prepare a specific first conversation
Let it gather signals

Strawberry pulls audience overlap (do their customers look like yours) and go-to-market motion (do they sell the way you'd want), then layers public web sources in parallel. You should see citations next to each fact - that is the audit trail. Watch the Google Calendar side: Calendar permission scopes are split between read and write; cross-calendar visibility depends on org sharing settings
Review before write-back

Output lands in the shape you asked for: A partnership brief: fit thesis, audience overlap, proposed shape (integration, co-marketing, distribution), first ask. Read it once. Fix anything off. The success metric is first meeting booked within 14 days, clear next step at the end of that meeting - if the draft does not hit that bar, send it back with a one-line correction.
Save it as a routine

If you will research a potential partner leads 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 partnership research with Google Calendar

You are helping me research a potential partner partnership research. Use Google Calendar as one input and the public web for the rest.

Target: [paste one founder, partnerships lead, BD target here - a Google Calendar reference, a name + company, or a URL]

Goal: decide if a partnership is worth pursuing and prepare a specific first conversation

Signals to gather:
- audience overlap (do their customers look like yours)
- go-to-market motion (do they sell the way you'd want)
- history of co-marketing (do they ship with partners or not)
- current ecosystem partners (where do you fit relative to them)
- executive sponsor identification
- any prior conversations with their team

Output shape: A partnership brief: fit thesis, audience overlap, proposed shape (integration, co-marketing, distribution), first ask

Rules:
- Cite every fact with a link or a Google Calendar 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 Calendar or send anything externally until I approve.

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

When Google Calendar + Strawberry is the right combo for partnership research

the timeline of who you're meeting with and when Strawberry can read next-7-days events, pull attendee LinkedIn profiles, and compile a prep brief before each meeting For partnership research specifically, that means the agent already has upcoming events, attendees, meeting links, free/busy, recurring rules, event description 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 Calendar data you would feed in is stale or wrong. Garbage in, confident garbage out.

Three mistakes to avoid

treating every integration as a partnership when it's just a checkbox
no clear thesis so the first meeting is a generic 'let's see how we can help each other'
skipping audience overlap and pursuing partners whose users don't buy what you sell

Honest tradeoff

Calendar permission scopes are split between read and write; cross-calendar visibility depends on org sharing settings 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

Partner: Kime (GEO platform),Fit thesis: their users (in-house marketers tracking AI-search visibility) need an AI browser to run the research workflows that produce the content Kime tracks,Audience overlap: 30-40% based on Kime's customer list (Saxo, Superb, THEMAGIC5),Shape: mutual referral, 15% rev share, 18-month attribution,First ask: a 30-min product demo from each side, decide if MCP integration is worth building

Use Google Calendar with an AI Browser for Partnership Research