Latest / Hardware Startups with Fexingo: Devices, Robotics, and Manufacturing Tech Companies / How Hardware Startups Master Component Obsolescence
Transcript
- Lucas: The most dangerous moment in a hardware startup's life isn't the prototype failure or the first bad batch. It is the email from your primary IC supplier saying they are discontinuing a specific microcontroller next quarter. Luna: Right. Because you have already sold units based on that exact spec sheet, so you cannot just pivot software without re-certifying the hardware. Lucas: Exactly. And this is what we call component obsolescence. It is not just about finding a replacement part. It is about the two-year lag between the notification and the actual end of production. Most founders ignore it until it is too late because they are focused on sales velocity rather than supply chain durability. Luna: But if you lock in massive inventory early, you risk holding dead stock if demand drops. How do you balance that liquidity trap? Lucas: You treat it like insurance. You calculate the cost of downtime versus the cost of carrying extra inventory. For a Series A robotics company, a six-week production halt costs more than buying three months of extra chips upfront. The math favors pre-buying when the volume is high enough to justify the warehouse space. Luna: So it is essentially an option value calculation on your own supply chain reliability. Lucas: Precisely. And this brings us to the current market environment in October twenty twenty six. We are seeing a shift where major semiconductor firms are consolidating their legacy nodes. They want to move everyone to newer processes, which means older parts are getting deprecated faster than before. Luna: That sounds terrifying for any startup building industrial IoT devices that need long-term stability. Lucas: It is. But the smart ones are changing how they design their Bill of Materials. They are no longer picking the cheapest component. They are picking the most durable one. They look for parts with extended lifecycles and guaranteed availability windows. Luna: Does that mean paying a premium for those specific chips? Lucas: Usually a five to ten percent premium. But compared to the total bill of materials, that is cheap insurance. I spoke with a founder last week who lost forty percent of his margin because he switched suppliers mid-production to chase lower costs, only to find the new part was incompatible with his existing firmware stack. Luna: So the hidden cost is actually engineering hours, not just unit price. Lucas: Absolutely. Re-qualification takes time. Testing takes time. Certification takes time. Every day you spend re-testing is a day you are not shipping revenue-generating units. That opportunity cost is where the real damage happens. Luna: It feels like we are circling back to why pilot programs fail earlier, but this is specifically about the upstream constraints. Lucas: It is a subset of that. If your pilot uses a component that goes obsolete during the pilot, you cannot scale to production. You are stuck. So you must anticipate obsolescence before you even sign the first customer contract. Luna: Do you recommend using third-party distributors to secure these parts? Lucas: Only as a backup. Your primary relationship should be with authorized distributors. Third-party markets are risky because of counterfeits. In hardware, a fake capacitor can ruin a whole batch of boards. The risk is not worth the slight discount unless you have rigorous incoming inspection protocols. Luna: Which most early-stage teams do not have the budget for. Lucas: Correct. Which is why you design out the risk. You choose components that are available across multiple vendors. If you can swap a resistor from Vendor A to Vendor B without changing the schematic, you have built resilience into your design. Luna: That sounds like standard engineering practice, yet I hear so many founders complain about single-source dependencies. Lucas: Because they get excited about a novel part. They see a feature on a competitor's device and rush to use the same specialized sensor. They forget to ask if that sensor is being phased out. Enthusiasm overrides due diligence. Luna: So the lesson is to prioritize boring, common parts over flashy, rare ones. Lucas: Yes. Common parts have longer lifecycles. They have better documentation. They have multiple sources. They are the unsexy backbone of reliable hardware. If you want to survive past year three, you must fall in love with boring components. Luna: It seems like the key is treating supply chain management as a product feature, not just an operational afterthought. Lucas: That is the mindset shift. If your supply chain is fragile, your product is fragile. Investors know this now. They ask about your bill of materials stability just as much as they ask about your customer acquisition cost. Luna: I bet they do. Especially after the last couple of years of global disruptions. Lucas: Definitely. So, let me take a quick break here. If these conversations about building resilient hardware operations are useful for what you are building or running, consider supporting the show directly. It helps keep the production ad-free and allows us to dig deeper into these operational realities. You can find us at buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Luna: Yeah, it really does help us afford the detailed case studies and the expert interviews that make these episodes possible. Lucas: Thanks to everyone who supports us. Now, let's get back to the technical side. Once you have secured your components, how do you manage the actual inventory flow without tying up all your cash? Luna: That is the classic working capital problem. You buy the chips, but you don't sell the units for months. Lucas: Right. So you need a pull-based system where possible. You trigger procurement only when you have confirmed orders or very strong forecasts. But for long-lead items like custom ASICs, you have to forecast further out. Luna: How far out are we talking? Six months? A year? Lucas: For custom silicon, often twelve to eighteen months. That is why you need strong relationships with your foundry partners. They will give you lead times if you treat them as strategic partners rather than transactional vendors. Luna: It sounds like networking is just as important as engineering skills in this phase. Lucas: It is. You are not just buying parts. You are buying access to information. Your supplier tells you what is coming down the pipeline. That intel is worth its weight in gold. Luna: So the best hardware founders are also part-time diplomats. Lucas: Exactly. They cultivate trust so that when things go wrong, they get the phone call before anyone else. That early warning system is your greatest asset against obsolescence and shortage alike. Luna: And that trust is built on consistency and transparency, not just big orders. Lucas: Always. If you ghost your suppliers for three months while you debug a board, you will never get priority support when you need it. Treat them like teammates. Luna: One final thought then. Should startups try to verticalize their own component manufacturing? Lucas: Almost never. Not at the early stage. The capital intensity is too high. Stick to designing the integration layer. Let others make the raw materials. You add value through innovation, not through commodity production. Luna: Focus on what makes your product unique, not what makes your factory efficient. Lucas: Spot on. Unless you are making batteries or display panels, leave the heavy lifting to the specialists. Your job is to solve the user's problem, not to become a mini tsmc. Luna: A goal worth remembering as you navigate the next round of funding. Lucas: Indeed. Because the market rewards those who deliver reliably, not just those who launch earliest.