A service, and the system behind it
| Role | Founder and operator. I run the service and built the agent system that runs its operations. |
|---|---|
| Context | ERGO BOX, a CrossFit equipment maintenance service in Málaga. I started the service itself, then built the system that runs it. |
| What it is | A harness of AI agents on Hermes that connects scheduled outreach, inbox monitoring, follow-ups and dashboards into one operational setup. |
| Status | Operating privately. No public dashboard or case-page screenshots. |
The service came first
ERGO BOX maintains CrossFit equipment in Málaga. The service itself is straightforward. What interested me was that running a small business is mostly repeatable work: outreach, follow-ups, monitoring. I built a system to run that work, so the business and the machine behind it were designed together.
The system is built on Hermes, the agent framework I use daily. The agents do not replace the service; they run the operations around it.
What the harness does
The harness connects the repeatable parts of running the business into one setup.
- Scheduled outreach on a cadence, executed by an agent.
- Inbox monitoring with service-level expectations on follow-up time.
- Follow-ups and tracking of hot leads.
- Dashboards that keep an eye on the operation.
What it does not claim
The system is private and operational, not a public product. It runs real business workflows, but I do not claim full autonomy, measured efficiency gains, or guaranteed outcomes. What it demonstrates is systems thinking: starting a service and building the machine that operates it.
Methodology grounding: Service design; agent harness design and build on Hermes; operational automation.