Hey everyone!
I’ve been thinking a lot about why building hardware still feels so fragmented compared to building software.
Even for a relatively simple product, you might be moving between CAD, PCB design, firmware, datasheets, BOM spreadsheets, manufacturing notes, and a bunch of conversations that live outside all of those tools. Each individual tool can be powerful, but none of them really understands the product as a complete system.
AI tools for hardware are starting to appear, but a lot of them seem focused on isolated outputs, like generating a CAD model from a prompt or helping route a PCB. That feels useful, but also a little like generating one React component and calling it a full software development environment.
I wrote a blog post arguing that hardware needs its own “vibe coding moment,” but that it cannot just be text-to-CAD. It would need to understand the relationships between:
- Mechanical design
- Electronics and PCB constraints
- Firmware
- Components and the BOM
- Materials and manufacturing processes
- Assembly
- Cost
- Design revisions
I’m currently working on an early-stage project called Protobench, which is exploring this idea as an AI-native workspace for developing complete electromechanical products.
The long-term idea is that you should be able to describe what you are trying to build, work through it conversationally, inspect and modify the actual engineering outputs, and have the system help coordinate changes across the product.
For example, moving a connector on the PCB should not stop at the PCB. The tool should understand that the enclosure opening may need to move, the internal mounting geometry may change, the cable path could be affected, and the documentation and BOM may need to be updated.
I’m still early, and I’m especially interested in hearing from people who have actually taken hardware products through prototyping and manufacturing:
What parts of your current workflow create the most friction?
Would you trust an agent to make changes across CAD, ECAD, and firmware if every change was inspectable and reversible?
And where do you think this idea becomes unrealistic or dangerous?
Here’s the full post:
https://opuslabs.substack.com/p/hardware-needs-its-vibe-coding-moment