Choosing a contract manufacturer (CM) often gets decided primarily on quoted unit price, with everything else assumed roughly equivalent across vendors. In practice, the differences that matter most — quality consistency, communication during problems, capacity to actually scale with the product — don't show up in a quote, and they're expensive to discover after committing tooling and a first production run to the wrong partner.
Volume and product fit
CMs specialize by volume range and product type, and a mismatch in either direction causes real problems. A CM set up for high-volume consumer electronics may be a poor fit — and a poor priority — for a low-volume, higher-complexity industrial product, and vice versa. Asking directly about their typical customer's volume and product complexity, and whether the specific product fits comfortably within that range, surfaces mismatches before they become a scheduling or quality problem.
Quality systems and certifications
- ISO 9001 (general quality management) as a baseline, and industry-specific certifications (ISO 13485 for medical devices, IATF 16949 for automotive) if the product's target market requires them
- Actual quality control process — incoming component inspection, in-process testing, outgoing inspection — not just a certification on paper, which is worth verifying through a facility visit or a detailed process walkthrough, not just a claim on a sales call
- First-pass yield history for comparable products, which is a more concrete signal of real quality performance than a certification alone
Communication and responsiveness under normal and abnormal conditions
Every production run eventually hits a problem — a component shortage, a quality issue, a schedule slip. The CM relationships that work well are the ones where problems get communicated proactively and clearly, not discovered after the fact when a shipment doesn't arrive. This is genuinely difficult to assess from a sales conversation alone; talking to existing customers (references, not just the ones the CM offers up) about how the relationship holds up when something goes wrong is far more informative than how it looks when everything's on track.
Capacity to scale with the product
A CM that comfortably handles a pilot run of a few hundred units doesn't automatically scale to tens of thousands without strain — line capacity, component sourcing relationships at volume, and the CM's own supplier network all matter more as volume grows. Asking specifically about their experience and capacity at the volume the product is actually expected to reach, not just the pilot volume, avoids finding out about a capacity ceiling only once demand requires exceeding it.
DFM collaboration, not just execution
A CM that only executes exactly what's specified in the design files, without flagging manufacturability concerns before production starts, puts the full burden of catching DFM issues on the design team. A CM that actively reviews designs for manufacturability and raises concerns before committing to tooling is a meaningfully better partner — and this is worth testing directly by sending an early design for DFM feedback before committing, to see how substantive and specific the feedback actually is.
IP protection and contractual terms
Design files, firmware, and any proprietary processes shared with a CM represent real IP exposure. NDAs are standard, but worth checking the specifics: ownership of tooling (who owns it if the relationship ends), non-compete or exclusivity terms, and what happens to design files and remaining inventory if the relationship is terminated — questions that are far easier to resolve upfront than after a dispute.
How we approach this
We help clients evaluate and vet CM options against the product's specific volume, quality, and IP requirements, rather than defaulting to whichever vendor is fastest to quote. See our embedded hardware work for how this fits into taking a design from prototype to production.