Who this is for: Founders and solo operators.

The Bot team

One Bot per theme, not per task. Each has its own accounts (see own accounts).

Chief of Staff Bot — The only Bot you talk to daily. Delegates to specialists, collects approvals and outputs into one morning message, keeps the shared knowledge file current.

Inbox Bot — Owns triage on shared inboxes; drafts; 'waiting on' tracking.

Calendar Bot — Owns prep: one-page briefs before meetings from Drive, CRM and email.

Ops Bot — Owns the boring: spend watcher, heartbeat log, monthly cleanup of the shared computer, paging us.

Routines

08:00 daily — the morning message: approvals, outputs, routine health, spend
Before each meeting — brief
Daily — inbox pass and drafts
Daily — spend and heartbeat checks

What's behind approval

Anything outbound. The chief of staff batches approvals; it never approves on your behalf.

What the win looks like

You talk to one Bot. It runs the others. You approve in one place, once a day.

What we won't build here

Giving the chief of staff your personal accounts 'so it can do everything'. It gets a Bot identity like the rest.

Setup and cost

This playbook fits our Setup package at the 3-Bot tier, one week, fixed price. Plan cost is separate: see which plan you need. Every routine ships with a heartbeat line and the spend watcher.