What Business Automation Actually Looks Like
Last updated:
The word oversells the thing
“Automation” suggests something dramatic. In practice it is a small program that watches an inbox, a folder or a queue, does the handful of steps a person did, and raises a flag when the input does not look like it should.
That modesty is the point. The projects that pay back fastest are the ones nobody would put in a brochure.
Four real shapes
- Inbox to system. Orders arrive as email or PDF, get read, validated and posted. Saves 60–90 minutes a day in most businesses that receive orders this way.
- System to system. Two tools that should share data and do not. A person is currently the integration.
- Watch and alert. Nobody does this today, which is the problem — a stock level, an overdue payment, a job with no engineer assigned.
- Scheduled assembly. The weekly report someone builds by hand from four sources every Monday morning.
If somebody in your business has a routine that starts with “first I download…”, you have found an automation candidate.
What one costs
| Project | Cost | Typical payback |
|---|---|---|
| Single email-to-system flow | £3k–£8k | 3–6 months |
| Two-system integration | £4k–£12k | 4–9 months |
| Monitoring and alerting | £2k–£6k | Often immediate — one prevented incident |
| Report assembly | £3k–£9k | 6–12 months |
| Multi-step workflow with exceptions | £12k–£35k | 9–18 months |
The exception path is the project
Automating the normal case is usually a few days. Everything after that is the exceptions: the malformed order, the customer who does not exist yet, the quantity that cannot be right.
A good automation handles what it can and hands the rest to a person with a clear reason attached. A bad one either fails silently or stops entirely, and both create more work than they removed.
Keeping a person in the loop where it matters
- Anything spending money or committing stock gets a review step at first
- Confidence thresholds, so uncertain cases route to a human
- A daily digest of what ran and what was skipped
- A visible off switch anyone can use without calling us
We usually launch with review on everything and relax it as evidence accumulates. It costs a couple of weeks of someone clicking approve, and it buys trust that the system keeps for years.
How to pick the first one
Frequency times duration times error cost, divided by how many departments are involved. The winner is almost always something boring that happens daily inside one team.
Start there, prove it, then use the credibility to fund the ambitious one. Businesses that start with the ambitious one usually do not get a second project.
Frequently asked questions
How long does a first automation take?
Will it break when a supplier changes their format?
Do we need to change our systems?
What if our process is not consistent?
Got a process somebody still does by hand?
Show us how it works today and we will tell you what it would cost to automate — or when a cheaper change would do the same job.
Related services
What we build for problems like this one