Five years ago, I became the person at my company who flinches when someone asks "how much is that module?"
I'm not an engineer. I wasn't hired to understand RF paths, protocol stacks, or carrier aggregation. My job is procurement—buying the right components at the right price and keeping our product launches on schedule and on budget. But in the world of IoT connectivity, those two goals often collide.
I've signed off on over 200 purchase orders for wireless modules since 2020. Quectel EC20s, RM500Q 5G modules, GNSS units, antennas, the works. And the most expensive lesson I've learned is this: the spec sheet never tells you the whole story.
The $18,000 Mistake I Made in My First Year
When I took over purchasing, I did what most non-engineers would do. I compared specs, compared prices, and picked the cheapest module that looked like it would work. I remember watching our senior engineer's eyes roll when I asked whether we should even be looking at the NXP vs Quectel question. I didn't understand the debate. I just saw two brands making silicon and assumed the cheaper one made sense.
That assumption cost us about $18,000 in engineering time, nine weeks of schedule delay, and a significant chunk of my credibility with our CEO.
Here's what happened. I found a cellular module that was $3.18 cheaper per unit than the Quectel EC20 our engineers originally requested. Spreadsheet-me was thrilled. A win is a win, right? Then the integration work began, and the hidden costs started piling up faster than I could track them.
The module needed extra external components just to meet the same RF performance the EC20 achieved with its integrated design. Our engineer spent a week reworking the power supply because the module's transient current behavior was, let's say, undocumented. We had to pay extra for reference design documentation that Quectel gives away for free. And when we hit a registration issue, support responses came four to six business days apart.
Six business days. For a team already staring down a launch date, that's an eternity.
Then came certification. We had budgeted for PTCRB testing and assumed carrier approval would follow smoothly—in our industry, you quickly learn how wrong that assumption can be. It wasn't smooth. The module's compliance documentation wasn't ready, and the carrier review stretched nine weeks beyond our plan.
By the time we shipped, that $3.18 per unit "savings" had cost us roughly $18,000 in engineering hours and goodwill. The EC20 we could have bought off the shelf, with certifications already in hand and a support team that responds within hours instead of days? That would have been the cheap option all along.
I've learned to ask "what's NOT included" before "what's the price." The vendor who lists all fees upfront—even if the total looks higher—usually costs less in the end.
The NXP vs Quectel Question Comes Up in Every Design Review
At some point in every project, our hardware team debates the same thing: should we build our own connectivity chain from discrete components instead of using a module? Sometimes it gets framed as "NXP vs Quectel." NXP makes excellent processors; they're a giant in the embedded world. So surely, the argument goes, we can use an NXP chip and design our own modem path.
I've now been through this conversation enough times to have strong feelings.
A chip is not a module. A module is the entire connectivity problem pre-solved: antenna matching, power sequencing, protocol stacks, EMI shielding, thermal management, and certifications. When you go the discrete route, you inherit all of those problems. That's not a knock on NXP—it's just the reality of RF design. The question should never be "NXP vs Quectel." It should be: does our team have the RF expertise and the months (or years) required to get a discrete solution carrier-approved?
For most companies, the answer is no. That's why they buy modules.
That conversation taught me something valuable about vendors, too. When a manufacturer helps you understand the full scope of what you're getting into—rather than just selling you chips and moving on—you remember that. Quectel's application engineers talk like engineers, not like salespeople. They've told us flat-out when one of their modules was overkill for a project. That kind of honesty is rare in B2B, and it's worth real money when you're betting on a product launch.
The RM500Q 5G Module—Expensive on Paper, Cheap in Reality
In 2023, we were spec'ing a device that needed 5G sub-6GHz connectivity across North America and Europe. The first reaction from our team was sticker shock. 5G module pricing was a different universe from the 4G world we were used to.
But I dug into what the Quectel RM500Q 5G module actually includes. Global band support. Real carrier certifications that apply to actual networks. Active thermal design. A support team that answers the phone. Pair that with the EC20's proven track record at lower speed tiers, and Quectel's module family lets us standardize across our device line.
What would it cost to build a 5G-capable design from discrete components? I genuinely can't give you a number—the design effort alone would take a year and a small fortune. Compared to that alternative, the RM500Q is one of the best investments our company has made.
And when our engineering team hit a band configuration question in a country where the module wasn't officially certified, Quectel came back with a workaround in two days. Two days. With our old vendor, we'd still be waiting.
Sometimes the Right Answer Is a Flip Phone
Let me tell you why there's a Nokia 2660 Flip sitting on my desk.
We issued these to our field technicians about a year ago. They're simple 4G flip phones. They have a headphone jack—a standard 3.5mm jack—which is actually critical for our techs who use earpieces while working around loud machinery. Battery lasts for days. They work in areas where our smartphones don't get a signal.
The 2660 Flip works because it relies on mature, proven 4G technology. No cutting edge, no complications, just reliable connectivity.
That's the same logic I now apply to module selection. The Quectel EC20 might not be the most glamorous product in anyone's lineup, but it's been through so many real-world deployments that most of the "gotcha" problems are already found and fixed. That maturity is a feature. When you're building a product that needs to just work, you don't want the highest-risk component in your supply chain to be the thing that connects it to the world.
Five Questions Every Module Buyer Should Ask
If you're reading this because you're getting into IoT product development, let me save you the pain I went through. Before you place your first module order, ask these questions:
- What exactly is included in the price? Setup fees, certification files, reference designs, support access—get it itemized in writing.
- What's your average support response time? If they won't give you a number, that's your answer.
- Which carriers have already accepted this module? Modules that need fresh carrier certifications will add months to your timeline.
- Can we talk to an application engineer before we order? Not a salesperson. The actual engineer who'll be supporting us later.
- What happens when carriers evolve their networks? Good vendors track those changes and communicate. Others leave you to discover it when your devices start failing.
These questions will separate transparent vendors from the rest faster than any price quote. In my experience, Quectel is one of the few that passes all five without hesitation.
They're not always the lowest price. But they're always the clearest about what that price includes. And in this industry, clarity is the rarest feature of all.
