Who actually signs
At a hardware startup between ten and a hundred people, the signer is the CTO, the VP of engineering, or the founder who designed the board. There is a mechanical engineer, an electrical engineer, and a firmware engineer, and none of them has laid out a radio before. The antenna was chosen from the module vendor's reference design and placed where there was room.
The champion is whoever owns the schedule, because certification is on the critical path and it is the one item on the plan with a duration nobody on the team can estimate. At larger companies adding wireless to an existing product line, the buyer is the engineering manager who inherited the feature.
The one sentence version
Your buyer is a hardware founder with a working prototype, an antenna placed by the enclosure designer, and a lab booking they are going to fail.
The triggers, and where each one is visible
- FCC equipment authorization grants. Every intentional radiator sold in the US gets a grant, and the database is public with the grantee, the date, the equipment class and the test firm. A first grant is a company that just went through it and is about to do it again. A competitor's grant in your category is a deadline for everyone else in it.
- Crowdfunding hardware launches. Campaign pages state the wireless features and the delivery month, and the amount raised tells you which ones are real. A campaign with Bluetooth and a Q2 ship date has committed publicly to a certification timeline nobody on the team has estimated.
- Hardware funding rounds. Seed and Series A at connected device, wearable, robotics, drone and industrial IoT companies fund the design that needs certifying. Form D filings and the usual databases surface them, and the company's site says what the product does.
- RF and hardware engineer job posts. A company advertising for an RF engineer has a radio problem now and no one to solve it. A company advertising for a hardware engineer and naming FCC or CE in the description has discovered certification exists.
- The EU cyber requirement for wireless products. Since August 2025, radio equipment sold in the EU has had to meet cybersecurity requirements under the radio equipment rules, and the applicable standards are new to most US hardware teams. Any company selling a connected product in Europe is in scope.
- Product announcements with new radios. A company adding Wi-Fi 6E, ultra wideband, cellular or a second band to an existing product has a new certification cycle and often a new antenna problem.
The grant database and the crowdfunding pages are the two to build on. One tells you who finished, the other tells you who has promised to.
Qualify in sixty seconds
- Is there a radio in the product? Bluetooth, Wi-Fi, cellular, LoRa, UWB, Zigbee. A wired product still needs unintentional radiator testing, but the expensive work is intentional radiators.
- Is there an RF engineer on the team? Check the team page and the job posts. None means the antenna was placed by whoever had room on the board.
- Which markets? US only is one regime. US plus EU is two plus the cyber requirement. Adding Japan, Korea, Canada and Australia is a certification management problem as much as an engineering one.
- Where in the schedule are they? Pre layout is when you save them the most. Post layout with a lab date booked is when they will pay the most. Post failed lab run is when they will pay anything.
The angle that gets replies
Lead with the enclosure. Not the radio, not the certification, the plastic. The founder has not considered that the box detunes the antenna, and the lab run they are about to book will tell them at a cost of weeks and a five figure invoice.
Three openers you can adapt
- On a crowdfunding campaign with a ship date"Congratulations on the campaign, that is a real number. With Bluetooth and a June delivery, the certification lab date needs to be in April and the design needs to pass it the first time. The most common first time failure is the antenna detuning inside the final enclosure. An hour with the CAD file usually shows whether that is a risk. Happy to look."
- On an RF engineer job post"Saw the RF engineer posting. That search usually runs four months, and if the board is already laid out the radio needs attention before then. The two things I would check first are the ground plane under the antenna and the keep out on the module vendor's reference. Two paragraphs on what usually goes wrong at that stage, attached to nothing."
- On a competitor's FCC grant"Your competitor's grant posted last week for the same product category. The lab they used and the equipment class tell you roughly what they had to pass. If you are targeting the same shelves, the pre compliance scan that predicts a pass is about a week. Here is what it covers."
Each one names a physical thing about their product and connects it to a date they care about. That is a colleague's note, not a lab's brochure.
What not to send
- "Guaranteed to pass." Nothing is guaranteed to pass, and every engineer who has stood in a chamber watching a spur at the wrong frequency knows it.
- A list of test standards. "We test to FCC Part 15, CE RED, ISED, MIC and more" is a lab's menu. The reader does not have a menu problem, they have an antenna problem.
- Confusing certification with design help. If you sell design, do not lead with lab services. If you sell lab services, do not pretend to be a design house. The founder can tell.
- Penalty fear. Nobody at a hardware startup is worried about an enforcement action. They are worried about a ship date.
The objection you will hit
We are using a pre certified module, so we do not need testing. The module's grant covers the module, under the conditions on the grant, with the antenna the module vendor tested. Put it in an enclosure, change the antenna, move it next to a battery, and the conditions no longer hold. The host product still needs its own unintentional radiator testing regardless, and the EU requirements do not care about the module at all. Say the module saves the intentional radiator work and nothing else.
The second is our contract manufacturer handles certification. They do, after the design is locked, at which point every fix is a respin. The CM is the right party to run the final lab visit and the wrong party to catch the problem in layout.
The third is we will deal with it at the end. That is the plan that produces the failed lab run. A failed run is typically four to eight weeks and a five figure invoice, and the fix is a board respin with its own lead time. The pre compliance scan is a week and it predicts the result.
Deal shape
- Design review of the RF section and enclosure: commonly $3K to $10K. The engagement that opens most relationships.
- Pre compliance testing and characterization: $5K to $20K, and the deliverable that predicts the lab result.
- Antenna design and integration for a custom radio: $15K to $60K.
- Certification management across multiple regimes: $10K to $40K in fees plus lab costs, which commonly run $15K to $50K and up for a multi market product.
- Retainer for a product line: $3K to $10K a month for companies shipping several SKUs a year.
- Signer: CTO, VP Engineering or founder. Cycle: two to six weeks, tied to hardware milestones, and days after a failed lab run.
The design review is the funnel. It is small enough that the founder approves it without a conversation, and it produces a written list of what will fail, which is the rest of the engagement.
A cadence you can actually run
- Weekly, pull new FCC grants in the equipment classes you serve, and note which test firm each used. A grantee that went through a large lab with no design partner is a prospect for the next product.
- Weekly, pull hardware crowdfunding campaigns above a funding threshold with wireless features and a delivery date.
- Weekly, pull hardware funding and RF or hardware engineer job posts.
- Qualify against the four checks, with the schedule position first. One message per account, naming the physical thing about their product. Fifteen to twenty accounts a week is a full program.
- Three touches over two weeks, then stop. The next product announcement or the next funding round is a fresh reason to write.
The founder has told the world their ship date on a campaign page. The consultants who grow are the ones who write to them the week the campaign closes, before the lab is booked.
The sending mechanics most people get wrong
Everything above is about who and what. This is about how, and it is where most outbound in this niche quietly dies. Seven rules. None of them are optional.
1.Three to five sentences. That is the whole email.
Your reader is on a phone between meetings. One observable fact about their company, one consequence they have not thought about, one specific thing you would do. Anything past five sentences is a memo, and memos get archived unread.
2.Lead with a technical differentiator that turns into a number.
The messages that work best name something concrete you do differently and translate it into time or money saved. In this niche the differentiator is first pass rate. A consultancy that can say what fraction of the products it reviewed passed the lab on the first run, against the industry's common experience of two or three attempts, has the only number the founder cares about. The second is enclosure work: state how many antenna integrations you have done in the product category.
Most services firms do not have a technical differentiator, and pretending to have one reads as exactly that. The substitute is a verticalized case study: a company like theirs, what you did, what happened, in one sentence. For this niche the line is: a 14 person wearable company, campaign shipped on the announced month, antenna redesigned for the final enclosure in week two, FCC and EU grants on the first lab visit, one respin avoided. The ship month and the single lab visit are what the reader will check.
3.Ten to twenty emails a day per mailbox. Not a hundred.
Sender reputation is scored per mailbox and per sending domain. One inbox pushing a hundred cold emails a day looks like exactly what it is, and the penalty lands on the domain, which means it lands on your client correspondence too.
If the math says you need more volume, the answer is more mailboxes on more warmed sending domains, separate from the domain you invoice from. It is never more volume per mailbox. Fifteen to twenty accounts a week at three touches is nine to twelve emails a day, one warmed mailbox. The crowdfunding calendar clusters around a few launch windows a year, and those are the weeks to consider a second mailbox.
4.Write ten versions of every step and test them.
Versions A through J, not A and B. Rotate subject lines and bodies. You learn which angle is actually working instead of guessing, and there is a second reason that matters more: identical bodies going out over and over is one of the patterns postmaster tools flag. Variation is a deliverability tool as much as a testing one.
Subject line seeds for this niche, each of which should become several variants: "your June delivery", "the RF engineer posting", "your competitor's grant". Lower case, no punctuation tricks, and nothing that would look odd in a reply from a colleague.
5.Stop at three.
Most replies arrive on the first and second email. The third is already thin. Every touch past that raises the odds the whole thread gets classified as spam, and that classification follows the mailbox to the next person you write to. The long cadence is over. Three touches, each with something new in it, then leave them alone for ninety days.
6.Know what good looks like.
A one percent reply rate with a quarter of those replies positive is a healthy trigger based program. Anyone quoting you double digit reply rates is counting out of office messages or selling a course.
7.LinkedIn Sales Navigator is not optional.
Every other data source tells you who held a title at some point. Sales Navigator tells you who holds it today, because the person maintains it themselves. That is the difference between a three percent bounce rate and a fifteen percent one, and bounces are scored against the mailbox the same way spam complaints are. Verify the name there before anything goes out.
It is also the cheapest trigger detector you will own. The job change filter surfaces people who arrived in a role in the last ninety days, which is the moment they have budget and no incumbent. The posted recently filter surfaces companies talking about the exact problem you solve. Account lists with headcount growth alerts tell you who is scaling before the press release does. For this niche the saved search is headcount 10 to 100 in consumer electronics, IoT, wearables, robotics and drones, titles CTO, VP Engineering, Head of Hardware and founder, with the job change alert on for hardware titles and a keyword alert on RF engineer, FCC and antenna across job listings. Navigator confirms the person. The FCC grant database and the crowdfunding platforms are the source.
Use it for the research and the verification, not for the message. InMail reply rates are a fraction of email, and the person who replies to a thoughtful email is the same person who ignores a connection request with a pitch attached. Pull the work email from a data provider once Navigator has confirmed the person is real and current.
None of this is specific to your niche. All of it is specific to whether anyone ever reads the angle you spent an hour getting right.
If you would rather not run it yourself
That is what we do. ExpertLayer runs this exact loop for expert led firms: the weekly grant and campaign pull, the qualification with the schedule question first, the angle per account naming the physical thing, the sending across warmed mailboxes, and the reply reading. You take the conversations and do the RF work.
The first step is free and it is the same research described above. Send us your website and we will come back with 10 companies that hit these triggers right now, with the grant or campaign, the contact, and the opening line for each.
Questions from people running this
The FCC grant database shows companies that already got through. Why write to them?+
Three reasons. A first grant is a company about to design its second product with the same team and the same mistakes. A grant obtained through a big test lab with no design help usually cost two or three lab runs, which the founder remembers. And a competitor's grant in your product category tells you every other company in that category is now late.
Crowdfunding campaigns are full of products that never ship. Worth the time?+
The ones that raise real money ship, and almost all of them ship late, and the most common reason for the delay is certification. A campaign page with a wireless feature and a delivery date is a company that has committed publicly to a date it cannot hit without you. Filter by funds raised and you remove most of the noise.
Module or custom radio, which do I lead with?+
Neither. Lead with the enclosure, because that is where the antenna gets detuned and where the founder has not thought to look. The module question comes up in the first call, and the honest answer is that a pre certified module removes the intentional radiator testing and none of the rest.
Is the EU cyber requirement for wireless products a real opener?+
For any company selling wireless products in Europe, yes. The requirement has applied since August 2025, it reaches every connected product with a radio, and most US hardware startups discovered it from their EU distributor. A note that names it and explains what it means for a product with a Bluetooth chip is both new information and immediately actionable.