What the Bot does
- Review approved channels, inbox, calendar, and meeting notes since yesterday.
- Return only items that map to the priorities you name.
- For each: source, why it matters, proposed next step, whether you owe a decision.
What changed. What needs you.
Chief of staff
A source-linked digest of Slack, inbox, calendar, and notes — only the items that map to this week’s priorities. Does not send. Does not move meetings.
The week is scattered across Slack, Gmail, and a calendar. You need a brief, not another inbox.
Never without you
- Send messages
- Change meetings
- Message anyone outside the thread
First message
Talk first. The first message is a real task — not a template to configure.
Chief of Staff
Turn this meeting into a Notion page: decisions, owners, dates. Put it under Ops. Don’t ping anyone.
Notion
create_pageOps / Week of Aug 17
Page is under Ops. Three decisions, owners, dates. I didn’t ping anyone.
Message Chief of Staff
Tools this job uses
Connect them when the Bot hits a wall. Nothing goes live until you say so.
FAQ
Is this an orchestration canvas?
No. It is a person in the sidebar. You hire a Chief of Staff, then specialists — inbox, expenses, recruiting. You message one Bot. It files the week.
Also hire
Other jobs
Hire for the work. Each Bot is a person in the sidebar.
Gmail without the guilt
Inbox triage
Sort the pile. Draft the replies. Never send. The inbox is still yours.
A computer, a ticket, a fixture
Bug reproduction
Reproduce the bug from the report. Write steps, expected vs actual, and a minimal fixture. Do not change production.
GitHub and Linear, in English
Shipping updates
What shipped, what is stuck, what needs you. No merge, no deploy.
A sourcer who does not email anyone
Talent scout
Source candidates from the brief. Never email anyone without approval. End with a shortlist and why.
Hire the first one
Meet your first Bot.
Name, optional job, how it should work. Open the thread. The first message is a real task.
Get started