fullauto.online

Harnesses

What to automate first with Hermes

Five jobs a small business can hand to an agent this month, ordered by how little damage they do when the agent gets it wrong.

Published
6 Aug 2026
Reading
9 min
Class
harnesses

half-life 90dfrom 6 Aug 2026

The usual failure when a small business adopts an agent is starting with the most valuable task instead of the safest one. The most valuable task is usually the one with customers and money attached, which is exactly where an unproven system should not begin.

What follows is five jobs ordered by blast radius — how much damage is done when the agent gets it wrong, because it will. Work down the list. Do not skip ahead because something further down looks more useful; it is further down for a reason.

1. The Monday morning summary

Blast radius: none. Nobody outside the business sees it.

Every Monday, Hermes reads what happened last week — inbox, calendar, whatever project tool you use — and posts a summary to your team channel. What came in, what is outstanding, what is due this week, what went quiet.

This is the right first task because the failure mode is "the summary is a bit rubbish". You will spend two weeks correcting what it emphasises, and those corrections teach you how the thing responds to direction — on a task where being wrong costs nothing. Use Hermes's built-in cron for the schedule.

2. Drafts that a human sends

Blast radius: none, provided you hold the line on sending.

The agent reads incoming enquiries and prepares a draft reply. It does not send. A person reads it, edits it, sends it.

This is where most of the actual time saving in a small business lives, and it is available at almost no risk. Answering a routine enquiry takes eight minutes; approving a good draft takes ninety seconds. Ten enquiries a day is an hour back.

The discipline is absolute: the agent does not get send access, not even once it has been reliable for a month. The moment it can send, an inbound email containing instructions becomes a way for a stranger to make your business say something.

Load-bearing

Draft-not-send is the highest-value, lowest-risk pattern available to a small business, and it stays that way permanently. Reliability is not a reason to remove the human — the human is what makes an inbox-reading agent safe at all.

3. Chasing your own paperwork

Blast radius: small and internal.

Which invoices are unpaid and how overdue. Which quotes have had no reply in ten days. Which certifications expire next quarter. Which jobs have no follow-up booked.

The agent watches and tells you. It does not contact the customer. The worst case is being nagged about an invoice that was actually paid, which costs you thirty seconds and a correction.

This is often where a small business finds the money — not in saved hours, but in the two overdue invoices nobody was tracking.

4. Keeping a record straight

Blast radius: moderate. It writes.

Taking information that arrives as messy text — emails, messages, notes from a job — and putting it into a structured place. Updating a spreadsheet, filing a document, logging a job against a customer.

This is the first task where the agent modifies something you rely on, so it needs two conditions before you allow it: the target must be versioned or backed up, and the agent must write to its own column, sheet, or folder rather than editing rows a human owns. Segregating what it touches means a bad week is recoverable by deleting its work, not by reconstructing yours.

5. Watching something and acting on it

Blast radius: real. Only once the first four are boring.

Monitoring a supplier's stock, a competitor's pricing, a tender portal, a form — and taking a small defined action when a specific condition is met. Booking a slot, submitting a routine form, reordering a consumable under a fixed value.

This is genuine autonomy and it belongs last. Bound it hard: a written list of permitted actions, a value ceiling, and a notification on every single action taken. If you cannot write the permitted actions down in one sentence, it is not ready to be automated.

What to keep well away from it

  • Anything that moves money outbound. Payments, transfers, refunds. No exceptions, no matter how reliable it has been.
  • Anything legally binding. Contracts, formal quotes, regulatory submissions.
  • Anything involving a person's employment or a dispute.
  • Anything you could not explain to the affected customer afterwards. If "an AI did it" is not an acceptable answer, do not let the AI do it.

The rhythm

One task at a time. Two weeks each. If a task is still producing surprises at the end of a fortnight, it stays under supervision instead of graduating, and you do not start the next one.

That is slower than the marketing suggests and much faster than adopting five things at once, watching them all misbehave, and concluding the technology does not work.

Background on why the platform suits this shape of work is in Hermes Agent for small businesses; the mechanics are in the setup guide.