Product Development Team: Roles, Structure and Cost

A product development team is more than engineers. Here are the core roles, when each one joins, and what in-house versus outsourced structures actually cost.

June 7, 20185 min read

Written by Konstantin Dolgan, Ph.D., NPDP

Founder & CEO, Product Development Engineer

Published June 7, 2018Updated August 20, 2026

A product development team is the cross-functional group that takes a product from requirements to production. For physical products that means design, mechanical, electrical, manufacturing and quality working against one schedule. Understaff any one of those and the program does not fail immediately - it fails at tooling, which is the most expensive place to discover a problem.

Diagram of a product development team structure showing core roles around a central program — The core roles on a hardware product development team and the phase each one joins.

Core roles and when they join

Role	Owns	Joins at	Typical US salary
Product manager	Requirements, tradeoffs, roadmap	Kickoff	$120k-$180k
Industrial designer	Form, ergonomics, user experience	Concept	$85k-$140k
Mechanical engineer	Architecture, mechanisms, materials	Concept development	$95k-$150k
Electrical / firmware engineer	PCBA, power, embedded software	Design development	$110k-$170k
DFM / manufacturing engineer	Process selection, tooling, cost	Design for manufacture	$100k-$155k
QA and regulatory	Verification, validation, compliance	Design verification	$95k-$150k

Three ways to structure the team

In-house - highest control and retained knowledge, but a full hardware team costs $600k-$900k per year loaded before tooling, and idles between programs.
Outsourced product development firm - one accountable partner covering all disciplines, typically $25k-$90k per month for an active program, scaled down between phases.
Hybrid - internal product manager and system owner, external design and engineering capacity. Most common for companies shipping one to three products a year.

What a program costs by phase

Phase	Team involved	Duration	Typical cost
Discovery and requirements	PM, ID	3-6 weeks	$15k-$45k
Concept development	ID, ME	4-8 weeks	$30k-$90k
Detailed design	ME, EE, firmware	10-20 weeks	$90k-$300k
Prototyping and testing	Full team	6-14 weeks	$40k-$150k
Design for manufacture	ME, DFM, supplier	6-12 weeks	$45k-$120k
Pilot production	DFM, QA	8-16 weeks	$50k-$250k

Signals that the team is structured wrong

Manufacturing joins after the design is frozen - guaranteed rework at tooling.
No single owner of requirements, so scope shifts silently between reviews.
Design reviews with no supplier present and no cost target on the agenda.
Regulatory work starts after the first working unit rather than as a design input.
Prototype iterations measured in months because fabrication is outsourced ad hoc rather than planned.

Our own structure is built to avoid exactly these failure modes - design, engineering and manufacturing sit on one program team from week one. See how we run engagements on the product development consulting page.

What a hardware team costs

Role	US in-house (loaded)	Agency or contract	When you actually need it
Product manager	$140k-$200k	$90-$160/hr	From day one
Industrial designer	$110k-$160k	$85-$150/hr	Concept through DVT
Mechanical engineer	$130k-$185k	$95-$170/hr	EVT onward, continuous
Electrical engineer	$145k-$200k	$110-$190/hr	EVT and DVT bursts
Firmware engineer	$150k-$210k	$100-$180/hr	EVT through launch
Quality / DFM engineer	$120k-$170k	$85-$150/hr	DVT onward
Sourcing and supply chain	$110k-$160k	$70-$130/hr	From DVT

Hire, contract or agency

Hire the roles that carry institutional memory: product management and the lead mechanical or systems engineer.
Contract the burst roles: RF, compliance, packaging and test fixture design come and go.
Use an agency when you need a full stack quickly and have no engineering manager to coordinate contractors.
Never outsource the DFM relationship entirely. Someone on your payroll must be able to argue with the factory.
Budget 15-25% of engineering spend for post-launch sustaining. Teams that skip it stall on their second product.

Staffing a team you cannot afford to hire

Most first products are built by a team that does not exist on anyone's payroll. The roles still have to be covered — they just get covered by a mix of founders, contractors and a development partner. The failure mode is not missing people; it is unnamed responsibility, where three parties each assume someone else owns thermal, or compliance, or the bill of materials.

Role	Hire	Contract	Partner firm	Cost signal
Product owner / decision maker	Always in-house	No	No	Founder time
Industrial design	Rarely early	Yes	Yes	$8k–$40k per program
Mechanical engineering	At scale	Yes	Yes	$120–$220/hr
Electronics / firmware	At scale	Yes	Yes	$130–$250/hr
Manufacturing / supply chain	Before tooling	Yes	Yes	$100–$180/hr
Quality and compliance	Regulated products only	Yes	Yes	$8k–$40k per certification

How the team changes by stage

Discovery: two or three people. Product owner, a designer and one engineer who can say what is physically possible.
Concept and prototype: add discipline engineers as the architecture firms up; this is the widest the team gets relative to output.
Detailed design: mechanical and electronics carry the load; add a manufacturing engineer before tooling, not after.
Pilot and launch: quality, supply chain and support come forward; design engineers move to a support role rather than leaving.
Post-launch: a small sustaining team handles the first revision, field data and cost reduction.

The meetings that are worth the hours

Hardware teams do not need more meetings; they need three specific ones. A weekly design review with the actual open questions on the agenda. A phase gate at each stage transition with an explicit go/no-go and a named approver. And a risk review that reads the top ten risks aloud — the item nobody wants to discuss is almost always the one that later slips the schedule. Everything else can be asynchronous.

