Electronics guide
PCB prototyping for hardware startups.
A printed circuit board is where the electronics of a product stops being a diagram and starts being hardware. PCB prototyping is the process of proving that hardware works and can transfer to production. This is how the stages run, and where the budgets go.
Why it matters
The board is not the product until the firmware runs.
A populated board on the bench is evidence that the hardware is correct. It is not evidence that the product works. Firmware bring up is where the two meet, and it is the task most often underestimated, because it depends on hardware that is correct and hardware that is ready at the same time.
Prototype electronics have to transfer to production.
A board built on modules or an interim schematic proves function but cannot prove cost, size or certification. A production intent prototype, on the final schematic and layout, is what transfers to manufacturing. Building the right prototype for the question keeps the electronics work from being thrown away.
The stages
Five stages from schematic to tested board
The stages run in sequence, but firmware and hardware overlap. The risk is not in any single stage, it is in the dependencies between them, where a delay in one pushes every stage that follows.
- 01
Schematic and design
WHERE THE ELECTRONICS IS DECIDED
The schematic captures the circuit, the component selection and the interfaces. For a first prototype, off the shelf modules and development boards answer function questions quickly and cheaply. For a production intent prototype, a custom schematic with named parts is the only way to answer cost, size and certification questions. The decision between modules and custom silicon is a volume decision, and it belongs up front.
- 02
Layout and fabrication
BARE BOARDS, READY FOR PARTS
The layout places components and routes traces against the stackup, the impedance and the manufacturing rules. Fabrication produces the bare boards, typically 5 to 10 pieces for a prototype run, in one to two weeks. Layer count, copper weight, controlled impedance and finish all move the cost and the lead time. A layout that ignores the fabricator's design rules is a board that comes back wrong.
- 03
Assembly
PARTS ON BOARDS, READY TO POWER
Assembly places and solders the components. For a prototype, this can be manual for through hole and low pin count, or automated for surface mount. Component sourcing is the hidden timeline risk: long lead parts have to be ordered before the board is back from fabrication. A prototype that is ready on the bench but missing a part is not ready, it is waiting, and the wait is usually weeks, not days.
- 04
Firmware bring up
WHERE THE BOARD STARTS TO WORK
Firmware bring up is the first power on, the first signal path verified, the first peripheral initialised. It is where the electronics stops being a collection of parts and starts being a product. Firmware is often the longest single task in a prototype program, and it is the one most often underestimated, because it depends on the hardware being correct and on the hardware being ready at the same time.
- 05
Test and design for EMC
WHAT PRODUCTION AND CERTIFICATION DEMAND
Precompliance testing checks the board against the EMC and safety regimes it will have to pass, before the full certification test. Test points, programming access and fixture datums belong on the prototype, not added later. A board that passes on the bench can still fail EMC, and the fixes are easier on a prototype revision than on a production run. Designing for test from the start keeps the evidence on the critical path.
What moves the cost
Four decisions that set the electronics budget
The stage ranges are wide because the same stage costs very different amounts for different products. These are the decisions that push a build toward the low or the high end of its range.
Modules versus custom design
Off the shelf modules save weeks in a works like prototype and cost yield, size and BOM cost in production. Custom design costs more up front and earns it back at volume. The right answer depends on how much of the electronics is core IP and how many units you will build. The audit establishes this against your actual volume, not against a guess.
Component sourcing and lead time
A prototype board is only as fast as its slowest part. Long lead components, end of life notices and allocation all extend the timeline. Sourcing decisions belong in the schematic stage, not after fabrication, because a part that is unavailable when the board is ready is a redesign. We source through the Shenzhen ecosystem, where lead times are shortest, but the design still has to tolerate alternatives.
Layer count and stackup
A two layer board is cheap and suits simple circuits. Four or six layers are needed for dense routing, controlled impedance or power integrity, and they cost more. The stackup decision is a function of signal integrity, density and cost, and it is cheaper to decide it correctly in layout than to re spin the board after it fails EMC.
Firmware scope
Firmware is where electronics budgets quietly double. A prototype that proves the hardware works still needs the firmware to make the product work, and firmware scope, drivers, comms stacks, application logic, OTA updates, is often larger than the hardware effort. Scoping firmware honestly during the audit keeps the prototype timeline realistic.
Common mistakes
Three patterns that stall a PCB prototype
Designing the board before the schematic is settled.
Routing a board against an unsettled schematic is a commitment to re spin. Every schematic change after layout means rerouting, refabricating and reassembling. The schematic gate exists to make the circuit settled before the layout commits to it, not after.
Ignoring component availability.
A part specified because it was convenient in the CAD library may be out of stock, end of life or allocated. A board built around an unavailable part is a redesign waiting for a re spin. Check availability and alternatives during the schematic, and specify parts your factory can actually source in volume.
Leaving EMC to the certification lab.
A board that passes on the bench can fail EMC on the first test, and the fixes then happen under deadline pressure with a certification booking already paid for. Precompliance testing and design for EMC, grounding, filtering, layout discipline, catch the failures while a board revision is still cheap.
FAQ
What founders ask about PCB prototyping
What is PCB prototyping?
PCB prototyping is the process of designing, fabricating and assembling a small number of printed circuit boards to prove an electronics design before production. It runs from schematic and layout, through bare board fabrication and component assembly, to firmware bring up and precompliance testing. The goal is to answer whether the electronics work and whether they can transfer to manufacturing at volume.
How much does a PCB prototype cost?
Bare board fabrication for a small run of 5 to 10 boards typically costs EUR 100 to 500, depending on layer count, finish and lead time. Assembly with components adds EUR 300 to 2,000, depending on part count and whether placement is manual or automated. Firmware development is usually the largest cost, from a few days to several weeks of engineering. The full breakdown, including what drives each number, is in our cost of prototyping guide.
How long does PCB prototyping take?
Bare board fabrication takes one to two weeks, faster for a surcharge. Assembly takes a few days to a week once parts are on hand. Component sourcing is the variable: long lead parts can add weeks, which is why they are ordered before fabrication. Firmware bring up depends on the complexity of the design and runs in parallel with later hardware work. A straightforward prototype is ready in two to four weeks, a complex one in eight or more.
Should I use off the shelf modules or a custom PCB for a prototype?
Use modules for a works like prototype that proves function quickly and cheaply. Use a custom PCB for a production intent prototype that answers cost, size and certification questions. Modules save time at the start and cost yield, size and BOM at volume. The right answer depends on how much of the electronics is core IP and how many units you will build, which the audit establishes against your actual volume.
How do hardware startups test their PCB prototypes?
Testing runs from power on and signal path verification in firmware bring up, through functional test against the specification, to precompliance EMC and safety testing before certification. Test points, programming access and fixture datums belong on the prototype, so the board can be tested and the evidence collected. A board designed for test is cheaper to validate and produces the records certification and production both demand.
What is the difference between PCB fabrication and PCB assembly?
PCB fabrication produces the bare board, the fibreglass and copper with the traces and pads, but no components. PCB assembly places and solders the components onto the bare board to make a working circuit. Fabrication is a chemical and imaging process, assembly is a placement and soldering process. A prototype needs both, and the timeline for each is different, with assembly dependent on parts being in hand.
Can I use the same PCB prototype for certification?
A production intent prototype, built on the final schematic and layout with the production bill of materials, can be used for certification testing. A works like prototype built on modules or an interim revision cannot, because the certified product has to match the tested design. Precompliance testing on the production intent prototype catches EMC failures while a board revision is still cheap, before the formal certification booking.
How do I move from a PCB prototype to production?
Moving to production means settling the schematic and layout, completing a design for manufacturability review, sourcing the bill of materials in volume, and running a first article inspection on the production assembly. The prototype documentation, the schematic, the layout, the test plan and the precompliance results, is the evidence the production build and the certification depend on. The NPI process governs that handoff, stage by stage.
A guide explains the stages. An audit runs them on your design.
The Production Readiness Audit puts an engineer on your actual files and returns a written report with the electronics scope, the component sourcing risk, the firmware estimate and a clear verdict. If the answer is no, you get the changes that turn it into a yes.
Get your design reviewed