Dassault’s 18% Drop Isn’t a Blip. It’s a Signal.
Automation scaled tasks. It didn’t scale understanding.
This week, Dassault Systèmes had its worst day in years. The stock dropped 18%.
Markets don’t move like that over nothing. This was not just earnings noise. It was a signal that something deeper is breaking in how the world thinks about product development and manufacturing software.
For decades, “automation” has been the north star for software in hardware organizations. Automate the CAD workflow. Automate PLM. Automate documentation. Automate approvals. Automate change management.
That playbook worked. Until it didn’t.
As hardware companies scale, two structural failures show up fast:
1) Context breaks across phases, teams, and products
Design lives in CAD. Decisions live in Slack. Constraints live in Jira. Requirements live in Confluence. Tribal knowledge lives in people’s heads. When something breaks, nobody has the full picture. See our deeper breakdown on why context fragmentation is killing velocity in modern hardware teams.
2) Coordination does not scale with complexity
Every new product line, supplier, compliance rule, and market adds dependencies. Humans do not scale across an exploding graph of decisions and handoffs. The result is predictable: more sync meetings, more process, slower iteration. We’ve written before about why meeting-heavy coordination is a tax on innovation.
Automation alone does not fix either of these problems. You can automate tasks all day. You cannot automate understanding.
The Shift: From Automation to Orchestration
At EverCurrent, we think the next wave of value creation in hardware software is not about doing the same workflows faster. It is about changing the structure of how work coordinates in the first place.
That means three things.
1) Orchestrating context and coordination
The right knowledge needs to reach the right person at the right time without adding process overhead. Not more dashboards. Not more tickets. Not more rituals. Real-time context that flows across tools and teams. We explore what “context orchestration” actually looks like in practice.
2) A second safety net through AI cross-checking
Modern hardware systems are too complex for any single human or team to fully reason about end-to-end risk. AI can act as an exhaustive cross-check layer. Not to replace engineers, but to bound risk across requirements, designs, compliance, and downstream impact.
3) Moving from sync meetings to traceable async decision-making
Most orgs confuse communication with coordination. Meetings move information. They do not create durable memory. Async, transparent decision trails do. When decisions are traceable, feedback loops close faster and organizations learn instead of relearn.
Why This Matters Now
The Dassault drop is not about one quarter. It reflects a broader tension: legacy platforms were built for a world where complexity grew slowly and workflows were relatively linear. That world is gone.
Hardware teams today are:
Shipping faster
Operating with more suppliers
Navigating tighter regulatory regimes
Building more software into physical products
Managing exponentially more cross-functional dependencies
You cannot process-manage your way out of this. The org either becomes context-aware by default, or it drowns in its own coordination overhead.
The Opportunity
The next generation of hardware organizations will not win by automating harder. They will win by staying lean as complexity explodes.
The real advantage is not speed alone. It is coherence at scale.
And that is the paradigm shift the market is starting to price in.
If you’re building or operating in hardware, this shift is already hitting you. The question is whether your tooling is helping you survive complexity or quietly compounding it.
So interesting! Wonderful insights.