What is business process automation?
Business process automation is software doing the routine steps between your existing systems (the copying, checking, chasing and filing) the same way every time, without a person in the middle. It is not a new system you move into. It is connective tissue between the systems you already run.
A worked example: an order arrives by email, and today someone reads it, types it into the accounting system, checks the price against the contract, creates the job, and emails a confirmation. Automated, that sequence runs on arrival in a few seconds, and the person only sees the ones that fail a check.
The distinction that matters commercially: automation handles work that follows rules. Work that needs judgment needs an AI agent, a person, or both. Most businesses have far more of the first kind than they think.
The four things it actually replaces
Almost every automation a small or mid-sized business buys is one of these four, or a chain of them. If you can name which one you are buying, you can scope it.
1. Re-keying
The same information typed into a second system because the two do not talk. An order in the shop and again in the accounts. A candidate in the job board and again in the tracker. Re-keying is the cheapest thing to automate and the easiest to measure, because the time is countable and the error rate is visible.
2. Chasing
Work that waits on somebody. Unpaid invoices, unsigned documents, unreturned forms, approvals sitting in an inbox. A person has to remember to follow up, and the follow-up is the first thing dropped in a busy week. Automation does not forget, and it escalates on a schedule rather than when someone notices.
3. Checking
Comparing one thing against another to see whether it is right. An invoice against a purchase order, an expense against a policy, a record against a duplicate. This is where the value is usually understated, because the cost of not checking (a duplicate payment, a wrong rate, a missed discount) does not show up as hours.
4. Filing
Putting things where they belong: folders created, documents renamed and stored, records tagged, statuses updated. Individually trivial and collectively substantial, and the first thing to go wrong when someone is away.
If you can explain the rule to a new starter in one sentence, it is automatable. If explaining it takes ten minutes and ends with "but it depends", you have found either an exception to handle or a decision that should stay with a person.
What it is not
It is not a new system
The most common misunderstanding. Automation sits between your CRM, your accounting package and your inbox; it does not replace them and you do not migrate into it. If someone is proposing that you move your operations onto their platform, that is a software purchase, and it should be judged as one.
It is not the same as RPA
Robotic process automation drives the user interface: it clicks buttons and reads the screen like a person would. It exists because some systems have no other way in, and it is genuinely useful for those. But it breaks whenever the screen changes, so it is the fallback rather than the default. Proper automation talks to systems through their APIs, which are stable and designed to be talked to.
It is not AI, though it increasingly includes some
A rules engine and a language model are different tools. Rules are deterministic: the same input gives the same output, every time, and you can prove it. A model handles language and ambiguity but is right most of the time, which means it needs a confidence threshold and a review queue. Good systems use rules wherever rules will do, and a model only where judgment is genuinely required. The agent-or-workflow question goes into where that line sits.
It is not headcount reduction
For a business under a couple of hundred people, automation rarely removes a role. What it reliably does is stop you needing the next hire as early, and give the people you have their week back. That is a smaller claim than the one usually made, and it is the one that holds up in daily use. See hire or automate.
How to tell if a process is a candidate
Five questions, in the order that matters. A process that clears all five is worth costing.
- Does it happen often? Frequency is what turns a small per-run saving into a real number. A daily task saving thirty minutes is worth roughly eleven hours a month; a quarterly one is worth almost nothing. This single factor decides more cases than the other four combined.
- Is it the same every time? Not identical. Branches are fine and expected, but governed by rules someone can state. A process that changes shape every month is not ready.
- Do the systems have APIs? Most modern ones do. Check whether API access is included in your current plan rather than a tier above, because discovering that mid-build is an avoidable surprise.
- Is the data clean enough? Duplicate records and three spellings of the same supplier do not stop a build, but they have to be dealt with, and it is cheaper to know before than during.
- Is there one person who can decide? The single best predictor of a project finishing on time. Scope questions arrive constantly, and a project moves at the speed of whoever answers them.
The readiness checklist works through these with the arithmetic, and what should not be automated covers the cases where the honest answer is to leave it alone.
Automation versus buying more software
Often the right answer is neither a build nor a bigger subscription, and a firm that will not tell you that is not worth hiring.
If your requirement is ordinary (expense management, e-signature, scheduling, help desk, payroll), a mature product will beat anything custom on cost, features and reliability, because its vendor has spent years on edge cases you have not thought of yet. Buy it.
Automation earns its place in the gaps between those products: the handoffs, the approvals that follow your rules rather than the vendor's, the sync that keeps two systems honest. That is work no product will do for you, because it is specific to how your business runs. Build versus buy works through the decision properly.
What it costs
Priced in two parts: a fixed setup cost once, then your choice of how it is maintained. The starter (one trigger, one action, in a tool you already use) is $499 one-off, with no monthly fee. Full systems run $1,500 to $12,000 to set up, and every setup includes 30 days of support after go-live. After that there is no fee per system: you pay $175 a change on pay as you go, or take a plan from $700 a month per account with changes, monitoring and fixes included. As an example, missed-call text-back, lead follow-up and an AI chat agent are $8,000 to set up, or $6,400 with 20% off for three systems. The first year is $14,800 with a Growth plan ($13,400 paying for the plan yearly), or $6,400 plus $175 for each change on pay as you go.
Two costs are not ours and continue after we finish: the platform subscription the automation runs on, usually $30 to $150 a month, and model usage where AI is involved. We estimate both during scoping so the running cost is on the table before you decide. The full breakdown is on the pricing page, and the cost answer covers what moves each number.
Not sure which of your processes qualify?
That is exactly what scoping is for, and it is free. Thirty minutes on a call, then a written proposal telling you which of them are worth automating, including when the answer is none of them.
You will talk to Fayez or Kareem. Nobody else.