Key takeaways
- A product development firm sells engineering hours and deliverables. It designs and documents your product; it does not manufacture it.
- “ESO” is vendor vocabulary. No professional association, standards body or government agency defines the term.
- The engagement usually stops at design release. You then find the factory, pay for tooling and manage the first build.
- Responsibility does not transfer with the files. Under several regulatory regimes the obligations were always yours.
A product development firm designs and engineers a product for you and hands over the documentation. It does not manufacture. The engagement ends at a released design package, and arranging production, qualifying a factory and carrying legal responsibility for the finished product all remain yours. That boundary is the whole subject of this article, because founders routinely discover it after the design is approved and the budget is spent.
The Product Development and Management Association calls the external version of this a contract developer: an external provider of product development services. Plain, and accurate.
What a product development firm is
It is a services business that sells engineering hours and deliverables. The US industry classification puts this work under NAICS 541330, Engineering Services, which covers applying physical laws and principles of engineering to the design, development and utilization of machines, materials, instruments, structures, processes and systems. Industrial design has its own separate code, 541420, and NAICS codes are mutually exclusive.
The staffing is the product. A typical firm bills a mix of disciplines:
- Electronics and firmware engineers
- Mechanical engineers
- Embedded software developers
- Test and validation engineers, often part time across projects
Those are salaried roles, and US labor data gives the only neutral anchor for what the underlying cost looks like. As of May 2025 the Bureau of Labor Statistics put the median annual wage at $130,220 for electronics engineers except computer, $104,110 for mechanical engineers and $135,980 for software developers. Those are employee wages across the whole economy, not consultancy rates and not project prices. A billing rate has to carry overhead, benefits, utilization and profit on top.
Free checklist: the 24 questions to ask any hardware firm before you hire →What ESO means and why firms use the term
ESO stands for engineering services organization. No professional association, standards body or government agency defines it. We looked. It is vendor vocabulary for the same thing a product development firm does, and it appears most often on the sites of larger outsourcing businesses.
Treat the label as a marketing choice rather than a category with content (see engineering firm vs design firm). What separates firms is scope and staffing, so ask two questions instead:
- Which disciplines are in-house, and which are subcontracted?
- Does the engagement end at a design, or does it continue into production support?
The wider set of labels, and which ones carry real distinctions, is mapped in our guide to the types of product development companies.
What the engagement typically covers
Concept, engineering, and prototype
A full engagement usually runs through requirements, architecture, detailed design, and one or more build-and-test cycles.
A caution on the stage names in the proposal. EVT, DVT and PVT are used across the industry as though they were defined terms, and no standards body, government agency or professional association defines them. Two firms can both quote “through DVT” and mean different scopes, different build quantities and different exit criteria. Get the definitions written into the contract rather than assumed.
Documentation and deliverables
The deliverable is a package, and its completeness is a variable you can specify. IPC-2611, the generic standard for electronic product documentation, treats completeness as a graded requirement rather than a yes-or-no, which is a useful idea to borrow even outside electronics.
What a factory typically needs to build a connected hardware product:
| Deliverable | Why the factory needs it |
|---|---|
| Dimensioned drawings with tolerances, plus a 3D model for tooling | A factory quotes and inspects against the drawing, not the model |
| PCB fabrication and assembly files | What a board house and assembler build and place parts from |
| Bill of materials with manufacturer part numbers | Generic descriptions cannot be sourced or second-sourced |
| Production firmware image and programming instructions | What the line loads and verifies on every unit |
| Test procedures and acceptance criteria | Defines what a passing unit is |
| Assembly drawings and work instructions | Tells the line how to build it |
Exactly what a firm delivers, and in which formats, should be set out in the agreed scope rather than assumed. At Inventornest, every client gets the full information from each stage: specifications, process documents, the parts list, test results and certification records.
Dimensioning and tolerancing practice is standardized (ASME Y14.5-2018, reaffirmed in 2024) and now explicitly covers models defined in digital data files, not just paper drawings. Quality management standards likewise treat design outputs and design changes as controlled items. Ask which standard the firm works to, and whether design sits inside the scope of any certificate it holds.
Where the engagement usually stops
The handoff to a separate manufacturer
The design firm releases the package. You then find a factory, get quotes, pay for tooling, and manage the first builds. Our article on what an EMS company is covers what a factory needs before it can even quote, and what a rapid prototyping shop is covers the vendors that make parts along the way.
The transfer itself is a recognized discipline with a standard behind it, at least in regulated categories. ISO 13485 Clause 7.3.8 covers design and development transfer, and requires procedures ensuring design outputs are verified as suitable for manufacturing before they become final production specifications.
For medical devices in the US that clause is now law by reference. Since 2 February 2026, 21 CFR 820.10(c) requires manufacturers of class II, class III and listed class I devices to comply with the design and development clause of ISO 13485. The former standalone design controls section, 21 CFR 820.30, is now reserved. A great deal of published guidance still cites it.
What the handoff gap costs you
The gap is rarely a single invoice. It shows up as:
- A tooling quote that arrives with a list of required design changes, after the design was signed off.
- Parts that pass inspection while the assembly still does not work, with each vendor pointing at the other.
- A bill of materials that cannot be bought at the quantities and lead times the schedule assumed.
- A second engineering engagement, priced separately, to make the design manufacturable.
Designing manufacturability in early is the mitigation, and it has a definition worth holding vendors to. The PDMA describes design for manufacturability as the systematic consideration of manufacturing issues during design and development, facilitating fabrication of components and their assembly into the product. Note that guidance exists, IPC-2231A “DFX Guidelines” being the electronics reference, but nothing makes DFM certifiable. No firm can hold a certificate saying it did DFM, so the requirement lives in your contract or nowhere.
What you are responsible for after handoff
Responsibility does not transfer with the files. In several regimes it was always yours.
Under FDA’s quality system rules, “manufacturer” means any person who designs, manufactures, fabricates, assembles or processes a finished device. Design is first in that list. Separately, FDA’s registration rules treat “initiation of specifications for devices that are manufactured by a second party for subsequent commercial distribution by the person initiating specifications” as manufacturing activity. Commission the design, have someone else build it, sell it under your name, and you are the manufacturer.
Consumer products reach the same destination by a different route. Under 15 U.S.C. 2052 a manufacturer is anyone who manufactures or imports a consumer product. CPSC’s certification rule at 16 CFR 1110.7 then puts the certificate on the importer for goods made abroad, and on the US manufacturer for goods made domestically, or on the private labeler where a domestically made product is privately labeled and the manufacturer does not certify. The trigger there is importing or branding rather than designing, so the mechanism differs, though the outcome for a founder importing their own product is the same.
Practical list of what stays with you:
- Selecting and qualifying the factory
- Paying for and owning tooling
- Regulatory registration, certification and labeling
- Product liability and recalls
- Deciding what a passing unit is, and enforcing it
When a design-only firm is the right call
The model works well in specific conditions:
- You already have a manufacturing relationship, and need only the engineering.
- Your company has operations capability but a gap in one engineering discipline.
- The product is a variant of something you already build, so the handoff is routine.
- You want the design to be portable between factories, and are willing to manage that yourself.
It works badly when a first-time founder assumes the finished design equals a finished product. If you are choosing between this and a single accountable partner, our guide to choosing a hardware product development partner frames that decision.
Frequently asked questions
Does a product development firm build my product?
No. It designs and engineers the product and delivers documentation, sometimes with prototypes. Volume manufacturing is a separate vendor and a separate contract.
Is an ESO different from a product development firm?
Not in substance. Engineering services organization is vendor terminology with no standards or association definition behind it. Compare scope and staffing rather than labels.
What should I receive at the end?
Whatever the agreed scope lists, typically drawings, a bill of materials with real part numbers, test procedures and assembly instructions. Check the deliverables list before you sign. At Inventornest, every client gets the full information from each stage: specifications, process documents, the parts list, test results and certification records.
Who is legally the manufacturer if a firm designs my product?
Usually you. FDA’s definition of manufacturer begins with whoever designs the device, and consumer product rules place duties on the importer or private labeler. Confirm your position with an attorney for your specific product and market.
Can a design firm recommend a factory?
Many will, and the introduction is useful. Ask whether any commercial relationship exists between them, since that changes how the recommendation should be weighed.
What is the most common mistake with this model?
Treating design release as the finish line. The released package is the point at which sourcing, tooling, certification and quality decisions start, and all of them are yours.
Where Inventornest fits
Inventornest does the engineering and, depending on the agreed scope, supports production rather than stopping at design release. Mechanical, electronics and firmware engineering sit in one team. We retain responsibility for engineering coordination and design clarification when production is handled by our manufacturing partners.
A design-only firm is the better choice when you already have manufacturing sorted and want the design portable between factories. That is a real advantage of the model, and we will say so when it fits your situation better than ours.
You can review the scope of our outsourced product development, or book a consultation to talk through where your engagement should stop. If a full firm engagement is more than you need, consulting at any stage gives you expert input on just the part you are stuck on.
