Offer Digital Planning Without a Robot
How an implant manufacturer can offer modern CT-based digital surgical planning without a robot: license a vendor-neutral software layer, not hardware.
Key takeaways
A manufacturer does not need a robot to offer modern digital surgical planning. Robots bundle planning to sell hardware, but the planning value, the part surgeons actually use, is software: CT-based segmentation, alignment options, phenotyping, and sizing support. A vendor-neutral, implant-agnostic planning layer delivers that same value tied to your own catalog, at a fraction of the capital and lock-in of a robotics program. For an implant maker without a robot or an in-house planner, licensing this software is the lightest credible path to a digital offering that travels with its implants. Salnus builds exactly this kind of vendor-neutral, CT-to-plan software for manufacturers to license under a manufacturer-pays model: segmentation, CPAK phenotyping, alignment options, and sizing support, with the implant relationship kept by the manufacturer and IP defined by contract. It is currently Research Use Only (RUO), not a cleared device, so engagements begin as pilots and co-development, not as the purchase of a finished, cleared product.
The value in a robot is mostly software
Walk through what a surgical robot does and separate the two halves. One half is the physical system: the arm, the console, the intraoperative tracking, the capital purchase, the service contract, the console footprint in the operating room. The other half is the plan: reading the CT, building a 3D model, computing alignment and rotation, estimating implant size, and letting the surgeon reason about the case before incision. Surgeons value both, but the part that shapes which implant goes in, and how, is the planning half. That half is software.
Robotic ecosystems bundle these halves on purpose. The planner is the reason a surgeon adopts the console, and the console is the reason the manufacturer captures the case. But the bundling is a commercial choice, not a technical necessity. Nothing about producing a competent CT-to-plan workflow requires a robotic arm. A manufacturer that wants to be present where surgeons plan can license the planning software directly, without financing a hardware program to carry it. For the underlying idea, see how CT-based 3D pre-operative planning works.
Why "build a robot" is the wrong reflex
When a manufacturer decides it wants a digital-planning story, the instinct is often to look at the robots and ask how to build or buy one. That reflex is expensive for three reasons.
- Capital and timeline. A robotics program is a multi-year, capital-heavy build with its own regulatory, manufacturing, and service burdens. It is a different company from an implant company, layered on top of the one you already run.
- A separate sales motion. Selling capital equipment into hospital procurement is not the same motion as selling implants. You inherit a new, slower, budget-gated commercial cycle.
- Lock-in cuts both ways. A robot creates lock-in that benefits its owner, but building one means you also carry the cost of that ecosystem, the installed base, the service, the retraining, before it pays back.
None of this is required to offer planning. The planning value can be delivered as a software layer that runs on the surgeon's existing DICOM workflow and fits your catalog. The trade-offs between a full robotic system and a software planner are worth understanding before committing capital to hardware you may not need. The broader build-versus-license decision is laid out in build vs buy for AI surgical planning as an OEM.
What a software-only planning layer gives you
A vendor-neutral, implant-agnostic planner does the anatomy work first and applies the implant library last. Conceptually it segments bone from CT, computes alignment, phenotype, rotation, and sizing on the patient's anatomy, then fits that plan to whichever implant system is selected, including yours. Because the anatomy steps are independent of the implant, the same engine can express a plan on your catalog without steering toward a competitor.
For a manufacturer without a robot or an in-house planner, the concrete gains are direct:
- A modern digital front door that works with your existing implant line, no hardware program required.
- Sizing support grounded in the patient's CT anatomy and fitted to your components, which can support more predictable inventory and tray conversations.
- Neutral alignment context, so the surgeon plans on the anatomy and your implant is fitted to that plan rather than the plan being built to sell a console.
- A closed value-chain gap in markets pushing domestic production, where the implant may already be locally made and the planning software is the last imported layer.
The honest boundary: this describes positioning, not internals. How the segmentation and alignment logic are built is exactly the part a manufacturer licenses rather than reinvents, and it is not a clinical-outcomes claim. Salnus software is RUO and not a cleared device, so the framing is workflow and evidence-building, not proven surgical superiority.
The commercial shape: manufacturer-pays, no console
Offering planning without a robot changes who pays and how. Instead of asking a surgeon to buy a planning subscription or a hospital to buy a console, the manufacturer-pays surgical planning model puts the software free at the point of use and the manufacturer funds it, because a sound plan supports correct sizing and confident use of that manufacturer's implant. The deal shapes are familiar from any software-licensing relationship and do not require a capital purchase:
- Per-plan, where the manufacturer pays for each plan generated on its implant library, aligning cost with usage.
- Annual floor, a committed yearly minimum for budget predictability and priority.
- White-label license, where the manufacturer presents the planning experience under its own brand while licensing the underlying neutral engine, as covered in white-label AI knee planning for implant companies.
- Co-development with IP retained, where the manufacturer co-funds specific extensions while the core planning engine stays with the software builder.
Across all four, intellectual property is contract-defined. A manufacturer can fund surrounding work and still not own the core engine, which is precisely what keeps a vendor-neutral layer neutral for the next manufacturer that licenses it. To see where each offering sits today, which manufacturers offer AI knee planning maps the current landscape. And to scope a specific engagement, see how Salnus works with manufacturers.
The honest caveat
Offering planning without a robot is a positioning and workflow choice, not a regulatory shortcut. Salnus is Research Use Only today, not a cleared device, and makes no claim of clinical superiority or outcome improvement. Any clinical deployment requires the appropriate regulatory clearance, data governance, and validation. An OEM engagement is a pilot or co-development path toward a jointly validated product, not the purchase of a finished, cleared system. That is the correct starting posture for a serious medtech decision-maker, and it is how every conversation begins.
Bottom line
The reason to buy or build a robot is rarely the planning itself; the planning value is software, and it can be delivered without a console. A vendor-neutral, implant-agnostic, CT-based planning layer lets a manufacturer offer modern digital planning tied to its own catalog, at a fraction of the capital and lock-in of a robotics program, under a manufacturer-pays model with IP defined by contract. If you make implants and want a credible digital-planning offer without financing a hardware division, see how Salnus works with manufacturers to scope a pilot. Salnus builds this software for manufacturers to license, as Research Use Only.
Reviewed by the Salnus biomedical engineering team.