Answers
How can I automate admin in my business?
Short answer
Start by listing every task done on a repeating schedule that follows a written-down rule, and cost each one at hours per year rather than how annoying it feels. The top two or three by cost are almost always recurring invoicing, chasing payment and re-typing data between systems. Automate those first, with a workflow tool if the logic is simple and purpose-built code once it isn't.
Step one: the two-week list
For a fortnight, have everyone note every task they do more than once. Not a formal time study — a running list. You are looking for repetition, not effort.
Then mark each one repetitive or judgement-based. Anything where a person applies a rule they could write down is a candidate. Anything requiring judgement stays with a person, and trying to automate it anyway is how automation projects get abandoned.
Step two: cost it per year
Multiply minutes by frequency by 52 and cost it at what the person actually costs. Ten minutes daily is roughly 43 hours a year. A painful half-day each quarter is 16. Owners consistently want to automate the second one, because it hurts more — but the first one is nearly three times the money.
Step three: the usual winners
- Recurring invoicing. Same customers, same amounts, same day. Almost always top of the list for a service business.
- Payment chasing. A reminder at seven days, a firmer one at fourteen, a human at thirty — steady, unemotional, and better for cash flow than anybody's good intentions.
- Re-keying between systems. The same customer typed into the website enquiry, the job sheet and the accounts package.
- Reminders. Appointment and job reminders reduce no-shows and cost nothing once they run themselves.
- The weekly report. Assembled on a schedule instead of rebuilt each time.
Step four: choose the right tool
For a simple link between two apps at low volume, a workflow tool like Zapier or Make is the right answer and you should use it. They stop being the right answer once there's real conditional logic, real volume, or a step that has to be correct every single time — at that point they get expensive and fragile, and a small piece of purpose-built code is cheaper and steadier.
The other case for code is when the automation belongs inside a system you already have, rather than bolted between two systems that shouldn't both exist.
What not to do
Don't automate a broken process — you'll get the wrong outcome faster and more consistently. Fix the process on paper first. And don't automate without a way of noticing when it fails: silent failure is worse than manual work, because nobody finds out until a customer does.
Related questions
What should I automate first?
Whichever repetitive, rule-based task costs the most hours per year. For most service businesses that's invoicing and payment chasing, not the task that feels most irritating.
Is Zapier enough, or do I need custom development?
Zapier is genuinely fine for simple, low-volume connections. Custom becomes cheaper once there's branching logic, real volume, or a step that can't be allowed to fail quietly.
Will automation mean laying people off?
In small businesses it almost never does. It usually means the person who spent Friday afternoon on invoices spends it on customers instead — which is normally why the owner wanted it.
Still not sure what you actually need?
Tell us how your business runs and we'll tell you straight — including when off-the-shelf software would serve you better than anything we'd build.