Hardware Product Development

A device taken from one-page brief to shipped units: a target cost stack, stage gates from EVT to PVT, a chosen factory, certification by market, and the routines that keep BOM cost, parts and changes under control.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Hardware Product Development, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

202

Starter tasks

🧩 Product Management

Hardware Product Development

Taking a physical or connected product from concept through prototypes, manufacturing readiness and certification to launch, with hardware's longer lead times.

  1. Hardware product brief on one page
  2. Target cost stack from retail price to BOM
  3. Device requirements and operating limits sheet
  4. Certification and compliance map by target market
  5. Stage gates from concept to mass production
  6. Master hardware schedule with long lead items
  7. Hardware budget through first production run
  8. Part numbering and design revision control
  9. Patents, design rights and supplier NDA checklist
  10. Weekly hardware programme and risk review
  11. Monthly BOM cost roll-up against target
  12. Component lead time and lifecycle watch
  13. Engineering change order process
  14. Supplier scorecard and quarterly review
  15. Prototype unit register and loan log
  16. Build and test failure triage
  17. Field returns and failure analysis loop
  18. Firmware release and over-the-air update routine
  19. Reading component datasheets with confidence
  20. Design for manufacturing and assembly basics
  21. Injection moulding and tooling fundamentals
  22. EMC and radio testing explained
  23. How electronics are made, from SMT line to box build
  24. Reliability testing fundamentals
  25. Incoterms, freight and landed cost basics
  26. Lithium battery safety and shipping basics
  27. Contract manufacturer selection
  28. Pre-certified radio module or chip-down design
  29. Enclosure prototyping method by build stage
  30. Value engineering pass on the BOM
  31. Connectivity choice for a connected device
  32. Second source qualification for critical parts
  33. Retail packaging and transit drop testing
  34. Tooling release sign-off
  35. Works-like and looks-like prototype review
  36. EVT build and exit review
  37. DVT build and formal certification testing
  38. PVT pilot run and mass production decision
  39. Factory visit for first article inspection
  40. Crowdfunding or pre-order readiness for a device
  41. First production shipment hand-off
  42. Solo founder's first prototype on a small budget
  43. Software product team adding its first device
  44. Engineer moving into hardware product ownership
  45. Technical due diligence pack for hardware investors
  46. Working rhythm with an overseas factory
  47. End-of-line test station and test coverage
  48. First pass yield improvement programme
  49. Connected device security and support period
  50. Repairability, spare parts and end-of-life plan

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Hardware product brief on one page

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before any schematic or sketch, a hardware team needs one page that says who the device is for, what job it does, the target retail price, the first-year volume and the date it must be on shelves.

First tasks

  • Write the target customer and use situation in two sentences
  • Set a target retail price and first-year volume, even as a range
  • List three must-have capabilities and two explicit non-goals
  • Share the brief with the founders or sponsor and record sign-off

Target cost stack from retail price to BOM

Most first hardware products fail on margin rather than engineering, because the bill of materials was designed before anyone worked backwards from the shelf price. Starting at retail and removing channel margin, duty, freight, warranty reserve, packaging and assembly leaves the maximum BOM cost the design team must hit, and that number should steer every part choice.

First tasks

  • Pick the main sales channel and note its typical margin
  • Estimate freight, duty and warehousing per unit from a forwarder's quote
  • Add assembly, test, packaging and a warranty reserve to the stack
  • Write the target BOM cost at the top of the bill of materials

Device requirements and operating limits sheet

Engineering cannot pick a battery, a processor or an enclosure material without hard limits: size and weight, battery life under a stated use pattern, operating temperature, water and dust protection, drop height and expected lifetime. A requirements sheet with a number and a reason for each line gives the team something to test against at every build.

First tasks

  • List the physical limits for size, weight and finish
  • Write a typical day of use as the battery life profile
  • Set the operating temperature range and ingress protection target
  • Add the test method and first build for each requirement

Make it yours.

Install Hardware Product Development, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.