Prototype BOM Budget: How to Plan What a Build Will Cost

A prototype BOM budget is the priced parts list for your build, multiplied by the number of boards you will make, then padded for the things a spreadsheet never shows. Those are shipping, scrap, spare parts, and the second and third revision. Price every line at the quantity you will actually buy. Add a landed-cost factor and a contingency, and keep the BOM separate from engineering time, because the two answer different questions.

This guide walks through that method step by step, with a worked example and the mistakes that most often blow up an early budget.

TL;DR

• Price each line at your real order quantity (often 1 to 100 pieces), not at the 1,000-piece break shown in a datasheet or a quote for production.
• Multiply per-unit prototype costs by a landed-cost factor of 1.2x to 1.5x for shipping, duties and procurement overhead, then add a 15-20% contingency.
• Budget for several board spins. Practitioners plan 3 to 7 iterations at the engineering prototype stage, not one.
• Keep parts, one-time setup (NRE, tooling) and engineering time as separate lines. Parts are usually the smaller number.
• Re-price before you order. Stock and price move, so a BOM priced last month is a guess.

Table of Contents

• What a prototype BOM budget actually covers
• The three buckets: per-unit, one-time, and infrastructure
• Step 1: Get a clean BOM
• Step 2: Price at the quantity you will really buy
• Step 3: Add the costs that are not parts
• Step 4: Budget for revisions, not one build
• A worked example
• Where the real money goes: engineering time
• Match the prototype to the question
• Our perspective: price it while you design it
• Price your BOM in minutes
• A short checklist before you order
• FAQ
• Sources

What a prototype BOM budget actually covers

The bill of materials is the list of every part on the board, with quantity and manufacturer part number. A budget built on it answers a narrower question than "what will this product cost?" It answers: how much cash do I need to get the next round of boards built and powered up?

That matters because prototype cost and production cost are different numbers. At production volume you care about the 1,000- or 10,000-piece price and a negotiated supplier. At prototype volume you pay break-for-one pricing, minimum order quantities, cut-tape fees, and shipping on several small orders from several sellers. A part that costs a few cents at volume can cost many times that for a pack of ten.

The cost-reduction side of this topic, price tiers and what to cut once you are scaling, is covered in our guide to BOM cost reduction for hardware teams. This article is about the earlier job: setting a number you can defend before the first order goes out.

The three buckets: per-unit, one-time, and infrastructure

The most useful framing we have seen splits prototype spending into three buckets: recurring per-unit costs, one-time setup costs such as NRE, tooling and pre-compliance scans, and internal infrastructure such as lab equipment.

Your BOM lives almost entirely in the first bucket. Treat it that way.

Mixing these produces the classic error. If you spread a one-time fixture cost across five boards, it looks like each board is expensive. If you leave it out, the first build looks cheap and the budget breaks on the second.

Step 1: Get a clean BOM

Before any pricing, the BOM has to be priceable. That means:

1. Every line has a manufacturer part number, not just "10k resistor." A value and package describe thousands of parts.
2. Quantities are per board, with a separate field for how many boards you are building.
3. Do-not-place lines are marked. Test points, optional footprints and mounting hardware you source elsewhere should not silently inflate or vanish from the total.
4. Mechanical and cable items are included. Connectors, standoffs, headers, and the battery holder are easy to forget because they are not on the schematic in the same way.

If your design is in KiCad, Altium or Eagle, export the BOM from the tool rather than retyping it. A retyped BOM is where the mistakes enter. Our write-up on how engineers track BOM pricing from spreadsheet to ERP covers the fields worth keeping as the BOM matures.

Step 2: Price at the quantity you will really buy

Price breaks are why the same BOM can show wildly different totals. A distributor listing may show prices at 1, 10, 100 and 1,000 pieces. For a five-board prototype run, you are usually buying at the first or second tier, plus a few spares.

Two rules keep this honest:

• Multiply before you look up. If a part appears twice per board and you are building ten boards with two spares, you need 24 pieces, and that decides which price tier applies.
• Round up to the package, not the need. Many small passives ship in reels or strips with a minimum. Needing 12 pieces and paying for a cut-tape minimum of 50 is normal. Count the minimum, not your need.

