
I’ve spent a lot of time building systems and automations over the years, both in technical roles and in my own business.
One lesson I’ve learned is that starting with the technology can send you in completely the wrong direction.
If I came into a business to look for opportunities around AI and automation, I wouldn’t begin by searching for places to implement AI. The first job would be understanding how the business actually works.
Only then can you make sensible decisions about what is worth changing and which technology, if any, should be involved.
I’d begin by looking at the workflows that meaningfully affect the business's performance.
For many service businesses, that means understanding what happens from the moment an enquiry arrives.
How does that enquiry get handled? How is it qualified? Who produces the quote? What happens during follow-up? How does a successful enquiry become a booking or piece of work, and what needs to happen before delivery?
I’d want to follow that journey through the business rather than looking at individual systems in isolation.
That’s because an operational problem often exists between systems, departments or stages of a workflow rather than neatly inside one piece of software.
Management can explain how a workflow is supposed to operate.
That’s useful, but it isn’t enough.
I’d also want to speak to the people doing the work every day and understand what actually happens when they try to follow that process.
The difference can be revealing.
A workflow that looks perfectly reasonable from above might require someone to enter the same information into two systems. Employees may have created an unofficial spreadsheet because the main system doesn’t give them what they need.
Data might need manual manipulation before another system can use it. Work could regularly stop while someone waits for approval, or an important part of the process might depend on knowledge that only one experienced employee possesses.
Those things can become so normal that the business stops noticing them.
An audit should make them visible.
Once you’ve identified an operational problem, the next question is whether it’s actually worth fixing.
That’s where I think the conversation needs to become commercial.
Imagine a workflow is unnecessarily consuming 500 hours of staff time each year. If there’s a relatively straightforward way to remove a substantial proportion of that work, it deserves serious attention.
Another problem might irritate employees every week but have little financial impact and require a significant investment to change.
Those two problems shouldn’t automatically receive the same priority.
I’d want to understand how frequently an issue occurs, which employees are involved, how much time it consumes and what that capacity costs the business.
It may also impact revenue or customer experience. Slow enquiry handling could affect conversion. A bottleneck might limit how much additional work the business can take on. Errors and rework can create costs elsewhere in the workflow.
Putting numbers to these problems turns a list of frustrations into something management can act on.
This is the point where technology should enter the conversation.
The appropriate intervention depends entirely on what the investigation uncovers.
Two existing systems might need connecting so employees no longer move information between them manually. A repetitive workflow with predictable rules could be handled through conventional automation.
The business might already own software capable of solving the problem but not be using the relevant functionality.
Sometimes the underlying process itself needs changing, with no new technology required.
And where interpretation, analysis or more complex decision-making is involved, AI may genuinely offer the most useful solution.
The audit shouldn’t be trying to justify one of those answers in advance.
It should establish which one makes commercial sense.
I don’t think the useful output from an AI and operational audit is a long list of things a business could automate.
There will almost always be plenty of those.
The useful output is a prioritised roadmap showing where time, capacity or revenue is being lost, what is causing those losses and what it’s realistically worth doing about them.
Some improvements might be relatively inexpensive quick wins. Others could require more significant changes but produce a substantial return.
Some problems may be real but aren’t worth solving yet.
That prioritisation matters, particularly for established businesses where years of accumulated processes, systems, and workarounds may need investigating.
Trying to fix everything at once isn’t necessarily the best use of time or money.
Operational weaknesses often become more visible as a business grows.
A process that works reasonably well at its current volume might struggle when enquiries double. A manual task that takes only a few hours today can become a major capacity problem as transaction volumes increase.
The natural response can be to hire more people.
Sometimes that’s exactly what the business needs.
But before adding another salary to compensate for increasing workload, I’d want to understand whether existing staff capacity is being consumed by processes that could
be improved.
If the business can free up meaningful capacity by changing a workflow, integrating systems, or automating repetitive work, it may be able to support more growth with the team it already has.
This is the thinking behind the way I approach audits at Qualifyd Consulting.
The objective isn’t to walk into a business looking for somewhere to put AI.
It’s to understand how the business operates, identify where commercially meaningful capacity, time or revenue is disappearing into its workflows, and determine which
improvements are worth prioritising.
AI and automation can be powerful tools in that process.
But they’re tools.
The business problem comes first.
If you’re planning to grow but aren’t sure whether your current operation can support that growth efficiently, that’s exactly the kind of question a Qualifyd Consulting audit is designed to investigate.
© September 28, 2026 Qualifyd Consulting Ltd. All rights reserved.
01244 456101 | jonathan@qualifydconsulting.com