Picking the process
We watch how a department really works and look for gestures that repeat, such as retyping into the sales system the orders that trade customers send as PDF files or spreadsheets.
Service · Artificial intelligence
AI implementation
We open with a plain question: which job do your people redo thirty times a day, and does that job leave a trace anywhere, in a shared mailbox, in Sage, in Odoo or in your support tickets? Without repetition and without history you end up with a pleasant demonstration that nobody mentions six weeks later. With both present there is usually working time to win back, and the pilot is what tells you how much.
1 process
to open the pilot
Before and after
time and accuracy recorded
EU region
for confidential material
Sign-off
a person approves each output
Where this service reaches
Projects that pay for themselves are rarely spectacular. Here is what a typical rollout covers, from picking the target to the team accepting the result.
Looking at the data
Are there examples from recent months, and can they be used? A hundred orders in five different layouts make good material; four emails do not.
Pilot with a threshold
A single scenario, a small group of users and a target agreed in advance: how many lines recognised without correction, how many minutes saved per document.
Integration
The output appears where the person already works: a draft entry in the accounting software, a note on the ticket, a prepared reply in Outlook or a message in a Teams channel.
Human control
While accuracy stays short of the threshold, every output goes past a reviewer. How much human oversight you keep is also one of the points the AI Act invites you to document with your counsel.
GDPR and records
As soon as personal data is involved: a processing agreement with the vendor, an entry in your record of processing activities and, where the case calls for it, an impact assessment prepared with your DPO.
The way an engagement runs
How long it takes from first call to decision depends on the process and on the state of the data. Everything runs remotely, and the next move follows the pilot figures rather than an impression.
01
Counting the work
We talk to the people who do the job and measure how much time each candidate for automation eats today.
02
A single scenario
We keep one process with a clear measure. Running three pilots side by side is the surest way to get no clean answer from any of them.
03
Working in parallel
For the first days the tool only suggests while the person carries on as before. We compare the two outputs and rework the instructions.
04
Widening
Once the numbers confirm the gain, the tool opens to the whole department, quality monitoring goes in and the documentation is handed over.
Clean data gets you halfway; the other half is whether the team trusts the tool. Anyone who doubts the output quietly returns to typing, because correcting a machine feels worse than doing the job yourself. That is why the future users sit in the pilot from the first morning: they report every mistake and they see their remarks change the behaviour of the system the following week.
Questions and answers
Usually yes. Sage, Cegid, EBP, Odoo and Business Central expose interfaces or import routines, and at the start we check what your particular version and support contract actually allow. When the software is old and closed, we go through an intermediate step: an import file that a person approves with one click, which keeps the saving without anyone touching the core system.
Say precisely what changes. Retyping and sorting go away; judgement, arbitration and customer contact stay. We promise no headcount reduction, because in practice the gain turns into time returned to work that had been piling up. Bringing the people concerned into the pilot settles the worry faster than any presentation ever does.
Two options, chosen before the start so that nobody is left alone with the tool. Either we keep it under a managed contract and watch consumption costs, accuracy and vendor changes, or you receive the full documentation and your own IT staff take it over.
A pilot on one process is quoted as a fixed price, typically a few weeks of work, or at EUR 95/hour excl. VAT with an agreed ceiling. What follows depends on the result, and model consumption is estimated before we begin. If the pilot fails to confirm the saving, closing the project is more honest than extending it out of habit.
Let us find a process worth automating
Tell us where your team loses the most time to repetitive work. We will look at the available data and propose a pilot scenario.
When we are around
Weekdays, 8:00 to 18:00 CET; answers land inside one working day
Weekdays, 8:00 to 18:00 CET; answers land inside one working day
Talking it through
A call on Teams or Google Meet, whenever writing is not enough
A call on Teams or Google Meet, whenever writing is not enough
Message received
An answer follows inside one working day. Report an outage that is stopping people working and it moves ahead of everything else.
- Anything unclear gets asked. Where a figure needs detail we do not have, expect an e-mail or an offer of a short call on Teams or Google Meet.
- A proposal follows. What is covered, the figure in euros excluding VAT, and a start date that will hold. Nothing hides beneath an asterisk.
- Then it is your call. The proposal sits in your inbox for as long as you need. Query any line of it, and decide once you are satisfied.