Hermes, a sales-ops agent
Building agent-driven operations for real teams. AI agents · Engineering · Business operations.
Challenge
A growth team's recurring work (BD standups, SEO reporting, creative requests) depended on people remembering to do it, and the deployment started with engineering-only coverage.
My role
Author and operations owner. I wrote the code, wired the environment, and took over the self-hosted deployment of Nous Research's Hermes Agent from engineering, then ran it end to end for six months.
What I built
BD standups run per rep on a schedule, with a team post, an admin digest and CRM access by role. SEO reporting runs Monday, Wednesday and Friday with a Friday recap, reading live analytics and search data. Creative requests are collected and summarized each Friday. One routing layer spans five skills, with a schedule whitelist, channel scoping and a pipeline gate. Nine required environment keys sync on every deploy, which closed off a class of config-drift failures.
Problems I diagnosed
Two independent authorization gates had silently turned away five people for weeks, and I found both in the agent log and wrote a two-sided onboarding checklist. The agent once described a post it never made, so I caught it and hardened the system against a repeat.
Result
Four pull requests authored in my name were merged to production on April 27, 2026. The deployment then ran with four teams.