Monday morning. The prospect who asked for a proposal on Thursday hasn't heard back. The client expecting a weekly update hasn't received one. The competitive research for a new pitch is still a tab of browser bookmarks. None of these tasks require the founder's judgment. All of them require the founder's time. Without support staff, there's no one else. Hermes handles the communication and research layer — drafting follow-ups, assembling updates, structuring research — across Slack and Gmail from a single deployment. The founder reviews and approves. Nothing sends without sign-off.
What fills a solo founder's week that shouldn't need them
McKinsey Global Institute found knowledge workers spend 28% of their week managing email and 19% gathering information — together nearly half the workweek.[¹] For a solo founder with no support staff, both categories fall entirely on them. There's no assistant to triage the inbox. No coordinator to chase outstanding deliverables. No ops person to compile the weekly report.
The tasks consuming founder time aren't the decisions that require their judgment. They're the communication and admin work wrapped around those decisions. Following up on a proposal that went quiet. Drafting a client status update. Pulling together a competitive summary for a new pitch. Each takes 20–40 minutes. None of them require the founder. Hermes handles them.
How Hermes handles the founder's communication layer
Hermes watches the connected channels — Slack, Gmail, or both — and handles the communication work that currently consumes the founder's attention.
For an unanswered prospect email sitting past 48 hours, Hermes drafts the follow-up and queues it for approval. For a client expecting a weekly update, Hermes pulls the week's activity from the connected project tool, drafts the update, and surfaces it for a 90-second review. For an incoming question Hermes can answer from context, Hermes drafts the reply and routes it for approval before sending.
Hermes runs a single instance across Slack, Gmail, and any other connected platform simultaneously. A client message in Slack, a prospect email in Gmail, an internal note in Telegram — Hermes handles all three from one deployment. Skills built on one channel carry to the others.
The founder reviews and approves. Nothing sends without sign-off.
How Hermes handles research and prep work
Research is a different category of task. Competitive research for a new pitch. Background on a prospect before a first call. A market summary for a proposal. Each takes 60–90 minutes of reading, tab-switching, and note-taking.
Hermes searches, reads, and structures findings into a draft document ready for the founder to edit. For meeting prep, Hermes pulls recent communications with the contact, summarises the context, and produces a brief. For a proposal section, Hermes pulls relevant data, structures the findings, and drafts the content.
Every assistant needs managing. Hermes handles the admin that doesn't.
The output is a starting point, not a finished product. The founder edits and approves. Hermes handles the assembly.
How Hermes improves on a founder's specific patterns over time
Hermes creates a Skill object from each completed task — encoding the task category, the approach used, and examples from the actual work. Skills accumulate from real tasks completed on the founder's specific workflows, clients, and communication patterns.
For a solo founder, Hermes in month three produces draft follow-ups that read closer to the founder's voice than the drafts in week one. Research summaries in month three match the structure and depth the founder expects without prompting. A Skill built from 15 prospect follow-ups for a specific client type understands the founder's tone, context, and preferred call to action in a way a freshly deployed Hermes does not.
The time the founder spends editing each draft decreases as Skills accumulate. The goal isn't autonomous operation — it's the review taking 90 seconds instead of the task taking 30 minutes.
What a founder Hermes deployment looks like
A solo founder Hermes deployment starts with three connections: the inbox (Gmail), the communication tool (Slack), and the project or knowledge tool (Notion or equivalent). Context definition — telling Hermes what the founder's clients look like, what the output formats are, and what the escalation patterns are — determines Skill quality from the first week.
On day one, Hermes handles configured workflows at a baseline level. A draft follow-up is structurally correct but needs tone editing. A research summary is well-organised but needs depth added. The output saves time from day one. It does not replace the founder's review.
By month three, Skills built from completed tasks have encoded the founder's specific patterns. The same follow-up that took 25 minutes to write in week one takes 2 minutes to review in month three. Hermes does not replace the founder's judgment on strategy, priorities, or relationships. Hermes handles the communication and research layer that consumes the time those judgments should be made in.
For a full overview of what Hermes is and how it works, see what is Hermes. For how the Skill-building mechanism works, see how Hermes learns. For how AI agents compare to the tools founders already use, see AI agent vs. automation.
Frequently asked questions
What types of tasks can Hermes handle for a solo founder? Hermes handles the repeatable communication and research layer of a founder's week — inbox triage, prospect and client follow-ups, status updates, research summaries, and meeting prep. Each output is surfaced for the founder's approval before anything sends.
Does Hermes work across multiple platforms for a single founder? Yes. Hermes runs a single instance across all connected platforms — Slack, Gmail, Telegram, and others — simultaneously. Skills built from a task on one channel carry to the others. There's no separate setup per platform.
How much editing does Hermes's output need? In the first two to four weeks, drafts typically need moderate editing — structure is correct but tone and client-specific detail need adjusting. By month three, Skills built from completed tasks produce output that requires less editing. The rate of improvement depends on task volume and how accurately context was defined at setup.
What's the difference between Hermes and a virtual assistant? A virtual assistant requires onboarding, management, and ongoing communication overhead. Hermes starts from context definition and produces drafts for approval — no management overhead, no onboarding period beyond context setup. Hermes also improves over time: a VA learns preferences through conversation; Hermes encodes them into Skills from every task it completes.
Notes
- McKinsey Global Institute, The social economy: Unlocking value and productivity through social technologies, 2012. https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy