Category: Getting started

If you are nodding at any of these five signs, automation will pay for itself faster than you think.

5 min read · 1 September 2026

Every business has a few processes that quietly eat hours. The problem is that the cost is spread across so many people that nobody sees it. Here are the five clearest signs.

If chasing approvals by email is a weekly ritual, and “it is with the approver” is a standard answer, your approval chain is the bottleneck. Automation routes requests, sends reminders and escalates, so nothing waits on a memory.

You cannot judge whether automation is worth doing without a number for what the process costs today. Here is how to get one honestly.

5 min read · 2 September 2026

Most automation projects start with a problem, which is correct, but they should also start with a number. Not a precise forecast straight away; an honest estimate of what the process costs now. Without that figure there is no way to judge whether the project is worth doing and no way to know later whether it worked. ROI is not the boring last slide of the business case. It is the reason the project exists.

Measuring the current process before building anything gives you three things. You find out whether automation is even worth it, because some processes are not. You get a baseline that proves the project worked once it goes live. And you build the business case from evidence instead of enthusiasm, which makes the approval meeting much shorter. Teams that skip this step can only say we think it saves time. Teams that do it can say what time, whose time, and how much of it, which is a different conversation entirely.

Your first automation project decides the fate of your whole programme. Pick well and it pays for itself. Pick badly and the second project never gets approved.

4 min read · 2 September 2026

The most common reason automation programmes stall is not a lack of ideas. It is the first project. Teams pick a process that is dramatic but rare, or broad but vague, and the project drags, costs more than expected and quietly dies. Then nothing else gets approved for two years. The fix is a deliberate choice, and three criteria scored simply will take you to the right project.

The worst first project touches every department, affects every record and needs six data sources to work. It fails for a simple reason: it cannot be tested step by step, and nobody agrees on what done looks like. The second worst is painful but rare, a process that happens twice a year. It stretches the approval cycle, shows little visible benefit and demoralises everyone. Both feel important, and both teach the organisation that automation does not work, which is the opposite of what a first project should do.