Latest / Hardware Startups with Fexingo: Devices, Robotics, and Manufacturing Tech Companies / How Hardware Startups Use Pre-Compliance Testing to Avoid Certification Delays
Transcript
- Lucas: If you're building a hardware product that emits any kind of radio frequency — which these days is basically anything with wireless connectivity — you can't just ship it. You need FCC certification in the US, CE marking in Europe, and similar requirements elsewhere. Luna: And that process can easily eat up three to six months and fifty to a hundred thousand dollars. But the real killer is if you fail the official test and have to re-design and re-test. Lucas: Exactly. And that's part of why we're able to keep this show ad-free — listener support through buy me a coffee dot com slash fexingo makes a real difference. A couple of dollars a month from people who find these episodes useful helps us cover research and production. Luna: Yeah, it's how we stay independent and focused on what actually matters for builders. So what's the smarter way to approach certification without betting your entire timeline? Lucas: Pre-compliance testing. Instead of booking an accredited lab for the full, formal test — which can cost $1,000 to $2,000 per hour — you go to a smaller, non-accredited facility or an open lab session and run a subset of the tests yourself. Luna: So it's like a dress rehearsal. You get a heads-up on whether your product will pass, and you catch issues when they're still cheap to fix. Lucas: Right. I talked to a startup that was building a Wi-Fi smart lock — one of those ones you can open with your phone. They spent about $10,000 on a few pre-compliance sessions at a local university's open lab. They discovered that the Wi-Fi module was radiating noise on a harmonic that would have failed the FCC Class B radiated emissions limit. Luna: A harmonic. Meaning a frequency multiple of the fundamental clock. That's the kind of thing that's hard to spot in simulation but shows up clearly on a spectrum analyzer in a semi-anechoic chamber. Lucas: Exactly. They fixed it by adding a small ferrite bead on the antenna line and adjusting the PCB ground-plane stitching. Total cost of the fix: maybe $200 in parts and a board respin. If they'd gone straight to the accredited lab and failed, they'd have lost six weeks and paid another $40,000 for a re-test. Luna: Forty thousand dollars — that's a huge chunk of a hardware startup's seed round. So pre-compliance isn't just about speed, it's about survival. Lucas: It really is. And the key distinction is between intentional emitters and unintentional emitters. A Wi-Fi module is an intentional emitter — it's designed to transmit. But even a device without any radio, like a smart coffee maker that only uses a wired connection, can still generate enough electromagnetic interference to fail radiated emissions tests. Luna: Because every clock signal, every switching regulator, every fast digital line is basically a tiny radio transmitter. The FCC cares about all of them. Lucas: Exactly. So when should you start pre-compliance testing? Ideally, as soon as you have a functional prototype on a PCB that's close to your final layout. Maybe revision two or three. You don't need a fully enclosed product — you can test with the board exposed and get useful data. Luna: And you don't need to test everything. Focus on radiated emissions, conducted emissions, and maybe electrostatic discharge if your product has exposed connectors or a touch interface. Lucas: Radiated emissions is the big one for wireless products. The FCC limit for Class B devices — that's consumer electronics — is 40 dB microvolts per meter at 3 meters for frequencies between 30 and 230 MHz. If you're above that, you fail. Luna: But in a pre-compliance setting, you might not be able to measure exactly at 3 meters. You can use a near-field probe or a smaller chamber and apply correction factors to estimate the far-field result. Lucas: That's the art of it. The correction factors aren't perfect, but they're good enough to tell you whether you're in the red zone or the green zone. If you're 10 dB below the limit in pre-compliance, you can be pretty confident you'll pass the full test. If you're only 2 dB below, you might want to rework your shielding before going to the accredited lab. Luna: So pre-compliance gives you a confidence interval. It's like a weather forecast: you know if you need an umbrella. Lucas: Exactly. And the cost is usually $200 to $500 per hour for an open lab session, compared to $1,000 to $2,000 for a fully accredited chamber. Many universities, like the University of Texas or Stanford, have open lab programs where startups can book time. There are also commercial pre-compliance labs that specialize in early-stage testing. Luna: And you can often bring your own test equipment if you know what you're doing. A decent spectrum analyzer and a set of near-field probes can cost under $5,000. That's a one-time investment that can save you tens of thousands in re-test fees. Lucas: Absolutely. But I want to be clear — pre-compliance is not a substitute for full certification. You still need to go to an accredited lab for the final test. The goal is to go there knowing you'll pass, ideally on the first attempt. Luna: How many startups actually fail the first time? I've heard numbers like 30 to 40 percent. Lucas: It's even higher for first-time founders. One certification lab I spoke to said about 60% of consumer electronics fail radiated emissions on their first try. And the most common fix is something simple: a poorly designed ground plane, unshielded cables, or missing ferrite beads on I/O lines. Luna: Which are all things you can catch and fix in pre-compliance for a few hundred dollars. So instead of paying $40,000 for a re-test, you pay $10,000 for pre-compliance and maybe one extra board spin. Lucas: Exactly. And here's another tip: schedule your pre-compliance sessions early in the week. If you find a problem on Monday, you have the rest of the week to implement a fix before the lab closes. Some labs let you come back for a quick re-scan at a reduced rate. Luna: That's practical advice. I also want to ask about intentional emitters like Bluetooth or Wi-Fi. Those have additional requirements like frequency hopping and power limits. Can pre-compliance help with that too? Lucas: Yes, but it's a bit trickier. For intentional emitters, the FCC requires module certification for the radio itself. If you buy a certified module — like a common one from Espressif or Qualcomm — you're allowed to use it in your product with less testing. But you still need to test the whole system for radiated and conducted emissions, because the antenna placement and enclosure can change the radiation pattern. Luna: Right. So if you put a certified Wi-Fi module into a metal enclosure, you might need to add an external antenna and re-test. Pre-compliance can tell you if your antenna choice is causing problems. Lucas: Exactly. And the same goes for Bluetooth. A lot of startups get caught out by the fact that Bluetooth uses frequency hopping spread spectrum — it's designed to be robust, but if your product has a noisy power supply, it can desensitize the receiver and reduce range. Luna: Pre-compliance would show that as a higher noise floor on the spectrum analyzer. You'd see that the Bluetooth signal is barely above the noise, and you'd know you need better power supply filtering. Lucas: Exactly. So the bottom line is: don't wait until you're ready to ship to think about certification. Start pre-compliance as soon as you have a representative prototype. It's one of the best investments a hardware startup can make. Luna: And if you're listening and you've been through this yourself, we'd love to hear your story. What was the most unexpected fail you caught in pre-compliance? Lucas: Or what question do you have about getting started? You can find us on the Fexingo network. For now, the key takeaway: pre-compliance testing is your safety net. Use it.