Automation · AI · Communications
I automate the repetitive work in sales, service and communications — using artificial intelligence where it measurably saves time. In production in weeks, not quarters.
01Services
No innovation theatre. Every project moves a number you already measure.
01Automation
Repetitive work in sales, service and administration — automated end to end, handing back to a person exactly where judgement is actually required.
02Artificial intelligence
Language models applied where they demonstrably save time — as part of the working process, not as a demo for the board.
03Enterprise communications
Internal and external communication made structured, traceable and automated — from a multi-country contact centre through to the channels your company already runs on.
02How it works
Every stage is time-boxed. If the pilot saves nothing, we stop there — that is the point of splitting it up.
We look at the process as it actually runs, not as it is documented. You end up with effort, saving potential and risk per step — and a straight recommendation about what is worth doing and what is not.
One part of the process goes live, with real data and real users. Fixed price, so you know the downside before you commit.
Extension to the full process, including training, documentation and handover to your IT team. After this you can run it yourselves.
Monitoring, adaptation to new cases and regular review — or you take it over entirely. No lock-in, no forced maintenance contract.
03Work
Each one with the problem, the approach, and a number.
Group compliance, construction chemicals
2026New EU packaging regulation required declarations of conformity in 12 languages for around 900 packaging materials. Instead of filling them in one by one, a pipeline generates and files them in a single run.
Customer service, construction chemicals
2026Callers say what they need in their own words instead of tapping through three menu levels. The language model is never allowed to name a destination — it picks from a list, and the phone system dials.
Service desk IT, building materials
2026Telephony logs are collected centrally from every workstation, parsed, and explained by a language model. The bill scales with the number of distinct problems, not with volume.
04About
For more than twenty years I have worked where process meets system — and I have deliberately never picked a side. I can walk a quoting workflow through with the sales team and then build the integration for it myself. The systems have changed names several times in that period. The problems behind them have not.
What I have learned along the way: automation rarely fails on the technology. It fails because nobody knows the whole process. There is almost always a step somebody added years ago for a good reason — and nobody remembers the reason. Automate that step without understanding it and you have automated a mistake, and made it faster.
So I start with the process, not the tool. Before anything gets built, it has to be clear what the workflow actually does, where it stalls, and what happens when the automation gets it wrong. That is unglamorous and takes about a week — and it is the difference between a system that lands in daily use and one people quietly work around.
05FAQ
The pilot runs at a fixed price, so you know the downside before you commit. Everything after that is billed by effort or as a package — you get the estimate before the work starts, not after.
Processing inside the EU wherever possible, under a data processing agreement. Where language models are involved, we agree in writing beforehand which data they see and which they do not. If a process touches personal data, that gets settled before a line of code is written.
Usually yes — both are the most common starting point in this market. During the analysis week we check which interfaces actually exist rather than promising it up front.
Two to three weeks to a working pilot. Not to a concept — to real cases running through it.
No. Documentation, source code and handover to your IT team are part of the rollout. Ongoing support is an offer, not a condition.
That is the normal case, and exactly what the analysis week is for. You come out of it knowing which three processes are worth doing, and in what order.
06Contact
30 minutes, free, no sales pitch. You describe what is costing you time — I tell you honestly whether automation is worth it.