Every automation has two essential parts, and often a third. A trigger is the event that starts it: a form gets submitted, a date arrives, an email lands. An action is the task it performs: send a message, update a spreadsheet, create a record. A filter is an optional condition: only do this if that field is empty, or only if the order is over a certain value.
Read any automation as a sentence: when this trigger happens, if this filter is met, do this action. If you can describe a repetitive task that way, you can probably automate it.
Where to actually look
Most owners default to thinking about admin first, and it's a good place to start, but it's rarely the only place worth looking. Walk through the business function by function and ask the same question of each:
- Customers: enquiry replies, booking confirmations, follow-ups after a purchase
- Admin: invoice chasing, appointment reminders, rota building
- Marketing: scheduling content, adding new subscribers to a sequence
- Operations: moving data between two tools that don't otherwise talk to each other
The tasks worth automating share three traits: they happen often, they follow the same steps every time, and forgetting them costs real time or money. Anything that changes rarely, or genuinely needs a person's judgement every time, isn't a good candidate, no matter how tedious it feels.
Native automation before a connector tool
Before adding a new automation platform, check what the tools you already pay for can do on their own. A CRM can often send follow-ups and move deals automatically. An email marketing tool can run a welcome sequence by itself. A store platform can trigger order confirmations without any extra setup. If the whole job happens inside one tool, use that tool's own automation; reach for a connector tool only when the job spans two or more tools that don't talk to each other. It keeps things simpler and cheaper.
When you do need a connector, the two that dominate the small-business world are both no-code and both have a free tier generous enough to learn on and run a handful of low-volume workflows. Pick one, don't try to learn both at once, and move later only if you outgrow it.
Working out what it's actually costing you
Once you've spotted a candidate, the honest next step is putting a number on it rather than automating by gut feel. A couple of minutes with a slider turns "this feels like it takes ages" into an actual hours-and-pounds figure, which is usually the more convincing case for doing something about it than the frustration alone.