Build the Layer Above the Hardware

Intuitive disclosed on May 22 that it is shipping more than 100 updates and user-experience improvements to da Vinci 5, with measured US launches starting in June, per MedTech Dive. Medtronic announced two days earlier that it is building a European software development hub in Galway, sized to add 85 jobs initially and stretch the engineering organization across a third time zone, per The Irish Times and MassDevice. Sentante won a CE mark in the same week for an endovascular robotic platform built around a remote-network architecture. Three different decisions, one underlying read. The defensible business in 2026 is built on the layer above the hardware. Understanding the market is only part of the job. Making money, building systems, and getting to where you want to go — those are the problems The Build exists to help you think through, and the structural question that runs through all three stories is the one most founders defer until the hardware ships. What does the layer above your hardware actually look like, and is the organization behind it sized for the cadence the market is now ranking you on?

Most Founders Defer the Layer-Above Decision Until After Launch

The default first-time founder treats the layer above the hardware as a post-launch problem. The build-phase logic is that the device, the platform, or the asset is the deliverable that has to clear regulatory, ship reliably, and produce reference customers, and the software, data, or network architecture can be added later once the hardware is in the field. The cost of that logic is that the strategic acquirers and the reference customers have already decided what they are pricing by the time the company gets around to thinking about the layer above. Intuitive’s 100-update disclosure is not a feature announcement. It is a signal to the buy-side that the engineering organization behind the platform was sized for the cadence years ago, and the comparable any challenger is going to be priced against is the engineering organization, not the robot.

The version of the business that compounds through that environment is the one that decided what the layer above the hardware looked like as a primary architectural choice, before the engineering plan for the hardware was committed. The work is to map what update cadence, data flywheel, or network architecture the category is going to require in the first twelve to twenty-four months after launch, decide which of those layers the company is going to own, and size the engineering organization to deliver against the chosen layer from day one. The discipline is real at the build-phase stage. The hardware milestones look the same on the operating plan whether the layer-above decision was made or not, so the founder who does the work and the founder who skips it look identical on the burn chart for the first two years. The difference shows up in the third year, when the installed base is large enough to want capability extensions and the engineering organization is either staffed to ship them or not.

The surgical-robotics category in May 2026 is the visible version of the same dynamic. Intuitive sized the engineering organization for cadence and is now showing what the cadence looks like in operation. Medtronic is sizing the engineering organization to catch the cadence, with Galway as the third time zone. Sentante is sizing the network architecture to deliver value the bedside-only platforms cannot reach. Three different layer-above decisions, all made deliberately, all visible to the buy-side, and all defining the category at a level the hardware contest by itself can no longer reach.

Three Categories of Layer-Above Decision Worth Studying

The first category is the update-cadence layer. Intuitive’s da Vinci 5 disclosure is the example. The company that owns the largest installed base extends the moat by shipping meaningful capability extensions on a sustained cadence, and the engineering organization behind the cadence becomes the asset the buy-side is actually pricing. The same logic applies to defense hardware founders shipping autonomy updates against deployed platforms, to industrial robotics founders shipping optimization software against installed factory floors, and to climate hardware founders shipping control-system updates against deployed assets.

The second category is the engineering-organization layer. Medtronic’s Galway hub is the example. The company that is competing against an incumbent with a stronger update cadence builds the time-zone-spanning software organization that can credibly match the cadence over time. The slot decision is about which engineering organizational shape can ship continuous updates at scale against a regulated installed base. The same logic applies to climate hardware founders building grid-integration software organizations, to physical AI founders building model-update organizations, and to diagnostics founders building bioinformatics organizations behind the assay.

The third category is the network-architecture layer. Sentante’s CE mark is the example. The company that cannot win the head-to-head hardware contest picks a slot where the value is delivered through the network rather than through the device, and the architectural moat is the secure remote workflow that the bedside-only platforms cannot replicate. The same logic applies to defense hardware founders building cross-platform mesh architectures, to industrial founders building distributed-asset orchestration layers, and to climate hardware founders building grid-edge coordination stacks.