Blueprint

Selling Hermes setups to small businesses

A demo-led route from pilot to client-owned accounts, separate environments and a support fee, with the pricing disputes shown rather than settled.

Type
Blueprint
Confidence
Low
Sources
6 sources
First published
Updated

Who this is for

You are a consultant or small IT shop thinking of installing Hermes for other businesses. The evidence is thin. Two posts carry most of it: a Reddit thread on selling Hermes to businesses and a thread by an SME automation consultant running client pilots. Together they draw about ten voices, mostly commenters (unnamed commenter · I made €2,700 last month installing Hermes… ¶ L1). The headline of the first thread says its author made €2,700 in a month installing Hermes for French companies, but the body was removed and no comment confirms it (the original poster · I made €2,700 last month installing Hermes… ¶ L1). Treat everything below as self-reported practice, not market proof.

The route at a glance

  1. Build a working version of the client’s own process.
  2. Demo it live against the real process.
  3. Sell the outcome, not Hermes.
  4. Run each client as its own environment, on the client’s accounts.
  5. Hand over after a short observation period.
  6. Price support, and expect an argument about the number.
  7. Plan for the second phase, and think about productising.

Step 1 — Build the client’s process first

The SME automation consultant builds a working version of a client’s own process before selling anything (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L9) (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L9). In his pilots, prospects from food expos are checked against their websites, validated by a human, enriched and only then pushed into the CRM (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L14). This step rests on one poster, though a second, below, uses a different form of demo.

Step 2 — Demo it live

The same consultant demonstrates the working version against the real process; he says clients easily grasp the value and the response has effectively been “Yes, please”, with no counts given (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L10). A second poster gave a prospect a phone number to call a Hermes agent that knew the proposed statement of work and could answer questions on costs, deliverables and schedule; he says this convinced the client after documents had not (@alexcovo_eth · Hermes + Vapi phone agent lands an AI… ¶ L3). That project is undelivered and no fee is stated (@alexcovo_eth · Hermes + Vapi phone agent lands an AI… ¶ L11). Two posters, two real cases, no conversion data (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L10).

Step 3 — Sell the outcome, not Hermes

A commenter in the installer thread notes that most companies do not know what Hermes Agent or Nous Research is (a Reddit commenter · I made €2,700 last month installing Hermes… ¶ L139). Another says the installer should expect questions on security, GDPR, hosting and who holds API keys, which were the most repeated objections (unnamed commenter · I made €2,700 last month installing Hermes… ¶ L179). A would-be entrant in Germany asked whether GDPR matters before starting; nobody replied (unnamed commenter · I made €2,700 last month installing Hermes… ¶ L406).

Step 4 — Separate environments, client-owned accounts

This is the most developed advice, and it comes from one poster. Treat every client deployment like production, with its own environment, credentials, model account and a documented recovery path, so one changed API key cannot cascade (a Reddit commenter · Anyone else deploying Hermes into SME… ¶ L330) (a Reddit commenter · Anyone else deploying Hermes into SME… ¶ L332). The client owns and pays for the server, model accounts and connected services; the consultant keeps access for implementation, maintenance and support (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L17). Where a client wants more than one agent, run a separate container per agent (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L349).

(a Reddit commenter · Anyone else deploying Hermes into SME… ¶ L330)

Other shapes exist. One installer commenter describes a box on the client’s premises as a hub the installer controls, with client machines as spokes over Tailscale (an installer charging a monthly fee · I made €2,700 last month installing Hermes… ¶ L29). Inside one firm, Michael Versluis serves a team from one gateway, identifying each person and applying a role (Michael Versluis · How do people run Hermes for more than one… ¶ L13), but gives no headcount (witcheer · How do people run Hermes for more than one… ¶ L6); his case answers a different question from client isolation. On privacy, a commenter suggests keeping customer data in a fetched tool call rather than in the agent’s memory (a founder who replaced their helpdesk · We replaced our helpdesk with Hermes… ¶ L21), though the claim is unverified (a founder who replaced their helpdesk · We replaced our helpdesk with Hermes… ¶ L19).

Client-owned keys cut both ways. They keep variable token cost out of your quote (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L388) (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L389), yet a commenter asks how clients who do nothing technical will manage their own keys (a Reddit commenter · I made €2,700 last month installing Hermes… ¶ L502).

Step 5 — Hand over after a short observation period

The installer commenter says they set up the box, then spend about a week observing and tuning before clients carry on by themselves (an installer charging a monthly fee · I made €2,700 last month installing Hermes… ¶ L149) (an installer charging a monthly fee · I made €2,700 last month installing Hermes… ¶ L149). The same commenter expects the model not to last (an installer charging a monthly fee · I made €2,700 last month installing Hermes… ¶ L33). One poster’s account; no outcomes.

