V5 Ultimate vs Propel PLM

Propel is a Salesforce-native PLM + QMS built for regulated product companies — medical devices, high-tech electronics, industrial equipment. It uses the Salesforce Lightning platform for records, workflow and reporting, which is a real advantage if the company already runs on Salesforce. V5 Ultimate competes for the same buyer with a very different bet: one purpose-built stack that owns execution + eDHR + QMS, instead of a PLM layered on a general-purpose cloud platform.

Start free trial Free trial, no credit card, onboard in days, not months.

What each product actually is

Propel is a Salesforce-native PLM + QMS: items, BOMs, ECO / ECR workflows, supplier collaboration, document control, training, CAPA, complaint and audit, all built on Salesforce objects. It is not an MES — DHRs and floor execution live in a separate system. V5 Ultimate is one platform: DMR-locked routing, per-serial eDHR self-building, calibrated tool integration at the workstation, WMS, and QMS objects on the same stack.

Platform trade-off — Salesforce-native vs purpose-built

Propel's biggest strength is also the biggest question: everything lives on Salesforce. If the company is already a Salesforce shop, the reporting, permissions and integration surface is a huge accelerator. If it isn't, the Salesforce licence overhead and the Force.com governor limits become the ceiling — especially for shop-floor kiosks running hundreds of concurrent sessions. V5 avoids that trade-off by being a native execution + quality platform from day one.

Execution on the floor and eDHR

Propel does not run the shop floor. The DHR is assembled after the fact from item-master data, quality events and whatever the MES exports. V5 is the build environment: the routing references the locked DMR revision, only that revision is visible on the operator kiosk, torque and vision tools are calibration-gated, the UDI label prints at the workstation, and the eDHR locks to the serial the moment final inspection signs — no end-of-batch reconstruction.

Design controls

Propel covers DHF, design inputs/outputs, RTM and ISO 14971 risk with Salesforce-native objects. V5 covers the same surface area with an execution-centric flavour — the same RTM that proves the URS is tested is the spine of the qualification of the manufacturing system itself, so evidence carries across the design→production boundary without a re-build.

Deployment

Propel is cloud-only on Salesforce. V5 ships as Lovable Cloud and V5 Ultimate On-Premises (containerised, air-gap capable, customer-owned keys and data). On-prem is a hard requirement for implantables, defence-linked programmes, and some combination products; Salesforce-native platforms cannot meet it.

AI behaviour

Propel benefits from Salesforce's Einstein AI stack for classification and drafting. V5's AI layer is regime-aware — for a device tenant it speaks DHR / DMR / UDI / DI+PI / GUDID / EUDAMED and uses ISO 13485 + 21 CFR 820 templates. Both vendors are explicit that AI does not e-sign; a qualified human always signs.

Pricing model

Propel is per-user annual on top of a Salesforce Lightning platform licence — the platform cost is real and often surprises first-time buyers. V5 publishes per-user / month with no separate platform tax. For a device company already deep in Salesforce Propel is often the fastest path; for anyone else V5 is usually cheaper end-to-end.

Where Propel PLM is the better fit

Companies already standardised on Salesforce who want PLM/QMS on the same platform as CRM and service, teams that value Salesforce's reporting and permissions model, or organisations who outsource manufacturing and only need the PLM + QMS layer.

Where V5 Ultimate is the better fit

Device manufacturers who own their production line and want eDHR self-building per serial, companies not already on Salesforce who don't want the platform tax, on-prem / air-gap requirements, or combination-product manufacturers who need pharma BMR + device DHR on one stack.

V5 Ultimate vs Propel PLM

Capability	V5 Ultimate	Propel PLM
Item + BOM master	Yes — DMR-centric	Yes
ECO / ECR / ECN workflow	Yes — routing-revision impact	Yes — Salesforce Flow
Design controls (DHF, RTM)	Yes — execution-linked RTM	Yes
CAPA + complaint + audit	Yes — tied to serial/lot	Yes
Execution on the floor (MES)	Native — kiosk, torque tools, gating	Not in scope
eDHR self-builds per serial	Yes — live as operator works	Assembled from inputs
UDI generation + GUDID-ready	Native — DI+PI at the workstation	Reference only
Warehouse + lot/serial genealogy (WMS)	Native	Not in scope
On-premises / air-gap deployment	Yes — containerised	Cloud only
Platform licence tax	None — standalone	Salesforce Lightning per user

Frequently asked

Do we need Salesforce licences to use V5?

No. V5 is a standalone platform. Propel requires a Salesforce Lightning platform licence per user in addition to Propel itself; V5 has no equivalent platform tax.

Can V5 replace Propel for a Salesforce-heavy company?

Yes technically, but if the whole company already runs on Salesforce the productivity trade-off often favours Propel until execution + eDHR become critical. Common hybrid: keep Propel for design-side item and BOM, V5 for work-order execution, eDHR and WMS.

Does V5 integrate with Salesforce CRM?

Yes — V5 exposes REST + webhook contracts and standard connectors, so serial-level warranty and complaint data can flow into Salesforce Service Cloud without Propel in the middle.

Which is stronger on manufacturing execution?

V5 by a wide margin — Propel is a PLM/QMS and does not claim to run the shop floor.

See it on your shop floor.

Free trial, no credit card, onboard in days, not months.

Start free trial See pricing →Browse all resources →