Automation gets talked about as a growth strategy, which puts most small businesses off it. The useful version is smaller and much duller: over a month you perform a set of actions that follow a rule you could write down. Those are the candidates. Everything else is a decision, and decisions are not what you are trying to remove.
The test for whether something should be automated
Four conditions. A task needs all four, and the fourth is the one people skip.
- It repeats on a schedule or on a clear trigger. Not "often" — a date, or an event like an invoice becoming overdue.
- The rule can be written in one sentence. If describing it takes a paragraph with an exception in it, it is a decision wearing a costume.
- Doing it wrong is cheap. A duplicate reminder is embarrassing; a duplicate invoice sent to a client's finance team is a phone call.
- You do it identically every time. If you actually adjust it per client, automating it means sending everyone the version you adjusted for nobody.
The five worth doing first
1. Retainer and subscription invoices
Same client, same amount, same day every month. This is the purest case there is: a monthly schedule, an unambiguous rule, and a task that is pure transcription. It is also the one with the largest cash-flow effect, because a retainer invoice raised on the 3rd instead of the 1st loses two days of payment terms every single month.
One caution: have it generate the invoice rather than send it blind, unless the amount genuinely never varies. A recurring invoice that quietly bills a client who paused last week is worse than a late one.
2. Payment reminders before and after the due date
A note three days before it falls due, a neutral notice the day after, a follow-up at seven days. All three are informational, they are identical every time, and sending them by hand means deciding — while wondering whether the client will be annoyed — over and over.
The hard requirement is that the reminders stop the moment the invoice is marked paid. If your reminders live in a calendar and your payments live in a bank tab, that condition cannot be checked, and you will eventually chase somebody who paid last week.
3. The checklist that starts every project
Every new client involves the same eight steps: create the project, send the welcome email, request the access you need, book the kickoff, set up the folder, add the recurring invoice. You already know all of them, which is exactly why they get done in a slightly different order with something missing.
This is not scheduled automation but templated automation: one action creates eight tasks with the right owners and offsets. Same for the monthly close, and for whatever your equivalent of a handover is. It is the cheapest automation on this list because it needs no rules, only a template.
4. Acknowledging an incoming request
A client emails a problem. Nothing happens for four hours because you are in the middle of something, and in those four hours they do not know whether the message arrived. That uncertainty is what generates the follow-up email, which is a second interruption caused by the first one being invisible.
An automatic acknowledgement with a ticket reference and a realistic response window fixes it. Do not make it apologise or promise a time you cannot hold — "received, we will come back to you within one working day" is enough, and it must be true.
5. The recurring internal task nobody owns
Backups checked, hosting renewals, the quarterly tax deadline, the annual price review, chasing the accountant. These are not client work, so they have no natural trigger and they live in your head until one of them fails visibly.
Automating these is unglamorous and has the best ratio of effort to relief on the list, because what you are automating is the remembering.
| Task | Trigger | Action |
|---|---|---|
| Retainer invoice | Day of the month | Generate invoice from template, ready to review |
| Payment reminders | Due date minus 3, plus 1, plus 7 | Send reminder; stop when marked paid |
| Project kickoff | New project created | Create the standard task set with owners and dates |
| Request acknowledgement | Email arrives | Reply with reference and response window |
| Internal recurring work | Schedule | Create the task assigned to a person, not to nobody |
What to leave manual on purpose
Three categories, and the third is the one that causes damage.
- Anything that names a consequence. A formal demand threatening escalation should be sent by a person who intends to escalate.
- Anything a client will read as personal. An automated "just checking in, how are things?" is worse than silence, because it is legible as a template.
- Anything where the rule has exceptions you handle by feel. Automating it does not remove the judgement, it just applies last month's judgement to this month's situation without telling you.
How to keep an automation from misfiring
Every automation eventually does something you did not want, and the difference between a nuisance and an incident is whether you built the off-switch first.
- Write the stop condition before the start condition. "Send until paid" is a rule; "send on day 7" is half a rule.
- Turn on one at a time and watch it for a cycle. Three new automations in one week means you will not know which one sent the odd email.
- Make sure you can see what it did. An automation with no visible log is a process nobody can debug, including you.
- Review the list twice a year. Automations outlive the situations that justified them, and the reminder emailing a client who left in March is a real thing that happens.
Automations that can see the rest of the system
Every example above depends on the automation knowing something else: that the invoice was paid, that the project is new, that the ticket is still open. That is why they work when they live alongside the invoicing and the tasks rather than in a separate tool.