How Chiefs Of Staff Use AI Browsers for Invoice And Ops Admin

This guide is for chiefs of staff who run invoice and ops admin. 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 invoice and ops admin 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 invoice and ops admin is to process invoices, reconcile expenses, chase receivables, and keep ops paperwork unblocked. For a chief of staff, success metric is concrete: no late payments, no missed renewals, all expenses categorised within 7 days. A finished invoice and ops admin run should look like this: an exec brief, a meeting recap with owners, or a synthesised view of cross-functional state.

Signals invoice and ops admin needs

The workflow needs these signals: incoming invoices from email/PDF; current overdue receivables; vendor metadata (terms, payment method); expense receipts that need categorisation. 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 invoice and ops admin for me using Notion, Gmail, Slack and the browser, then save the draft.

What a finished invoice and ops admin output looks like

Concrete example, not a placeholder:

• Week of June 2 - Ops admin
• Pay: Mailgun ($249) due Jun 8, Postmark ($150) due Jun 10
• Chase: 3 invoices over 30 days - Acme ($4k), Foo ($1.2k), Bar ($800)
• Renew: Notion Plus auto-renews Jun 14 - confirm we still need it
• Cancel: Loom Pro - team moved to internal screen recording

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

• Leaving invoices in email without filing
• Manual data entry errors when transferring PDF totals into accounting tools
• Forgetting to cancel a subscription before auto-renew kicks in

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.