What actually gives a small team its Friday back
Most automation advice starts with the wrong question. It asks what could we automate? — and the answer is always “almost everything,” which is how teams end up with forty brittle Zaps nobody trusts.
We start somewhere duller: what do you do every single week, the same way, that you resent doing? That question filters out 90% of the noise before we write a line of anything.
The test we run before building
Before we automate a task, it has to clear three bars:
- It repeats. Daily, weekly, per-order — some predictable cadence. One-off work is not worth a system.
- It has rules. Not necessarily simple ones, but rules a human could write down. “If the invoice is 14 days late, send this.”
- It is boring. The best automation targets are the tasks where judgment adds nothing. Copy-paste. Reformatting. Chasing.
If a task fails any of these, we leave it alone. Automating judgment-heavy work is how you get systems that quietly make bad decisions at scale.
The boring 80% beats the clever 20%
There is always a tempting edge case — the weird client, the one order type that breaks every rule. Teams spend most of their automation budget trying to handle it.
Don’t. Automate the consistent 80% completely, and route the weird 20% to a human with a clear flag. You get most of the time back, and you keep a person in the loop exactly where judgment matters.
The goal isn’t a system that never needs a human. It’s a system that only needs a human when it should.
What “getting your Friday back” actually looks like
- Invoices that draft and send themselves from the job record
- Late payers nudged politely, on schedule, without you remembering
- A Friday report that lands in your inbox already written
None of it is clever. All of it is reliable. That’s the trade we make on purpose.
If your Friday afternoons have a shape — the same three tasks, every week — tell us what they are. That’s usually where we start.