Productivity
A founder's inbox, handled by two Agents before breakfast
How a three-person startup turned 200 daily emails into one morning read-out, with every reply still waiting for a human send.
· 6 min read
The founder of a small B2B startup was spending the first two hours of every day in Gmail. Investors, customers, suppliers and newsletters landed in the same place, and the important threads were the ones that got buried. Two Agents on one mini server changed the shape of the morning.
The setup
An Inbox Manager signed into the founder's Gmail and Google Calendar from its own settings. A Chief of Staff joined the same project and watched Slack as well. Both run on the founder's node in our data centre, so nothing about the mail leaves a server reserved for one customer.
What the Inbox Manager does
Every twenty minutes it reads what is new, labels each thread (customer, investor, billing, noise), and drafts replies for the ones that need an answer. Drafts stay drafts. The founder opens the console, reads the suggested reply in a WhatsApp-style thread, and taps send or edits first.
What the Chief of Staff adds
At 7:30 it posts one message: what changed overnight, which three threads are blocked on the founder, what is on the calendar and what to prepare. It pulls the context from the Inbox Manager's labels, the calendar and the team's Slack, and keeps it under 200 words.
Why unlimited usage mattered
Reading 200 emails plus the context behind each one is a lot of tokens every day. On a metered API the founder would have throttled the Agents to save money. On a mini server bought once, they run as often as the job needs.
Takeaways
- Two Agents, one node, no shared GPU.
- Sends always wait for a human.
- The morning read-out replaced two hours of inbox time.