RadarSelector radar selection, from the supply side

Field note · Working together

How I Work — and Who I Am Not For

Most sourcing pages describe capability. This one describes the transaction, because the transaction is where you get hurt.

What I do not do

Starting here because it saves us both time.

What I actually do

Four things, in this order, and the first three are free.

  1. Rule options out. You describe the application — target, range, environment, mounting, power, certification market. I tell you which architectures are wrong for it and why. Sometimes the answer is "radar is the wrong technology here" and that is a useful answer.
  2. Read the datasheet against the test report. Vendors quote the favourable case. I go through what is actually specified versus what is assumed, and flag the parameters that are missing. This is where most bad purchases are avoided.
  3. Check the certification story. Which bands are approved, for which market, with which document. A module that is legal in Shenzhen can be illegal to install in Frankfurt, and the datasheet rarely says so.
  4. Quote and ship. This is the part I get paid for.

How I get paid, plainly

Margin on the transaction. You pay one price for the hardware; that price includes my margin; I do not invoice you separately for advice.

Where you need an on-site factory audit report issued by me in person, travel costs are reimbursed at actual cost and credited against your first order.

I also take no rebate, commission or kickback from any factory. What you get recommended does not change based on who is willing to pay me more.

This is a conflict of interest, and I am not going to pretend otherwise. The management is simple: the first order has to work, or there is no second one.

How I screen a factory

There is a fixed sequence, and most candidates drop out early.

If a factory is vague on any of these four, I stop and look for a better one. My screening method is mature and still being refined — that part you can rely on.

How a first engagement usually runs

StepWhat happensCost to you
1You describe the applicationNothing
2I shortlist two or three architectures with the trade-offsNothing
3Samples from one or two factories, shipped to youSample + freight
4You test. I answer questions and chase the factory.Your engineering time
5Quotation for production volumeNothing until you order
6Production and shipmentUnit price including margin

Steps 1–3 are where most of the value is delivered, and they cost you nothing but your attention. If you walk away after step 3, that is a normal outcome and I will not chase you.

Who I am not for

Being explicit about this is the fastest way to build trust, so:

Why not just contact the factory directly?

You can, and sometimes you should. What changes when you go through me:

If your volume is large enough that the factory will assign you an account manager directly, you do not need me and I will tell you so.

The short version: I am useful when you have an engineering team, a real volume, and a requirement that a catalogue cannot answer. I am not useful when you need a brand name, a next-day replacement, or a single sample.

Start with a question, not an order

Describe what you are trying to detect. That is enough for a useful first answer, and it commits you to nothing.

Tell me what you are trying to detect

Target, range, environment, mounting, power budget, and the market you need to certify for. That is enough for me to tell you whether radar is even the right answer.