Automating without regret: six questions every SME manager should ask

Most automation projects don't fail on the technology. They fail because the wrong question got asked at the start. We've watched it happen at dozens of small and mid-sized businesses over the past few years. Someone buys a slick tool, an enthusiastic colleague builds something over the weekend, an agency delivers a shiny report. Six months later: silence. Nobody's using it.

Before you call the next builder or sign a licence, walk through these six questions first.

1. Does this process run often enough?

Automating always costs something. Build time, money, and the mental weight of getting something new to work. If a process comes round twice a month, that investment is almost never worth it. It only really pays off at daily or weekly frequency.

A good rule of thumb: if you can express the time saved over a year in working weeks, there's a serious business case.

2. Is the process already any good?

Never automate something that's a mess underneath. Fix the process first, then automate it. Otherwise you're building a faster route to the wrong destination, and that's much harder to unpick afterwards.

Sounds obvious. But we see it happen every month. A team with a rickety quoting flow thinks: if we throw AI at it, it'll be faster. No. It'll just be rickety at volume.

3. Who owns it when it goes wrong?

An automated process with no owner becomes a mystery within six months. Someone has to carry the responsibility: this flow is mine, I make sure it keeps running, I'm the point of contact when something odd happens.

Name a person. Not a "team". The moment you say "team", nobody owns it.

4. What do you do with the time you free up?

This is the question that gets skipped most often, and the most painful one. If nobody decides up front where the freed-up hours go, they dissolve into extra meetings, longer coffee breaks, or work that slows down even further because there's room for it. The gain just evaporates.

Decide before you start: what are these people actually going to do with those five hours a week? Sales work? Customer conversations? Improving quality? If you don't have an answer to that, this project isn't really ready yet.

5. Does the process survive the supplier leaving?

Build on open standards. Document where the data lives. Make sure you're not locked into one person or one tool. If we get hit by a bus tomorrow, your team should be able to take it over, or bring in another party to keep building.

This isn't a theoretical risk. We regularly get calls from companies whose previous partner vanished somewhere, and who are now stuck with a black box.

6. What's the most annoying step?

That's where your biggest gain is. Not the step you understand least, but the step your team hates most. That's the step where people leave things half-finished, quietly skip ahead, or build a manual "little workaround" that nobody documents.

Ask in a team meeting: which part of your work would you happily throw away tomorrow? That list is worth its weight in gold.

---

Can't quite figure it out on your own? We help small and mid-sized businesses through exactly these six questions every week. No sales pitch, just an honest look. Book a conversation.