Back to writing

Groot Consulting: an agent that helps a solo consultant produce deliverables

Pierre-Alain Bloch, an occupational psychologist and the only consultant at Groot Consulting, has used his Hermes agent since 9 June 2026. No routine. Documents produced on demand. He is also a professional partner.

Context

Pierre-Alain Bloch runs Groot Consulting, in Saint-Leu. The practice supports organisations in occupational psychology. He is the only consultant.

He is also a professional partner: we both sit for the CPME on the regional cross-industry joint committee of Réunion, and we run projects together. The agent is added to that relationship. A case study that kept this link quiet would look self-serving.

His Hermes instance was opened on 9 June 2026, on an Ergonomia machine. He was the first to accept the plan, on 24 June, and he has been subscribed since 2 July. On 16 July I went and installed the agent on his Mac mini, so that it could reach his folders, his calendar and his mail directly. He uses the agent himself.

What was done

A sole consultant does not work like a firm with daily flows. He produces documents, on demand, for different clients. Automating routines made no sense: none is switched on.

What was tooled is the production of a deliverable from his own materials.

Producing a deliverable

  1. Materials

    scoping note, proposal, meeting recording, spoken exchanges

  2. Agent

    drafts from these materials

  3. Deliverable

    Word document, charts, checklist

  4. His hand

    Pierre-Alain rereads, corrects and sends

Path of the response file for a call for projects, July 2026. Source: fleet journal, July 2026.

Producing a deliverable. Path of the response file for a call for projects, July 2026. Source: fleet journal, July 2026.

The dated productions are these. On 15 June, a requested Word file. On 20 July, satisfaction analyses for a client, delivered in Word with charts, from the agent’s desktop. In July, a response to a call for projects for one of his clients: memo, form texts, checklist, built from his scoping note, his proposal, a meeting recording and spoken exchanges. The client of that file is not named here.

Deliverable
Date
Outcome
Word file
15 June 2026
arrived as HTML, defect fixed
Satisfaction analyses, Word and charts
20 July 2026
delivered
Call-for-projects file
30 July 2026
consolidated by me after the session failed

Fleet journal, 15 June, 20 July and 30 July 2026.

Fleet journal, 15 June, 20 July and 30 July 2026.

On 16 July, the agent created, at his request, a professional profile and a personal profile. The personal profile is used. The professional profile was created, with no use recorded by 13 September. On 24 August, the agent’s desktop was used for the Tiime accounting tool and for DNS settings.

The channels: Telegram mostly until mid-July, then the agent’s desktop, mail, and the phone. On 16 and 17 July, 13 phone sessions, 30 minutes in total. He was the first to call his agent. Phone use after those two days is not verified.

The support comes down to a few acts. Opening the instance on 9 June. Migration onto his Mac mini, on site, on 16 July. In June, a fix for a file-delivery defect, then deployed across the fleet. On 21 July, the first backup, with a restore test: until then, his agent was missing from every backup. On 30 July, recovery of the call-for-projects file after the incident described below.

What changed

Measured, on use, not on effect. The subscription has run since 2 July 2026. On 13 September it was active. From 14 August to 12 September, use covers 18 days out of 30, with no routine. On 28 August, about 2,071 messages were in the Telegram database. Deliverables came out of this work: the satisfaction analyses of 20 July, the call-for-projects file consolidated on 30 July. On that file, the agent’s share and mine have to be separated: the session crashed, and I consolidated the files.

Limits

On 15 June, the requested Word file did not arrive as an attachment: an HTML file was produced, and a server path was shown instead. The defect was fixed on the fleet side.

From 17 to 30 July, a conversation that had grown too long made the session fail in the middle of the file. I secured the files, consolidated a memo at version 0.9, the form texts and a checklist, and placed them on his Mac and his iCloud, with a mail that set out the next steps. Whether the file was submitted before the deadline, and what the organisation did next, is not verified.

After the migration of 16 July, the old machine restarted its service from 18 to 21 July, with a risk of a Telegram conflict. It was erased on 26 July. Since then the agent lives at his place, and I watch it less closely than before.

Sources

  • Instance opened: journal of 9 June 2026. Subscription: since 2 July 2026. Fleet inventory of 13 September 2026: 18 days of use out of 30, 0 routines.
  • Telegram messages in the database: about 2,071 on 28 August 2026.
  • Phone: 13 sessions, 30 minutes, on 16 and 17 July 2026.
  • Dated deliverables: satisfaction analyses on 20 July 2026; call-for-projects file consolidated on 30 July 2026.

Your Hermes agent: €249 a month excl. VAT, 30 minutes of monthly support, 15-day free trial. See the offer