Home/Guides/First steps

What should a small business not automate?

The short answer

Two things: Don't automate your special sauce: the judgment calls, the relationships, the moments where a person is the reason they chose you. And don't automate a bad process, because you'll get the same mess faster. Everything around those two, the data entry, the follow-ups, the reports, the scheduling, etc... can and usually should run on its own.

/ 01The Long Answer

The part your customers are paying for

Every business has a piece that can't be automated, because it's the reason customers pick you over the next option. For an advisor it's the relationships. For a contractor it's the instinct of where each nail goes. For an accountant it's the judgment call in March. The CEO of a 20-person design firm told me he wasn't going to take design away from his designers, because that's what they love to do, and he's right. He automated the takeoffs and the reporting around the design work and left the design alone.

Our rule on every build, in plain words: we don't automate human judgment, relationships, or the service that sets you apart. Almost everything else can be.

The process that shouldn't exist yet

Automating a bad process just gives you a faster bad process. A decade ago I built a project-management checklist for a team I ran. The first version failed, and it took me a while to see why: I'd written it as a report for myself, with the information I wanted to see, but the project managers doing the work needed a tool that fit how they actually worked. The second version did that and it stuck. It had nothing to do with the software. The lesson carries straight into automation: if the steps aren't right for the people doing them, a machine doing the same steps faster helps nobody.

That's why we walk through your workflows before we build anything. Challenge whether the task is really required, remove the steps you can, improve what's left, speed it up, and program it last. On some first calls the whole result is "delete that step," and the owner leaves with a more streamlined business and no invoice.

The step you keep manual on purpose

Some steps stay with a person because a person wants them. At the building-materials company I co-founded, we automated quoting from the deal record through to the signed document, and it stopped there. We decided that no proposals or invoices would go out without human review, and that made sense where a mistake in a large project proposal could cost tens of thousands. A good automation doesn't have to remove every human touch, and a deliberate manual step is a feature, not a bug.

A four-question test for any task

Before automating a task, ask: does it happen the same way every week, could you write the steps down for a new hire, is the information held in some software already, and would a customer notice if a machine did it? Yes to the first three and no to the fourth means automate it. A no on any of the first three means fix the process first. A yes on the fourth means leave it with a person and use AI automation to support them.

What we'd do about it

We tell owners when a step or process should be cut, and sometimes that's the whole deliverable. The free consultation produces a prioritized list of what to automate, what to fix first, and what to leave alone, and the list is yours whether you hire us or not. Where you want a human approval step, we build one in, and you can turn it off later if you want.

/ 02Questions That Usually Follow

My team is worried about being replaced. Should they be?

Automation takes the work good people hate, the re-typing and the copy-pasting, and gives them back the part they were hired for. The owners we work with want to stop hiring for admin, and they want to keep the people they have.

Can I approve things before they send?

Yes, and for anything that goes to a customer we'd suggest it, at least at first. You review the draft, send it or change it, and the system learns from your edits.

What about AI making mistakes?

It will, sometimes. The build has to catch its own exceptions and hand them to a person. A build that handles 90% on its own and flags the rest is worth having, and one that claims 100% will fail quietly at some point, usually in front of a customer.

Should I automate replies to customers?

Drafting them, yes. Sending them without anyone looking, only for the routine ones, like confirmations and reminders. Anything complex and mission-critical still needs human approval.

/ 04Start Here

Ask us about your own business.

What questions do you have about AI that you are too afraid to ask? We'll give an impartial look into what's possible with automating your business, pointing out the pitfalls, and why you haven't been able to get the results from AI that you want yet.

joe@arowise.com