Intuitive Surgical disclosed on May 22 that it has more than 100 updates and user-experience improvements queued for the da Vinci 5 platform, with measured US launches starting in June and an international rollout to follow, per MedTech Dive. Medtronic announced two days earlier that it is opening a European software development hub in Galway, the company’s first European software team, sized to add 85 jobs initially and stretch the global engineering organization across a third time zone. Sentante won a CE mark in the same week for an endovascular robotic platform built around a remote-network architecture, positioning the device around procedures the bedside-only competitors cannot reach. Three different choices, three different organizational shapes behind them, and one shared structural read. The surgical-robotics company that finishes the build phase against an installed base is the one that decided what its software organization looked like before the robot was committed, not after. Founders who finish in regulated and capital-intensive hardware categories do the same thing in their own verticals, because the layer that decides whether the product compounds is now one level above the hardware.
If You Are Building a Company in This Environment
The default first-time hard-tech founder treats software as a feature of the device. The build-phase logic is that the robot, the platform, or the asset is the deliverable, and the software is the operating layer that makes the deliverable work. The engineering plan is sized around the hardware milestones. The team is sized around the hardware milestones. The fundraising story is sized around the hardware milestones. The software organization is a service function inside the engineering org chart that ships whatever the robot needs to run, with a roadmap that follows the hardware schedule rather than driving it. The cost of that logic shows up after the first commercial deployment, when the installed base starts asking for capability extensions the original software organization was not sized to ship.
The Intuitive disclosure is the visible version of what the alternative looks like. The May 22 update list covers remote operating-room camera, telepresence cursor and audio, mobile phone login with multifactor authentication, six new simulation exercises in SimNow 2, increased reusable instrument counts on five of six Force Feedback instruments, a digital intraoperative ruler queued for later this year, and surgeon-initiated tool eject from the console, per MedTech Dive. The list is the output of an engineering organization that was sized to ship at this cadence years before the May 22 announcement. The 10,000x compute increase the company describes on the da Vinci 5 versus the prior Xi platform is the visible architectural decision that made the cadence possible. The engineering organization behind it is the invisible one, and it is the one that determines whether the cadence continues or stalls. Founders who finish in surgical robotics and adjacent verticals make the engineering-organization decision early enough that the cadence is real by the time the first installed base is large enough to need it.
Medtronic’s Galway hub is the same decision, made in a different position in the category. The company is no longer trying to catch Intuitive on hardware. The Hugo system cleared the FDA, ran its first US cases earlier this year, and now sits in front of the question every challenger platform has to answer. Where does the next twelve months of update cadence come from? Medtronic is answering it by building a European software hub with explicit time-zone-spanning architecture. Galway hands work to India in the morning and to North America at the end of the day, which is what an installed-base software organization at scale actually looks like. The founder who is competing for the same buy-side comparable Medtronic is now defining needs to either match that organizational shape or accept that the company is going to be priced one rung below it when the comparable is read.
What the Three Surgical-Robotics Decisions Show
The Intuitive, Medtronic, and Sentante decisions are useful as a case study because each describes a different architectural posture inside the same category. Intuitive owns the installed-base update cadence because the hardware was sized for years of software extension and the engineering organization behind it was sized to ship at quarterly cadence into more than 1,400 systems. Medtronic is building the time-zone-spanning software hub that the challenger position requires, putting Galway in front of the next phase of the competition rather than chasing the hardware story alone. Sentante is taking the specialist-network position, picking a slot where the value the company captures is not robot performance but the ability to deliver a specialist across a network for thrombectomy and other endovascular procedures at hospitals without local capability. Three different surfaces, three different organizational answers, and the common thread is that each company decided what its software and network architecture looked like as the primary structural decision, not as a downstream feature of the hardware.
The Five Questions for the Software-Layer Decision
The five-question framework in Founders Who Finish reframes the operating plan when the defensible slot is one layer above the hardware. Each question maps to an architectural decision that has to be settled before the engineering plan is fixed, not after the first device or platform is committed.
Question 1
What are you actually finishing?
If the answer is a single FDA clearance or a single robot platform, you are finishing a product, not a business. The finished business is a defensible slot the strategic acquirer or the reference customer reads as something only your engineering organization can ship into the installed base on a sustained cadence. Founders who finish identify the slot at the software, data, or network layer and size the organization to deliver against it from the first hardware decision.
Question 2
Who decides you are done?
The FDA reviewer reads the device. The reference customer reads the update cadence. The payer reads the procedure economics that depend on what the software adds inside the workflow. The strategic acquirer reads the engineering organization behind the update cadence as the asset it is actually paying for. A finished hard-tech company in 2026 has to read convincingly to all four, and the software-layer decision is what makes that possible.
Question 3
What does your evidence actually prove?
The pivotal evidence has to do two things at once. The first is to clear the device against the regulatory pathway. The second is to prove that the software, data, or network architecture is the structural moat, not a downstream feature. Founders who finish design the pivotal to defend both layers, and they design the post-market evidence plan to keep producing data the installed base and the acquirer can both read as proof the cadence is real.
Question 4
What does your path to clearance, reimbursement, and commercial scale actually look like?
The path to clearance has to align with the software-update cadence the company intends to run, so the predetermined change control plan, the cybersecurity submission, and the post-market surveillance plan are sized for the cadence rather than for a single one-time clearance. The path to reimbursement has to fit inside the procedure codes the payer already pays for, including the workflow effects the software changes. The path to commercial scale has to be staffed by an organization that can ship against an installed base, not only land the first ten installs. Founders who finish put all four work streams against the same software-layer plan.
Question 5
What does the finish line look like to your buyer, your payer, and the investor pricing the round?
Strategic acquirers and growth investors pricing hard-tech in 2026 are reading the engineering organization behind the cadence, not the cadence itself. The slot the company picks at the software, data, or network layer is what determines whether the engineering organization reads as scarce and defensible or as a hardware vendor with a roadmap deck. Founders who finish make the engineering-organization decision early enough that the cadence is the asset the acquirer is actually pricing when the conversation begins.
Founders Who Finish
The guide for founders building in regulated and capital-intensive markets
The five-question framework for building medical device, diagnostics, AI SaMD, defense, climate, and other hard-tech companies that finish what they start, in the regulatory, capital, and operating environment as it actually exists.
Get the Book