Business Process Automation

What business process automation covers

Business process automation turns a repeated sequence of office tasks into a system that runs them the same way every time. Most small businesses already have one. An enquiry comes in, someone copies it into a spreadsheet, replies with a quote, waits for a yes, books the job, sends a confirmation and later raises an invoice. Each step is simple. Together they take hours a week, and a step gets dropped whenever someone is busy.

It does not replace your team or run the business by software. It handles the parts of the process that follow a pattern, and it hands over the parts that need a person. The result is a process that is written down, measured and consistent, rather than one that lives in the head of whoever is at the desk.

Some of the work is done by a small custom app, some by an automation that moves information between the tools you already use, and some by an AI step that reads an enquiry and sorts it. Which mix fits depends on your process. We confirm it after we have mapped it.

Where the admin piles up between enquiry and invoice

The gap is usually in the same six places.

• Enquiry intake: details arrive by web form, email, text and phone, and end up in four different places.
• Quotes: someone rebuilds a quote from an old one, changes the numbers and emails it off.
• Booking confirmations: a time is agreed on the phone, then confirmed by hand, and sometimes the wrong one goes out.
• Reminders: appointments, deposits and quote follow-ups are chased from memory, or not at all.
• Invoice follow-ups: the invoice goes out, then nobody notices when it is overdue.
• Reporting: someone pulls numbers from three systems every month to answer one question.

None of these needs a senior person. All of them need to happen, and each one is easy to drop when the day gets busy. That is where automation earns its place.

Map one process end to end first

We start with one process, not the whole business. Pick the one that causes the most grief, usually enquiry to booked job or job completed to invoice paid. We sit down with the person who runs it and write out every step as it actually happens, not as the business manual says it should.

Take a small plumbing business as an example. The business is made up, but the steps are the sort most service offices run through. A quote request arrives by email. The office copies the name, address and job type into a spreadsheet. Someone checks the diary, drafts a quote from a template, emails it and makes a note to call back in a few days. If the customer accepts, the job is booked and the details are copied again into the job sheet.

Once the steps are on paper, the useful question is simple. Which steps follow the same rule every time, and which steps need someone to decide? That split is the whole design. The map also shows which personal data each step touches, so we can be clear about it. Our privacy policy sets out how the details you send us are handled.

What to automate and what stays with a person

Repeatable steps are the good candidates. Copying details from one place to another. Sending a confirmation when a booking is made. Creating a record when a form is filled in. Sending a reminder ahead of an appointment. Chasing an unpaid invoice on a schedule you approve. Filing a signed quote against the right job.

Steps that need judgement stay with a person. Deciding whether to discount a quote. Handling a complaint. Choosing a supplier for an unusual job. Approving a refund. Deciding whether a late payment needs a phone call or a payment plan. The system can prepare these for a decision. It should not make them.

Keeping a person on approvals

Automation should draft and wait. A quote is built from your template and sent only after the right person has approved it. A reminder is queued for review, and the reviewer can change the wording or hold it. Invoice chasers stop the moment a payment lands, and an overdue account goes to a person instead of an automatic letter.

Exceptions go to a queue. Anything outside the rules you set is held for a staff member, with the context already filled in, so nobody has to rebuild the case from the start. The usual triggers are listed below. You choose the thresholds.

• Quotes above a value you set
• Refunds and credits, always
• Any message that mentions a complaint or a dispute
• Changes to a booking after the confirmation has gone out
• Requests with missing details that the rules cannot fill

What one job looks like once it is mapped

Take the same plumbing quote. The request arrives through your web form and a record is created with the name, address and job type already filled in. A draft quote is built from the template for that job type. The office sees it in a review list, changes one line and approves it. The quote goes out with a link to accept.

If it is accepted, the job is booked into your diary and a confirmation is queued. Before the job, a reminder is queued for review. When the job is marked complete, the invoice is drafted from the quote, sent for approval, and a follow-up is scheduled for the due date.

Nothing in that chain is clever. It is the same work the office was already doing, done in the same order every time, with the person spending their attention on review screens instead of copying details.

Compared with hiring admin help and off-the-shelf tools

Most owners looking at this have already considered two other routes. Both are reasonable. Here is how they compare for the admin between enquiry and invoice.

Hiring an admin person is the right answer when the work is mostly judgement and relationships. It stops being the right answer when the work is mostly copying, because copying grows with enquiries, and a new hire grows slowly and costs wages whether the week is quiet or busy.

Off-the-shelf tools set up by your staff are often a good start for a simple process. They become a problem when staff end up as the glue between them, and nobody owns the setup once the person who built it has moved on.

When a standard tool is enough

Some processes are simple enough for a standard tool with a few rules. A booking form, one confirmation email and a reminder is a fair example. If that covers the process, buy the tool and set it up. We will say so on the discovery call rather than sell you a build you do not need.

The trouble starts with the exceptions. A standard tool handles the normal case well and the odd case badly, and the odd case is where most of the admin sits. A tool configured by staff often has no approval step, no record of what it sent, and no one assigned to fix it when a reminder goes to the wrong person. Business process automation is built around those edges: the exception queue, the record of every action and a named owner.

• Two or more tools need the same information copied between them.
• The process has approvals, value limits or exceptions.
• Nobody can say who fixes it when it breaks.

Is business process automation right for your business?

It tends to suit businesses where the admin has grown around one or two people, where enquiries get lost between channels, and where the owner is the one chasing invoices. It is a poor fit when the process changes every week, when the volume is too low to be worth the effort, or when the real problem is pricing or sales rather than admin. If a simpler fix will do, we will say so and recommend it.

Start with the discovery call. We map one process with you, say which steps are worth automating and quote the build after that. If you also get calls you cannot answer, the AI Receptionist page covers the voice side, and the pricing section covers what the receptionist plans include.