Hardware Product Development Process: From Idea to Production
The hardware product development process in nine stages, from requirements to launch: what each stage produces, where projects stall, and how to sequence the work.
Many hardware projects stall between the idea and a product in a customer's hands, usually not because the idea was bad but because the work in between was underestimated. The hardware product development process is a chain of decisions, and each one closes some doors and opens others.
We design and engineer electronics, firmware, enclosures and apps for clients. This guide is the whole hardware product development process in one place: nine stages, what each one should produce, and where the expensive mistakes tend to hide.
The hardware product development process in nine stages
Development is not a straight line. Several stages overlap, and the order below is the one that keeps the cost of change lowest. Each stage ends with something you can check, not a feeling that you are "mostly done".
1. Discovery and requirements
Before anything is designed, write down who the user is, where the product is used, and what limits you: size, cost target, battery life, environment, markets you will sell in. The result is a requirements document with numbers in it, not a list of features. "Runs for months on a small battery" is a wish; "runs for 12 months on one cell at one reading per minute" is a requirement you can design and test against.
2. Concept design
Explore several solutions before choosing one: form factors, key components, how it connects, how it is powered. This is the cheapest stage to be wrong in. Build quick proofs of the riskiest assumptions (does the sensor read what we need, does the radio reach far enough) and let the answers decide the direction.
3. Electronics: schematic and PCB
The electronic architecture takes shape: component selection, schematic, review, then board layout. This stage fixes your bill of materials, your power budget and many of your manufacturing constraints, so pick parts with supply and lifecycle in mind, not only datasheet fit. Common board mistakes are covered in our post on PCB design mistakes that hurt the first production run.
4. Mechanical and enclosure design
The physical form: CAD, materials, tolerances, how the product is assembled and opened, and how it survives being dropped. The enclosure has to carry the electronics, the antenna, the battery and the user, all at once, which is why it cannot be designed after the board is finished.
5. Firmware and app
The software that makes the hardware a product: drivers, power management, radio and protocols, updates, and the app or cloud service around it. Firmware starts alongside the PCB, but it cannot be finished until it runs on real boards. Pin assignments, debug access and test points should be agreed with the firmware engineer before the layout is frozen.
6. Prototyping and integration (EVT)
Bring electronics, mechanics, firmware and app together on one working unit. This is where problems appear that no single discipline could see alone: a radio that loses range inside the real enclosure, a battery that runs hot, an onboarding flow nobody can follow. Plan for more than one round. In industry practice this build is called EVT, engineering validation test.
7. Validation and compliance (DVT)
Production-intent units are tested against the requirements: reliability, drop and temperature tests, and the regulatory tests for the markets you sell in. For electronics sold in the EU and Norway that means CE marking, which the manufacturer carries out and documents. Our post on taking a product to market covers CE marking, the Radio Equipment Directive and what goes in the technical file.
8. Pilot run and manufacturing (PVT and mass production)
Tooling, supplier qualification, a pilot run on the real line, end-of-line testing and quality control. This is the stage where a design that works on the bench is proven to work repeatedly, in someone else's factory. A design-for-manufacturing review should happen before it, with the factory involved.
9. Launch and support
Packaging, manuals, shipping, returns, and the plan for firmware updates and the next hardware revision. Launch is not the end of engineering; the product now meets users, and you learn things no test could show.
Where EVT, DVT and PVT fit
The hardware industry names the main builds POC, EVT, DVT, PVT and MP. The names are industry practice, not a standard, and different companies draw the lines in slightly different places. What matters is the decision each one forces: does it work, does the complete design meet the requirements, and can the factory build it repeatedly.
We explain what each gate decides, and how founders get stuck at each one, in The five gates: prototype to shipping. The method behind it, the stage-gate process, was formalised by Robert G. Cooper for general product development.
Where hardware projects stall
These are the failure points worth planning for:
- Scope that grows before the first circuit exists. Every feature added at concept stage multiplies risk, cost and test effort.
- A board that does not fit the enclosure. Discovered after the mould tool is cut, this is an expensive mistake, because the tool has to change too.
- Compliance treated as paperwork at the end. A radio that fails EMC testing means a board re-spin. Compliance is a design constraint from the first schematic.
- Minimum order quantity surprises. A key component sold in large minimum quantities, or tooling that only pays off at volume, can break the plan for a first batch.
- Firmware left out of hardware decisions. Missing test points, no debug access or the wrong pin on the wrong peripheral make firmware slow or impossible on the production board.
- Nobody owning the whole product. Each specialist optimises their own part and no one optimises the product.
Why one team beats five vendors
It is tempting to hire a specialist for every discipline: an electronics consultant, a mechanical firm, a firmware freelancer, an industrial designer, an assembly house. Each is good at their piece, but nobody is responsible for the whole product, and every hand-off is a chance for something to be lost.
How long does it take, and what does it cost?
We will not give you one number, because an honest general figure does not exist. What moves the duration and the cost is a handful of drivers you can judge for yourself:
- Radio. Wireless adds antenna design, radio testing and a longer list of rules to meet.
- Tooling. A custom injection-moulded enclosure needs a mould tool, which sets cost and lead time; an off-the-shelf enclosure does not.
- Battery. Lithium cells add safety, transport and labelling requirements.
- Regulated sector. Medical devices fall under the EU Medical Devices Regulation, a separate regime from the ordinary CE marking routes.
- Prototype rounds. Each round that finds a real problem is a round that was worth doing, but it adds time.
- How settled the requirements are. Unclear requirements make every later estimate unreliable.
The way to get a real estimate is to price one stage at a time, starting with requirements and concept, and let each stage narrow the next.
If you are a Norwegian startup, parts of this work can be funded; our guide to Innovation Norway, SkatteFUNN and Norsk Katapult shows which scheme fits which stage.
How we work on this in projects
We work across the whole chain, so hand-offs happen inside one team. Some examples from our own portfolio, described as they stand:
- Hoviv, a cattle wearable. We delivered the system design: the module, sensor stack, power, firmware loop and chassis directions. The build is the next step once funding is in place.
- ARCIVE, a voice memory product. Web and mobile apps, back end and the firmware for a wireless capture device are built together, and a hardware prototype was shown publicly in June 2026. The product is still in development.
- Pebble and Tally Keys. A light-only environment sensor and a one-press habit keypad. Pebble is in development and Tally Keys is a concept; neither is a shipping product.
Frequently asked questions
How do you turn an idea into a physical product?
Write requirements with numbers, test the riskiest assumption with a cheap proof of concept, then build up in stages: electronics, mechanics, firmware and app, an integrated prototype, validation and compliance, a pilot run, and launch. Each stage should end with something you can check.
What are the stages of hardware product development?
This guide uses nine: discovery and requirements, concept, electronics, mechanics, firmware and app, prototyping and integration, validation and compliance, pilot run and manufacturing, and launch. Industry shorthand groups the builds as POC, EVT, DVT, PVT and MP.
What is EVT, DVT and PVT?
Engineering, design and production validation tests: three sequential validation builds, industry practice rather than a formal standard. The gate-by-gate explanation, with what each one decides, is in our post on the five gates.
How do you build a prototype?
Start with the smallest prototype that can answer the most dangerous question, for example a development board with the sensor and radio you are considering. Build a fuller prototype only once you know the core idea holds. Early prototypes should look rough; they exist to teach you something, not to be shown.
Why do hardware startups fail?
We found no reliable statistic for hardware specifically, so we will only say what we see: unclear requirements, scope growth, late discovery of fit or compliance problems, and no single owner of the whole product. Many are decisions made too late, not ideas that were wrong.
How do you put an idea into production?
Freeze the design only after validation, involve the manufacturer in a design-for-manufacturing review, run a pilot build on the real line, and have your CE documentation and packaging ready before shipping. Our post on taking a product to market covers that last stretch.
Sources
The facts above come from these pages, last checked on 2 October 2026.
- Stage-Gate International: The Stage-Gate Model, an overview (Robert G. Cooper)
- OpenBOM: EVT vs DVT vs PVT, the stages of product development
- European Commission: CE marking
- DSB: CE-merking (five steps to CE marking)
- Directive 2014/53/EU, Radio Equipment Directive (EUR-Lex)
- European Commission: Medical devices sector
Need a partner for the whole chain?
We take products from requirements to a build you can show, across electronics and PCB design and embedded firmware, and we also help founders shape the plan through product consulting. If you have an idea and are not sure where to start, book a short call.
Enjoyed this? Get the next one.
New posts on design, engineering, and building things that matter - straight to your inbox.
