Licensing Planning Software: What to Ask
Licensing an implant-agnostic planning platform as an OEM: a manufacturer's checklist for integration, data governance, regulatory status, IP terms, and pilots.
Key takeaways
If you are an implant manufacturer deciding how to offer modern digital planning, the build-versus-license question comes down to a short list of hard questions you should ask any planning-software partner before signing. The six that matter most: implant-library integration (can it plan onto your catalog without re-architecting the engine), data governance (where does patient imaging live and who is the controller), regulatory pathway and RUO status (is it a cleared device today or Research Use Only, and whose clearance carries the offering), IP and field-of-use terms (who owns the software, what is exclusive to you, and what is barred from a competitor), validation evidence (segmentation accuracy and reader agreement on real cases, not marketing claims), and pilot structure (a scoped, measurable co-development phase before any commercial rollout). A vendor-neutral, implant-agnostic engine is attractive precisely because it keeps your implant relationship yours while giving you a planning layer you do not have to build. This post is that checklist, written from the manufacturer's side of the table. Salnus builds this software for manufacturers to license, and is currently Research Use Only (RUO), not a cleared device.
Why manufacturers license instead of build
Building a computed-tomography-based planning engine in-house means bone segmentation, alignment logic, phenotyping, sizing support, a viewer, and a validation program, most of which sit outside an implant company's core competence. Licensing a vendor-neutral engine lets you offer digital planning quickly while keeping your capital and headcount on implants. The trade you are evaluating is control versus speed, and the questions below are how you protect control while buying speed. For the underlying model, see our explainer on implant-agnostic surgical planning and the landscape review in orthopedic 3D planning software compared for 2026.
1. Implant-library integration
The first question is whether the platform is genuinely implant-agnostic or quietly tied to one catalog. Ask how your implant library is ingested, how sizing and component geometry are represented, and how long a new or revised implant family takes to add. A true vendor-neutral engine treats the implant catalog as configurable input, not as something baked into the core. Confirm that adding your library does not require exposing anything you consider proprietary beyond what integration needs, and that the same engine can, in principle, support competitor catalogs without giving competitors access to your data or your terms.
2. Data governance
Patient imaging is regulated data, so settle governance before features. Ask where the computed-tomography data is processed and stored, whether processing can be client-side or region-pinned, who is the data controller versus processor, and how de-identification is handled. If your markets include the EU, ask directly about GDPR and cross-border transfer, because a planning partner that cannot answer this cleanly will become your compliance problem later. For how the imaging pipeline actually runs, see how CT 3D preoperative planning works.
3. Regulatory pathway and RUO status
Be precise here, because it is the question most likely to be blurred in a sales conversation. Ask whether the software is a cleared medical device today or Research Use Only (RUO). RUO software can be piloted and co-developed, but it must not be marketed for clinical decision-making until the appropriate pathway (FDA clearance, CE marking under MDR as SaMD, or local approval such as TITCK) is complete. Ask whose name the eventual clearance sits under, who funds and owns the regulatory file, and what the realistic timeline and evidence burden are. Salnus is transparent that it is RUO today, and OEM engagements are structured as pilot and co-development, not the purchase of a finished cleared product. Treat any partner that is vague about clearance as a red flag.
4. IP and field-of-use terms
This is where a license becomes a strategic asset or a liability. The clean structure separates a narrow patent, commercial secrets on the server side, and a contract that defines field-of-use. Ask what you get: exclusivity within your implant category or region, a re-training bar that stops the same offering from being handed to a competitor, and clear ownership boundaries so the core engine stays with the software company while your configuration, your data, and your branding stay yours. A sensible model keeps the platform IP with the developer and defines your rights by contract, rather than a messy joint-ownership that stalls every future decision. White-label branding, exclusivity scope, and the competitor bar are the three terms worth negotiating hardest.
5. Validation evidence
Ask for evidence, not adjectives. For a planning engine the questions are concrete: what is the segmentation accuracy on real cases, what is reader or expert agreement on the planning outputs, and on what cohorts was this measured. Because the software is RUO, the honest framing is research evidence and pilot data, not outcome claims, and you should be suspicious of any planning vendor that asserts clinical superiority. For the metrics that actually matter, see robotic versus software-only TKA planning, which frames where a software planner does and does not compete with capital hardware. Validation is also what your own regulatory and clinical teams will scrutinize, so a partner who shares methodology openly saves you months.
6. Pilot structure
Do not go from slide deck to rollout. A good OEM engagement starts with a scoped pilot: a defined case set, a small number of surgeon sites, explicit success metrics agreed in advance, and a fixed window. The pilot answers whether the engine plans well onto your catalog, whether the workflow fits your surgeons, and whether the data governance holds up, before anyone commits to commercial terms. Under the manufacturer-pays model, the structure is co-development first and licensing second, which keeps risk bounded for both sides. To see how this fits alongside other planning options manufacturers offer, see which manufacturers offer AI knee planning.
Bottom line
Licensing a vendor-neutral, implant-agnostic planning platform lets a manufacturer offer modern computed-tomography-based planning without building an engine, while keeping the implant relationship, the branding, and the customer. Protect yourself with six questions: integration, data governance, regulatory and RUO status, IP and field-of-use, validation evidence, and pilot structure. Salnus builds exactly this software for manufacturers to license, currently Research Use Only, and structures OEM work as pilot and co-development. If you are weighing whether to build or license planning, see the manufacturer engagement model on our manufacturer partnership page and start with a scoped pilot.
Reviewed by the Salnus biomedical engineering team.