What is business process automation?

The work that disappears is rarely in anyone's job description. It is copying a name out of an email into a spreadsheet and then into the invoicing system. It is the person who remembers that the second follow-up goes out on day four. It is the Monday report someone rebuilds by hand from three exports.

Those steps are cheap one at a time and expensive in aggregate. They also fail quietly. Nobody notices the follow-up that never went out, because there is no record of the thing that did not happen.

Automation is for rule-shaped work: when this happens, do that. Intake, scheduling, quoting, invoicing, status updates, reminders, and the handoffs between systems that nobody owns. If you can write the rule on an index card, software can run it.

It is a poor fit wherever the right answer depends on judgment, tone, or a document nobody has read yet. That work needs a different tool, and confusing the two is the most common way an automation project goes sideways.

In a field service business, one booking often touches three systems and two people before a crew is assigned. Automated, the intake form creates the job, prices it against your rate table, sends the confirmation, and puts the crew on the schedule. The same two people still work there. They spend that hour on the phone with customers instead of retyping addresses.

The number worth tracking is hours returned per week and the class of error that stops happening, not how many steps got automated. Write it down before the build starts, then check it a month after launch.