SS Innovations used the Global Multi-Specialty Robotic Surgery Conference in New Delhi this week to show drone-deployed battlefield surgery, a zero-footprint mobile operating room, and an AI-integrated humanoid robot alongside its commercial system. If you are building a company in surgical robotics or the enabling technology that runs on these platforms, the most important question SMRSC 2026 raises is not which concept will reach market first. It is whether the thing you are building right now is defined around a stable integration point or a temporary one.
If You Are Building a Company in This Environment
The surgical robotics market has operated for most of its commercial history on a simple assumption: the reference platform is a multi-arm, fixed-installation system in a hospital operating room, and the companies building for that market are building for that setting. That assumption has been unwinding for several years, and SMRSC 2026 makes it visible in concentrated form.
SS Innovations showed four concepts alongside a system that is commercially operating and running live telesurgeries. The range, from drone-deployed trauma surgery to a zero-footprint mobile OR, is not marketing speculation. It is a company with existing regulatory clearance, an installed base, and a clinical track record signaling where it believes the care delivery environment is heading. That matters for founders whether or not any of those specific concepts reach commercial reality on a particular timeline.
Founders Who Finish is built around a set of questions that do not change when the technology environment is volatile. What they require is more precision, not less. When the platform you are building for is itself still in motion, finishing something specific inside the current environment is not an obstacle to future optionality. It is the only way to have any.
The Platform Dependency Problem That Most Founders Are Carrying
The standard approach to building for the surgical robotics market involves picking a platform, understanding its integration architecture, and designing a product that works well in that workflow. That approach has produced real companies with real commercial traction. It also carries a dependency risk that has become more significant as the number of platforms in active commercial development has grown and as the form factor question has opened up.
Platform dependency takes two forms. The first is a direct technical dependency: your product requires a specific interface, communication protocol, or physical connection point that only exists on one platform family. The second is a workflow dependency: your product is designed for a care setting, procedural cadence, or clinical environment that is associated with a specific platform type. Both forms create fragility when the platform landscape is actively diversifying.
Founders Who Finish addresses this directly in its discussion of what a real finish looks like at the product stage. The question is not whether your product works on today’s leading platform. It is whether the specific clinical problem you are solving exists across platform environments, and whether the evidence you are building is attached to the problem or to the platform. Evidence attached to the problem travels. Evidence attached to the platform does not.
What Finishing Looks Like When the Roadmap Has Not Settled
The companies that survive form-factor transitions in device markets tend to share a pattern. They finished something specific before the transition occurred. They built a complete commercial asset, not a promising integration, in a defined clinical segment with real accounts and real outcomes data. When the transition happened, they had something portable: evidence of clinical value that existed independent of the platform that first made it visible.
AcuityMD’s $80 million Series C, announced this week, is a different kind of signal about what finishing looks like in MedTech. AcuityMD spent years building infrastructure to solve a specific commercial intelligence problem before the market recognized AI-powered commercial intelligence as a category. The $955 million valuation reflects the company having finished something: a complete data platform with real customers and real verified outcomes, not a concept that depended on the commercial landscape looking a particular way. The AI infrastructure question was secondary. The finished commercial asset was primary.
That pattern repeats across device categories. The companies that get acquired at premium valuations, that hold their commercial position through technology transitions, that build lasting institutional relationships at reference accounts, are consistently the ones that finished specific things before the environment rewarded them for doing so.
What the Execution Framework Looks Like When Platforms Are in Motion
The five-question framework in Founders Who Finish does not assume a stable platform environment. It was designed for the reality that founders in regulated markets face: the clinical evidence requirements, the regulatory pathway, the reimbursement strategy, and the platform integration all have to be completed under conditions of uncertainty that do not pause while you figure out the answer.
Question 1
What are you actually finishing?
In a volatile platform environment, the definition of done tends to drift toward platform-level completeness rather than clinical-problem completeness. Founders who finish keep the definition of done anchored to a specific clinical outcome in a specific patient population with specific evidence requirements, not to a specific platform version or integration state.
Question 2
Who decides you are done?
The stakeholder who validates your finish should be the clinical champion who cares about the problem you are solving, not the platform vendor who cares about the ecosystem. When your finish is defined by a clinical champion whose professional identity is attached to the outcome, not the tool, you have a finish that travels across platform generations.
Question 3
What does your evidence actually prove?
Evidence built around a platform-specific workflow proves that your product works with that platform. Evidence built around a clinical outcome proves that the problem is real and your solution addresses it. The second type of evidence is portable. The first is not. In a market where the platform roadmap is actively being rewritten, the distinction determines whether your first reference site has strategic value or just historical value.
Question 4
What does your path to reimbursement look like?
Reimbursement attached to a procedure code survives platform transitions. Reimbursement attached to a specific device or integration pathway may not. Founders building for surgical robotics adjacencies who are working through the reimbursement question early tend to discover this distinction before it becomes a crisis. Founders who defer the reimbursement question tend to discover it after.
Question 5
What does the finish line look like to an acquirer?
Strategic acquirers in surgical robotics are buying finished commercial assets, not platform integrations. The CathWorks acquisition last week is a recent example. Medtronic did not buy CathWorks because it ran on a particular imaging platform. It bought CathWorks because CathWorks had finished: cleared indication, reimbursement position, peer-reviewed outcomes data, and an account base. That finish existed independent of any platform dependency.
Founders Who Finish
The guide for founders building in regulated markets
The five-question framework for building medical device and surgical robotics companies that finish what they start, in the regulatory and clinical environment as it actually exists.
Get the Book