AI Process Audit
Map out your process
ServicesAI agentsAutomationCustom softwareIntegrationsGrowth & marketingAll servicesHow we workSectorsAboutAI Process AuditMap out your process

How we work

From the first callto AI that keepsrunning in your business.

Most AI stops at a demo that looks good once. I work in four phases, and after each one you decide whether we carry on. You know up front what you get, what you have to do, how long it takes and what it costs.

Map your process Jump to the four phases

Free, no strings. Your data stays in the EU.

€4 to €15what one invoice costs in time when someone types it
2 hrs → 10 minwhat a recurring task can come down to
3 to 6 mosusual payback period

These are general reference figures from practice, there for you to do your own sums with. They are not figures from Diginesso clients. Those go here once the first projects are running and the client agrees to it.

The real risk

The demo works. That is where it starts.

Almost anyone can show you something that gets it right once. The hard part comes later, when a hundred slightly different cases arrive every day and nobody is watching any more. That is what this way of working is for.

It only works on tidy examplesThe demo has one clean invoice in it. Your inbox has scans and phone photos that are half readable.
Nobody is watching itAfter handover it runs out of sight. When it stalls, you find out because a customer calls.
It sits next to your systemsWhatever the AI works out has to land somewhere, in your bookkeeping or your ERP. Otherwise someone retypes it anyway.
How I work

Four phases. After each one, you decide.

You are never locked into the next step. At the end of every phase something concrete is in your hands, and then you choose whether we go on.

Discovery

1 to 2 weeks

We look together at how the work really runs today. Which steps, which screens and where it sits waiting. I work out how much time and money is in it and what it would cost to fix. If automating does not pay off in your case, I say so and it ends here.

What you getA report with the bottlenecks and the arithmetic behind them, plus what I would build. The report is yours whatever you decide.
What you doAn hour or two of conversation and let me watch your own process. Nothing else.
How longUsually 1 to 2 weeks after the first call, depending on how quickly we can reach the people who do the work.
What it costsA fixed 1,250 euro excluding VAT. If we build together afterwards, that amount comes off the job in full.

Decision point. If the report names no opportunity worth more than the 1,250 euro over a year, you get your money back. And you can take the report to someone else without any awkwardness.

Pilot

2 to 4 weeks

We take one piece of the process, the piece that eats the most time, and I build it for real. On your own data and connected to your own systems, because everything works on made-up examples. Every week you see where we are and you can try it yourself.

What you getSomething working that you can try, with the numbers alongside it: how much it handles, how often it is wrong and what happens then.
What you doSupply real examples and arrange access. After that, half an hour a week to look along.
How longUsually between 2 and 4 weeks. It mostly depends on how quickly we can get to your data and your systems.
What it costsA fixed price we agree on the basis of the audit, so you know the amount before we start.

Decision point. We agree up front which score the pilot has to hit. If it misses, we do not go to production and you have paid for a pilot only.

Production

2 to 6 weeks

This is where it parts company with a demo. I finish it so it also copes with the messy cases, wire it into your systems and put monitoring on it. If something stalls or starts drifting, I see it before you notice. For the first weeks it runs alongside your old way of working, until the numbers hold up.

What you getSomething that runs every day, with monitoring, a log of what it did and a button to stop it. Plus the write-up of how it fits together.
What you doOne person on your side who knows the process well and checks the first weeks of output.
How longUsually between 2 and 6 weeks, depending on how many systems hang off it.
What it costsPart of the build. A project like this usually lands between 15,000 and 50,000 euro. The 1,250 euro from the audit comes off.

Decision point. It only goes live when you say it can go live. Until then you can fall back to the old way without anyone noticing.

Scale

ongoing

Your business changes, so the thing has to change with it. I keep an eye on whether it is still doing well, fix it when a supplier reshuffles their form, and take on the next piece of the process once that pays off. This is the phase where most AI projects quietly fall over.

What you getOversight of what is running, repair when something changes, and a short quarterly summary of what it brought in.
What you doLet me know when something changes on your side, like a new system or a new supplier.
How longAs long as you want. Maintenance can be cancelled monthly.
What it costsA fixed monthly amount for maintenance and monitoring. Extensions are agreed one by one, with a price up front.

Decision point. If you want to stop, you get the code, the keys and the documentation, and another developer can take it over.

About the prices, so you are not guessing

The 1,250 euro for the audit is fixed and published on this site. The price for the pilot and for the build we agree once we know what it involves, so after phase 1. I do not run an open hourly meter you only see the total of afterwards.

  • A fixed price per phase, always agreed before that phase starts
  • The audit is credited in full once we build together
  • Maintenance is a fixed monthly amount and can be cancelled monthly
  • You own the code and the data, so the price never buys you into a lock-in
What that looks like

One example, start to finish.

Below, an invented example runs through all four phases. That way you see what happens per phase without me pretending it is a client of mine.

Invented example, not a client

An installation company retyping supplier invoices

