Latest / Hardware Startups with Fexingo: Devices, Robotics, and Manufacturing Tech Companies / Why Hardware Startups Fail at Component Obsolescence
Transcript
- Lucas: The hardest part about building hardware isn't getting the first unit out the door. It's surviving the third year when the microcontroller you designed around gets quietly discontinued by the fab house. Most founders treat component selection like a one-time engineering decision, but it's actually a continuous supply chain liability. Luna: Right, and the worst part is usually that the change happens without any formal warning until the supplier stops shipping. You can be three months into a production run when you realize your core silicon is gone. Lucas: Exactly. And unlike software, where you push an update, hardware forces you to either redesign the board or liquidate inventory. We saw a case earlier this month with a small robotics firm that had to pause shipments because their preferred sensor module hit end of life. The cost wasn't just the new parts; it was the re-validation testing that took six weeks. Luna: That validation time is the real killer because it ties up capital while you're sitting on zero revenue. Do they have a protocol for monitoring these lifecycles proactively? Lucas: Most don't. They rely on their procurement team to spot issues, but by then the damage is done. The ones that survive are the ones who treat the bill of materials like a living document. They map every critical component to its manufacturer's roadmap and set alerts for retirement notices. Luna: It sounds like a lot of administrative overhead for a early stage company. Is it really worth the resource commitment before you hit scale? Lucas: If you plan to sell units for more than eighteen months, yes. I spoke with an operator who builds industrial IoT gateways. They keep a secondary list of pin-compatible alternatives for every integrated circuit in their design. It adds a layer of complexity to the engineering phase, but it prevents total stoppages later. Luna: Pin compatibility is a good standard, but what if the newer chip has different power requirements? That could force a whole power supply redesign. Lucas: That is the trap. Pin compatibility doesn't mean functional equivalence. You still need to verify voltage tolerances and thermal profiles. But having that alternative ready means you aren't scrambling. You can order samples immediately rather than waiting for a quote from a distributor who might not even have stock. Luna: So the strategy is less about avoiding change and more about reducing the friction of switching when it becomes inevitable. Lucas: Precisely. Think of it as insurance against your own success. If your product sells well, demand spikes, and suppliers tighten allocations. If you've already vetted a backup source, you can pivot to them without delaying delivery. It turns a potential crisis into a manageable logistics adjustment. Luna: I wonder how many founders lose sleep over this versus how many just hope for the best until it breaks. Probably most hope for the best. Lucas: Almost certainly. There is also the issue of firmware. When you swap chips, even similar ones, the drivers might need rewriting. That requires QA cycles that eat into your marketing timeline. You can have the perfect product launch window ruined because the engineering team was busy debugging a new peripheral interface. Luna: It highlights why hardware investors ask so hard about supply chain resilience. It isn't just about getting parts; it's about keeping the product stable over time. Lucas: And stability is what keeps customers returning. If you release a batch of devices that behave differently because you swapped components mid-cycle, you open yourself up to warranty claims and reputation damage. Consistency matters more than novelty in durable goods. Luna: Are there specific tools or services that help startups track these component lifecycles automatically, or is it mostly manual spreadsheets? Lucas: There are enterprise-grade platforms that integrate with your electronic design automation files and pull data directly from manufacturer databases. For smaller teams, it is often manual. They subscribe to industry newsletters and check vendor portals weekly. It is tedious, but it is necessary. Luna: Tedious work that pays off by preventing catastrophic delays. It reminds me of how software teams manage dependency updates. They can't ignore libraries forever. Lucas: That is a great analogy. Software dependencies rot too, but you can patch them remotely. Hardware dependencies rot physically, and you have to ship replacements or recall units. The stakes are materially higher. Luna: Definitely. So for someone listening who is just starting to build their first serious product line, what is the very first step they should take? Lucas: Audit your bill of materials right now. Identify the ten most critical components that have no substitutes. Then check their current status. Are they in mass production? Are they approaching end of life? If you find any red flags, start looking for alternatives immediately, even if you don't need them yet. Luna: Proactive auditing instead of reactive firefighting. It shifts the mindset from pure creation to sustainable operations. Lucas: Exactly. Building a company is about creating something that lasts, not just something that launches. The founders who ignore the backend details usually find out too late that their foundation is cracking. Luna: We should talk about listener support briefly. A handful of people chip in monthly through buy me a coffee dot com slash fexingo, and that is literally what funds making this many of these shows possible. Lucas: It allows us to keep this ad-free and focus on deep dives like this one. If you get value from the analysis, consider joining that group of supporters. Luna: It makes a real difference to the production quality and the ability to bring you these detailed conversations every day. Lucas: Back to the topic. Let's look at the financial side of this obsolescence problem. What does it actually cost a startup to replace a major component mid-stream? Luna: Beyond the obvious retooling costs, there is the opportunity cost of delayed sales. How do you quantify that loss in your business model? Lucas: You calculate it based on your burn rate and projected revenue per week. If a delay pushes your launch back by four weeks, multiply that weekly revenue by four. That is the direct hit. Add in the engineering hours spent on the fix, and you often see a double-digit percentage drop in the first quarter's margins. Luna: That is a significant dent. It underscores why some companies choose to pay a premium for older, established components that are guaranteed to stay in production longer. Lucas: They do, and it is a valid trade-off. Sometimes buying a slightly more expensive chip from a legacy manufacturer saves you millions in downstream risks. It is about weighing immediate unit cost against long-term continuity. Luna: It changes how you view the bill of materials entirely. It stops being just a list of parts and becomes a risk portfolio. Lucas: I love that framing. A risk portfolio. Every component is an asset with a depreciation schedule and a failure mode. Managing that portfolio is half the job of a hardware CEO. Luna: Do you think this discipline separates the hobbyist makers from the serious commercial players? Lucas: Absolutely. Hobbyists care about function. Commercial players care about reliability and scalability. The moment you try to sell thousands of units, the lack of a robust component strategy becomes a fatal flaw. Luna: It seems like the skills required to run a hardware business are becoming more akin to running a logistics network than a tech lab. Lucas: They are. The best hardware founders are part engineer, part supply chain manager, and part financial analyst. You cannot succeed with just one lens. Luna: What about the environmental angle? Does choosing longer-lasting components align with sustainability goals for modern consumers? Lucas: It does indirectly. By avoiding mid-cycle redesigns, you reduce waste. You aren't throwing away working boards because of arbitrary part swaps. It creates a more circular and efficient production loop. Luna: So good supply chain hygiene is also good corporate citizenship. It is another reason to invest in these systems early. Lucas: Exactly. It is a holistic approach to building a brand. People notice when products arrive on time and work consistently. Those basics are built on the boring, unglamorous work of component management. Luna: It is easy to overlook the boring parts until they cause a crisis. Starting the audit today could save a launch next year. Lucas: That is the takeaway. Don't wait for the phone call from the supplier. Check your own numbers. See where you stand, and build that buffer now. Luna: A practical, proactive step that protects both the product and the bottom line. It is a smart way to end our discussion on hardware resilience. Lucas: For sure. If you are building the future, make sure the pieces you need will still be there when you are ready to assemble it.