If you are covering these roles with a small internal team plus outside help, our product development consulting engagements are designed to slot into exactly that structure.

Frequently asked questions

What is a product development team?

It is the cross-functional group responsible for turning a product concept into a manufacturable, compliant product - typically product management, industrial design, mechanical and electrical engineering, manufacturing engineering, and quality or regulatory.

How big should a product development team be?

A simple consumer product can run with 3-5 people. A connected or regulated device typically needs 7-12 across mechanical, electrical, firmware, manufacturing and quality. Size the team to the number of technologies in the product, not to the schedule.

Is it cheaper to outsource product development?

For companies launching fewer than about three products a year, usually yes. An outsourced team costs $25k-$90k per month only while a program is active, versus $600k-$900k a year for an equivalent in-house team that idles between programs.

When should manufacturing join the team?

At concept development, not after design freeze. Process selection constrains geometry, materials and tolerances, and reversing those decisions after tooling quotes is the single most common source of cost overruns.

Who belongs on a product development team

A hardware team is not a software team with a machine shop attached. The roles arrive at different times, and hiring them in the wrong order is the most common way small companies burn a year. Early on you need breadth - one systems-minded engineer who can define requirements and say no. Depth in manufacturing, compliance and quality is needed later, and much of it is better rented than hired.

Cross-functional product development team reviewing sticky notes on a whiteboard while an engineer holds a grey prototype housing

Role	When they join	Hire or contract	US cost range
Product owner / systems engineer	Day one	Hire	$120k-$180k per year
Mechanical engineer	Concept phase	Hire or contract	$95k-$150k or $95-$150 per hour
Electrical / firmware engineer	Works-like phase	Contract first	$110k-$170k or $110-$185 per hour
Industrial designer	Concept phase	Contract	$85-$160 per hour
Manufacturing / DFM engineer	Before tooling	Contract	$110-$175 per hour
Quality and compliance	Before verification	Contract	$120-$200 per hour
Supply chain / sourcing	Pilot phase	Hire when volume justifies	$85k-$140k per year

Team structures that work at different stages

Founder plus agency (0-1 product). Cheapest path to a validated design; the risk is knowledge leaving with the contract.
Small core team plus specialists (1-3 products). Two or three staff engineers own the architecture, everything narrow is contracted.
Functional departments (10+ SKUs). Mechanical, electrical and quality groups with a program manager coordinating gates.
Platform teams (mature portfolio). Shared subsystems - power, connectivity, enclosure family - maintained centrally and consumed by product squads.

How to keep a small team from stalling

Three practices carry disproportionate weight: a single written requirements document that everyone signs, a weekly build-and-test cadence so decisions are settled by hardware rather than opinion, and one named decision maker per subsystem. Teams that run consensus on every trade-off do not converge; they oscillate until the budget runs out.

Key takeaway 1: Hire breadth first, rent depth later.
Key takeaway 2: Manufacturing and compliance expertise must arrive before tooling, not after.
Key takeaway 3: Structure follows portfolio size - do not build departments for one product.
Key takeaway 4: One owner per subsystem beats consensus on every decision.

Handoffs that quietly break a product development team

Most delays in a product development team are not caused by slow work; they are caused by handoffs where information is lost or ownership becomes ambiguous. Naming the handoffs and defining what must transfer at each one removes a surprising amount of schedule risk at no cost.

Critical handoffs and what must transfer

Handoff	What must transfer	Common failure
Research to design	Prioritized requirements with rationale	Design invents its own requirements
Industrial to mechanical design	Surfaces plus intent and tolerances	Aesthetic intent lost in engineering
Design to prototyping	Full build package and known risks	Prototype tests the wrong thing
Engineering to supplier	Drawings, GD&T, cosmetic spec	Supplier interprets, then argues
Development to production	Validated process and control plan	Yield collapses at ramp
Production to support	Failure modes and service parts	Support learns from customers

The cheapest fix is a short written handoff note per transition, listing what is complete, what is open and who owns each open item. It takes twenty minutes and routinely saves weeks.

Handoff discipline checklist

List every handoff in your program and name both sides.
Define the artifacts required at each transfer.
Write a short handoff note with open items and owners.
Keep the sending side available for questions afterwards.
Review missed handoff information in retrospectives.

Key takeaways

Handoffs, not slow work, cause most program delays.
Define required artifacts and open-item ownership per transition.
A twenty-minute handoff note routinely saves weeks.

Need to fill gaps in your product development team?

Talk to our team

Work with LA NPDT: if you are moving from here to execution, start with our our product development process or talk to us about end-to-end product development.

Sources and standards

USPTO — patent basics — Official guidance on provisional and non-provisional filings for new products.
NIST Manufacturing Extension Partnership — Federal program supporting US small and mid-size manufacturers.
ISO 9001 quality management — The quality-system standard most contract manufacturers are audited against.

Filed under:Education News

Tagged:Idea Marketing Innovation Marketing Innovative Product Design Product Design

All articles

Product Engineering Company: What They Do, What They Cost, How to Pick One
A product engineering company turns a product idea into a manufacturable design. Here is the full scope, the cost of each stage, and how to tell a real team from a sales deck.
Engineering Trade-Offs: Balancing Cost, Performance, and Time-to-Market
In today’s fast moving landscape – defined by intense global competition, rapid technological progress, and increasingly sophisticated customer expectations – product life cy
Mold Flow Analysis: How It Cuts Injection Molding Cost
Injection molding cost is decided by tool steel, cavity count, geometry, resin and tolerances long before the first shot. Here is what each lever is worth and which savings are safe.