I have seen this pattern more times than I care to count. A team completes every schematic review without a red flag, selects a certified module, and confirms the antenna fits within the allotted footprint. Then the first prototype comes back from the chamber with weak radiated power—or worse, a certification result that sends the whole program back for another spin.

In every one of those cases, the root cause was not the component. It was the RF system built around it—designed without ever treating the antenna as an integrated part of that system from day one.That is an engineering process failure, and it is one we can fix.

The Antenna-Last Habit Is Costing Us Spins

The default sequence on most wireless product programs goes like this: define the application, select the module, shape the enclosure, route the PCB, then find an antenna that fits whatever space is left. When board area is generous and RF requirements are straightforward, you can get away with it.

We no longer have that luxury. Today’s wireless devices are shrinking while simultaneously adding bands and tightening certification requirements. Berg Insight estimates that annual cellular IoT antenna shipments hit 757 million units in 2025—with 90% of them internal. Every one of those antennas must radiate from inside a product where the PCB ground plane, enclosure, battery, and surrounding metalwork become active participants in the radiating structure.

That constraint has an uncomfortable implication: changing any one of those structural elements after antenna position is set can shift impedance, resonant frequency, or radiation pattern enough to invalidate the design. At sub-GHz and low cellular bands, the margin shrinks further—wavelength is inversely proportional to frequency, so these antennas need more electrical length and more help from the host structure. A ground plane that is too small or broken by slots does not just degrade performance—it can make a design that tuned cleanly on the bench fail completely in the final product.

When teams discover this late, the consequences compound. We reach for a matching network to correct frequency shifts. TRP shortfalls found at certification force layout or enclosure changes that reset tooling. Each fix restarts a timeline that was already committed. The further downstream we find this, the fewer options we have.

Datasheets Do not Predict Product Performance—Integration Does

I want to address a misconception that creates false confidence early in a program. Antenna datasheets describe behavior on a reference board with controlled clearance and defined measurement conditions. That reference board is engineered to show the antenna at its best:clean ground plane, proper keep-out, no enclosure effects, no battery pressing against the element.

A finished wireless product presents a fundamentally different RF environment. A tracker bolted to a metal asset changes the ground plane geometry. A meter mounted inside a metal cabinet creates reflections and blockage. A wearable pressed against skin introduces lossy tissue into the near field. Each deployment shifts the impedance the antenna sees and the radiation the device produces.

The variables that determine the outcome are well understood by anyone who has done this work: antenna position relative to metal and ground, whether the keep-out zone is actually clear of copper, components and mechanical parts, whether the feedline is properly referenced to 50Ω across its full length, and whether the matching network compensates for the real-device environment rather than masking a deeper layout problem. These are not antenna selection problems.They are integration decisions made—or not made—during PCB layout.

One clarification worth stating explicitly for our teams: bench return-loss measurements and OTA measurements answer different questions. Bench measurement tells you whether the antenna is matched. OTA measurement—TRP for radiated power, TIS for receive sensitivity—tells you whether the complete device actually works in the real world. Both are necessary. Neither replaces the other.

Multi-Radio Designs Multiply the Integration Risk

The integration gap widens significantly when multiple radios share a small enclosure, and that is the reality of most modern IoT designs. A typical wireless tracker might combine LTE-M with GNSS and Bluetooth. A smart meter might run cellular alongside a short-range wireless stack. Each radio brings its own bands, power levels, sensitivity requirements, and antenna constraints.

The coexistence problem is quantifiable,and it is severe. A cellular transmitter operates around 23 dBm. A GNSS receiver is trying to detect signals around −130 dBm.That is a 150+ dB difference. If cellular energy couples into the GNSS receive path, the receiver desensitizes—resulting in slow positioning, unstable fix, or complete failure. Antenna spacing, filtering, grounding, and shielding can address this. But they must be considered during layout. By the time coexistence problems show up in the chamber, every layout decision that could have prevented them is already locked.