DiscoveryAround four hundred supplier invoices arrive by email every month. Someone in the office retypes them into the bookkeeping and hunts down the matching delivery note. We measure how long that really takes, what it costs per month, and put next to it what fixing it would cost.
PilotI build the reading and the booking proposal for the three largest suppliers. Nine out of ten invoices go straight through. On the rest it flags a question and a person steps in. All of that sits in a list you can check yourself.
ProductionThe other suppliers come in, plus the credit notes and the invoices that arrive as photos. It gets wired into the bookkeeping and monitoring goes on it. For six weeks it runs alongside the manual work, and the manual work only stops once the numbers hold up.
ScaleA supplier switches to a different format. That gets fixed before anyone in the office notices. After that we look at the next step, for example the job sheets that still come in by app.

This company does not exist and the numbers are made up. They are here to show the shape of a project. The only figures I stand behind are the general reference figures at the top of this page.

Why is there no real client case here?

Because Diginesso has only just started. I would rather you read this than have me write down figures I cannot back up. Once the first projects are running and the client agrees, the real numbers go here, with the story behind them, named or anonymous, whichever the client prefers.

Honest about the risks

What can go wrong, and what I do then.

Every project has rough spots. These are the six I run into most. Better you read them here than find out halfway through.

The AI gets it wrong

What I do. Above a set level of doubt it settles nothing on its own. It hands the case to a person. You set that threshold yourself and you can always make it stricter.

Your data is messier than expected

What I do. That surfaces in phases 1 and 2, while stopping still costs almost nothing. Sometimes cleaning up your data is the first win and pays for itself on its own.

A supplier reshuffles their form

What I do. Monitoring trips as soon as the numbers drift from normal. The repair sits inside maintenance, so you get no separate bill for it.

It works, and nobody uses it

What I do. That is why phase 2 always has someone on your side who really works with it. If that person cannot be freed up, that is the honest signal to wait.

I drop out

What I do. I work alone, so this is a real risk and I am not coy about it. The code sits in your own environment with the write-up next to it, so another developer can pick it up. We arrange that at handover, long before it is needed.

It returns less than hoped

What I do. After the pilot, what it handles is in black and white. If that disappoints, I say so and we stop there. You have paid for a pilot and not for a whole build.

Ownership

The code and the data are yours.

You are not renting a box you can never look inside again. Everything sits in your own environment, inside the EU, and you can walk away with it at any moment.

The code sits on your accountIn your repository and on your servers or cloud account. I have access while we work together and not after that.
The data stays yoursI train no models on it and I share it with nobody. Your data stays inside the EU, and on your own machines if you want it there.
The write-up comes with itAt handover you get documentation another developer can take over from. Without that, a handover is not finished as far as I am concerned.
Leaving is always possibleMaintenance can be cancelled monthly. What runs keeps running, and I hand it over properly to whoever takes it on.
Secure and European

Your data stays in Europe.

Most AI comes out of the United States and behaves like a black box. I build inside the EU, which is also what lets a European buyer say yes without a legal detour.

Built inside the EUYour data does not quietly travel to the United States. On-premise if you prefer that.
GDPR and the EU AI ActBuilt in from the start, with the documentation your auditor will ask for.
You hold the keysNothing leaves your environment without your say-so.
Who builds it

I build it myself and I stay reachable.

I have built AI and software for companies for years, from one-person businesses to factory floors. No team of juniors to talk through. You deal with me directly, in English, Dutch, German or Italian.

I care a lot about it still working in practice, including the month nobody looks at it. And about your data staying in Europe. I am strict about that.

Wesley Beerendonk · Diginesso

Frequently asked

The questions you probably have.

Do I have to take all four phases?
No. You decide again after every phase. Plenty of people start with the audit alone and look further only after that. The report is yours either way.
Can I skip the pilot?
Sometimes, if the process is small and predictable and there are few exceptions. For anything touching documents or customer contact I advise against it. You would only discover in production what actually comes in, and that is exactly where projects break.
How quickly can we start?
The first call is usually arranged within a few days. When the audit can start depends on what is running at that moment. You hear that straight away in the first call, so you are not waiting on a schedule you cannot see.
Who does the work?
I do. You are not talking to an account manager and you are not getting a junior on your project. For heavy lifting I sometimes bring someone in, and you hear up front who that is and what they do.
We are outside the EU and want to sell into Europe. Does that work?
Yes, and it is a common reason people end up here. Your data stays inside the EU, the build follows GDPR and the EU AI Act, and you get the documentation your European customers and their auditors ask for. That removes the objection before it is raised.
Do you work under contract?
Yes. A fixed price per phase, a month of notice on maintenance, and the arrangements on ownership and data in writing. Each job has its own deliverable and its own price.
What happens to my data during a project?
It stays in Europe and it stays yours. I work in line with GDPR and the EU AI Act, and everything can run on your own machines if you want. For the pilot I need real examples, and we agree up front which ones those are.

Just start at phase 1.

Spend a few minutes with Digi on the work that eats most of your time. After that you know where the gain sits in your case, and you decide for yourself whether phase 1 is worth it.

Map your process

Free, no strings. Your data stays in the EU.