How to Vet a Hardware Development Company Before You Sign

To vet a hardware development company, separate what you can verify against an independent record from what exists only in the company’s own sales material. Most of what a development firm tells you about itself is unverifiable: team size, shipped-product counts, domain expertise. A short list of things is checkable in public records: the legal entity, accredited certifications, regulatory filings, engineering licensure, and the testimony of clients you found yourself. A vetting program moves as many claims as possible from the first column into the second before money changes hands.

The six stages below run from shortlist to signature, written for a founder without an engineering background.

What vetting is actually for

The point is not mainly to catch frauds. The realistic failure mode is a competent company competent at something else: a studio that designs beautiful enclosures asked to deliver certified electronics, or an assembly house asked to solve a design problem it has no engineers to solve. The engagement fails slowly, and the money is gone before anyone names the mismatch.

A Government Accountability Office review found that Department of Defense programs which did not resolve manufacturing risks during development carried them into production, where nearly two-thirds of programs entering production after 2000 saw average unit cost growth above 5 percent (GAO-10-439, April 2010). Defense programs run at a different scale from a startup, and the mechanism transfers: unexamined capability assumptions convert into cost later.

What the process is trying to establish, in order:

• The company exists as a contracting party you could hold to an agreement.
• Its advertised credentials are real and mean what a reader would assume.
• It has done work of your kind, not adjacent work described in language that sounds like yours.
• The engineers who would do your work are the ones you have met.
• The terms name deliverables that can be judged complete or incomplete.

Stage 1: Build a shortlist you can defend

A shortlist is defensible when every company on it is there for a stated reason and you can name what each would be hired to do. Three to five firms is enough. Decide first which category your product needs: the types of product development companies split into firms that design without building, firms that build without designing, and firms that do both. A list mixing an industrial design studio, a full-service engineering firm and a contract assembler is not a shortlist. It is three different projects.

• Referrals from founders who shipped a comparable product. Highest signal, hardest to get.
• Trade shows and standards-body member directories. Membership proves dues were paid, not capability, but it narrows the field to firms operating in the open.
• Published portfolios and search results. Good for finding candidates, weak for verifying them.

One category needs separate handling. Invention marketing companies sell promotion and licensing rather than engineering, and 35 U.S.C. § 297 imposes written pre-contract disclosures on statutorily defined invention promoters, including how many customers ever received a net financial profit. The USPTO publishes complaints against invention promoters and their responses, while stating plainly that it does not investigate them. If a pitch centers on selling your idea rather than building it, check that register first.

Stage 2: Confirm the company is what it claims

This stage is public-record work and can be done in an afternoon, before you speak to anyone.

Entity, location, and who you are actually contracting with

The name on the website is frequently not the name on the contract. A US-facing brand may contract through a foreign parent, a holding company, or a new entity with no assets. Establish four things:

• The exact legal entity name and state of registration. There is no federal business registry in the United States. The Small Business Administration’s guidance confirms that LLCs, corporations, partnerships and nonprofit corporations register with the states where they do business.
• Its current status in that state’s records. California, as one worked example, distinguishes an active entity from one suspended or forfeited for failure to file or tax noncompliance, and from one dissolved or merged out.
• What “not found” means. Less than it appears. California’s search excludes general partnerships and limited liability partnerships, and the state disclaims responsibility for the timeliness of the data.
• Where the engineers sit. A US address and a US engineering team are separate claims. Ask both questions separately.

Two checks in older vendor checklists no longer work as described. There is no public IRS lookup for a for-profit company’s EIN, since the IRS publishes EINs only for tax-exempt organizations through its Tax Exempt Organization Search, so an EIN a commercial vendor gives you is not independently checkable. And the D-U-N-S number stopped being the federal entity identifier on April 4, 2022, when GSA systems switched to the Unique Entity ID; D-U-N-S remains a commercial credit-file identifier, not a credential.

Certifications and standards

Certification claims are the most checkable thing on a development company’s website and the least often checked. The chain matters more than the logo:

1. ISO writes the standard. ISO states that it does not perform certification, does not issue certificates, and does not permit use of its logo in connection with certification (iso.org). Nobody is certified by ISO.
2. An accredited certification body issues the certificate. Ask which one.
3. An accreditation body accredits that certification body. In North America the largest is the ANSI National Accreditation Board.
4. You verify the chain. Accredited management system certificates can be cross-checked at IAF CertSearch, covering the organization, the certification body and the accreditation body together. The International Accreditation Forum and the International Laboratory Accreditation Cooperation both ceased independent operation on January 1, 2026, unified into Global Accreditation Cooperation Incorporated.

Two accuracy notes, because most published material still gets both wrong. FDA’s Quality System Regulation has been replaced: the Quality Management System Regulation took effect February 2, 2026, amending 21 CFR Part 820 to incorporate ISO 13485:2016 by reference (89 FR 7496). A firm still describing medical device work in QSR terms is working from stale material. And IPC became the Global Electronics Association in June 2025, though the standards keep their IPC designations. IPC-A-610 remains the assembly acceptability standard and its section 1.3 classifies assemblies into three product classes. Ask which class a firm builds to, and why it fits your product.

Stage 3: Test capability, not sales polish

A sales conversation is built to survive scrutiny. An engineering conversation is not. This stage is about getting into the second kind.

Evidence of shipped work

A portfolio page proves a firm was involved in a project. It rarely says which parts. Ask questions that are hard to answer without having done the work:

