How Chiefs Of Staff Use AI Browsers for Content Planning

This guide is for chiefs of staff who run content planning. 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 content planning 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 content planning is to decide what to publish next week and why, with each piece tied to a specific search query or audience. For a chief of staff, success metric is concrete: ratio of published-to-planned > 80%, average time-on-page above 2 minutes, organic traffic up week over week. A finished content planning run should look like this: an exec brief, a meeting recap with owners, or a synthesised view of cross-functional state.

Signals content planning needs

The workflow needs these signals: current search rankings and traffic; competitor content gaps; questions the sales team gets repeatedly; internal subject-matter expertise. 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 content planning for me using Notion, Gmail, Slack and the browser, then save the draft.

What a finished content planning output looks like

Concrete example, not a placeholder:

• Week 24 - Content plan
• Mon: comparison post 'Strawberry vs Manus' - target 'manus AI alternative' - draft by Laurits - publish Tue
• Wed: customer story Iltihouse - target 'AI for outbound sales' - draft by Lotte - publish Thu
• Fri: weekly product release recap - target loyal users + Github watchers - draft by Charles - publish Fri

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

• Planning content nobody actually searches for
• No internal owner so the calendar slips week after week
• Writing about generic topics where the team has no edge

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 content planning more than once a week and the stack is mostly online. Skip it when the run depends on hand-held domain context Strawberry cannot see - private investor calls, off-the-record conversations, paywalled databases the chief of staff has special access to. Run it manually those times and capture the playbook for the next iteration.

The other anti-pattern: using content planning to flatter a senior buyer with surface-level facts they already know. chiefs of staff that scale this workflow always pair Strawberry with a sharp opinion or hypothesis the chief of staff brings. The agent is great at gathering. It is not great at picking a fight.

3 mistakes that kill the run

• planning content nobody actually searches for
• no internal owner so the calendar slips week after week
• writing about generic topics where the team has no edge

Honest tradeoff

Strawberry will not invent missing signals. If a partner does not have a public hiring page, the agent says so - it does not pad the brief with guesses. That is the right behaviour, but it means a chief of staff sometimes sees 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

A chief of staff should be able to send the result to the buyer (content marketer, founder writing for the company, brand lead) without a major rewrite. If the draft needs more than ten minutes of editing, that means the input scope was too broad or the wrong signals were prioritised. Re-run with a tighter subject. Concretely, a strong content planning brief includes:

• Week 24 - Content plan
• Mon: comparison post 'Strawberry vs Manus' - target 'manus AI alternative' - draft by Laurits - publish Tue
• Wed: customer story Iltihouse - target 'AI for outbound sales' - draft by Lotte - publish Thu
• Fri: weekly product release recap - target loyal users + Github watchers - draft by Charles - publish Fri

Anything thinner than that and the run is not done.