The Hardware RFP Clauses That Decide Who Owns Your Product: Firmware, Data, Calibration and Design Files
What funded hardware startups should write into a Shenzhen vendor RFP before the first sample: data routing, firmware source and escrow, calibration, BOM transparency, design-file transfer, NRE separation and acceptance testing.
Before the first sample, a hardware RFP should require: all device data routable to a server you control; complete firmware source at delivery or in escrow; per-unit calibration files in an open format; a full BOM with manufacturer part numbers; design-file transfer terms; NRE priced separately from unit cost; and a measured acceptance test that gates payment.
Most hardware ownership problems are decided in the first document a startup sends a factory. By the time a sample arrives, leverage has moved to the vendor. These are the clauses we write into every RFP for wearables, capture devices and edge hardware.
1. Data routing
All device data — raw sensor data, processed values, logs and device state — must be routable to a broker or server specified by the client, without passing through vendor infrastructure.
Ask for the protocol (MQTT, HTTPS, BLE GATT), the payload schema and whether the device can be provisioned to your endpoint at the factory.
2. Firmware source and build environment
- Complete source at delivery, including drivers, build scripts, toolchain versions and third-party licences.
- The ability to build, flash and update without vendor involvement.
- Proprietary blobs (ISP tuning, sensor calibration firmware) explicitly listed.
- If full source is not possible for a white-label product: escrow with defined release triggers (vendor insolvency, end-of-life, failure to support).
3. Calibration
Per-unit calibration — camera intrinsics and extrinsics, IMU biases, sensor gains — delivered in a documented, open format with the unit’s serial number, plus the procedure used to produce it.
4. BOM transparency
A full BOM with manufacturer part numbers and approved alternates. Without MPNs you cannot second-source, cost-down or assess lifecycle risk.
5. Design files
State what transfers and when: schematics, PCB layout (native format plus Gerbers), mechanical CAD and tooling ownership. For a phased programme, tie transfer to milestones.
6. Price structure
NRE, tooling, samples and unit price on separate lines; MOQ and price breaks; lead time for standard and modified units. Holiday calendars (Chinese New Year, National Day) written into the schedule.
7. Measurement and acceptance
Every performance claim becomes a test with a method, a pass threshold and raw data delivered with the result. Payment milestones attach to passing it. For capture devices, see Timing Is the Spec.
8. Certification and support
Which certifications are included (CE, FCC, RoHS, local radio approvals) and who holds the certificates; warranty, RMA process and spare-part availability.
How to ask without losing the vendor
Put the clauses in the first RFP, not after the quote. Explain why: ownership is what lets you scale volume with them. Separate “must” from “negotiable”. Vendors respond better to a clear, professional document than to a request that grows after every reply.
HOLON writes and negotiates these RFPs as part of the Spec & Vendor Sprint.
Frequently asked
Can a Shenzhen vendor give us the firmware source code?
Often yes, if it is required before the deal and priced in. Vendors resist releasing source for a white-label product sold to many customers; for a custom or modified design, source delivery or escrow is a normal negotiated term.
What is the most important clause for a connected device?
Data routing. If device data only flows through the vendor's cloud, the vendor controls your product, your users' data and your ability to switch suppliers. Require that all raw and processed data can be sent to a broker or server you control.
HOLON (2026). The Hardware RFP Clauses That Decide Who Owns Your Product: Firmware, Data, Calibration and Design Files. HOLON-GDE-2026-007, v1.0. https://www.holonai.ai/research/hardware-rfp-clauses-firmware-data-ownership