Salesforce bought to customize as an inventory system.

Someone in the room says, "Salesforce is just a database, we can configure inventory on top of it." Founders sign a multi-year Salesforce contract on that premise and treat it as both their CRM and their inventory backbone. For a medical device company that ships physical product, this is exactly backward. Inventory and traceability are the foundational systems. The CRM is secondary in direct enterprise medtech sales.

Founders without an IT background often think the work is small: a few custom tables, a few screens, some workflow rules. In a normal company, that is true. In medtech it is the wrong question. The inventory system holds regulated records (lot numbers, serial numbers, traceability, audit trails). The FDA, notified bodies, and hospital procurement teams treat it the way they treat a calibrated scientific instrument. The company must prove, on demand, that it does what it says it does, every time, for every record. That proof is called validation, and it is a posture, like calibration. Every change, vendor-side or company-side, requires re-validation, re-testing, re-documentation, signed by Quality. The evidence library has to be current at any moment an auditor asks.

Now layer Salesforce on top. Salesforce ships three platform releases a year. In a normal company, that is a quarterly maintenance task. In a regulated company, every release triggers impact analysis, re-test of validated workflows, and often re-execution of validation tests. Three times a year, for the life of the company. And Salesforce was not designed for regulated medical device inventory: no native lot or serial traceability, no UDI (Unique Device Identifier) support, no quarantine workflow, no shelf-life management. Every one of those capabilities is built in custom code. Every line of that code becomes part of the validated system and gets re-validated on every change. "A few tables and screens" becomes a permanent staffing line: a Salesforce admin who understands medtech validation, a Quality team member who can read Salesforce metadata, and a developer who can write validated code against the regulator's data integrity standards. That intersection of skills is rare, expensive, and hard to retain.

The Salesforce contract is paid for the years before anyone realizes the wrong tool was chosen. Every custom field, custom object, and line of custom code added to make Salesforce act like inventory becomes part of the validated system, with its own change control, test coverage, and documentation burden. The hiring profile to maintain the implementation (a Salesforce admin who understands medtech validation, a Quality team member who can read Salesforce metadata, a developer who can write validated code) becomes a permanent recruitment problem. When the company eventually buys a purpose-built medical device inventory system on top, the migration is its own validated project: parallel build, data migration, decommissioning of the old system, Quality sign-off on every step. The avoidable cost runs into six figures across contract, headcount, and migration. The avoidable time is the years between the wrong choice and the right one, which is time the company never gets back.

A regulated-product inventory and traceability platform first, appropriate for 21 CFR Part 11 and QMSR / ISO 13485 interfaces. The CRM later, when direct enterprise sales actually require one.