Build in-house or outsource — who should develop your hardware

Every company building a product with hardware in it reaches this question, usually right when the prototype starts working: hire engineers and build a team, or hand the embedded development and PCB design to an outside group. There is no single right answer — but there is an orderly way to decide, and it does not start with money.

First: one-off or ongoing

The first question is not "what does it cost" but "how many times will this happen". If hardware is the core of your product and will change every quarter, the knowledge has to live in-house, and embedded development outsourcing only postpones a hire you will make anyway. If you need one board to mature into production, followed mostly by firmware maintenance, then a full team sitting idle after revision B is the genuinely expensive decision.

The real arithmetic of hiring

A salaried engineer costs more than a salary: months of recruiting in the current market, equipment and licences, and ramp-up time before they know the domain. More important — one engineer is not a team. A product needs firmware, circuit design and layout, and those are three different specialties that very rarely live in one person.

Outsourcing turns that fixed cost into a variable one: you pay for a project, not for a year. The hourly rate is higher — but you pay only for the hours the project actually needs, and you get several specialties in parallel instead of one.

The expertise cliff

Projects almost never stall in the first 90%. Bringing up a board, getting UART running, writing a driver — any good engineer will do that. Trouble starts in the last ten percent: an EMC test that fails, a power rail that sags under load, a component that goes end-of-life mid-project, certification. These are problems someone who has solved them five times closes in a week, and someone meeting them for the first time burns a quarter on.

This is the factor hardest to price up front, which is why it gets ignored. Worth asking honestly: does the project contain a stage nobody on the team has taken end-to-end before?

When outsourcing is the right call

• You need a manufactured board and nobody in the company has PCB design experience
• The schedule is shorter than a hiring cycle — the investor is waiting for a demo, not a recruitment round
• The project is a one-off, and a team would sit idle after it
• A narrow specialty is missing: RF, high power, ultra-low current draw, certification

When to hire

• The hardware is your competitive edge and will evolve for years
• There is already a steady stream of work: production support, revisions, field issues
• The knowledge itself must stay in the building — not just the files

The answer most companies land on

In practice, many companies choose something in between: outsource the PCB design and the first revisions, and hire early on the firmware side — because firmware is where the product keeps living for years after the board settles. Full disclosure: this is exactly the service inteRFace R&D sells — embedded development and PCB design services, end to end, from a team in Israel — but the framework above holds against any vendor you pick.

What to demand from any vendor

• Full IP ownership: schematics, fabrication files and source code sit with you, not with them
• Documentation that lets the next engineer continue without phone calls
• A proper handover stage, including knowledge transfer to the team you hire later

A hardware development partner that hesitates to commit to those three items has answered your question — just from the other direction.