Bespoke Software
Which business processes are worth automating first?
The short answer
Automate the processes that are high-frequency, rules-based, currently done by hand across more than one system, and easy to check for correctness. In most UK SMEs that means enquiry routing, quote and document generation, data transfer between systems, scheduling and reminders, and reporting. A single process typically costs £4,000 to £12,000 to automate properly and pays back within twelve months if it runs daily.
Indicative price ranges
One process
£4,000 – £12,000
A single workflow automated end to end, with monitoring and a fallback when it fails. Most businesses start here deliberately.
A connected set
£12,000 – £35,000
Three to six related processes sharing one data model, so the output of one becomes the input of the next instead of being re-keyed.
Operations-wide
£35,000 – £70,000+
Automation across sales, delivery and finance with a management layer, exception queues, permissions and reporting on throughput.
These are indicative UK ranges based on projects we have actually delivered. Scope drives the number, not the sales conversation — we quote a fixed price after a scoping session, and we will tell you if an off-the-shelf tool is the cheaper answer.
Typical timescales
- 1–2 weeks
Mapping
Every step of the process written down as it really happens, including the workarounds nobody mentions in meetings.
- 3–5 days
Scoring and selection
Each candidate scored on frequency, time taken, error cost and how cleanly it can be checked.
- 3–6 weeks
First build
One process, delivered and running, so the business sees a result before committing to more.
- Ongoing
Extension
Further processes added against a fixed price each, once the first has proven itself.
Who this suits
- Businesses where the same information is typed into more than one system.
- Teams whose growth is currently limited by admin capacity rather than demand.
- Companies with a documented process and a named owner for it.
- Work that happens daily or weekly rather than occasionally.
Who it does not suit
- Processes nobody has written down. Mapping has to come first.
- One-off or seasonal tasks where the engineering cost cannot be recovered.
- Work requiring genuine professional judgement at every step.
- Organisations mid-way through changing the underlying system — automate after the move, not before.
What actually drives the cost
Number of handoffs
Each point where work passes between people or systems is a separate integration and a separate failure mode.
Exception rate
A process that runs cleanly 99% of the time is cheap. One with constant special cases needs an exception queue and review screens.
Legacy systems
Anything without an API has to be integrated the hard way, and that is consistently the single largest line in a quote.
Compliance requirements
Audit trails, approvals and retention rules add real engineering in regulated sectors.
Reporting depth
Knowing the automation ran is free. Knowing what it saved you needs instrumentation.
The four tests
Before automating anything, put the process through four questions:
- How often does it run? Daily beats monthly by an order of magnitude on payback.
- Are the rules stable? If the answer changes case by case, you are automating a judgement, not a process.
- How many systems does it touch? Manual transfer between systems is the highest-value thing to remove and the most common.
- Can you tell when it is wrong? If correctness cannot be checked, the automation cannot be trusted to run unsupervised.
A process that passes all four is worth doing. One that fails the fourth should draft for human approval rather than act alone.
What usually comes first
Across the UK businesses we work with, the same handful of processes come out on top: routing and acknowledging inbound enquiries, generating quotes and standard documents, moving records between a website, a CRM and accounting, scheduling and reminders, and producing the weekly management report someone currently builds by hand.
None of these are glamorous. All of them run constantly, which is precisely why they pay.
What to leave alone
Pricing decisions, anything client-facing that needs tone and context, one-off negotiations, and any process currently being redesigned. Automating a process you are about to change is money spent twice.
Start with one
Do one process, measure it against the baseline, then decide. A business that automates one thing well has proof; a business that attempts eight at once usually has an unfinished project. Costs and timescales for the AI-assisted versions of this work are set out in AI automation cost.
Proof
Where we have done this
How we worked these numbers out
The price bands and timescales on this page are first-party figures taken from projects The Digital Hub has quoted and delivered for UK clients since 2020, not from third-party survey data. Ranges are rounded and exclude VAT. They are reviewed at least every six months and updated when our own delivered costs move. Where a figure depends on a third-party licence or hosting cost, that cost is named in the text so you can check it yourself.
Written by
Tom Beachell
Technical Director, The Digital Hub
Tom leads scoping and delivery at The Digital Hub, quoting and shipping bespoke websites, CRM platforms and private AI systems for UK businesses. The price bands and timescales on this page come from projects he has personally scoped.
Published 21/09/2026 · Last reviewed 21/09/2026 · About The Digital Hub
Common questions
How do we know a process is worth automating?
Multiply how long it takes by how often it runs, then compare a year of that against the build cost. If it does not clear the cost within about eighteen months, it is usually the wrong first choice.
Should we use an off-the-shelf automation tool instead?
Often yes, and we will say so. Tools like those built into your CRM or accounting package handle simple, single-system automation well. Bespoke work earns its place when the process crosses systems that were never designed to talk.
What happens when the automation fails?
It should fail visibly into a queue a human can clear, never silently. Designing that fallback is part of every build we do.
How long before we see a result?
A single process is typically live within three to six weeks of the mapping being signed off.
Do our staff need technical skills to run it?
No. Rules and thresholds are exposed in an admin screen, and your team is trained to adjust them without writing code.
Next step
Get a fixed price for your own version of this
A 30-minute scoping call, then a written fixed price and delivery date. If an off-the-shelf tool is the cheaper answer for you, we will say so on the call.
- 1You tell us the process and the tools you pay for today.
- 2We map the scope and flag anything that will move the number.
- 3You get a fixed price, a schedule and an honest recommendation in writing.
Reply within one working day · No obligation · Full code ownership on every build