Key takeaways
- Treat the first substantive call as a working session, not a sales pitch. Bring the product description and your year-one volume.
- Ask which disciplines are handled in house and which are subcontracted. That one answer reshapes accountability for everything else.
- Non-recurring engineering is the one-time design, tooling and test cost, charged separately from per-unit price. Get change-order handling in writing.
- IP ownership in a commissioned engineering relationship depends entirely on what the contract says, not on any default assumption.
Before hiring a hardware development company, ask about their capability split (what they build in-house versus subcontract), their stage-gate process and what happens when a gate fails, how non-recurring engineering (NRE) costs and change orders are structured, who owns your intellectual property, which certifications your product will need, and what you receive if you leave the engagement early. The answers matter more than the questions themselves: a firm that answers specifically, in writing, is telling you something different from one that answers in generalities.
This question list is a companion to our broader guide on how to vet a hardware development company before you sign, which covers the full six-stage process from shortlist to signature. This article is the question bank you bring into the conversation itself.
How to run the conversation
Treat the first substantive call as a working session, not a sales pitch to sit through. Bring your product description, your target volume for year one, and a rough budget range, and ask the firm to respond to your specifics rather than describing their process in the abstract. Take notes, and follow up anything important in writing afterward so you have a record of what was said.
A useful test is to ask the same question twice, once early in the call and once near the end, phrased slightly differently. A firm that gives you the same specific answer both times is describing a real, repeatable process. A firm whose answer shifts is likely improvising.
Questions about capability
What they build in house versus subcontract
- Which disciplines does your team handle directly: mechanical, electrical, firmware, industrial design?
- What gets subcontracted, and to whom?
- Will you tell me before you bring on a new subcontractor for my project, or after?
Who is actually on your team
- Can I speak with the engineers who would work on my product, not only sales?
- How many active projects does this team run at once?
- Who is my single point of contact once the engagement starts?
Questions about process
Stage gates and what happens if a gate fails
Hardware development commonly moves through engineering validation (EVT), design validation (DVT), and production validation (PVT) testing, each confirming a different thing: EVT that the design works as intended, DVT that it can be built at production intent, and PVT that it can be built repeatedly at volume. Ask what happens if a gate fails, since it is a normal part of the process, not a sign of vendor incompetence, and the answer tells you how the firm handles setbacks.
| Stage | What it validates | Ask |
|---|---|---|
| EVT | Design works, in one combined form factor | What is your typical failure rate at this stage, and what happens next if we fail? |
| DVT | Design can be built with production-intent tooling and process | What triggers a return to EVT versus a fix-forward at DVT? |
| PVT | Design can be built repeatedly at volume and yield | What yield do you consider a pass before we move to full production? |
How they handle DFM and the move to production
Design for manufacturing (DFM) and design for assembly (DFA) reviews should happen well before tooling is committed, not discovered as a problem during production validation. Ask when in your specific timeline a DFM review happens, and who signs off on it.
Questions about money
NRE, change orders, and overruns
NRE is the one-time cost of design, tooling, and test development, charged separately from the per-unit cost of the product itself. Ask for a line-item breakdown, not a single bundled number, and ask specifically how change orders are priced and approved. A firm with a clear, repeatable process for both will be able to answer immediately; a firm without one will describe it vaguely.
- What is included in the NRE quote, and what is explicitly excluded?
- What triggers a change order, and how is it priced?
- What happens to cost if a component becomes unavailable or a supplier changes price?
Questions about IP and confidentiality
Intellectual property ownership in a commissioned engineering relationship depends entirely on what your contract says, not on any default assumption. Under US copyright law, a commissioned work only counts as “made for hire,” with the hiring party as owner, if there is a signed written agreement that says so and the work falls into one of a specific, narrow list of statutory categories, a list that does not clearly cover general product design work. Absent an explicit, properly drafted assignment clause, you should not assume you automatically own the design files a vendor produces for you. This is a question to ask directly, and an answer to have a lawyer confirm, not a detail to leave to assumption.
- Does our agreement include a present, irrevocable assignment of IP to us, not just a work-for-hire label?
- If I leave the engagement, do I receive native CAD files, the bill of materials, test procedures, and firmware source, or only finished outputs?
- Will you sign a mutual confidentiality agreement before we discuss the product in technical detail?
No answer here should be treated as legal advice. Have an attorney review the actual assignment and confidentiality language before you sign.
Questions about certification and compliance
Most electronic products sold in the US need some form of equipment authorization from the FCC before they can be marketed or imported, and specific product categories carry additional requirements, such as Consumer Product Safety Commission certification for children’s products. Ask the firm directly which certifications apply to your specific product, not in general terms, and ask for an example of a past product they took through that exact certification process.
- Which certifications does my product category require before I can sell it?
- Have you taken a product through this specific certification before? Can you name it?
- Who manages the relationship with the testing lab, and is it accredited for this certification?
Questions about what happens if you leave
- What deliverables do I receive if we end the engagement after EVT? After DVT?
- Is there an escrow arrangement, or another mechanism, that protects my access to design files if you cannot continue the work?
- What is the notice period, and what does it cost to exit cleanly?
The answers that should worry you
Watch for answers that stay general when you ask for specifics, a refusal to put commitments in writing, and any hesitation around the direct IP-ownership question above. These map closely to the broader pattern covered in our guide to red flags in a product development partner, which goes into more detail on what each kind of evasive answer usually means.
- A specific answer names a stage, a document, or a person. A vague answer names a philosophy.
- A firm that welcomes hard questions is telling you something different from a firm that treats them as an obstacle to close the deal.
- If you are choosing between a firm that does all of this in house and one that coordinates several outside vendors, our comparison of how to choose a hardware product development partner covers that decision directly.
Frequently asked questions
How many firms should I interview before deciding?
Enough to compare answers side by side, typically three to five, so you can tell a consistent, specific answer from an outlier.
Should I ask these questions before or after signing an NDA?
Most of these questions can be answered without disclosing your product’s technical details, so you can ask them before an NDA is in place. Save the specifics of your design for after mutual confidentiality is agreed.
What if a firm cannot answer a certification question specifically?
That is worth pressing on directly. Certification requirements vary by product category, and a firm with real experience in your category should be able to name the specific standard, not just gesture at “compliance.”
Is it normal for NRE costs to change after the first quote?
Some movement is normal once real scoping happens. What matters is whether the firm can explain why the number moved and show it against a specific change in scope.
Do I need a lawyer for this stage, or only before signing?
Having an attorney review the IP and confidentiality terms before you sign is the point where legal review matters most. Earlier conversations can happen without one.
Where Inventornest fits
Inventornest answers these questions directly because we structure engagements around named deliverables and defined stage gates. If you want to run this exact question list past a proposal you already have, you can book a private consultation. Our OEM development and manufacturing services page has more on how we scope and price engagements.
