Deep-tech doesn't fail at the technology. It stalls when complexity compounds faster than the coordination and trust built to absorb it. CompoundWorks exists for that exact moment.
It shows up as headcount growing faster than output. Pilots that impress but don't extend. The same integration work, rebuilt for every new customer. None of that is a failure of effort — it's a maturity gap, and it's diagnosable.
Some technologies grow in parallel. Others start to compound — and Physical AI, industrial systems, and defence & dual-use are exactly where that's happening right now. What happens next is where most ventures stall.
A new generation of deep-tech is being built at three convergence points: Physical AI, where perception, simulation and autonomy converge into systems that sense and act; Industrial Systems, where XR, digital twins and AI become the operational layer of industry; and Defence & Dual-Use, where commercial deep-tech faces its most structurally complex scaling transition.
Between a system that works under controlled conditions and one that absorbs real multi-vendor, multi-site, multi-institution complexity. Architecture built for demos. Governance that breaks when a second organisation enters. Organisations configured to build, not operate at scale. Invisible in the pilot. Structural at the second integration.
Read the full paperThis is also where many of these companies fail to scale. The technologies compound. The organisations, architectures and commercial models built around them often do not. The technology works, the first customers are real — but the business stops compounding when complexity outpaces the architectural maturity and decision systems of the organisation.
Three coupled dimensions — Technology, Organisation, Trust — across four maturity levels. Read the framework vertically: the lagging dimension is the binding constraint. Naming it is the first act of diagnosis.
| L1 · Initial | L2 · Managed | L3 · Defined | L4 · Adaptive | |
|---|---|---|---|---|
| Technology | Prototype-centric. Technical debt accumulates invisibly. | Technical coupling. Architecture limits scale. | Architectural runway. Designed for growth. Parallelism is safe. | Continuously optimised. Open interoperability. Scales without redesign. |
| Organisation | Decisions through founders. Heroic coordination. | Formal process, implicit decisions. Delivery depends on heroism. | Delivery without heroism. Coordination at scale. Explicit decision systems. | Adaptive governance. Scales without refounding. Leadership multiplies. |
| Trust | Personal trust. Fragile at distance. | Trust in people, not process. Strong internally, opaque externally. | Structural, evidence-based. Selling reliability, not potential. | Trust as system property. Self-reinforcing. Survives change. |
A client enters through one of two doors, depending on whether the question is direction or delivery. Either path, followed honestly, walks into the other's territory — which is why the same engagement usually ends up needing both faces.
Your technology is proven, your first customers are real — but the system around it won't scale. Or an institutional project didn't extend and you don't fully know why. The question is delivery, not direction.
The question isn't repair — it's direction. Where should the R&D roadmap go? How do you architect the product for where convergence is heading, not just where it already is?
Systems rigor, platform thinking, and business execution — together, not separately.
That mix of building, founding, and scaling forged two ways of reading the same experience — not by design, but because the work itself kept demanding both.
The Operator is the constant: every stage meant building something from scratch — a venture, an engineering organisation, a platform — and being personally accountable when it didn't hold under pressure. The Architect surfaces at the moments of new architecture: combining HLA and DDS into a data-centric, services-oriented distributed architecture at Simware, then convergence across AI, digital twins, XR and IoT at TMRW. That's the coin: one face built in every stage, the other forged at the architecture moments.
Narrow is replaceable: a specialist can be hired for any single piece of this. Compounded across four companies and 25 years is not — which is exactly the value a narrower consultant or advisor can't replicate. CompoundWorks is the evidence that compound works.
jose.lopez@compoundworks.ioFounding NADS in a regulated, fiercely competitive defence market meant building delivery excellence at the intersection of discipline and agility — the root of what the practice now calls Hybrid Agile — and building trust runway with partners like the Spanish MoD, US Navy, NATO, Airbus, Thales, Lockheed Martin and Navantia, delivering mission-critical solutions on time and to standard.
Turning a reusable tech-stack into a standalone commercial product meant disrupting a military simulation industry still selling bespoke systems one customer at a time — and forcing the real question early: distributed simulation, open architectures and interoperability were no longer optional. The answer became a paradigm of its own: the Internet of Simulations.
Building new categories of industrial metaverse and immersive collaboration — at the intersection of digital twins, simulations, XR, AI and IoT — made the Compound Innovation Gap visible firsthand: coherence drives adoption, then fractures the moment it has to hold at scale.
Rolling out digital twin adoption across automotive and industrial corporates — BMW, Stadler, Hella, Porsche — confirmed the Compound Innovation Gap pattern from the customer's side: digital twins compound value only when integrated with the operational IT stack — PLM, ERP, CAD/CAE, AI — and scale as engineering tools only when the organisation using them matures in parallel.
Posts and short essays as the practice develops — the same arguments worked out in public, before they're settled enough for this site.
The visible problem is rarely the real constraint. Diagnosis has to come before intervention — until you find where the system is losing compounding power, even good people end up solving the wrong thing.
Read on LinkedInMost teams using AI agents feel faster, but throughput hasn't improved. That's not an AI problem — it's a system maturity problem, and it's exactly where Hybrid Agile gets more relevant, not less.
Read on LinkedInValue emerges from integrating sensing, spatial abstraction, cognition, compute and governance into one coherent stack. Most failures don't happen inside the model — they happen at the interfaces.
Read on LinkedInIf it's the technology — where convergence is heading and how to architect for it — the Compound Innovation Gap explains where most ventures get the architecture wrong, before it's expensive to fix. If it's the system, the Scaling System Maturity Framework locates exactly where you are and what breaks next.