Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Don't over-engineer early hardware prototypes. Instead, create a version that—even if technically fake—effectively demonstrates the core user experience. This storytelling approach is more compelling to early-stage investors than a perfectly functional but less engaging product.

Related Insights

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.

Instead of a functional prototype, Mirror's founder raised a seed round with a "smoke and mirrors" version: an animated video behind one-way glass. This focused on selling the *feeling* and brand experience to investors, proving demand before spending capital on complex engineering.

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.

For early R&D, don't waste time designing custom components in CAD. Instead, buy existing products, tear them apart, and reuse their mechanisms. A simple tape measure can serve as a constant force spring, saving hours or days of design work and getting to a proof-of-concept faster.

The goal of high-fidelity prototyping isn't just to show features, but to create an experience so real it makes people ask, "Is this real?" This suspension of disbelief elicits more genuine, emotional feedback than a simple functional demo ever could.

Before writing code, you can string together hyperlinked screenshots in a design tool like Figma. This creates a 'hacky' prototype that feels like a fully built app to potential customers, allowing for rapid, low-cost user testing and validation.

De-risk new product initiatives by validating them directly with the market using low-fidelity prototypes like sketches. By building a following and an adoption list before development begins, you create undeniable proof of demand that can overcome internal resistance and ensure a successful launch.

Hardware startups must not wait for physical prototypes to get customer feedback. Steve Blank advocates for creating 'digital twins'—advanced, interactive simulations—that customers can use. This allows for rapid iteration and customer discovery, mirroring the agility of software development.

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.

Instead of waiting for sophisticated 3D prints, an engineer used duct tape and plastic scraps to create a proof-of-concept. This crude but functional prototype not only worked but also impressed the client. It demonstrates that the goal is rapid learning, not polished hardware, in the early stages.