What to Automate First: How to Decide with Data, Not Hype
Key takeaways
- Good automation is a prioritization decision, not a technology decision.
- Every task needs three numbers: annual hours, automatable percentage, and associated cost.
- Automating to free people for higher-value work — not to cut headcount — is the version people actually adopt.
- Real value appears when the diagnostic ends in a working bot, not a slide deck.
57% of working hours are automatable with technology that already exists, according to McKinsey. It's a statistic that comes up in every conversation about AI. What almost no one answers is the question that actually matters for your organization: which hours are those, in which roles, and where should you start?
The mistake of automating out of enthusiasm
Most automation projects start backwards. Someone sees a promising tool, buys it, then looks for somewhere to apply it. The result is usually a pilot that impresses in the demo and dies three months later — because it automated a task that wasn't significant enough, or that the team wasn't ready to let go of.
Automating well is a prioritization decision, not a technology decision. And prioritizing requires data: which tasks are repetitive and predictable, how many hours they consume per year, what they cost, and how straightforward they are to automate. Without that map, you automate by intuition — exactly the problem automation was supposed to solve.
The three numbers you need per task
Before automating anything, an informed decision requires three concrete figures:
- 1
Annual hours
A repetitive task consuming 300 hours per year is an opportunity; one consuming 10 doesn't justify the effort.
- 2
Automatable percentage
Not everything can be automated 100%. Knowing whether a task is 85% or 30% automatable completely changes the calculation.
- 3
Associated cost
Hours have a price. Manually generating financial reports that takes a senior analyst 312 hours per year has a cost you can name: approximately USD 14,500 annually.
With those three numbers, the question 'what do we automate first?' stops being a matter of opinion and starts sorting itself — by impact and by ease of implementation.
Automate to augment, not to cut
There is a distinction that determines the outcome: automating to cut headcount, or automating to free people for higher-value work. The analyst who stopped spending 40 hours a week copying data into reports didn't disappear. They moved on to analyzing that data — which is what they were hired for. That's the version of automation people adopt instead of resist.
That's why the decision of what to automate can't be made in isolation. It must be crossed with the team's real workload — what capacity you're freeing up — with available skills — what higher-value work the person can move to — and with digital fluency — whether the team is ready to operate alongside an automated process. Automating with that complete picture is the difference between a pilot that dies and a change that sticks.
From diagnosis to a working bot
Most automation diagnostics end in a presentation. Real value appears when they end in recovered hours. Escal8 detects opportunities with Kova, calculates the exact savings in hours and money, and builds the automation turnkey — integrated with what you already use. From finding to implementing, all in one place.
Find out what to automate first.
In 30 minutes we show you where your biggest talent opportunity lies.
Book a demo