Every radio added to a design is another constraint our layout engineers need to understand from the start of the project—not as an afterthought during bring-up.

Certification Tests the System—Not Just the Antenna

There is a persistent misconception I have heard from program managers and even some engineers: that we are“certifying the antenna.”We are not. For wireless products, the device is certified. The antenna is one component of the RF system under test.

Two OTA measurements decide the outcome: TRP, which captures how effectively the device radiates power, and TIS, which captures how well it receives weak signals. Both are shaped by antenna placement, board layout, noise floor, and enclosure effects. Both reflect integration quality—not component quality alone.

A device can show clean return loss on the bench and still fail TRP in the chamber because radiation is absorbed, blocked, or redirected by the enclosure and internal structures. The bench measurement tells you the antenna is matched. The chamber tells you whether the complete device radiates or receives efficiently.

The commercial consequences of discovering an RF integration problem at certification are significant. As Berg Insight notes, cellular device certification spans regulatory, industry, operator, and application-specific requirements. By the time a device is in the certification chamber, enclosure tooling is paid for,component sourcing is committed, operator approval timelines are running, and launch dates are on the record with customers. A board respin at that point is not just an engineering cost.It is a product launch delay.That is not a risk any of us should be accepting when it is preventable.

What Antenna-First Engineering Actually Means in Practice

Antenna-first design does not mean selecting an antenna before selecting a radio. It means treating antenna integration as a layout requirement from the start—not a post-layout correction.

Concretely, this means our teams evaluate whether antenna position, board dimensions, and ground plane will support the required bands before the first layout is locked. A structured approach toIoT antenna designstarts with these constraints. We review clearance zones against actual component placement. We review clearance zones against actual component placement. We verify that the feed transmission line preserves 50Ω impedance. We confirm the matching network is accessible for tuning when the first prototype arrives. These are not heroic engineering acts. They are process disciplines that prevent expensive late discoveries.

The goal is not to eliminate RF measurement—RF still requires measurement, full stop. The goal is to make the first prototype close enough to expected behavior that measurement confirms the design rather than reveals its problems. When that happens, the lab becomes a validation step. When it does not, the lab becomes a discovery phase that feeds an unplanned respin cycle.

Managing RF Risk with the Right Tools and Partners

One approach worth understanding is Ignion’s Virtual Antenna® technology—a three-part architecture comprising an antenna booster, a tunable matching network, and the PCB ground plane, with over 100 million devices deployed. What makes this model relevant to our process discussion is the matching network path: it gives engineering teams a tuning mechanism accessible during DVT without requiring a board respin.

Their Oxion™ platform enables pre-prototype evaluation of placement, clearance, and ground plane constraints against actual layout—exactly the kind of upstream validation our teams need to be doing regardless of which antenna solution they choose. When a prototype shows a frequency shift due to enclosure effects or component proximity, having a matching network that can compensate—provided the underlying layout supports it—is operationally meaningful.

The broader point: tools and partners that support pre-prototype RF evaluation and DVT-stage tuning are worth integrating into our standard development workflow. The alternative—treating RF as something we validate at the end—has a well-documented cost in respins, delays, and certification failures.

The Direction of Travel Is Clear

Berg Insight projects cellular IoT antenna shipments will exceed one billion units annually by 2030. More internal antennas, more compact enclosures, more bands per product, more certification paths per region. The integration challenge is not getting simpler.

The teams that manage this well in the years ahead will not differentiate by picking better antennas.They will differentiate by building RF constraints into their process early enough that those constraints shape the design rather than break it.

That is the shift I am asking product development engineering teams to make—treat RF integration as a first-class design constraint from day one, not a problem to solve after the layout is locked. Teams that commit to this discipline will spend less time in debug, less time firefighting at certification, and more time moving confidently from DVT through PVT and into a clean product launch. The antenna does not get easier to integrate as the schedule compresses. But the path to launch gets significantly shorter when the hard RF decisions are made at the start of the program, not at the end of it.