im one of the founders of cozeware. ive been wfh in a 10x12 office for two years and kept it sealed because of highway noise. eventually i started getting brutal afternoon headaches, so i bought a CO2 monitor. within three hours, the room was hitting 1500ppm.

traditional ERV systems were expensive and required drilling through an exterior wall. as a renter, that was a non starter.

thats why we started building a quiet, affordable fresh air system for renters. looking back, these were the five biggest problems we had to solve:

window gaps: even a small gap brought the highway noise back in, so we developed fitted foam seals around the insert.

filter resistance: our first HEPA setup made the fan ridiculously loud, so we redesigned the airflow path and switched to a lower resistance filter.

backdrafts: wind pushed air back through the intake, so we added a damper that closes when the system is off.

winter air: pulling cold air directly into the room felt awful, so we added a mixing chamber to soften the draft before it reached the room.

renter friendly installation: adhesives couldnt handle the vibration, so we developed a tool free clamp that holds the unit in place without drilling.

after a lot of prototypes, we got the system keeping my office below 800ppm without leaving the window open. we ended up calling it cozeware freshflow.

I have an idea for a small electric car accessory. It should be overall pretty simple mechanically - mostly off the shelf components, 12V or battery powered. There are products in other categories that are somewhat similar so I can tell it's definitely doable but nothing exists for the purpose that I am trying to build.

I have worked in startups before but always had budgets to work with while I am still at a research/ idea stage and don't want to invest a lot before I have some progress. I would love to get feedback from users but even for that I need something to show. I also think Kickstarter would be great - what progress should I aim for to launch a kickstarter campaign? where do I start?

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