The advisor
Amadeus Lederle
Technology executive working where software, industrial operations, AI and enterprise strategy meet. Enterprise systems, manufacturing environments, AI, cybersecurity, software architecture, process design, automation and technology strategy — and the economics that decide which of them matter.
That background matters less as a résumé than as a vantage point. Industrial and enterprise technology is where the distance between a demonstration and a system somebody depends on is widest, and where the difference between what is technically possible and what is commercially defensible is easiest to see.
It is also where the two halves of a technology decision are hardest to separate: what the technology can do, and what the organisation around it can actually run.
The work turns increasingly on a single question.
When creating technology stops being the hard part, what decides whether a company is worth more in five years than it is today?
The answer is not the same for every company, which is why the work is advisory rather than a product. It runs through three channels: technology and AI due diligence for investors and acquirers, board advisory for a deliberately small number of companies, and operating-model transformation where the opportunity is clear and the organisation is stuck.
01
Built in the real world.
Technology behaves differently when a mistake reaches production, customers, compliance or a shipment date.
Most technology opinion is formed in environments where being wrong is cheap. A demonstration that fails is embarrassing; a planning system that is wrong stops a line, and a quality decision that is wrong reaches a customer.
Work in industrial and enterprise environments enforces a particular discipline. Systems run for years rather than quarters. They are used by people who did not choose them and cannot avoid them. They connect to physical processes with their own tolerances, and to organisations where the workaround is often the real process. Nothing about that is romantic, and all of it is informative.
It leads to a specific view of what technology is for. Technology is the operating system of a company, not a set of products it owns. Which is why an argument about architecture is usually an argument about the organisation, and why an AI strategy that ignores how work is actually divided will produce pilots and not results.
02
Positions
Views held consistently enough to be argued with.
Technical quality and defensibility are different questions.
Well-built software is easier to maintain, not harder to replace. Diligence that conflates the two produces confident answers to the wrong question.
A productivity gain everyone receives is not a strategy.
If a capability arrives on the same schedule for every competitor, it belongs in the cost baseline, not in the investment case.
Abundant code does not make reliable systems abundant.
The scarce part of a mission-critical system was never the code. It is the installed base, the process integration, the operational history and the fact that someone is answerable for it.
Cheap creation is an opportunity; unmanaged dependency is the risk.
Companies should build aggressively where it pays. They should also know which of the things they built the business now depends on, and classify accordingly.
Most disruption arguments are timing arguments in disguise.
Whether a category is exposed is usually easy. When it is exposed is the hard part, and it is where nearly all the disagreement actually lives.
Boards are rarely underinformed. They are under-contradicted.
The material is generally adequate. What is missing is someone in the room whose position does not improve if the proposal is approved.
Overestimating disruption is the more expensive error in a good business.
Panic destroys durable advantages faster than competitors do. The point of examining exposure honestly is to know which parts are not exposed.
03
Areas of work
The domains the judgment is drawn from.
- Enterprise systems
- Manufacturing and industrial environments
- AI strategy and AI-driven disruption
- Cybersecurity
- Software architecture
- Process design and operating models
- Automation and robotics evaluation
- Technology strategy
- Technology due diligence
Independence and conflicts
Engagements are accepted only after a conflict review. A mandate must not conflict with existing executive responsibilities, commercial interests or confidentiality obligations, and any engagement that would is declined.
Everything written and said here is a personal professional view. It does not represent any employer, client, investor or portfolio company, and it never draws on confidential information or confidential examples.
Organisation
Amadeus Lederle is managing director of IEX Labs UG (haftungsbeschränkt), registered at Amtsgericht Deggendorf under HRB 6472 and seated in Regen, Bavaria. Advisory work is carried out through that entity. His personal profile — career, published work and current executive role — is at amadeus-lederle.de.
Bring a decision worth arguing about.
Requests are reviewed personally. The relevant question is whether an independent technology judgment can change what happens next.