The automation that needs no software

The cheapest automation involves no software. It is writing the thing down once so it does not have to be thought about again, and for a small business it frequently saves more hours than anything you could connect together.

Why it works better than it sounds

Most repeated work is not mechanical, it is decisional: deciding what to say, in what order, and whether anything was forgotten. That decision is the expensive part and it is the part a template removes.

It also survives everything. A template does not expire, does not need an authorisation, costs nothing monthly, and works when the internet does not. Nothing you build will have a better ratio of benefit to maintenance.

What to write down

• The messages you send repeatedly: the enquiry reply, the quote, the chase, the handover, the refusal. Five saved replies covers most correspondence in most small businesses.
• The steps of anything with an order, where missing one costs you: onboarding somebody, closing a job, publishing a thing, dispatching an order.
• The questions you ask every new customer, as a form rather than as a conversation.
• The structure of anything you produce repeatedly: a proposal, an invoice, a report, a listing.
• The things you check before something goes out, as an actual list rather than as a feeling of having checked.

Making templates that get used

1. 01Keep them where the work happens. A saved reply in the mail client gets used; a document in a folder does not.
2. 02Mark the parts that must change, so sending one with the placeholder still in it becomes obvious rather than embarrassing.
3. 03Keep them short enough to read. A twelve-page process document is a document; a nine-line checklist is a tool.
4. 04Fix them in place when they are wrong, at the moment you notice, rather than keeping a list of templates to revise.
5. 05Delete the ones you stop using, so the set stays trustworthy.

The personal-message objection

Worth answering, because it stops people doing this. The fear is that templated replies read as impersonal, and they do when they are sent unchanged.

Used properly a template is a starting structure, not a finished message: the shape and the things that must be covered are fixed, and the first and last lines are yours. That version reads more personal than an improvised reply, because the attention goes into the part that is about them instead of into remembering what to include.

A form instead of a conversation

The highest-value item on the list for most service businesses. The same five questions get asked by email, in a slightly different order, over three exchanges, and the answers arrive incomplete.

A short form collects all of it once, in a consistent shape, and the exchange goes from three days to one message. It also makes the information comparable across customers, which is what eventually lets you see what people actually want. Keep it short enough that nobody abandons it, and accept that one or two will reply in prose anyway.

One document, not a library

Process documentation fails by being too thorough to use. A handbook nobody reads is the normal outcome, and the version that survives is considerably smaller than it feels it should be.

One page per process, nine lines or so, written as actions rather than descriptions, kept where the work happens. If it does not fit on a screen it will not be followed, and the parts that get omitted when you shorten it are usually the parts that were obvious anyway. Thin and used beats complete and ignored, and this is also what makes bringing somebody in possible without a fortnight of explaining.

Checklists for the things that go wrong

The most valuable list in a small business is often the one for the rare event: the site is down, a payment failed, a delivery went missing, somebody is complaining publicly. These happen under pressure, which is exactly when you improvise badly. Five lines written calmly in advance, saying what to check and in what order and who to tell, is worth more than any amount of preparation on the day.