What do investors actually want to see from a hardware startup before funding it?

It takes more than a good idea.

Investors backing hardware want to see proof of a real problem worth paying to solve, a prototype that demonstrates function, not just looks, a cost structure that still works at true production scale, and a manufacturing plan that's grounded in reality, not wishful thinking. Nail those four and the pitch practically sells itself.

Let's break it down and explain why our clients like to do a product design for startups workshop with a leading Industrial Design Agency

Is this solving a problem people actually have, or one you find interesting

This comes before manufacturability, before unit economics, before everything else. If the problem isn't real, nothing downstream matters, and "real" here means something specific: not just a problem that exists, but one frequent, painful, or costly enough that people will actually pay to make it disappear.

This is where a lot of founders trip up. It's easy to fall for your own solution and work backwards to convince yourself the problem is bigger than it is. The real test is going straight to the people who supposedly have this problem and asking about their day-to-day, without bringing up your idea at all. How do they handle it now? How often does it crop up? What have they already tried? What are they currently spending, money, time, or sheer hassle, to work around it? If they can't put the problem into their own words unprompted, or their current workaround is genuinely good enough for them, that's something you want to know before burning a year and a design budget on it.

Willingness to pay is the harder, sharper test, and it's not the same as interest. "I'd definitely buy that" costs someone nothing to say. What actually matters is behavior that costs them something: a pre-order, a deposit, a signed letter of intent, a waitlist people had to genuinely opt into rather than a form nobody bothered filling out, a pilot customer willing to spend real time trialing it. Investors can tell the difference between polite enthusiasm and real commitment, and they'll ask for proof of the latter, not the former.

Digging into the real problem, not the solution, is one of the biggest parts of our startup workshops at FLYNN. Founders often walk in fixed on their idea and walk out with a much sharper picture of who actually has this problem, how they're living with it now, and whether it's worth solving at all.

A working prototype isn't proof it's fundable

Getting something to work once, on a bench, with hand-picked components, is roughly 20% of the journey to a fundable, manufacturable product. The other 80% is proving it can be built repeatably, sourced reliably, tested, certified, and delivered at the volumes the business plan calls for, and that's the part a lot of first-time hardware founders haven't tackled yet by the time they start pitching.

It's worth knowing the difference between the two types of prototype investors will ask about.

A "looks-like" prototype shows form: size, shape, how it feels in the hand.
A "works-like" prototype shows function: whether the actual mechanism or electronics do what's claimed, often built roughly with no attention to finish.

Some founders lean too hard on the first one, because a polished-looking demo is what wows a room. Experienced hardware investors have seen that trick before and see straight through it. A beautiful shell with nothing proven inside is a bigger red flag than an ugly prototype that clearly works. Being upfront about which stage your prototype is actually at sends a better signal than pretending it's further along than it really is.

A prototype isn't a finished product in miniature, it's a tool for answering a specific question. Testing whether a mechanism actually works needs a different kind of prototype than testing how something feels in someone's hand, or whether it can be built the same way twice. Knowing which question you're actually trying to answer is what determines the right prototype to build next, not just building 'a prototype' and hoping it proves everything at once. Learn more about how to get a prototype

Unit economics have to work at real volume, not just on a slide

ready to talk through all three without hesitating. This is one of the most common places hardware pitches fall apart, not because founders haven't thought about it, but because they've thought about it using the wrong numbers.

A common mistake is pricing the BOM based on what components cost in prototype quantities, then presenting that figure as the production cost. Component pricing drops meaningfully at volume, but so do several other things founders forget to model: tooling costs spread across a production run, fixed costs like certification fees, and the negotiating leverage that comes with being a real ongoing customer rather than a one-off buyer. Investors want to see the maths worked out properly at the volume the business plan actually requires, not the volume that happens to make the prototype look cheap.

Manufacturability, can this actually be built repeatably, not just once

This is where a lot of otherwise promising pitches lose credibility, because it's the part founders without a manufacturing background genuinely don't know to look out for.

Single-source components are the classic trap: a part that's available in small quantities from one supplier when you're prototyping, but comes with a long lead time, limited stock, or a real risk of going end-of-life right as you try to scale. It happens more often than people expect, and it's exactly the kind of thing that quietly derails a production run months after a design has already been signed off. Investors who've funded hardware before will ask about this directly: what does your BOM risk actually look like, and do you have alternates lined up for the parts that could cause trouble?

This is design for manufacture territory, and it's worth taking seriously early, rather than discovering the problem during due diligence, or worse, during your first production run.

Building one is proof of concept. Building the same thing reliably, at volume, with components that won't disappear on you six months into production, that's manufacturability, and it's a much harder problem than it looks from the outside.

Do you have a real manufacturing plan, or just a hope

A named manufacturing partner, or a shortlist of contract manufacturers you're actually in conversation with, is worth more to an investor than a polished slide about "scaling to 10,000 units." Vague plans read as inexperience.

Timelines matter here too. Claiming you'll go from prototype to market in under a year, with no manufacturing relationships or supply chain in place yet, doesn't read as ambition to an experienced hardware investor, it reads as not having done this before. Build in buffer for prototype iterations and tooling revisions, because there will be iterations, and a realistic roadmap you beat is a far better position to be in than an unrealistic one you miss.

What investors are really looking for here is confidence that you understand the road from prototype to production, not that you have every answer, but that you know exactly what the questions are and you're already working through them.

What actually makes it hard to copy

Every hardware pitch eventually runs into the unspoken question: what stops someone else, probably with more money, from just making this too. A clever mechanism alone rarely holds up as an answer, because most mechanisms can be reverse-engineered or worked around given enough time and budget, which bigger competitors usually have.

The stronger, more durable answer is usually the relationship between the product and what it means to the people who buy it, the brand meaning, the trust, the reason someone chooses this specific product over a near-identical one at a lower price. We think of this as Product Brand Fusion ^TM: the product and the brand built around it becoming difficult to separate, so that copying the mechanism doesn't get a competitor very far, because they haven't earned the reason people actually buy it. It's a much harder thing to answer in a pitch deck than "we have a patent," but it's usually the more honest one and it's the kind of answer that tells an investor you understand what you're actually building a moat out of

Product Brand FusionTM is the idea that a product and the brand around it should be designed as one conversation, not two separate workstreams stitched together afterwards. When they're properly fused, a competitor may be able to copy the mechanism, but they will never be able to replicate the reason people actually choose it.

The pattern behind all of this

None of these things are really separate checkboxes. They're all versions of the same underlying question an investor is asking: do you understand this business as well as you understand the product?

Founders who've spent months obsessing over the mechanism sometimes haven't spent the same energy on whether anyone's actually going to buy it, or whether it can be built twice, let alone ten thousand times.

The founders who come across well aren't the ones with every answer polished. They're the ones who've clearly done the thinking, who know where their BOM risk sits, who can say honestly whether their prototype works or just looks like it does, who've talked to real users rather than assumed they know what they want. That kind of groundedness is very hard to fake in a pitch meeting, and it's usually the thing that gets a second meeting booked.

If you're at the point of pulling a pitch together and some of these questions don't have confident answers yet, that's normal, it's also usually a sign of exactly where to spend the next few weeks before you're in the room.

Flynn is an award-winning product design consultancy working with startup founders and emerging brands to bring physical products to market, from first concept through to design for manufacture. If you have an idea you'd like to explore, get in touch.

We provide businesses with product design consultancy, industrial design, prototype design & related services.