Step 6 — Price support, and expect the dispute

Prices on the record are few and self-reported:

  • €200 a month for maintenance, from the installer commenter (an installer charging a monthly fee · I made €2,700 last month installing Hermes… ¶ L30).
  • £25-30 a month for upgrades, backups and uptime, still undecided, from the consultant (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L145).
  • $200-1,000 a month, which one commenter expects others to charge for internal use (a Reddit commenter · Anyone else deploying Hermes into SME… ¶ L51).

Setup-fee and income questions were asked and not answered (unnamed commenter · I made €2,700 last month installing Hermes… ¶ L527).

The sides:

  • Cheap works: routine upkeep such as version updates and patching can be delegated to a coding agent, with workflow changes charged separately (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L146) (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L181).
  • Cheap does not work: support would cost far more than £25-30 a month in work (a Reddit commenter · Anyone else deploying Hermes into SME… ¶ L157); do not price too low, because the work replaces employees (a Reddit commenter · I made €2,700 last month installing Hermes… ¶ L632). One commenter calls €200 a month a crazy price (a Reddit commenter · I made €2,700 last month installing Hermes… ¶ L503).

Step 7 — Plan for phase two, and consider productising

After a first workflow earns trust, one commenter says the question becomes what else to automate, and that this is harder to manage than the pilot (a Reddit commenter · Anyone else deploying Hermes into SME… ¶ L333); the poster says this is an assumption (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L20). Productising evidence is scattered. A hosted one-click service was floated, with a seller noting that MCP and Google sign-in setup is not user friendly (an SME automation consultant · Anyone else deploying Hermes into SME… ¶ L205) (a commenter selling hosted assistants · Anyone else deploying Hermes into SME… ¶ L192). An open-source front end built on Hermes to avoid the command line remains a personal project (SchezHugo · Verso: open-source agent orchestrator for… ¶ L7) (SchezHugo · Verso: open-source agent orchestrator for… ¶ L5).

Where posters disagree

  • Is a low monthly fee viable? See Step 6.
  • Should you install for clients at all? One commenter expects most readers to use Hermes internally and charge a monthly fee instead (a Reddit commenter · Anyone else deploying Hermes into SME… ¶ L51); others say installing is a live business that people run now (an installer charging a monthly fee · I made €2,700 last month installing Hermes… ¶ L29) (an installer charging a monthly fee · I made €2,700 last month installing Hermes… ¶ L30).
  • Is Hermes safe enough for client production? Commenters say security is a sieve (a Reddit commenter · I made €2,700 last month installing Hermes… ¶ L438) (a Reddit commenter · I made €2,700 last month installing Hermes… ¶ L470); the consultant’s answer is isolation (a Reddit commenter · Anyone else deploying Hermes into SME… ¶ L330).

What can go wrong

  • The installer role may disappear (an installer charging a monthly fee · I made €2,700 last month installing Hermes… ¶ L33) (a Reddit commenter · Anyone else deploying Hermes into SME… ¶ L51).
  • The question of who takes responsibility if something goes wrong went unanswered (unnamed commenter · I made €2,700 last month installing Hermes… ¶ L179).
  • Unverified income and demand claims set expectations too high (unnamed commenter · I made €2,700 last month installing Hermes… ¶ L1).

How strong is the evidence

Weak, and narrower than the number of voices suggests.

  • Steps 1, 2 and 4 rest on one consultant (with a second poster on the phone demo).
  • Step 5 rests on one installer commenter.
  • Step 6 has three price points from three posters, each self-reported and disputed by commenters.
  • Step 3 is commenter observation.
  • Nothing is delivered, measured or independently confirmed; no conversion, churn or income numbers exist.

Go deeper

Selling Hermes installs to companies · Selling Hermes installs to companies · Selling with a working demo · Selling Hermes installs to companies · One agent, several people · Data privacy and client data · Demo-led client onboarding · Hub-and-spoke client setup · How do you charge clients for a Hermes setup? · Your first Hermes setup for a small business

Sources

  1. (01)

    Anyone else deploying Hermes into SME businesses?

    Post

  2. (02)

    Hermes + Vapi phone agent lands an AI consulting assignment

    Post

  3. (03)

    Verso: open-source agent orchestrator for knowledge work, built on Hermes

    Post

  4. (04)

    I made €2,700 last month installing Hermes Agent for French companies (post removed; comments remain)

    Post

  5. (05)

    We replaced our helpdesk with Hermes (comment on 'Salesforce to acquire Fin')

    Post

  6. (06)

    How do people run Hermes for more than one person? (incl. Versluis RBAC reply)

    Post

(By email)

Compounding Insights