PCB Design Outsourcing Versus an In-House Engineering Team
The decision to build an engineering team or to buy engineering time is presented as a cost question, and cost is only part of it. A company that hires will own the capability and will also own the fixed cost, the recruitment risk and the management overhead. A company that outsources buys a variable cost and a schedule, and gives up some of the control that comes with employment. PCB design outsourcing is the right answer for some companies and the wrong answer for others, and the difference is usually in the shape of the workload rather than in the hourly rate.
The Fixed Cost of an In-house Team
The visible cost of an in-house engineer is the salary. The full cost includes the workstation, the software licences, the laboratory equipment, the training, the management time and the recruitment effort, and it is incurred whether or not there is work to be done. That last characteristic is what makes the model expensive for a company whose design workload is intermittent.
The recruitment problem is the second issue and it is frequently underestimated. A competent designer who can take a requirement through the schematic, the layout, the review and the release is not easy to find, and the search takes months during which the schedule is stalled. Once the person has been hired, the company is dependent on them, and the departure of a single individual can remove the capability entirely.
The third issue is coverage. A small team cannot contain specialists in every discipline, so a design that touches high speed routing, a switching supply, an analog front end and a wireless interface is likely to be strong in one area and weak in another, and the weakness is not always visible from inside the team.
The Variable Cost of PCB Design Outsourcing
The outsourcing model converts the fixed cost into a cost per project. The company pays for the work it needs and nothing in the quiet periods, and the engineering resource can be scaled up for a launch and down afterwards without a recruitment cycle. For a company whose products arrive in bursts, that flexibility is worth more than the difference in the nominal hourly rate.
The second advantage is design resource depth. A design house works across many products and many domains, so a requirement that is unfamiliar to one customer is familiar to the team, and the second project in a domain is faster and less risky than the first. The customer receives the benefit of the previous work without having paid for it.
The third advantage is objectivity. An external team reviews the requirement rather than inheriting the assumptions that grew inside the company, and it is more willing to say that a specification is unclear or that a target is not achievable. That willingness is difficult to maintain inside an organisation where the assumptions have become part of the product’s history.
What Outsourcing Requires From the Customer
The model depends on the customer being able to state the requirement and to make decisions. A project stalls when the specification is unclear, when the review points are not attended, or when the person who owns the decision is not in the room. None of those is a failing of the supplier, and all of them are common.
The second requirement is a defined boundary. Which parts of the work are inside the engagement and which are not has to be written down: the schematic, the layout, the firmware, the prototype build, the compliance work, the document release. A boundary that is left to develop naturally produces a disagreement about scope at the least convenient moment.
The third is access to the information the design depends on. The mechanical envelope, the connector list, the existing platform, the certification requirement and the cost target are all inputs, and an engagement that begins without them will spend its first weeks discovering them.
Where the Decision Usually Falls
The pattern that emerges from practice is that a company with a continuous stream of similar designs is better served by an in-house team, because the learning curve is paid for once and applied repeatedly. A company with a single product, a product that changes rapidly, or a workload that varies sharply is better served by outsourcing, because the flexibility is worth more than the retention of the knowledge.
The two can also be combined. A company that keeps one engineer to own the architecture and the product knowledge, and buys the detailed layout work where the volume demands it, obtains the continuity of the internal role and the elasticity of the external one. That arrangement is common and it works, provided the boundary between the two is defined.
The Questions Worth Asking
An outsourced design engagement is worth evaluating on the same criteria as any other engineering service. Who will do the work, and what have they designed before? How is the design reviewed before it is released, and against what? How are the manufacturing and assembly constraints taken into account, and are they known to the person doing the layout? What is delivered at the end, and in what form?
The answers describe the process rather than the price, and the process is what determines whether the delivered design can be manufactured. Our PCB design and layout service works beside the fabrication and assembly operations, so the capability limits published under PCB capabilities are applied while the layout is being drawn rather than checked afterwards. The design then moves through PCB manufacturing, SMT assembly, component procurement and PCBA testing inside the same organisation.
How the Engineering Cost Is Really Formed
The comparison is usually made between an annual salary and a project quotation, and the two numbers are not comparable because they cover different things. The salary covers the person. The project quotation covers the design, and the design includes the schematic, the layout, the review, the manufacturing data, the assembly support and the corrections that follow the first prototype.
A more useful comparison puts the total engineering cost on one side and the total cost of the engagement on the other, over the period the product will exist rather than over the year. A product that will be revised five times and built for three years carries its design cost across all of it, and a design that was produced once and then maintained by the same team often turns out to be cheaper than the quotation suggested at the outset.
The hidden cost of the in-house route is the ramp. A new engineer spends their first months learning the product, the platform and the conventions, and that time is paid for without producing output. The hidden cost of the outsourced route is the transfer of knowledge at the end of the engagement, which is worth managing deliberately rather than discovering when the relationship ends.
What the Design Resource Decides
Whichever route is chosen, the quality of the delivered design is decided by the same four things: the completeness of the requirement, the review before release, the awareness of the manufacturing constraints and the quality of the data that is handed to production. Those are properties of a process rather than of an employment relationship, and a company that holds an in-house team to them will obtain better designs than one that does not, just as a company that requires them of an external supplier will.
The converse is also true. An internal team that is never reviewed and never asked to justify its choices will produce designs that work and are difficult to manufacture, and the cost of that appears later as an assembly price or as a defect rate rather than as an engineering line item.
FAQ
Is outsourcing cheaper? It is cheaper when the workload is intermittent, because the fixed cost is avoided. For a continuous workload the comparison changes.
Who owns the design data? The customer, who receives the artwork, the bill of materials, the coordinates, the programme where applicable and the native design files.
What makes an outsourced project fail? An unclear specification, a decision that is never made and a scope that was never written down.
