The True Cost of PCB Design: A Practical Cost-per-Board Model

A software license is one part of PCB design cost. To compare workflows, measure the resources needed to reach the same release standard: a reviewed design, manufacturing outputs and the required validation. Count both the visible invoices and the engineering effort, while keeping schedule forecasts separate from actual expenditure.

Define the cost boundary first

Decide whether the model stops at fabrication release, assembled prototypes or validated hardware. Comparing one workflow's routed candidate with another workflow's tested board produces a misleading result. Use the same board scope, constraints and acceptance criteria for both.

• Software and services: licenses, project fees, support and required add-ons.
• Engineering: preparation, placement, routing, review, cleanup and release documentation.
• Physical work: fabrication, assembly and testing when included in the chosen boundary.
• Rework: diagnosed changes and repeat builds, counted once.
• Enablement: training, libraries, integration and IT support.

Turn effort into a cost per board

Use your finance team's loaded hourly rate. Salary alone does not include every employer cost. Record active engineering hours separately from unattended computation and calendar waiting time.

Engineering cost = total active hours × loaded hourly rate.

Cost per released board = allocated software and service cost + engineering cost + included build and test costs.

Illustrative calculation

Assume 100 active hours at $100/hour, $1,000 of allocated software/services and $2,000 of prototype work. The modeled total is $13,000. If an alternative workflow requires 70 active hours, its total before any additional automation fee is $10,000. The difference is $3,000; subtract the actual incremental fee and any extra integration or verification cost to obtain the modeled net saving.

These are hypothetical inputs, not Quilter prices or measured performance. The example assumes equal build costs and unchanged quality requirements. It makes no assumed improvement in respin rate.

Handle uncertainty explicitly

Use low, central and high cases for uncertain engineering effort and repeat-build cost. If you use expected rework cost, calculate probability multiplied by cost per event and document the basis. Do not count the same debugging labor in both normal effort and the rework allowance.

Earlier delivery may have business value, but that value is not automatically a cash saving. Report it separately with its assumptions and confidence level. A quicker candidate does not itself prove earlier manufacturing or validation.

Where Quilter fits

Quilter adds placement and routing automation to an existing CAD workflow; engineers still review the output and own release decisions. Its current pricing page describes per-project pricing based on pins to route. Obtain a quote for the actual project and deployment instead of inserting a generic per-board price.

For a useful pilot, track input preparation, automated runtime, candidate review, cleanup, final checks and any repeat work separately. Compare the total with a documented baseline, then use the results to budget the next board.