All partners are trained in a natural science as well as in computing. That is the reason we can take on some projects others can't.
Between natural science
and software engineering
Two kinds of supplier,
one wall
Software houses build clean systems once the subject matter was explained to them. Not building on own domain knowledge, they deliver what was asked, but will find the gaps the specification left too late.
Domain specialists know the subject but write software that starts as a script and ends as a script: no tests, no interfaces, and nobody who can run it once the project is over.
We sit in between
We speak your specialists' language and still deliver software to ordinary engineering standards: versioned, tested, containerised, documented and ready to hand over.
We won't need a document to understand your domain, and we won't leave you with a script only its author can operate, either.
Partners
Consulting engineers in software, data and cloud engineering.
Dr. Simon Stier
Managing Partner, IT and materials engineer
Dr. Lukas Gold
Partner, IT and physics engineer
Dr. Matthias Albert Popp
Partner, IT and physics engineer
Dr. Simon Feiler
Partner, IT and physics engineer
Andreas Räder, M.Sc. B.Eng.
Partner, IT and process engineer
How we work
Three principles we apply to every engagement.
Most data projects do not fail on technology. They fail because the same quantity means three different things in three systems. We settle that first.
We build one process completely, instead of drafting components. With that base, any extension has predictable cost.
Documentation, tests and onboarding belong to the engagement, not to a follow-up invoice.
We build systems that outlive our involvement. Every value stays traceable to its origin and derivation.
For a first shape of the work,
a conversation is usually enough.
Tell us about the actual case.