An engineering company from Cologne.
Built for the shop floor.
Around 50 people who bring AI where it rarely arrives: into the plant. Measured on site, with numbers you can check. We started as software engineers, which is why our answer to most questions is to build something small and measure it rather than to write a strategy.
Three commitments we do not trade away.
A number before an invoice
Every engagement starts with what the situation costs today. If we cannot agree on that figure with you, there is nothing to measure afterwards and the project has no way to end well.
We say no in the call
Roughly one in five assessments ends with us advising against a build, usually because the data is not there yet or the bottleneck is a process rather than a tool. Saying it early costs us a project and keeps the reference.
The team keeps the system
We hand over documentation, the model behind the decisions and the people trained to run it. An engagement that leaves a dependency behind has failed, whatever the metrics said.
The people on the call are the people on the project.
No account layer between you and the engineers. The person who scopes your pilot is one of the people who will build it.
Cologne, and close enough to the plant to walk in.
Most of our clients are within a few hours by train, which matters more than it sounds. Industrial projects are decided in the hall, next to the machine, by someone who wants to show you the problem rather than describe it. Being able to be there the same week is part of why the pilots work.
For clients further out, including the UK and the US, we run the same model with two on-site weeks bracketing a remote middle. The measurement week is always on site.
“Measured. Built. Proven.”
The three words on the bottom of every page we publish, in that order deliberatelyCome and ask us something difficult.
Thirty minutes with someone from the team. Honest answers about the work, the stack and where we would not be a good fit.