Latest / Hardware Startups with Fexingo: Devices, Robotics, and Manufacturing Tech Companies / Why Hardware Startups Need a Second Supply Chain
Transcript
- Lucas: So you've spent eighteen months designing a piece of robotics hardware. You've raised your seed round, you've got a prototype that works, you've signed with a contract manufacturer in Shenzhen. And then one day, the factory loses power for a week because of a grid issue. Or a key component gets stuck at customs. Or a trade dispute suddenly adds a twenty-five percent tariff on your main imported subassembly. Luna: And suddenly your entire timeline — your entire company — is hostage to a single point of failure. Lucas: Exactly. That's the nightmare scenario for a hardware startup, and it's more common than people think. In the last few years, we've seen pandemic-era shutdowns, the Suez Canal blockage, semiconductor shortages. For a young company with thin margins and no safety net, one supply chain hiccup can be fatal. Luna: So what's the fix? Because I think most founders I talk to say, look, we can barely manage one supply chain. How are we supposed to manage two? Lucas: That's the tension. The textbook answer is dual sourcing — having a second supplier for your critical components, ideally in a different geography. But for a startup, that's expensive and complex. You're splitting smaller volumes across two suppliers, which means you lose economies of scale. You have to qualify a second manufacturing line, test for consistency, maintain relationships. Luna: And the second supplier might not be as good. Or they might be more expensive. Lucas: Right. So the question becomes: where do you draw the line? You can't dual-source everything. But you can identify the components that are highest risk — longest lead times, sole-source parts, things that are commodity-like but still critical. Let's take a concrete example. Luna: I'm listening. Lucas: Say you're building a small autonomous delivery robot. The motors, the lidar sensor, the battery pack — those are likely single-source, custom parts. But the fasteners, the wiring harnesses, the PCB assemblies — those can often be sourced from multiple vendors without a huge quality delta. A smart startup might dual-source the PCBs and the harnesses, while accepting single-source risk on the lidar. Luna: But if the lidar supplier has a fire, you're still dead. Lucas: You are. And that's where you need a different strategy: buffer inventory. You hold, say, three months of lidar units in a bonded warehouse. That costs capital — maybe two hundred thousand dollars sitting on a shelf — but it buys you time to find an alternative supplier if something goes wrong. Luna: And that's a hard sell to investors who want to see that cash deployed into product development. Lucas: It's a very hard sell. But I've seen startups that survived precisely because they had that buffer. There was a robotics company I followed a few years ago — they had a single source for a custom motor controller. Their supplier in Thailand had a flood. They had six weeks of inventory, which was enough to air-freight parts from a backup supplier they'd qualified but never used. That six weeks saved them. Their competitor, who had just-in-time inventory, was down for four months. Luna: So the buffer is insurance, and you have to decide how much insurance you're willing to pay for. Lucas: Exactly. And the calculus changes as you scale. In the prototype phase, you might accept higher risk because your volumes are tiny. But once you're shipping a thousand units a month, the cost of downtime is huge. Your customers are dependent on you. Your investors are watching your gross margin. Suddenly that buffer inventory looks like a good investment. Luna: Let's talk about geography. A lot of hardware startups have been moving from China to Mexico or Vietnam to reduce tariff risk. But does that create its own single point of failure problem? Lucas: It can. If every hardware startup in your cohort moves to the same industrial park in Guadalajara, you're all exposed to the same local risks — labor shortages, energy prices, maybe even cartel activity. The smart play is to have your primary line in one country and a secondary line — even if it's smaller — in a different region. Maybe your main assembly is in Mexico, but your PCB stuffing is done in Vietnam. Luna: That adds complexity in logistics. Now you're managing freight between two countries for subassemblies. Lucas: It does. But that complexity is a manageable problem. The unmanageable problem is not being able to ship anything. I'd rather deal with a complicated bill of materials than a zero-revenue month. Luna: Are there any tools or platforms that help startups model this? Like, 'if I dual-source this component, what's my expected cost increase versus my risk reduction'? Lucas: There are supply chain simulation tools — companies like Resilinc or SourceDay offer platforms that can model disruption scenarios. But they're often priced for enterprises. For a startup, you're doing this on a spreadsheet. You list your critical components, assign a risk score, estimate lead times, and then decide where to invest in redundancy. Luna: And you're making judgment calls. There's no perfect formula. Lucas: No perfect formula. But there are patterns. One pattern I see in successful hardware startups is that they start thinking about supply chain resilience before they need it. During the prototype phase, they deliberately qualify two suppliers for every critical part — even if they only order from one. They keep the second supplier warm with small orders every quarter. That way, if disaster strikes, they can ramp up quickly. Luna: That's a good habit. It also gives you negotiating leverage with your primary supplier. Lucas: Absolutely. If your primary supplier knows you have a qualified backup, they're more likely to give you better pricing and lead times. It's a subtle power dynamic, but it matters. Luna: We should talk about the cost side more concretely. What's the premium for dual sourcing? Lucas: It depends on the component. For commodity parts like resistors or capacitors, the premium might be negligible — a few percent. For custom mechanical parts, the tooling cost alone might be ten thousand dollars per supplier. So you're doubling your tooling investment. For a startup, that's real money. Luna: But you can phase it. Maybe you dual-source only after you hit a certain volume. Lucas: Right. A common approach is: in year one, single-source everything and accept the risk. In year two, once you have revenue, start qualifying a second supplier for your top three riskiest components. By year three, you want full redundancy on anything that would halt production. Luna: That's a pragmatic roadmap. And it matches what I've seen from founders who've been through a disruption — they all say they wished they'd done it sooner. Lucas: Exactly. The ones who survive a supply chain shock are the ones who had a plan B, even if plan B was more expensive or slower. The ones who don't have a plan B often don't survive. And in hardware, the failure rate is already high. You don't want to add supply chain fragility on top of all the other risks. Luna: Before we move on, I want to touch on something you said earlier about investor pressure. A lot of founders feel like they can't justify the cost of a second supply chain to their board. Lucas: It's a tough conversation. But I think the framing matters. Instead of presenting it as a cost, present it as risk management. Say: 'We have a thirty percent chance of a supply chain disruption in the next two years. If it happens, we lose six months of revenue. Investing fifty thousand dollars now in dual sourcing reduces that probability to five percent.' That's a conversation investors understand. Luna: And you can show them the math. If your monthly revenue is a hundred thousand, six months of downtime is six hundred thousand. Fifty thousand is a good insurance premium. Lucas: Exactly. And if they still push back, you can start with a smaller step — just buffer inventory on one critical component. Something that gives you a few weeks of breathing room. Luna: Speaking of breathing room — there's another angle I've been thinking about. These conversations we have on the show, they're useful for founders who are building real companies. And I think it's worth mentioning that we deliberately keep this show ad-free. No sponsors, no commercial breaks. That's a choice we made because we want the content to be purely valuable, not interrupted by someone selling you a CRM tool. Lucas: That's right. And that only works because some listeners choose to support us directly. If you find value in episodes like this — if it helps you think about your own supply chain strategy — there's a link where you can buy us a coffee, as the saying goes. It's buy me a coffee dot com slash fexingo. That's it. No pressure. It just keeps the show independent and focused on what matters. Luna: And it means we can keep drilling into these specific, nitty-gritty topics that might not get covered elsewhere. Now, back to supply chains — I want to ask about the software side. How do startups manage the complexity of multiple suppliers? Is there a minimum viable approach? Lucas: There are lightweight tools, even just a shared spreadsheet with lead times, minimum order quantities, and contact info. Some startups use a simple ERP like Odoo or even a Notion database. The key is to keep it updated. I've seen companies where the supply chain data is in someone's head, and when that person leaves, everything falls apart. Luna: So institutional knowledge matters, but so does documentation. Lucas: Absolutely. And one more thing: don't forget to actually test your backup supply chain. I've seen startups that have a second supplier on paper, but when they try to place an order, they find out the supplier has changed their specifications or gone out of business. You need to run a small order through the backup line at least once a year. Luna: That's a great point. It's not just about having a name in a spreadsheet. It's about having a relationship that's alive. Lucas: Right. And that takes time. But it's time well spent. Because in hardware, the difference between a successful company and a failed one is often just the ability to keep shipping. Luna: So to summarize what we've learned today: identify your critical components, decide where to dual-source, build buffer inventory for the rest, and keep your backup relationships warm. And start early. Lucas: That's the playbook. It's not glamorous, but it works. And for a hardware startup, that's what matters. Luna: Thanks for listening, Lucas. Lucas: Thanks, Luna. And thanks to our listeners. We'll be back next time with another deep dive into the real mechanics of building hardware companies.