Most hardware failures aren't engineering failures. The enclosure fit fine, the firmware shipped on time, the certification came through — and the product still didn't sell, because nobody confirmed anyone wanted this specific version of it before the tooling was cut.
The frustrating part is that this is almost always avoidable. Real customer feedback and purchase intent are available well before a single line of firmware is written. The problem is sequencing: most teams build first and validate later, when the cost of being wrong has already multiplied.
Why the cost curve is so unforgiving in hardware
In software, a wrong assumption costs you a sprint. In hardware, the same wrong assumption discovered late can cost a full mechanical respin, a new mold, a recertification cycle, and months of schedule. PCB layouts, tooling, and regulatory filings lock in assumptions that are cheap to change on paper and expensive to change in metal.
That asymmetry is the whole argument for validating early: every stage of hardware development makes your assumptions more expensive to revisit. Be wrong while it's still a conversation — not a mold. Our prototyping and manufacturing support teams exist to keep that conversation cheap for as long as possible.
Stage 1: talk to the market before you design for it
Before CAD or schematic work starts, talk to the people who'd use the product — and the people who sell to or support them. Make it useful:
- Ask about the problem, not the product — existing frustration beats hypothetical enthusiasm
- Seek strangers and low-stake reviewers; warm networks soften feedback
- Capture language, not just conclusions — the words people use become positioning later
For engineering teams, this stage reorders technical requirements: must it work one-handed, survive drops, prioritize battery over app features? Those answers reshape mechanical and electrical priorities before a single drawing is locked.
Stage 2: test demand before you commit to a design
Once there's a working thesis, test whether people will act — not just say they would. A small deposit or early-access waitlist creates a stronger signal than a survey. Controlled tests on feature framing and price can tell you which capabilities are worth architectural cost — because in hardware, a display, radio, or extra sensor can reshape the entire BOM.
Only test features that are roughly feasible within your cost and form factor. Validating enthusiasm for something your engineering budget can't support just relocates disappointment later. Wearable teams should cross-check feasibility against our wearable prototyping roadmap, and any team pricing out a BOM should read 10 Design Mistakes That Quietly Drive Up Your Product's Cost before those features get locked in.
Stage 3: let real commitment fund and de-risk production
By the time a working prototype exists, the strongest validation is a customer paying before delivery — pre-order, crowdfunding, or direct pre-sales. Build real schedule margin informed by certification and tooling lead times before making public delivery commitments. Demonstrated demand also changes how manufacturing partners treat your proposal.
Why the stages compound
Customer conversations surface the real problem and language. That language sharpens demand tests. The resulting data — price, features, audience size — becomes evidence for pre-sales and for manufacturing or retail buyers who see credible traction, not just an idea.
What this means for the engineering roadmap
The earlier a hardware team brings in real market signal, the fewer expensive surprises show up once tooling starts. A validated feature set and price point don't just strengthen go-to-market — they narrow the design space before detailed engineering begins, which means fewer late-stage architecture changes and fewer wasted mold revisions.
Validation isn't a substitute for good engineering. It's what makes good engineering point at the right target. When you're ready to turn validated requirements into EVT/DVT builds, start a conversation with CoBuild Labs or review how we structure end-to-end delivery across our services.