Then check where the number came from. A price from a live distributor feed is not the same as an old listing, and a listing that says "in stock" with stale data is how a budget turns into a surprise. Circuit Center's search says plainly whether a price comes from a live feed or an older listing, which is the first thing worth checking on any expensive line.

Find the 20% of lines that carry 80% of the cost

Sort the priced BOM by extended cost. In most boards a handful of lines dominate: the microcontroller or SoC, a radio module, a power IC, a display, a large connector. Spend your attention there.

For each of these ask three things:

• Is it in stock at the quantity you need, from more than one seller?
• Is there a lifecycle warning? See our guide to spotting component lifecycle risk before it hits your BOM.
• If you had to swap it, is there a drop-in? The checks before a BOM swap are worth reading before you assume a cross-reference is equivalent.

The cheap passives rarely sink a budget. A single unavailable controller can sink a schedule.

Step 3: Add the costs that are not parts

A parts total is not a build cost. For a prototype, these are the lines to add, in roughly the order they bite.

Bare PCB and assembly

Fabrication and assembly are quoted separately from parts, and for small runs they can rival the component cost. Setup items like stencils and machine programming are one-time charges spread over very few boards. As one low-volume assembly guide points out in a worked example, a stencil fee that disappears across a production run becomes a visible per-board cost at around 50 boards. Get a quote for your actual quantity and layer count instead of using a per-board rule of thumb.

Landed cost

Shipping, import duties and the time spent buying are real costs. The guidance we trust here multiplies low-volume per-unit costs by a landed cost factor of 1.2x to 1.5x. Use the low end if everything ships domestically from two sellers. Use the high end if you are mixing international sources or buying from many small suppliers.

If one part is blocking the build, local pickup can save the freight and the wait. That is what our Parts for Pickup map is for: it shows nearby suppliers with a pickup counter. Our piece on finding local electronics suppliers with same-day stock goes through how to use that route without paying a premium for convenience.

Yield loss and spares

Build more boards than you need, and buy more parts than the boards use. You will lose parts to reflow mistakes, wrong orientation, dropped reels and the board you probe too aggressively. A common starting rule is to add a spare allowance of 10% on passives and a spare unit or two on expensive ICs. Treat these as starting points to adjust to your own build, not as industry law.

Contingency

On top of everything, add a contingency. Experienced teams use 15-20% on total estimates to cover supplier changes and design iterations. If the design is new and the supply chain is unproven, take the top of that range.

Step 4: Budget for revisions, not one build

The most common structural error is to budget a single prototype. The second or third revision is usually where a design becomes manufacturable, and engineering-stage projects often run 3 to 7 iterations before the design freezes.

That does not mean multiplying the first BOM by seven. Later spins reuse parts and are often smaller builds. A workable approach:

• Spin 1: full BOM, full contingency, learn what is wrong.
• Spin 2 and 3: price only the changed lines plus a fresh set of boards. Expect fixes to touch your most expensive parts less than you fear.
• Pilot: re-price at the 100 or 1,000-piece tier and see how the unit cost drops.

Write the number of spins down as an assumption in the budget. When someone asks why you need more money after spin 1, the answer is already on the page.

A worked example

Here is an illustrative calculation with made-up numbers, to show the arithmetic rather than to benchmark any real product. Say a small sensor board has a parts BOM that prices at $18.00 per board at 10-piece quantities, and you want 10 boards.

Notice that the $18 BOM ended up as about $70 per board in the budget. That gap is normal. It is also why quoting the raw BOM total to a manager or investor sets you up for a hard conversation.

Where the real money goes: engineering time

The BOM is often the smaller part of the story. According to a 2026 prototype cost breakdown, a simple sensor or accessory prototype typically runs $30,000 to $80,000 all-in, a connected consumer product $80,000 to $250,000, and an industrial or medical-grade device $250,000 to $1.5M, with most of that being engineering time rather than parts. The same source notes that electronics stages such as PCB design and hardware and firmware integration can cost $10,000 to $50,000 or more per round.