• “Which parts of this were yours?” Industrial design, mechanical, electrical, firmware, test and certification are separable, and firms routinely display projects where they did one of them.
• “What did the first build fail on, and what changed?” Common products with established functions and few unique features can pass the first build without changes.
• “Who was the applicant on the certification?” For anything with a radio, an FCC grant of certification sits in a public database under a named grantee.
• “Can I see the DFM feedback you gave that client?” Redacted is fine. The document’s shape shows whether the process exists.
• “What tooling did you specify, and who owned it?” Tooling ownership is settled by contract, not by who paid. A firm that treats the question as routine has been through it.

Engineering licensure is narrower than most founders assume. It runs state by state through the boards that make up NCEES, and only a licensed engineer may sign and seal engineering drawings, though drawings may be prepared by others working under that engineer’s responsible charge. In most states an industrial exemption removes even the sealing requirement for products manufactured and sold as goods. The NCEES Model Law also provides for firm-level certificates of authorization. What licensure does not give you is a register to look up for a company that designs consumer electronics, which is why the rest of this process matters.

Talking to the engineers who would do the work

Ask for an hour with the engineers who would be assigned, not the technical director who joins sales calls. Then ask about your product specifically:

• What is the hardest part of this design, and why?
• What would you build first, and what question would that build answer?
• Which components here have lead times you would worry about?
• What would make you tell me this cannot be built at my target cost?

The last question is the most useful. A team willing to describe the conditions under which they would decline the work is a team that has declined work.

Stage 4: References and back-channels

Vendor-supplied references are selected, which makes them a floor rather than a verdict. USPTO guidance for inventors evaluating firms recommends requesting references from current clients, checking with the Better Business Bureau and local chambers of commerce, reviewing the official fee schedule so you know what legitimate costs look like, and checking the FTC site for investigations (USPTO scam prevention).

• Find one reference yourself. A product on a shelf has a brand behind it, and founders answer email about who built their hardware.
• Ask about the middle of the project. “What happened when the schedule slipped?” and “Who told you about the first cost overrun, and when?” produce information. “Were you happy?” does not.

Ask referees how the firm handled their files too. NIST SP 1326, published July 2026, organizes supplier due diligence around supply chain tiers, foreign ownership or control, provenance, resilience and foundational cyber practices. It is written for information and communications technology, and those five headings transfer.

Stage 5: Commercial terms and the proposal

A proposal is a vetting instrument. What a firm makes measurable tells you how it expects to be judged. FAR 37.602 requires a federal performance work statement to describe work in terms of required results rather than how the work is done, and to permit assessment against measurable standards. Read a private proposal against that test.

• Deliverables named as artifacts. “Released mechanical CAD package, tolerance analysis and a DFM report” can be judged complete. “Design phase” cannot.
• An explicit statement of exclusions. Certification testing, tooling, compliance filings and companion-app firmware are the usual omissions.
• NRE separated from unit cost. Non-recurring engineering is an industry term rather than a defined standard, covering the one-time engineering, layout, tooling and test fixture charges that precede per-unit pricing. Ask for it line by line.
• Ownership in writing. Design ownership, tooling ownership and the right to move production elsewhere are three separate clauses. Whether the arrangement suits you is a question for your attorney, and this is the point to involve one.
• Change control. How a scope change gets priced, and who signs it.
• Milestones tied to artifacts rather than elapsed calendar time.

Stage 6: A paid discovery or feasibility step first

The most reliable vetting instrument is a small paid engagement before the large one. A product feasibility analysis or scoped discovery phase costs a fraction of a development program and produces a document you can take elsewhere plus direct evidence of how the firm works.

• Do they tell you something you did not want to hear? A feasibility step returning only encouragement was a sales document.
• Did the deliverable arrive when promised? A missed two-week deadline predicts a missed six-month one.
• Is the output usable by a third party? If it only makes sense to its authors, you are locked in already.

Structure the discovery agreement so the output is yours whether or not you continue. That one term converts a sales process into a purchase.

What a clean vetting result looks like

At the end you should be able to state, without consulting the vendor’s website:

• The legal entity, its state of registration, and its status.
• Each advertised certification, its issuing certification body, and the result of checking it.
• Two comparable projects, with the firm’s specific scope on each.
• The engineers assigned, by name, and what each would do.
• One reference you found independently.
• A proposal whose deliverables are artifacts, with exclusions written down.
• Who owns the design, the tooling and the documentation, in the contract’s own words.

Gaps are not automatically disqualifying. A young firm may have no ISO certificate and excellent engineers. What matters is knowing which line is blank and pricing that risk. Choosing between finalists is covered in how to choose a hardware product development partner. This process produces the finalists.

Frequently asked questions

How long should vetting take?

Two to four weeks for public-record and reference work across three to five firms, alongside proposal conversations. A paid discovery step adds two to six weeks and removes most of the remaining guesswork.

Can I verify a company’s ISO certificate myself?

Yes, for accredited management system certificates. Ask which certification body issued it, then cross-check the organization, the certification body and the accreditation body at IAF CertSearch or the accreditation body’s own directory.

Does “FDA registered” mean the FDA checked the company?

No. Establishment registration is an administrative filing. FDA states that registration does not denote approval, clearance or authorization, that it issues no registration certificates to device facilities, and that representations implying official approval constitute misbranding.

What if the company will not let me speak to the engineers?

Treat it as information rather than a refusal. Some firms genuinely protect senior engineers’ time. Ask instead for a technical work session on your product, paid if necessary, and see who turns up.

Should an attorney review the agreement?

Yes, for anything involving IP assignment, tooling ownership, exclusivity or indemnity. This article is factual background rather than legal advice, and contract terms are where that difference matters.

Where Inventornest fits

Inventornest takes hardware from concept through design, prototyping and production handoff, so the questions above are ones we expect to answer rather than deflect: scope stated as artifacts and exclusions written down. Our OEM services cover that path. For budget context first, the cost to develop a hardware product breakdown sets out the line items, and you can book a consultation to walk through your product.