Circuit board design costs: how is your project cost calculated?

Separate design fees from PCB manufacturing costs

The one-time development budget may cover requirements clarification, schematics, PCB layout, software and validation. Per-board production costs include the bare PCB, electronic components, assembly, programming, inspection and final assembly where required. Custom test fixtures, enclosure development and external laboratory work are defined separately. Combining everything into a single 'PCB price' makes it harder to understand which costs recur in later production orders.

For example, the initial design and software work for a remote temperature monitor is not repeated for every subsequent board. However, the sensor, processor, communication module and testing add cost to every unit. New features or hardware changes may require a new development budget. The first quotation should also identify the approved version and quantity assumptions used to calculate later repeat orders.

Which requirements affect circuit design costs?

Board size is not the only factor. The number of sensor types, motor or valve control, measurement accuracy, power source, battery life and operating environment affect the engineering scope. A device connected to a local network over Wi-Fi has different software and testing requirements from one managed remotely over a cellular connection. Discuss the display, user settings, data storage and update method from the outset.

Mechanical constraints also matter: fitting an existing enclosure, matching specific connectors or operating on a vibrating machine requires additional design decisions. Separating essential features from later-version features makes the first-stage budget clearer. You do not need to know component choices, layer counts or processor models; describe the intended behaviour and operating conditions.

Having an existing board does not mean its design can be reused directly. The availability and condition of editable files, rights to use them, component availability and requested changes must be reviewed. A seemingly minor component change can affect the software, layout or tests. Compare revising the board with creating a new design in terms of the functions to retain and the validation work required.

Compare board revision and new design options →

Define prototype quantities and acceptance conditions for the first prototype

The cost of an electronic prototype is more than printing a few PCBs. Components must be procured and assembled, the board brought up and programmed, and target functions tested. An initial demonstration using development tools, a custom PCB prototype and a production-ready device are different delivery stages. Document which stage the quotation covers, how many prototypes are included and how prototype shortcomings will be handled.

Express acceptance criteria from the user's perspective: does the device read the specified sensors, preserve records through power loss and resume data transfer when reconnected? Measurement and environmental targets require an appropriate test scope. Revision conditions should distinguish new requests from findings that fail to meet the agreed scope. Decisions about a second prototype and additional work can then be based on concrete results.

Production volume, component supply and testing affect unit cost

Do not treat the unit price of a few prototypes as the series-production price. Production preparation, purchasing quantities and testing arrangements may change with volume. State the first-batch quantity and expected subsequent quantities separately. Ask which date and supply conditions underpin component prices and who approves alternatives. Higher volume does not produce the same discount in every project.

Supply continuity matters alongside low component prices. Manufacturer product status and technical characteristics inform selection; replacing an unavailable component may require design changes and testing. Budgeting for programming and functional checks on every board supports consistent repeat production. Removing testing to reduce price is a different decision from simplifying the design to reduce cost.

Prepare a brief project description for quotations

A one-page description can be enough to begin. State the device's function, users, power source, connected equipment, operating environment and approximate quantities. Include files for your existing board and the reason for redesign where applicable. Instead of simply saying 'urgent', give the target date and the delivery expected by then: a working prototype, a field trial or a first production batch.

Sharing an available budget range can help choose the initial stage. A limited prototype validating the core function can precede a complete product. However, discuss how much of that work will transfer to the later custom board. You can request an NDA before sharing confidential details; the initial discussion can establish the required assessment files from the general objective and current status.

• Device function, interfaces and operating environment
• Existing design files or reference product information
• Initial prototype and subsequent production quantities
• Target date, acceptance conditions and expected delivery

Compare quotations by deliverables and responsibilities

When evaluating circuit board suppliers, compare design, software, prototypes, testing, revisions and file delivery using the same checklist. If performance is guaranteed, establish how it will be measured. Changes after delivery, production support, payment stages and third-party costs should be explained separately. Clarify ambiguous items in writing rather than assuming they are included in a low price.

At the end of VOMRO projects, editable schematics and PCB designs, source code, manufacturing outputs and technical documents developed within scope are delivered. Third-party software, libraries and tools are explained with their own licences. Share your project's purpose and expected quantities to begin; after technical assessment, we can define development stages, acceptance conditions and comparable cost items together.

Explore the server and software scope for connected devices →