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
When the data is not there yet or the bottleneck sits in a process, we advise against a build. 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.
From Cologne, much of the industrial mid-market is within reach 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. Being able to come by in person is part of how our pilots work.
For clients further out, including the UK and the US, we run the same model with on-site visits at the start and for the measurement, and remote work in between.
“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.
From bottleneck to a measured number, on your own data.
Tell us the process that eats your time. We build on your real data, measure with the method agreed before the start, and if the numbers do not carry it, we say so.
Request the callRequest the callAnswers with the source attached.
Industrial knowledge, readable by the people who need it: in the hall, on the road, on the night shift.
See how it works