Understanding what happens after delivery.

In 1999, five researchers saw something most people had not yet understood: products were about to change. Engines, vehicles and machines would no longer be only mechanics and electronics – they would be governed by software, talk to their surroundings, and be updated over time.

It began with telematics and connected products built around Volvo Penta's marine engines. Most people saw engines. Diadrom saw data – and a harder problem behind it: not how to build software, but how to understand, control and maintain complex systems once they have left the factory.

That insight carried us into the automotive aftermarket – into diagnostics, embedded software, traceability, configuration and lifecycle management. We grew, and in 2007 we became a publicly listed company. When our software reached serial-production vehicles, the stakes changed: no longer single projects, but thousands – then hundreds of thousands – of systems that have to work every day, for years.

Then came defence. In 2012 we delivered a ruggedised flight recorder for a military platform – still in service today. Defence had the same questions we had spent years on: which software is actually installed? Is the right version in the right place? How do you manage change across a lifecycle measured in decades? The knowledge we had built in automotive proved directly relevant where systems cannot fail.

Many consultancies sell people. We have spent more than two decades doing the opposite – capturing experience so it does not leave when a project ends or a person moves on.

That experience lives in our own products, platforms, modules, methods and training programmes. Every new specialist builds on the generation before. It makes us less a consultancy and more a specialist and knowledge company in complex, software-intensive systems.