Those figures come from a services firm pricing full development, so they describe a team contracting out the work, not a hobbyist building a board on a weekend. Still, the proportion holds as a warning. Bring-up, debugging and firmware validation are often 30 to 50% of the integration budget, and a quote without a bring-up line is incomplete.

So keep two numbers on the page: the BOM budget (what you will spend on materials and builds) and the development budget (what the time costs). Funding conversations go better when each is clear.

Match the prototype to the question

One more source of overrun is building the wrong prototype. Hardware consultants Equilinq argue that prototyping cost is driven mostly by the question you are trying to answer. A proof-of-function board does not need the finish of a market-ready unit.

For a BOM budget this has a practical meaning. If you are proving that a sensor chain works, use dev-board modules, through-hole parts you can hand-solder, and the cheapest compatible package. Save the tight 0402 layout, the custom module and the premium connector for the spin where they answer a real question.

Our perspective: price it while you design it

We built Circuit Center because the usual workflow is split across too many tabs. You design in one tool, export a file, upload it to a pricing site, check stock somewhere else, and then repeat it all after a design change. By the time the number arrives, the design has already moved on.

Our view is that a prototype budget is most useful early, while changes are cheap. A part swap on the schematic costs minutes. The same swap after boards are ordered costs a spin. So we put pricing next to the design: the Circuit Designer opens a KiCad project in the browser and shows a BOM priced from the catalog, and the BOM tool accepts a spreadsheet or a KiCad, Altium or Eagle export and prices the build at your quantity with a recommended supplier per line.

We also think pricing tools should be honest about their limits. Each result shows whether a price is from a live distributor feed or an older listing, and our thermal map is described as an early estimate for comparing options, never a sign-off. A budget built on numbers you cannot trace is just a hope in a spreadsheet.

— Matthew

Price your BOM in minutes

If you have a BOM export ready, the Circuit Center BOM tool matches each line to real parts, prices the build at your quantity, and lets you send a share link to a colleague or buyer. If your design is in KiCad, you can open it in the Circuit Designer and see the priced BOM beside the schematic and board. The file is read in your browser, and only part numbers are looked up.

A short checklist before you order

1. Every BOM line has a manufacturer part number and a per-board quantity.
2. Quantities are multiplied by boards plus spares, and priced at the matching tier.
3. The top five lines by cost are in stock at more than one seller, with no lifecycle warning.
4. Bare board, assembly and one-time setup are quoted, not guessed.
5. A landed-cost factor and a 15-20% contingency are applied.
6. The number of revisions is written down as an assumption.
7. Engineering and bring-up time are budgeted on their own line.
8. Prices were checked recently, ideally the same week you buy.

If several people buy for the team, agree on suppliers up front. A preferred supplier list with the right fields stops a build from fragmenting into ten small orders with ten shipping charges.

FAQ

How do I calculate BOM cost for a prototype?

Multiply each part's quantity per board by the number of boards plus spares, then price each line at the tier that matches that total. Add bare PCB, assembly and one-time setup, apply a landed-cost factor and finish with a contingency. The worked example above shows the arithmetic.

How much contingency should a prototype budget include?

A buffer of 15-20% on top of the total estimate is a common practice for covering supplier changes and design iterations. Use the high end when the design is new or the parts are hard to source.

Is the BOM the biggest cost of a prototype?

Usually not for a funded product. Engineering time is the largest share in the 2026 breakdown we cite. For a maker building one board, parts and fabrication can be most of the spend, so know which case you are in.

How many prototype revisions should I plan for?

Plan for more than one. Engineering-stage projects often take 3 to 7 iterations before the design is frozen. Price spin 1 in full, and later spins by the lines that change.

How often should I re-price a prototype BOM?

Re-price whenever the design changes and again just before you order. Stock and prices shift, and a part that was available when you drew the schematic may not be when you buy.

Sources

• Prototype costing for deeptech hardware startups: three-bucket budgeting
• Hardware Prototype Cost (2026 Breakdown), inteRFace R&D
• What does it cost to prototype a product?, Equilinq

Recommended

• BOM Pricing: 6 Costs Engineers Track From Spreadsheet to ERP
• BOM Pricing Tool — Price Your Build
• BOM Cost Reduction for Hardware Teams: Price Tiers to P&L