In hardware automation, a "go slow to go fast" approach is essential. Iterations are too slow and costly once hardware is built. Front-loading validation through drawings and simulations avoids major architectural issues that often get buried later due to project momentum or "go fever."

Instead of guarding prototypes, build a library of high-fidelity, interactive demos and give sales and customer success teams free reign to show them to customers. This democratizes the feedback process, accelerates validation, and eliminates the engineering burden of creating one-off sales demos.

Don't wait for a prototype to get traction. Hardware founders should first engage potential customers and demonstrate a profound understanding of their specific problems. This expertise builds the necessary trust for customers to commit, even before a physical product is ready.

Validate business ideas by creating a fake prototype or wireframe and selling it to customers first. This confirms demand and secures revenue before you invest time and money into development, which the speaker identifies as the hardest part of validation.

Unlike software, hardware iteration is slow and costly. A better approach is to resist building immediately and instead spend the majority of time on deep problem discovery. This allows you to "one-shot" a much better first version, minimizing wasted cycles on flawed prototypes.

Early demos shouldn't be used to ask, "Did we build the right thing?" Instead, present them to customers to test your core assumptions and ask, "Did we understand your problem correctly?" This reframes feedback, focusing on the root cause before investing heavily in a specific solution.

In AI, low prototyping costs and customer uncertainty make the traditional research-first PM model obsolete. The new approach is to build a prototype quickly, show it to customers to discover possibilities, and then iterate based on their reactions, effectively building the solution before the problem is fully defined.

Moving from a science-focused research phase to building physical technology demonstrators is critical. The sooner a deep tech company does this, the faster it uncovers new real-world challenges, creates tangible proof for investors and customers, and fosters a culture of building, not just researching.

In design thinking, early prototypes aren't for validating a near-finished product. They are rough, low-cost "artifacts" (like bedsheets for walls) designed to help stakeholders vividly pre-experience a new reality. This generates more accurate feedback and invites interaction before significant investment.