Hardware Development Timeline Planner

What each phase proves

A hardware schedule is a sequence of questions, and each phase exists to answer one of them before money is spent on the next. Skipping a phase does not remove its question; it moves the answer to a stage where it costs more.

• Discovery and architecture decides what the product must do and how: the requirements, each with the test that proves it, the architecture, and the handful of parts that set cost and lead time.
• Proof of concept retires the riskiest assumptions on dev kits and modules: the radio range, the sensor, the battery life. It is not supposed to look like the product.
• EVT (Engineering Validation Test) is the first custom board in a near-final enclosure, and it proves the design works, with every requirement demonstrated on 5 to 50 units.
• DVT (Design Validation Test) proves the design survives. Units are form, fit and function final, on production tooling, and go through thermal, drop, vibration, humidity and EMC testing.
• Certification is formal testing on form-final units: FCC and ISED, CE or UKCA, product safety, battery transport, carrier approval, or IEC 60601 and FDA for a medical device.
• PVT (Production Validation Test) proves the factory can build it repeatably, on the real line with real fixtures and operators, judged on first-pass yield.
• The production ramp is the first production run built, tested and packed.

The unit counts, exit criteria and the mistakes that sink each build are in EVT vs DVT vs PVT: what each build actually proves.

Why hardware schedules slip

Most slips are not engineering surprises. They are waiting: for a tool, for a lab slot, for a part. The first shots from an injection mold rarely match the drawing, and each correction loop at the toolmaker costs one to three weeks. A radiated-emissions failure at the formal test costs a fix, often a board spin, and a new slot in a lab that was booked weeks ahead. One component with a lead time measured in months can hold the first production run hostage.

The rest is self-inflicted. Requirements that change after the EVT design starts arrive as board spins and tooling changes. Firmware and the companion app start late and finish last, and a product cannot pass DVT if a stranger cannot set it up. When electronics, firmware and mechanical sit with three different vendors, every handoff adds a week of questions, and nobody owns the schedule as a whole.

How to shorten it

The levers that move a hardware schedule by weeks rather than days are mostly decisions, and most of them are cheap if made early:

• Use a pre-certified radio module unless your volume justifies chip-down. It removes the slowest part of certification, as the certification cost estimator shows line by line.
• Pre-scan EVT boards in an EMC chamber for a day, while a fix is still a layout change.
• Freeze the mechanical design at the end of EVT, get the toolmaker's DFM review before steel is cut, and run tooling alongside DVT instead of after it.
• Buy long-lead parts and book the test lab when DVT starts, not when it ends.
• At small volume, shrink the builds instead of skipping them: EVT on 5 to 10 units, a combined DVT of 20 to 50, and a PVT that is your first production run, watched closely.
• Keep electronics, firmware and mechanical in one team, with one person accountable for the date.

From a range to a plan

This planner gives the shape of a programme. A plan you can raise money against needs your requirements, your bill of materials and your launch date. inteRFace R&D is a Silicon Valley engineering firm with electronics, firmware, mechanical and the transfer to production in one team: 150+ products delivered and 200+ boards shipped. We work with teams across the United States. The budget side is in the project cost estimator and the PCB cost calculator; the engagement is described in hardware for startups; and a free 30-minute call with an engineer turns these ranges into phases for your product.

Questions founders ask about hardware timelines