AI AUDIT · FEASIBILITY & READINESS
Before adding AI, know what the organisation can actually support.
The audit does not try to place a model in every process. It checks where AI can create value, what the organisation can support, which data is available and which architecture can be operated without losing control.
See what the audit coversAn audit must be able to conclude that a project is not ready. Its value is as much about avoiding a poorly framed investment as identifying an opportunity.
WHY AUDIT
Eight recurring friction points before AI can scale.
AI tools are already being used, but nobody has a complete view.
Teams test tools, sometimes with their own accounts and methods. The organisation no longer knows exactly which data is circulating, which models are used or what genuinely works.
There are many use cases, but nothing is prioritised.
Automating a visible task is not always the best investment. Friction points need to be identified, potential gains measured and attractive demos separated from durable uses.
The data exists, but it is not ready to be used.
Scattered documents, inconsistent access rights, incompatible formats and no trusted reference version: the model is often not the first problem.
Confidentiality constraints arrive too late.
Cloud, local, hybrid, hosting, logging, rights and retention need to be designed before the prototype, not added afterwards.
Nobody really knows who is supposed to validate what.
AI introduces new decision points. Human responsibilities, exceptions, controls and stop conditions need to be explicit.
The real cost is difficult to predict.
Tokens, API calls, oversized models and verbose workflows can turn a cheap prototype into an inefficient system. Frugality has to be designed.
The team is not ready to operate the system.
Without understanding, documentation and rules of use, the tool remains dependent on its creator or is eventually bypassed by users.
A prototype exists, but production adoption is blocked.
The gap between a demo and an operable system lies in access, robustness, traceability, updates, support and integration into real work.
ORGANISATIONAL READINESS
The audit looks at the use case and the organisation that will have to carry it.
Feasibility is not just ‘can the model do it?’. The system must be feedable, operable, controllable, maintainable and understandable.
Use & value
Observed process, friction, frequency, time consumed, criticality, users, human decisions and indicators that can verify whether the solution actually adds value.
Data & knowledge
Sources, quality, formats, location, rights, sensitivity, reference version and conditions under which the data can be used.
Infrastructure & security
Local capacity, hosting, network, workstations, possible models, external dependencies, access, logging and on-premise or hybrid scenarios.
Organisation & maturity
Skills, governance, owners, documentation, adoption, maintenance capability and how humans regain control.
Architecture & trajectory
Compared technical scenarios, components, interfaces, model choices, automation level, prototype stages and route to operation.
WHAT YOU RECEIVE
A decision document, not a sales presentation.
The report should make it possible to decide what happens next, in which order, with which prerequisites and limits.
Map of needs and priority friction points
Assessment of organisational readiness
Analysis of data, access and technical constraints
Qualified and prioritised use cases
Compared architecture scenarios, including on-premise when relevant
Register of risks, unknowns and prerequisites
Governance and human-control recommendations
Concrete roadmap for the first steps
Full report and team debrief
PROCESS
Four stages from uncertainty to an argued decision.
Scoping
Define the scope, people concerned and the question the audit must answer.
Fieldwork
Observe the process, tools, documents, data and constraints with the people who actually perform the work.
Architecture
Compare several ways of solving the problem instead of starting from a preselected technology.
Decision
Present what is recommended, what is not ready yet, the prerequisites and an implementation path.
If the project is ready, the audit can lead into design and development. If it is not, the report states what must be prepared before anything is built.
See possible next stepsLET’S TALK ABOUT THE PROCESS