Someone picks up a sensor, a compact piece of industrial equipment or wearable device the size of a fist. They turn it over in their hands and think: how hard can this be? It looks finished, and self-contained.
The product looks simple because the people who built it spent years making it look that way. Simplicity, in hardtech, is the final result of enormous complexity carefully hidden.
The single most common misconception we encounter, regardless of sector or founder background, is around timeline (and money, but that’s for another day). Founders consistently underestimate how long the journey from working prototype to manufacturable product actually takes and why.
Closing that gap is one of the most important things we do at Garage&co. This article is an attempt to make the reasoning explicit.
The prototype is not the product
The gap between a working prototype and a manufacturable product is where most hardware development timelines expand beyond any original estimate. A prototype proves that something can work, and helps founders learn what doesn’t.
Building it reliably, a thousand times, at a cost that makes sense, using components you can actually source at volume is a separate and considerably larger undertaking.
Getting from a validated concept to pilot production typically takes between two and five years for products requiring rigorous certification, and that timeline starts only once the core technical idea has been proven. The manufacturing process then demands the same level of discipline as the engineering itself: tooling development, assembly sequence design, quality control systems, and supplier qualification. Each is its own project with its own timeline and its own failure.
First-time hardware founders often treat the prototype demo as the culmination of the work. In practice, it marks the beginning of a longer and more demanding phase, one where the skills that got them to the prototype are necessary but no longer sufficient.
"In software, you push a fix and it's live in minutes. In hardtech, the cost of fixing mistakes after mass production can determine whether the company survives."
Iteration is the process, not a detour from it
Three to eight full prototype iterations before arriving at something that both works and can be manufactured consistently is entirely normal for a complex physical product. We see it across our portfolio. The number is higher for products with novel materials or unconventional manufacturing requirements, and lower for products that fit within well-established production processes.
Each iteration surfaces something real : a component that performs perfectly in prototyping, but is unavailable at the volumes required for production, from any supplier, at any price. For example, a sealing solution that passes lab testing and fails in field humidity conditions (or our personal favorite, is eaten by crows).
What we have observed in the founders we work with is that the ones who progress the fastest through iteration are the ones who treat each cycle as a structured experiment rather than a repair exercise. They define what they're testing before they build. They document what they learn. They resist the temptation to fix multiple variables simultaneously, because that makes it impossible to know which change produced which result.
Finding problems in the lab, before production commitments are made, is one of the most valuable things a hardware team can do. The infrastructure to iterate efficiently, access to prototyping equipment, manufacturing partners willing to engage early, a network of technical experts who can diagnose failure modes quickly, is a genuine competitive advantage for hardware startups. It's a significant part of what we try to provide at Garage&co.
Physics doesn't move at software speed
The startup ecosystem has internalized a particular rhythm of innovation: ship, learn, adjust. The cycle runs in days or weeks. This is a genuine and powerful approach to building software products, and it has produced remarkable results. But it has also quietly become the default mental model for all technology development, including hardware, in ways that create systematic misalignment between expectations and reality.
Physical products operate under constraints that software doesn't encounter. Regulatory certifications, such as safety testing, electromagnetic compatibility, industry-specific approvals, each follow timelines set by certifying bodies, not by product teams. A safety certification for a medical device or an industrial product can take twelve to eighteen months. That timeline doesn't compress because the engineering team is moving fast.
Supply chains introduce lead times that can stretch months. A design change that takes an afternoon to model can take weeks to validate in material, and weeks more to source the modified component at production quantities. A supplier who performed well at prototype quantities may not have the capacity or the process control to maintain quality at volume.
We work with founders from software backgrounds fairly regularly, and the adjustment is always the same: learning to plan around constraints that exist in the physical world and cannot be engineered away through faster iteration. It's the nature of building things that have to perform reliably in real conditions, for real users, with real consequences if they fail. That constraint is also what makes a well-executed hardware product genuinely defensible in ways that most software products are not.
The market keeps moving while you build
There is a final layer of difficulty that doesn't appear on any engineering timeline: the competitive and commercial environment doesn't pause while a hardware product is in development. Customer needs evolve or competing products reach the market before yours or the worst regulatory frameworks shift.
We've seen this create real pressure on founders at the worst possible moment. When they're deep in the certification process, or working through a tooling revision, and a competitor announces something that looks adjacent to their product. The temptation to accelerate, to cut corners on validation, to ship before the product is fully ready, can be significant.
The founders who navigate this well are the ones who built enough validation into their early development process that they have genuine confidence in their product's performance, and genuine clarity about what differentiates it. A hardware product that works reliably, that can be manufactured consistently, that has passed rigorous testing, is far more defensible than one that shipped earlier but carries unresolved questions about quality or durability.
Shortcuts in hardware tend to produce products that require a complete restart to correct rather than an incremental fix. We've seen that pattern enough times to treat it as a near-certainty. The five-year timeline is an accumulation of decisions made carefully, problems surfaced and resolved before production, and a product hardened against conditions that prototypes never fully replicate. It's hard and costly to think it will take less than five years.
What this means for founders considering hardware
If you're building a hardware startup, or considering one, the most useful reframe is this: the timeline is the product. The years between concept and production run are not a delay before the real work begins, they are the work.
Each stage adds something that cannot be added later without significantly greater cost.
At Garage&co, we've spent three years building the infrastructure and the network to help founders move through that timeline as effectively as possible:
access to prototyping facilities,
connections to manufacturing partners who engage early in the development process
relationships with regulatory specialists,
and a community of founders who have already navigated the stages you're about to encounter.
The goal is to make the inevitable complexity navigable, not to pretend it doesn't exist.
The difficulty of hardware development is precisely what makes it defensible. Building physical products well, with the discipline the process requires, produces something that cannot be replicated quickly. In a world increasingly shaped by physical technology, that's worth understanding deeply.