Hermes runs film-office tasks with document approvals

The owner of Aumen Film Co uses Hermes for the office work around commercial film production, while people still make the films on set. Separate profiles handle intake, production administration, sales, content and research. They share an Obsidian vault containing company processes, equipment, rates and operating rules.

The production profile prepares budgets and crew lists, converts photographed schedule markups into digital documents, tracks invoices and runs finished files through QA. A sales profile checks proposal status each business morning and drafts follow-ups. A content profile draws ideas from call transcripts and time logs into a review queue. These are specialised jobs with separate instructions and permissions, rather than a single unrestricted assistant.

The owner starts profiles read-only and can graduate them to drafting. E-signature sending requires an approval code tied to the reviewed document; changing the document invalidates the code. The account also reports nine scheduled runs failing on one login problem, plus an incorrect claim about a service’s free-document limit. The owner now requires workflows to report when they stop and verifies changing prices against current sources. The reusable lesson is to bind approval to the exact artifact and monitor scheduled failures, not merely successful outputs.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Reddit · u/chrisaumen on Reddit