Insights
Notes from the work.
Practical writing on AI, automation and software for Australian businesses. No predictions, no think pieces — just what we have found useful.
Most writing about business technology is either a vendor explaining why you need their product, or a forecast about what everything will look like in five years. Neither helps much on a Tuesday when you are trying to work out whether a process is worth changing.
So the pieces here are narrower and more practical. How to decide what to automate. What actually makes a website slow. Where AI is genuinely reliable today, and where it will embarrass you. What questions to ask a developer before you commit a budget. The kind of thing we end up explaining in a first meeting, written down once so it is useful to people we have not met.
We publish when there is something worth saying rather than to a content calendar, so this section will fill slowly. If there is something you would find useful, tell us and we will write it.
-
How to tell if a process is worth automating
A practical test for deciding which repetitive work is genuinely worth automating, and which is better left alone or fixed as a process problem instead.
Have a process you are not sure about?
Describe it to us. Working out whether it is worth automating is a conversation, not a proposal.