1
Start
Weeks 1 to 4. One week on one process, for example a drawing or a week of work orders, to show the first module and its price. The first look is free, then a fixed price.
The process first, then the software.
We do not start with code. First we look broadly at where the most manual work sits, then we choose one process together and work it out with the people who do the work. Then we build one module for a fixed price. After every step you decide whether we go on.
How we work
From working session to tested software
You bring the knowledge, we build the software with it. The people who do the work review the description of their work. A change to it only goes through once they agree.
- Start
- Tailor
- Run with us
- Hand over
Step 1 of 8, Start
Free scan
We look broadly at processes, IT, data and AI. We speak to people in each department, spend time on the floor and map opportunities and bottlenecks.
Outcome
An opportunity map with value, feasibility and advice on the first step.
Alongside the scan
Make your people co-owners of the AI transition.
In sessions with management and teams, your people learn to spot opportunities and experiment responsibly. Where it fits, they also build agents themselves.
The working sessions
The product feels as if your people built it themselves.
In five sessions we capture how the work runs now, how it can improve and what the software must do. Everything is recorded and transcribed, so your input is not lost.
01 · Magic wand
How would it work in an ideal world?
02 · Value
What does it return in time, quality and money?
03 · Integration
Which systems does it need to talk to?
04 · Design
What does the work look like per role?
05 · Validation
Does it work for the people who use it?
How we build
AI agents build, product engineers steer.
The agents work with three sources: what we gather in your organisation, the sector ontology and our blueprints. Tests, architectural guidelines and reviews check every step.
After the first module
We stay until it works, and after that for as long as it is useful to you.
After the build come improvement, data migration, adoption and management. You decide after every phase whether we continue. If you want to take it over, we plan the handover around your team.
Questions answered up front
Can you understand code written by AI?
What the software must do, we set down first in a specification that you review. We write tests for it, and only then comes the code. An engineer reviews every change before it goes live. We deliver tests, runbooks and documentation, so that another party could take it over.
Will this be our fifth system?
No. What we build works beside the systems you already have, through standard integrations, and you decide what gets replaced. That can be nothing. We start with one module.
Why not a standard package?
If your process fits a package, that is often a good choice. We are for work that does not fit: your own way of working, knowledge in Excel and mailboxes, or a package that assumes a process you do not have.
What is already built?
Three blueprints, in a fixed chain from drawing to work order. Technical Schema Mapping is live at a Dutch energy company. Asset registration and field service are working blueprints, ready to demo. More modules follow.
What happens to our data?
Your drawings, work orders and measurement data stay in your own cloud environment in the EU, or we host them for you in the EU. The AI models store nothing and do not train on it. What we send to an AI model, and how long it is kept, we agree in writing beforehand. Nothing we build sends commands to your installations. Book a demo.
Will we be locked in?
No, and it is in the contract. You can stop after any module and keep what is built. The code and the data are yours from day one. You get a perpetual licence on the framework and the sector ontology, which stays valid if the collaboration ends.
What does it cost, in money and time?
A fixed price per module, no hourly rate, and for management a yearly subscription with unlimited users. The first look at one process is free. We discuss the amounts once it is clear which module you need first. In time we ask for a sponsor who decides, and during tailoring two hours a week from one expert.
The route and what you pay
2
Tailor
The first quarter. The module is fitted to how you work, connected to your systems, and your people are trained. A fixed price per module.
3
Run with us
As long as it helps. We manage, fix and improve, for a yearly subscription with unlimited users. AI agents that watch the operation are an option.
4
Hand over
Only if you want it. Your team takes over step by step, with us as tech partner. A fixed price, only if you choose it.
What you get
Software that is tested beforehand, at a fixed price per module.
Working software
We deliver it module by module, fitted to how you work and running on your own data.
Tests and documentation
Tests first, then the code. You can always read back what was agreed.
Adoption as a phase of its own
Key users take part from week one. We stay until everyone really uses it.
No lock-in
The code is yours. You can stop after any module.
If your work does not fit a package, we build the software that is missing.
- A first module within weeks
- You speak directly with the people who build
- A fixed price per module, no hourly rate