Start with the physical job
Write down the physical action the product must perform. If a phone, web app or commodity accessory already does it well, custom hardware is usually a weak starting point.
FIELD NOTE / PRE-DEVELOPMENT
OEM vs custom hardware
A practical decision framework for founders and product studios deciding whether to adapt an existing OEM device or fund clean-sheet hardware development.
DECISION FRAMEWORK
Search finished supply before architecture freezes
Before committing to a PCB, enclosure or sensor stack, search for finished devices that already cover most of the physical requirement.
Separate “looks similar” from “can be adapted”
A useful OEM base needs more than similar industrial design. Look for exact-SKU evidence of OEM/ODM customization, firmware access, an SDK, API, protocol documentation or a realistic integration surface.
Treat supplier claims as signals
Listing claims are not engineering facts. SDK, API, certification and MOQ claims should become exact supplier questions before you depend on them.
Compare the remaining gap
The real decision is the gap between the best finished base and the requirement. If the gap is mostly software, workflow and branding, adaptation may be attractive. If the gap is core sensing, safety, power, mechanics or regulated performance, custom development may still be necessary.
NEXT STEP
Test the market before you fund the hardware.
The first 3-device signal check is free. If the evidence is weak, stop there. If there is a credible manufactured path, the full 48-hour scout is $349.
FREE3-DEVICE SIGNAL CHECK → $349 FULL SCOUT
Send a problem brief ↗
No card or commitment is required for the signal check. Prefer email? [email protected]