Business operations / AI readiness
Most businesses do not need another general explanation of AI. They need to know which repeated process is worth changing, what the change could return and what risks must be controlled before anything connects to live work.
Your business is ready for an AI audit when repeated manual work creates measurable time, delay, error or revenue cost, but the correct automation is not yet clear. An audit should turn operational pain into a prioritised build plan—not produce a generic list of tools.
Five Readiness Signals
1. The same work repeats every week
Enquiries, quotes, scheduling, follow-ups, summaries or reporting follow recognisable patterns. Repetition creates the evidence needed to design a dependable process.
2. The cost can be measured
You can estimate time spent, response delays, errors, missed handoffs or lost opportunities. Without a baseline, return cannot be assessed honestly.
3. Information already exists
The business has examples of good messages, documents, decisions and outcomes. AI performs better when the required standard is visible rather than held only in one person's head.
4. Someone owns the workflow
An accountable person can explain the process, approve changes and handle exceptions. Automation without ownership creates a faster route to confusion.
5. The business can test one process
There is willingness to begin with a controlled workflow, measure it and improve it before expanding.
When Not to Audit Yet
Delay the audit if the business cannot identify a repeated problem, the underlying offer changes every week or there is no owner able to implement a recommendation. First stabilise the process enough to observe it.
An audit is also not a substitute for resolving legal, data-protection or governance questions. Those constraints should be part of the design, not discovered after deployment.
What to Prepare
- List the five most repeated administrative processes.
- Estimate weekly time and delay for each.
- Collect examples of the current inputs and outputs.
- Name the errors or exceptions that matter.
- Define what improvement would be commercially meaningful.
Do not clean the process before the audit until it stops representing reality. The friction is evidence.
Include the exceptions as well as the normal route. A workflow that appears simple on paper may rely on experienced judgment at several points; those decisions determine where AI can safely assist and where approval must remain human.
What a Useful Audit Should Produce
The outcome should identify the priority workflow, the current-state map, the proposed future state, required systems, data and approval controls, expected return, implementation order and the measures used to judge success.
Audit standard: if the recommendation cannot explain what to build first and why, it is not yet an operational plan.
Turn Operational Friction Into a Prioritised Plan
The Acquisition Works Audit is the structured entry point for mapping where time is lost, what should be automated first and whether a larger AI operator build is justified.
Start with the £297 Acquisition Works AuditFrequently Asked Questions
Do I need to know which AI tools I want?
No. Tool choice should follow the workflow, constraints and return rather than lead them.
Is an audit only for large businesses?
No. Small service businesses often have clear repeated processes and feel the time cost more directly because administration sits with the owner.
Will the audit automate anything?
An audit defines the opportunity and build plan. Implementation is a separate stage so the commercial case and controls can be assessed first.
How do I measure success?
Use the baseline relevant to the workflow: time per case, response speed, error rate, conversion, rework or capacity recovered.
AI readiness is not enthusiasm for technology. It is the presence of a repeated operational problem, enough evidence to design a solution and ownership to make the change hold.