How Chiefs Of Staff Use AI Browsers for Meeting Prep

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

Why this matters for chiefs of staff

A chief of staff spends time on this: shadow the CEO across every meeting, surface what is being lost in the noise, and turn decisions into shipped work. The pain that makes meeting prep feel slow is real: context lives in every channel at once; the chief of staff is the only one with cross-functional visibility but no time. The reason an AI browser helps is that chiefs of staff already use multiple surfaces (Notion, Gmail, Slack, Google Workspace, the company CRM and analytics tools) 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 chief of staff, 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: an exec brief, a meeting recap with owners, or a synthesised view of cross-functional state.

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 chief of staff the practical question is which signals come from the tools already in the stack (Notion, Gmail, Slack, Google Workspace, the company CRM and analytics tools) 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 chief of staff stays in one surface.

Paste-ready Strawberry prompt

I'm a chief of staff. Run meeting prep for me using Notion, Gmail, Slack 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 chiefs of staff when the work is repeatable and crosses multiple tools. It is wrong when anything that requires the CoS to become the bottleneck on a function that should own itself. In that case, the chief of staff 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 chiefs of staff

This workflow earns its keep when chiefs of staff run meeting prep more than once a week and the stack is mostly online. Skip it when the run depends on hand-held context Strawberry cannot see - private investor calls, off-the-record conversations, paywalled databases chiefs of staff have special access to. Run it manually those times and capture the playbook for the next iteration.

The other anti-pattern: anything that requires the CoS to become the bottleneck on a function that should own itself. Chiefs of staff that scale this workflow always pair Strawberry with a sharp opinion or hypothesis chiefs of staff bring. The agent is great at gathering. It is not great at picking a fight on your behalf.

3 mistakes that kill the run

• 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 a subject does not have a public hiring page, the agent says so - it does not pad the output with guesses. That is the right behaviour, but it means chiefs of staff sometimes see a shorter output than expected. The fix is upstream: feed it better sources, or accept that this subject is information-sparse and move on. Pretending the signal exists is what gets chiefs of staff into trouble; an empty section is a feature, not a bug.

What a finished output looks like

Chiefs of staff should be able to send the result to the next person in the chain (buyer, manager, client, hiring partner) without a major rewrite. If the draft needs more than ten minutes of editing, the input scope was too broad or the wrong signals were prioritised. Re-run with a tighter subject. Concretely, a strong meeting prep brief includes:

• 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

Anything thinner than that and the run is not done.