Workflow automation: what it costs
The four processes worth automating first, and the three cheaper fixes to rule out before you pay anybody.
Updated 19 September 2026 · 8 min read
The short answer
Most workflow automation projects fail the same way: somebody automates a process nobody had written down, and the software faithfully reproduces a mess.
Write the rules first, that step is free. Then check the three cheap fixes below. A build only earns its cost when the decision depends on information the tools you already own cannot see.
A workflow is any sequence where something moves between people and somebody has to say yes. Approving a spend, signing off a quote, booking a job, releasing an order, passing a candidate to the next stage. In most businesses under 200 people these run on email, and nobody ever decided that.
The result is familiar. A request sits with somebody who is in meetings all day. Nobody can say who approved what. The policy that says two people must sign above five thousand pounds holds right up until somebody is in a hurry.
The four processes worth automating first
Ranked by how reliably they pay back. If your candidate process is not one of these, be more sceptical of the business case.
| Process | Why it pays | What it usually costs |
|---|---|---|
| Spend approval | Blocks work while it waits, and produces the audit answer you cannot otherwise give. The delay is the expensive part, not the admin. | Lower band |
| Handover between teams | Sales to operations, survey to install, order to dispatch. This is where things get dropped, and where the customer notices. | Lower to middle band |
| Recurring document production | Anything assembled by hand on a schedule. A drinks manufacturer had three people spending a fortnight a cycle on compliance paperwork, and the same job now runs unattended. | Middle band |
| Exception spotting | Where somebody experienced scans for the thing that looks wrong. Automating the scan and escalating only the exceptions frees the most expensive person in the chain. | Middle band |
Write the rules down first. That part is free
Software cannot enforce a rule nobody has stated, and this is the step every failed automation project skipped. Four questions, and the answers belong on one page.
- What are the thresholds, in pounds or in risk, and who decides at each one? Most companies find they have two different answers depending on who you ask, which is the actual finding.
- Who decides when that person is away, and do they have the same limit or a lower one?
- What skips the process entirely, and who decided that? There is almost always a list, and it is almost always unwritten.
- What happens when reality comes in above what was agreed? A tolerance, a fresh decision, or a conversation. Pick one now rather than each time.
Answering those produces a document that is useful on its own and doubles as the specification for anything built afterwards. A fair number of businesses stop here, circulate the page, and find most of the problem goes away, because it was never really a software problem.
Three cheaper fixes to rule out first
| Option | When it is right | Roughly |
|---|---|---|
| Turn on what you already pay for | Most mainstream accounting and operations packages include approval routing, and a lot of companies have never switched it on. This is the commonest thing businesses pay to have built twice. | Included, or a tier upgrade |
| A form plus an off-the-shelf automation tool | Simple thresholds, one or two decision makers, modest volume. Quick to set up and genuinely sufficient for a lot of businesses. | Tens of pounds a month |
| Change who decides | Not software at all. Raising one person’s authority limit removes more delay than most automation projects, and costs nothing. | Free |
What pushes a business past these is rarely the routing. It is that the right decision depends on something the finance system does not hold: which contract this sits against, whether that budget has room, whether this supplier is approved, what the site is doing this week.
What it looks like when it works
A construction contractor we worked with had a policy that existed and was not followed, because following it meant chasing a director who was on site all week. The fix was not a stricter policy.
- The existing rules built in as they were rather than rewritten, so nobody had to learn a new policy.
- Progress visible to the person waiting, which stops "where is my request" being a phone call.
- Decisions possible from a phone, because the person holding things up is rarely at a desk. This is the single detail that decides whether it gets used.
- A complete record produced as a by-product, with nobody maintaining it.
The last one is undersold in every business case and matters most the first time an auditor, an insurer or a supplier in dispute asks who authorised something. The same pattern applies to work in the field: forty engineers who could not see what had happened at a site before they arrived had the history sitting in a cabinet forty miles away.
What it costs
A single defined workflow sits in the lower band at four to eight weeks, and most of that time goes on agreeing the rules and the exceptions rather than on building screens. Several workflows across departments is a platform and sits higher. The bands are published.
Where the workflow has to read from or write to systems you already run, the integration is usually the largest single line rather than the automation itself.
Common questions
What does workflow automation cost in the UK?
A single defined workflow starts in the lower band, from £10,000, at four to eight weeks. Simple routing through an off-the-shelf automation tool costs tens of pounds a month and is worth trying first. Most mainstream accounting packages already include approval routing at no extra cost.
Which process should we automate first?
The one where waiting costs you money rather than the one that annoys people most. Spend approval and handovers between teams pay back most reliably, because the delay blocks work and the missing record is the thing somebody eventually asks for.
Could an off-the-shelf automation tool do this?
Often, and it is worth trying before commissioning anything. It stops being enough when the right decision depends on information the tool cannot see, such as which contract the work sits against or whether that budget has room left.
Why do automation projects fail?
Almost always because the process was never written down, so the software reproduced an undocumented mess faithfully. Writing the rules on one page before anybody quotes is free, takes an afternoon, and is the single highest-value step in the project.
How long does it take to build?
Four to eight weeks for one defined workflow. Most of that is agreeing the rules and the exceptions rather than building screens, so it goes faster where the policy is already written down.
Will people actually use it?
They use it when it is faster than the email was, which in practice means it has to work on a phone. Anything requiring a desktop gets routed around within a month, because the person holding things up is usually the one who is never at a desk.
Bespoke software development
Custom systems for the work no off-the-shelf product does properly, built around your process rather than around a template.
About the serviceSystems that do not talk to each other
How to put a yearly number on the retyping, and how to check the cheap fixes before paying for the expensive one.
Read the guideHow to make your business run without you
Everybody says delegate. This is about why that does not work yet, and what has to change first.
Read the guideTell us what is not working
Describe the process that is costing you time. If software is the wrong answer we will say so, and if a product already covers it we will name the product.
From £10,000Most projects land between £15,000 and £55,000.