Build
When it is not one flow but the company itself.
Past a certain point the question is no longer which flow gets automated, but how the company works as a whole. A single process is then not enough - several interlock, across departmental lines.
from €45,000 · after an audit only
Why this requires an audit first
A single process can be bounded: one purpose, a few systems, one department. A system spanning departments cannot. It touches responsibilities, approvals and data ownership, and every one of those questions has already been answered somewhere in the company - usually implicitly, and not identically everywhere.
Without that groundwork a quote would be a guess, and not by twenty per cent but by a multiple. That is why this stage only exists after an audit. It is not a sales mechanism: we would not sign such a quote ourselves.
What comes out of it is not a bigger process but something different: flows that interlock, with a shared data basis, shared permissions and operations that keep the whole in view.
What separates a system from a process
- Across departments
- Flows that cross lines of responsibility - sales to production, purchasing to accounting. That is exactly where the large losses of time sit.
- Roles and permissions
- Who may see what, who may trigger what, who signs off. This is not rebuilt but adopted - a system gets no more rights than the route it replaces.
- Its own infrastructure
- A dedicated environment rather than shared tooling, with its own logging and its own deletion policy. At this scale that is not optional.
- Purpose-built tools
- Where no interface exists, we build one. In a system that usually means several - and they belong to you afterwards.
- Operations for the whole
- Not five processes with five maintenance contracts, but one system with one contact.
Frequently asked
What does a cross-department AI system cost?
From €45,000. The reliable figure comes after the audit; at this scale a number without groundwork would be off by a multiple, not by twenty per cent.
Why can I not commission this without an audit?
Because we would have to guess. A system touches responsibilities and data ownership - that cannot be settled at a desk. We would not sign such a quote ourselves.
Can we start small and expand later?
That is the usual route and the better one. One process that runs convinces a company more than a plan covering ten - and the access established in the first project carries the ones that follow.
Who owns what gets built?
You do. Tools, integrations and documentation transfer to you with the project; you are not technically tied to us.
Tell us where your time goes.
In the audit we record the process, work out what is worth automating, and you get a plan with fixed prices - credited against the build if you go ahead.