Nobody schedules a meeting to announce that a task is wasting hours every week. It just becomes part of how things are done, described as normal rather than noticed as a problem, until someone finally adds it up. The patterns below are some of the more reliable signals that a process is quietly costing more than it should.
The same copy-paste happens across multiple tools, repeatedly
Someone manually moving a new lead's details from a form into a spreadsheet, then into a CRM, then into an email tool, is a strong signal on its own. If it happens dozens of times a week, the time cost is substantial even though each individual instance feels too small to bother automating, which is exactly why it survives unnoticed for so long.
A recurring report takes a real chunk of someone's day
Weekly or monthly reports that pull from the same sources, in the same format, every single time, are close to the textbook definition of a good automation candidate. If someone dedicates a meaningful part of a Monday to compiling the same numbers into the same template they compiled last Monday, that's hours reclaimable with a reasonably straightforward workflow, and it's usually one of the easiest wins to point to when building the case for automating further.
"I'll just check that manually to be safe" comes up often
This phrase usually signals a process that was automated poorly, or not automated at all, and has lost enough trust that someone feels they need to double-check it by hand regularly. The fix isn't necessarily removing the manual check entirely, sometimes a human checkpoint is genuinely the right call, but it's worth distinguishing a deliberate safety check from a habit born of not trusting a broken system.
Onboarding a new tool or process takes an unusually long time to explain
If training someone new on a task takes an hour of walking through manual steps, that's often a sign the task itself has more repetitive structure than complexity, which usually makes it a better automation candidate than a genuinely judgement-heavy task would be. Judgement-heavy work tends to resist a quick explanation regardless of how it's documented, while repetitive work explains itself easily precisely because it follows the same steps every time.
What to do once a pattern is spotted
Write down roughly how many times a week the task happens and how long each instance takes. Multiply it out over a month. That number, once actually written down rather than estimated in passing, is usually what makes the case for automating obvious, and it's the starting point for deciding which processes are actually worth automating first, rather than automating whatever happens to be top of mind that week.
The trap of getting used to inefficiency
The longer a manual process has existed, the more invisible it tends to become, since it stops feeling like a problem and starts feeling like just how things are done here. Revisiting workflows that have been unchanged for a year or more, specifically asking whether they'd still be built the same way if starting fresh today, tends to surface opportunities that a team stopped noticing simply because they'd gotten used to them.