How to Spec an RF Front End for Your CubeSat Mission: The Five Questions We Ask Every Customer

If you’re sourcing an RF amplifier or front end for a LEO, SmallSat, or CubeSat mission, the conversation you have with your supplier in the first 30 minutes will tell you almost everything you need to know about whether they’re going to deliver.

At Triad RF Systems, the customer discussion is one of the most critical things we do when designing RF subsystems for use in space. We have a solid lineup of COTS products built for the space environment — but more often than not, customers need something specific to their platform, mission, or use case. We treat our COTS line as a set of building blocks, not a finished menu. The real work happens in the conversation that decides which blocks to use, which to modify, and which to design from scratch.

We call these conversations “uncovering” calls, and we always insist on having engineers in the room. Customers find it frustrating to spend an hour walking through their mission only to have a salesperson take notes and promise to “get back to you.” Ultimately, what we’re selling is our engineers’ skill — so our engineers are on the call from the start.

Here are the five questions we ask every new space customer. Use this as a playbook if you’re a supplier trying to do better customer discovery — or use it as a homework checklist before you reach out to suppliers for your own mission. If a potential supplier isn’t asking you something close to these five questions, that tells you something important about how they’ll behave once your purchase order lands.

The five questions Triad RF asks every new space customer

1. Technical specifications and details. What does the hardware need to do — frequency, power, gain, size, weight, environmental survival?
2. Short-term and long-term potential. Is this a one-off prototype, a flight unit, or the start of a constellation?
3. Timeline. When do you need hardware in your hands, and how does that map to a realistic design and qualification cycle?
4. Concept of operations. Step back from the spec sheet — what job does this hardware actually have to do inside your system?
5. Where is this system design causing you pain? What’s frustrating you, what hasn’t worked before, and what are you trying to avoid repeating?

Below, we walk through why each question matters and what good answers look like.

Question 1: What are the technical specifications?

You’d think this is the most important question we ask. It isn’t — but it’s the foundation everything else sits on.

We need to understand frequency, output power, gain, linearity, harmonics, DC input, thermal envelope, mass, volume, and the environmental requirements your bus and orbit demand. The earlier we have those numbers, the more flexibility we have to design something that fits.

Here’s the thing most customers don’t expect us to say: a change in frequency is not the end of the world. A shift in output power isn’t either. These things can be dealt with — as long as the design team knows about them early enough in the process. The technical spec is a starting point, not a contract. What kills programs isn’t a frequency change. It’s a frequency change that surfaces six weeks before delivery.

Questions 2 & 3: What’s the short- and long-term potential, and what’s the timeline?

These two questions go together, and they’re how we figure out whether a project is the right fit for both sides.

On the business development side, our job is to do the internal sale at Triad. To take on a custom new space program, we have to convince our management of two things: that the opportunity is real, and that it’s reasonable. Real means there’s enough hardware at the end of the day to justify the engineering capital we’ll spend getting there. Reasonable means the timeline is achievable without setting the entire team up for failure.

If a customer needs a fully custom amplifier delivered faster than a normal design and qualification cycle allows, and we accept the work without flagging that mismatch, we’ve already failed. The only thing that hurts more than turning down an exciting program is accepting one and missing the date. That’s why we ask hard questions about quantity, follow-on potential, and timing on the very first call.

If a supplier isn’t asking how many units you’ll need, when you need them, and what the program looks like 18 months from now — they may not be thinking carefully enough about whether they can actually deliver.

Question 4: What’s your concept of operations?

This is the question that’s most often overlooked, and it’s one of the most valuable.

What we’re really asking: step back from the technical details of the hardware you’ve been envisioning, and describe the job that piece of hardware needs to do inside your system. What signal is going in, what’s coming out, what’s around it, what’s it talking to, and what does the mission need it to accomplish?

You’d be surprised how often a fresh look — one not bogged down in dB and GHz — reveals a different or simpler way to accomplish the goal. We’ve expanded the capability of customer systems by combining functions that were traditionally treated as separate. We’ve reduced the technical complexity of a design dramatically by pulling filtering out of the amplifier and treating it as its own block. Stepping back and challenging preconceived notions can benefit both sides of the table.

If your supplier doesn’t want to understand your concept of operations, they’re going to build exactly what you spec’d — which sometimes isn’t what you actually need.

Question 5: Where is this system design causing you pain?

If you’re not asking your customer about pain points, you’re not doing a complete job.

This question does two things at once. It signals to the customer that we’re thinking about the project from their perspective — and it gets people to open up. When we ask about previous challenges and frustrations on past programs, we hear the real story behind the spec sheet. Customers describe experiences that explain why certain design decisions were made, why certain margins were added, and why certain suppliers didn’t get a second program.

It also gives us context on what’s truly an objective requirement versus a threshold requirement. There’s a meaningful difference between “we need 50 watts because the link budget says so” and “we need 50 watts because the last amplifier we flew degraded over time and we’re padding for margin.” Both produce the same number on a spec sheet. They lead to very different conversations about design trade-offs.

What this checklist tells you about your supplier

Whether you’re a supplier trying to become a better partner, or a new space program manager doing homework before reaching out to RF amplifier vendors, these five questions are the ones that matter.

A capable supplier will absolutely want to understand the technical ins and outs of your requirements. That’s table stakes. But they should also be thinking about your project from a business perspective. If a program doesn’t make sense for the supplier on fiscal or schedule grounds and they take it anyway, ask yourself whether you really want that company building your flight hardware. A supplier that takes work without thinking through whether they can deliver may not be in business long enough to deliver it.

And finally: are they approaching your project with a fresh mindset? Are they challenging the “why” behind your requirements? Do they want to understand the bigger picture of what makes or breaks your mission? Are they asking about your previous experiences — the good ones and the painful ones?

Those are the questions that separate a design partner from a supplier. For new space programs, where every gram, every watt, and every week matters, you want a design partner.

---

Planning an RF front end for a LEO, SmallSat, or CubeSat mission? Triad RF Systems designs and builds high-reliability RF amplifiers and subsystems for new space platforms. Reach out to start an uncovering call with our engineering team.