Process automation
The work nobody enjoys: retyping invoices, moving data from system A to system B, producing the same report every Monday. I map the steps and build the chain that runs without you.
The question is never whether something can be automated, but whether it is worth it. So every automation starts with measurement: how often does it happen, how much time does it take now, and what goes wrong when it goes wrong. Only once those three numbers exist do we build. Then you also know afterwards whether it worked.
Typical jobs
Priced per case. We first measure what the process costs you today and how complex the integrations are. You then get a fixed quote, per phase or for the whole project.
Questions and answers about this service
What is process automation?
Process automation means software takes over repetitive manual work: processing invoices, moving data from one system to another, handling mailboxes and forms or producing the same report every week. Where text has to be read or interpreted, such as an email that contains a price, I use AI for exactly that step. The rest is ordinary, predictable software.
Who is process automation for?
For organisations where people spend every day retyping, copying and checking things a system could do. At Equote two people pulled prices and properties out of hundreds of emails by hand; that now happens automatically and they only look at the exceptions. It works for an office of three and for a large organisation, where I then work alongside the internal IT department.
Which process should you automate first?
The one that scores highest on five points: it happens often, it varies little, a mistake has limited consequences, the data is already in good order and the people who do it now want it. If building it costs less than the process costs you per year, you have your first project. Keep it small enough to go live within six weeks.
How does an automation project work?
It starts with measuring: how often does it happen, how much time does it take now and what goes wrong when it goes wrong. Then I map the steps, build the chain and test it with real cases, including the messy ones. On your side that takes two hours in week one and half an hour a week after that. A first automation is usually live within two to three weeks.
Which systems can Datawonder connect to?
Any software with a properly documented API. In projects I use n8n for the automation flows, as well as Microsoft 365, Google Workspace, Google Sheets, Airtable, Instantly and government APIs. The result lands where your team already works, such as a spreadsheet, your bookkeeping or your mailbox.
What happens when the automation does not recognise something?
It does not guess. Every message or document first passes a fixed set of conditions, and anything that does not meet them is skipped or handed to a person. The system keeps track of what it did, so you can check it afterwards. Up front we agree which data it may see and how long it is kept.
How can I automate my invoicing?
By connecting the steps that are now done by hand. Datawonder automates incoming invoices: they are read and prepared in your bookkeeping. Outgoing invoices can also be created automatically from data that already exists, such as orders or logged hours. That works with any accounting package that has a properly documented API.
Can AI book incoming invoices and receipts?
Yes. AI reads invoices and receipts from your mailbox or an upload folder, pulls out the supplier, amount, VAT and date and prepares the entry in your bookkeeping. Anything the automation does not recognise with certainty is put to a staff member instead of the system guessing. That keeps the books accurate.
Can a report prepare itself every morning?
Yes. Datawonder builds reports that fetch the figures from your bookkeeping, CRM or webshop at a set time. The result is then ready in your mailbox or a shared folder. Nobody has to put together the same overview by hand every Monday any more.
Thinking along, arranging it, staying inside the law
Three things that don't fit in a service list, but that decide how working with me feels.
I think along with you
You're not hiring a pair of hands that builds whatever the brief says. If I think your question isn't your real problem, I'll say so. Often there's a simpler or cheaper route, and sometimes the answer is that you shouldn't build this yet. Sparring over that choice is part of the work.
You don't have to figure it out
I run the whole track: choice of technology, the build, integrations with your existing systems, testing with real cases, explaining it to your team and maintenance afterwards. One point of contact, and one person responsible when something breaks. No vendors pointing at each other.
Compliant, and provably so
Everything I build has to survive current legislation: GDPR, the EU AI Act and the Data Act. That means agreeing up front which data the system may see, where it is processed, retention periods, a data processing agreement and a log of what the system did. So you can explain it when somebody asks.
Further reading
Which process do you automate first? Five questions as a scorecard.
The method I use in every audit to get from twenty ideas to one first project. With the arithmetic included.
Read the article → AutomationWhy most AI pilots never go live
Not because the model is too weak. Four causes I find in almost every stalled project, and how to cover them in week one.
Read the article →Other services
AI voice agents and telephony
An agent that answers the phone after hours, at peak moments and when everyone is already on a call. It recognises why someone is calling, books an appointment in your calendar, transfers when unsure and emails you the rest.
View this service →Custom software, SaaS & AI assistants
For when off-the-shelf doesn't fit: a portal, an internal tool, or an assistant that answers from your own documents and data. Built around your way of working, not a vendor's.
View this service →AI audit & AI training
The cheapest way to start. I come to you, and afterwards you get a report with the processes that return the most, what each costs, what it saves and what goes wrong if you approach it badly. I also run AI training for teams: what the technology can and cannot do, how to use it safely, and where the gains sit in your own work.
View this service →GDPR & privacy in order
Mapping what happens to personal data and delivering the documents you need to be able to show: a record of processing activities, a DPIA where one is required, processor agreements and a working method for data breaches and data subject requests.
View this service →EU AI Act: from scan to dossier
For anyone using AI or shipping AI inside their own product. We determine per system which risk category it falls into, which role you hold and what that means in obligations. Then we build the dossier that goes with it.
View this service →European software regulation
GDPR and the AI Act are not the only laws that touch your software. Depending on what you build and for whom, NIS2, the Cyber Resilience Act, the accessibility directives, the Data Act or DORA apply too. I work out which ones apply to you and what has to happen next.
View this service →Penetration testing and security testing
I attack your own software with your written permission, looking for what an attacker would find: logging in without the right password, reaching another customer's data, changing an amount in an order. Whatever works, you get on paper with the evidence attached and with the check that proves later on that it is really closed.
View this service →Ready to see what's being left on the table?
Book a free thirty-minute call. You'll get an honest answer, even when that answer is “don't do this yet”.
Book your free intro call → Free · 30 minutes · no obligations