
Every business I walk into thinks it's unusual.
It isn't.
The industry changes. The software changes. The same five manual jobs turn up almost every time, quietly eating hours nobody has ever added up.
Here they are, and the cheapest way to stop each one.
1. Typing the same thing in twice
An order comes in by email. Someone types it into the system. Then into a spreadsheet. Then into the invoice.
Three places. Three chances to get it wrong.
The fix: decide where that information lives, once. Then connect everything else to it. Most of the time the systems you already pay for can talk to each other. Nobody has switched it on.
2. Chasing
Chasing invoices. Chasing timesheets. Chasing approvals. Chasing the person who was meant to chase.
Chasing feels like work. It isn't. It's a reminder a computer could send.
The fix: automatic reminders, with a named person who only steps in when the reminder doesn't work.
3. The report that takes a morning
Every Monday someone pulls numbers from four places, pastes them into a spreadsheet, tidies the formatting and emails it round.
Ask who reads it. Really reads it.
In one business I worked in, half the "urgent" reports hadn't been opened in six months.
The fix: retire anything nobody reads. Automate what's left, straight from the source.
4. Quotes written in the evening
The owner visits the job, then goes home and writes the quote at the kitchen table.
Meanwhile the customer is getting prices from two competitors.
The fix: a standard pricing template, and capturing the details while you're still on site. For one trade business we built a phone app where the surveyor says the job out loud and gets a priced quote in seconds.
5. "Where's the latest version?"
Five copies of the same spreadsheet. Names like FINAL_v3_USE_THIS_ONE.
Nobody trusts the numbers, so everybody keeps their own.
The fix: one shared file or system, one owner, and switch the old copies off on day one. Not day thirty.
What these five have in common
None of them needs a big transformation programme. Most don't need new software.
They need someone to notice, put a number on the cost, and fix the process before automating it.
Because automating a bad process just makes the mistakes happen faster.
Start by counting. Ask each team: what do you do every week that a computer, or a better process, should be doing? Then multiply the hours by what those people cost.
The number is usually bigger than anyone expected.


