How much does it cost to develop a hardware product?
An honest look at what hardware product development actually costs a founder, where the money goes, and how to spend it in the right order so you de-risk before you commit.
An honest look at what hardware product development actually costs a founder, where the money goes, and how to spend it in the right order so you de-risk before you commit.
The honest answer is that nobody can quote you a single number for “a hardware product” any more than a builder can quote you for “a house” without knowing whether you mean a shed or a mansion. But that is not a useful answer if you are trying to plan, so this guide sets out where the money actually goes, roughly what each stage is worth, and, more importantly, the order to spend it in so you never gamble a large sum on an unknown.
Founders often ask what it costs to “get to production”, picturing one big invoice. In practice a product is developed in stages, and each stage exists to answer a question and reduce a risk before the next, more expensive, stage begins. Spend a little to learn whether the idea holds up, then a bit more to prove the concept works, then more again to verify and prepare it for manufacture. Done well, you are never committing the big money until the big unknowns are gone.
That ordering is the single most important cost decision you will make. The most expensive way to build a product is to skip the cheap early thinking, commit to tooling, and discover the problem on the factory floor.
A physical product typically spends its budget across a handful of buckets:
The reason to name these is that they do not arrive at once, and the early ones are cheap relative to the late ones. A day of hand calculation that moves a wall thickness costs a fraction of the tool you would otherwise recut.
Every product is different, so instead of a figure, think in relative terms. A focused early study to pressure-test an idea is a few hundred to a couple of thousand. Turning that idea into a working prototype you can test and raise on is a larger, scoped phase. Verification before tooling is scoped to what actually needs proving. Tooling and first production are usually the largest single commitments, and they are exactly the ones you want to reach with the design already proven.
If a number matters to you before you start, that is itself a reason to run a short feasibility study first: part of what it delivers is indicative costs for the different routes to manufacture and design directions, so you can budget against real options rather than a guess.
Each phase is scoped and priced on its own, and you approve it before it begins, so the cost never runs away from you and you can stop at any gate.
The founders who spend the least overall are almost never the ones who tried to save money by skipping the early engineering. They are the ones who spent a little to be certain before spending a lot. Good early work is not an added cost, it is the thing that keeps the expensive stages from going wrong.
If you want a realistic, product-specific picture of what yours will take, the honest first step is a short study that prices the options. That is exactly what a feasibility study is for.
Part of How to develop a physical product: a founder's guide from idea to market · all guides