Match capability to the product
A manufacturer optimized for high-volume consumer products is the wrong fit for a low-volume connected industrial board, even if their headline pricing looks attractive. They will quote the cost of running a small batch on a line built for large batches, and they will run it as such.
Conversely, a manufacturer sized for low to medium volume connected products is the wrong fit for 500000 unit consumer electronics runs. The line will not produce at the cost or rate the buyer needs.
The right capability fit means:
- Their line size matches your batch size
- Their component range covers your BOM (smallest passive, largest BGA)
- Their test capability matches your test needs
- Their experience covers your product class
Communication style at quote stage
How the manufacturer responds to your initial RFQ predicts how they will communicate during production:
- Slow response and vague answers at quote: expect slow response and vague answers during production
- Quick, specific, technical questions back: expect specific technical communication during production
- Pushy on closing the deal without understanding the product: expect a focus on volume over fit
The quote conversation is the cheapest test of the future relationship. Use it.
Traceability discipline
Per-unit traceability is hard to bolt on after production starts. Either the manufacturer has it as a standard part of their workflow or they will improvise it badly when you ask for it later.
Ask: "what data do you log per unit, and how do I query it after production?" The answer should be specific and concrete. If the answer is "we log everything in a spreadsheet" or "we can build that for you", that is a warning sign.
IP handling
Ask:
- How are signing keys stored?
- Who has access to firmware binaries?
- What is the NDA process?
- How is per-unit data protected?
The answer should reflect that the manufacturer has thought about IP before. If they have not, you become the manufacturer's first customer to care about IP, which is not the role you want.
Warning signs
- Certifications listed without an issuing body or expiration date
- Client logos with no permission to display (or worse, no real customer relationship)
- Pricing that looks unrealistically low (volume kickback, rework cost hidden, or just inaccurate)
- "We can do anything" answer to capability questions
- No willingness to do a pilot batch before committing to repeat production
- Reluctance to share photos of their line or to host a visit (in-person or virtual)
- Vague answers about test capabilities
- Slow or absent response to specific technical questions
Better signs
- Clear, specific answers to technical questions
- Willingness to scope a pilot batch as a low-risk first step
- Concrete examples of similar products they have built (without naming customers if NDAs apply)
- Specific machine names and capabilities
- Reference to standards (IPC-A-610, IPC-J-STD-001) used as acceptance criteria
- A documented NPI gate process
- A traceability story that does not depend on spreadsheets
Decision framework
Score the candidates on:
- Capability fit
- Communication quality
- Traceability discipline
- IP and security posture
- Reference work (anonymized is fine)
- Pilot batch terms
The lowest unit cost rarely wins after these factors are weighted.