The quiet renaissance in surgical robotics

Beyond the da Vinci moat

The next wave of surgical robots are not trying to be platforms. They are single-procedure systems — spine, ENT, ophthalmic, endovascular — with capex under a million dollars and a per-procedure cost structure that finally works for ambulatory surgery centers.

The AI layer

Where the last generation was mechanically differentiated, this generation is software-differentiated. Real-time tissue recognition, automated safety envelopes, and post-op analytics are the features surgeons now ask about first.

The ASC channel

Ambulatory surgery centers, not hospitals, are the wedge. They buy faster, care about throughput obsessively, and are willing to standardize on a single robot per procedure. Founders should build for this channel first.

The quality system is a product

Founders who treat the QMS as a compliance obligation build slower and stall harder than founders who treat it as a product for their internal engineering org. A well-designed QMS lets a small team run parallel design changes, chase multiple indications, and keep the design history file coherent through three CEO memos and two contract manufacturers.

The teams we admire hired their first quality engineer earlier than felt reasonable and gave them a seat at the roadmap table, not a seat at the audit table.

Manufacturing is the second product

The instinct to defer manufacturing until after clearance is understandable and, in most cases, wrong. Design-for-manufacturability decisions made in the year before first clearance define the gross margin of the business for the following five years. Founders who bring a manufacturing engineer into the core team early ship a device that a CM can actually build without heroics.

Every hour spent renegotiating tolerances after clearance costs three hours of runway.

The field notes

Across the last quarter we sat in on operating reviews with fourteen portfolio and prospective teams working adjacent problems. Three patterns kept surfacing. First, the teams that moved fastest were not the ones with the deepest research bench — they were the ones with the shortest feedback loop between a real clinical user and the roadmap. Second, the winners had unusually opinionated evaluation harnesses. Third, none of them treated regulatory strategy as a phase; they treated it as a running conversation with the product.

What follows is a longer look at what we saw, what we think it implies for founders, and where we are actively deploying capital and studio effort in the coming twelve months.

A note to founders

If you are early on this problem, the most useful thing you can do in the next ninety days is get a real clinical user to use your product on real data every week and to write down what breaks. Not a design partner. Not a friendly advisor. A user. The founders who do this compress two years of learning into two quarters.

If you are further along, the highest-leverage investment is almost always in evaluation and in the human workflow around the model — not in the model itself. Capability is table stakes. Trustworthy capability is the moat.

As always, we are happy to be an early call. The teams we back tend to reach out before they think they are ready.