Latest / Hardware Startups with Fexingo: Devices, Robotics, and Manufacturing Tech Companies / How Hardware Startups Master the Certification Maze
Transcript
- Lucas: You spend months designing a prototype, you get it working, you're ready to ship — and then you discover the real last mile isn't manufacturing. It's certification. Luna: Right. The FCC, the UL, the CE marks — it's this whole hidden layer that can kill your timeline and your budget if you don't plan for it. Lucas: Exactly. I was talking to the founder of a smart-lock startup — let's call it LockIn — that had a beautiful product. Wireless, biometric, sleek. They raised two million dollars on a prototype that worked perfectly in the lab. Luna: The classic trap. Lucas: The classic trap indeed. They'd never budgeted for certification. When they finally sent their device to a certified testing lab, they got hit with a list of failures. The radio emissions were too high. The battery compartment didn't meet UL safety standards. The enclosure material didn't pass the drop test. Luna: How much did that set them back? Lucas: Eighteen months and roughly four hundred thousand dollars in re-spins, retesting, and engineering time. They almost ran out of money. And they're not unusual — I've heard similar stories from a dozen hardware founders. Luna: And it's not just about money. It's the opportunity cost. While you're stuck in certification hell, your competitors are shipping. Lucas: Exactly. So let's break down what certification actually means for a hardware startup. There are really three main buckets. First, radio and wireless — that's FCC in the US, CE in Europe. They test that your device doesn't interfere with other electronics, and that it's safe from an RF exposure perspective. Luna: And that's mandatory. You literally cannot sell a wireless device in the US without FCC certification. Lucas: Right. Second bucket is safety certification — UL in the US, IEC standards globally. That covers things like fire risk, electric shock, battery safety. For a smart lock, UL 294 is the standard for access control systems. Luna: And the third bucket? Lucas: Environmental and performance — things like IP ratings for water and dust ingress, or drop tests. Those aren't always mandatory, but they're often required by retailers or insurance companies. Luna: So the startup has to navigate all three, often simultaneously, with different labs and different timelines. Lucas: Right. And the killer is that each certification cycle can take two to six months. If you fail, you iterate, resubmit, and wait again. The LockIn startup failed their FCC test three times because of a noisy power supply design. Luna: Three times. That's brutal. Lucas: Yeah. And each retest cost them around fifteen thousand dollars and eight weeks. So the single biggest piece of advice I hear from seasoned hardware founders is: do pre-compliance testing. Luna: Pre-compliance. Meaning you test early and cheaply, before you go to the official lab. Lucas: Exactly. You buy or rent a spectrum analyzer, you set up a basic EMC test in your own office, you catch the obvious problems yourself. It's not a substitute for the real thing — but it filters out maybe eighty percent of the common failures. Luna: And that can save months. I've heard of startups that built a small shielded enclosure in their garage for a few thousand dollars and did their own pre-scan. Lucas: Yeah. The other big tactic is to bring a compliance engineer onto your team early — even part-time. Someone who's been through the process before and knows exactly what the labs look for. Luna: Because there's a lot of tribal knowledge. For example, did you know that if your device has a USB port, the FCC considers it a 'digital device' and has different rules than if it's purely wireless? Lucas: I did not know that. And that's exactly the kind of gotcha that can derail you. Another one: UL has very specific requirements for the spacing between PCB traces and the enclosure — if you're off by a millimeter, you fail. Luna: So what about the CE mark for Europe? Is it similar? Lucas: Similar in spirit, but the process is different. CE marking is self-declared — you, as the manufacturer, declare that your product meets the relevant EU directives. But you need technical documentation to back it up, and if you're caught falsifying it, the penalties are severe. Luna: So you still need to test. It's just that the testing can sometimes be done in-house if you have the right equipment. Lucas: Right. And for some products, you need a 'notified body' — an independent lab — to certify you. Medical devices, for example, or anything with a battery over a certain watt-hour rating. Luna: This is really making me rethink the whole 'hardware is hard' cliché. It's not just about making the thing work — it's about making it legal to sell. Lucas: And that's actually a moat. Because once you've navigated certification for your first product, you have a process. You know the labs, you know the timelines, you know the failure modes. Your competitors who haven't done it are at a huge disadvantage. Luna: So for a new hardware founder listening: where should they start? Lucas: First, identify which certifications apply to your product. The FCC has a searchable database of equipment authorization — look for similar products and see what they're certified under. Luna: That's smart. Reverse engineer the compliance path of products already on the market. Lucas: Exactly. Then, budget for certification as a line item from day one. The rule of thumb I've heard is to allocate ten to fifteen percent of your total development budget for compliance. Luna: And plan for at least one retest. Because you will miss something. Lucas: If today was actually useful to you, the way these stay ad-free is listener support. You can buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. No pressure — just if you got value. Luna: Yeah, it's a small gesture that keeps us independent and lets us dig into these nitty-gritty topics. We appreciate it. Lucas: Alright, back to certification. One more thing I want to hit: don't treat certification as a one-time event. If you update your firmware or change a component, you may need to recertify. Luna: That's the hidden recurring cost. Especially for IoT devices that get firmware updates. Lucas: Right. The FCC rule is that if a change affects the radio frequency characteristics — which a firmware update can — you need a new certification. So you need a process for managing that. Luna: I've seen startups that design their hardware with certification in mind from the start. For example, using modular RF modules that are already certified — like those from u-blox or Sierra Wireless. Lucas: That's a huge time saver. If you use a pre-certified module, you can leverage its certification under the 'modular approval' rules. It doesn't exempt you entirely, but it reduces the testing burden significantly. Luna: So the takeaway: certification is not a checkbox at the end. It's a design constraint you need to integrate from the beginning. Lucas: And the startups that treat it that way are the ones that get to market faster and with less waste. The ones that ignore it are the ones we hear about at post-mortem panels. Luna: Yeah. So next time you're sketching a PCB layout, think about the FCC engineer who's going to look at it six months from now. Lucas: Great way to put it. That's all for this episode of Hardware Startups with Fexingo. Next time we'll look at how hardware startups are using simulation to cut prototyping costs. See you then.