All posts

What is an AI audit, and what should an Irish business get out of one?

An AI audit maps where your week goes before anyone names a tool. What it covers, what you should receive, and how to spot a sales call.

Natan Trolka · Founder, Otomatic Digital

What is an AI audit, and what should an Irish business get out of one?What is an AI audit, and what should an Irish business get out of one?

The short answer

An AI audit maps how a business currently operates, then identifies which repeated work is worth changing and which is not. A good one covers the workflow, the tools, the data, the handovers and the risk, and ends in written findings and a scoped proposal. It should recommend nothing until the mapping is done.

The word audit does a lot of work in this market and most of it is marketing. What usually arrives is a call, a slide deck, and a proposal at the end, and the only thing that gets audited is your appetite for spending. A real one leaves you holding written findings you can check against your own week. That is the whole test, and it is worth applying before you pay anybody for one.

What it looks at

An audit worth the time works through 5 layers, and the order matters because each one changes what you notice in the next.

It starts with the workflow: every task that repeats, who touches it, how often, how long it takes, and what happens to it when that person is on holiday. Almost everything else follows from this, and it is the layer people describe least accurately, not through any dishonesty but because work you delegated 3 years ago tends to stay frozen in your head exactly as it was when you handed it over.

Then the tools. Which systems hold which data, which of them overlap, and where information gets retyped from one into another. Retyping is the clearest signal there is. Every instance marks a connection that was never made, and the staff have usually built a workaround around it that nobody upstream knows about.

Then the data itself, which is really a question about trust. There is normally a system of record on paper and a different one in practice, and the gap between the two is where reporting quietly goes wrong. The Data Protection Commission says to establish, before using an AI system, what personal data it uses, how it uses it and where that data goes when a third party is involved (DPC, AI, Large Language Models and Data Protection).

Then the handovers. Work passing between people is where things get dropped, and those points are invisible on any org chart because they are not anybody's job. They are the gaps between jobs.

Last, the risk. Which steps need a person to approve them, which calls software should never make alone, and who gets the call when something goes wrong at 6 on a Friday. Suppliers who skip this layer are the ones who later describe an outage as an edge case.

The questions it should ask you

You can judge an audit by what it asks. If none of these come up, the mapping was shallow.

Which task would cause the most damage if the person who does it left tomorrow. What gets retyped from one system into another, and how many times a week. Which enquiries arrive outside working hours, and what happens to them now. What you rebuild by hand every month that looked automatic when you bought the tool. What somebody has already tried to automate here, and why it got switched off. And what must never happen without a person seeing it first.

The last 2 carry the most weight. A previous failed automation tells you where trust was broken and what the team will quietly resist, which is the single best predictor of whether anything new gets adopted. The approval question surfaces where the risk sits in your own words rather than the supplier's assumptions, and those answers become the escalation list. The escalation list is what the build gets judged on 6 months later.

What you should walk away holding

A document, rather than a feeling that the call went well.

It should name the workflows worth changing in priority order, with the dependencies and the scope boundaries, so you can see what has to happen before what. Where the evidence supports a build, it should come with a scoped proposal: what would be built, what it assumes, what you would need to provide, and how success would be judged. Ours arrives within 48 hours of the working session, once we have the inputs we agreed.

It should also name what to leave alone. Every business has work that looks automatable and is not, usually because the volume is too low, the exceptions arrive too often, or the relationship depends on a person doing it. An audit with no exclusions has not looked closely enough to have formed an opinion.

Findings you cannot check against your own week were written for the sale.

How to tell it from a sales call

A sales call opens with capability. An audit opens with your Monday.

If the first 10 minutes go on what the supplier can build rather than on how your week runs, the conclusion was written before the call started and the rest is a demonstration. Timing gives it away too. A sales call names a tool early, because the tool is the product. An audit refuses to name one until the mapping is done, because until then the requirements are unknown and any recommendation is a guess with a logo on it.

The last signal is willingness to say no. Somebody who has done this work before will tell you in the first conversation that a system is the wrong purchase, if it is, and there are more questions worth asking before you sign anything.

What Irish SMEs usually find

Three things surface again and again, across sectors that otherwise have nothing in common. The CSO found AI in use at 17.2% of small Irish enterprises and 57.7% of large ones in 2025, so most small firms start from the tools they already run (CSO, Information Society Statistics: Enterprises 2025).

Enquiries that arrive outside working hours and get answered a day late, if at all. Reporting rebuilt by hand every month from the same 4 sources, arriving too late to act on. And a process living entirely in one person's head, which nobody notices until that person takes annual leave and the week falls over.

The hours attached to these are almost always larger than expected, because each instance on its own is small. Stuntworxelite say their roster and confirmation systems eliminated 4 to 5 admin hours every week.

The total is not really the point. The number that changes a decision is the specific hour, on a specific person's week, that you can put your finger on.

Where the mapping happens

Paid audits exist and some are excellent, particularly at a scale where the mapping genuinely runs to weeks of work. The risk with any paid one is that the document becomes the product, and documents that are products tend to stay comfortably abstract. The protection is in the terms, so read them before you pay.

We do not sell an audit. The Free Business Check is a 30-minute conversation about the problem, your priorities, budget, team, tools and timing, and whether we are the right fit. Afterwards you get your AI Recommendation Plan, with our recommendations, the fit decision and the next step, and we go through it with you. If you want the full review, with value and cost estimates, ranked priorities and a written 90-day plan, that is AI Strategy & Advisory.

If you want to go ahead, you get a fixed-price proposal that sets out what the price covers, how we will both judge the work finished and the monthly management terms. You pay nothing until you accept it. The detailed mapping then happens at the start of the build, inside the fixed price, where we walk your workflows and tools with your team.

If you report a fault against the agreed specification within 30 calendar days of acceptance, we work on it for free until it is fixed.

How to prepare

Track your own time for 5 working days in half-hour blocks. Not for anybody else's benefit and not to show anyone. The point is that you will notice things you stopped seeing years ago, and the conversation gets sharper for it.

Bring whoever actually does the admin. Owners consistently underestimate the number of steps in work they handed over, and the person doing it will name the workaround in 30 seconds flat.

Then apply for the Free Business Check, or send over the 5 tasks that repeat most often and we will start from there.

Frequently asked

Ready to remove the work itself? Start with Workflow Automation.

Start here

Find the work your week repeats.

Tell us your business priorities and bottlenecks in a 30-minute call. Our initial recommendations, the fit decision and the next step follow in writing, and they are yours whether you hire us or not.

Starts with a 30-minute Business Check and your AI Recommendation Plan.