Checklist
Hardware Prototype Checklist Before You Build
Updated July 2026
Before you spend money building hardware, write down what must be true for the prototype to count as successful. This checklist helps founders and product teams avoid vague scopes, missing interfaces, surprise BOM costs, and painful redesigns.
Requirements checklist
A prototype should start with a short but explicit requirements document. It does not need to be perfect, but it needs to remove ambiguity.
- Core function and success criteria
- Target users and operating environment
- Power source, battery life, and charging needs
- Connectivity, sensors, actuators, and external interfaces
- Target size, enclosure, and mounting constraints
Engineering checklist
Confirm the MCU, sensors, radio, power architecture, enclosure, firmware features, and test procedure before board layout begins. Changes after fabrication are slower and more expensive.
Production-readiness checklist
Even if the first prototype is only for validation, track BOM cost, supply risk, DFM, DFT, certifications, enclosure tooling, and the files your manufacturer will need later.
Frequently asked questions
Do I need a complete spec before contacting Raonebytes?
No. A rough brief is enough to start. Raonebytes can help turn it into a scoped requirements document and fixed quote.
What should I prepare for a hardware quote?
Prepare the product goal, required functions, size constraints, power needs, connectivity, target quantity, timeline, and any reference products or sketches.
Can the first prototype be manufacturing-ready?
Sometimes, but most products need at least one iteration. The first prototype should be designed so lessons can transfer cleanly into a production-intent revision.