Counter-UAS companies: supplier selection guide and evaluation brief

Define the part of the counter-drone system you need

Counter-UAS suppliers may sell a sensor, a command interface, a mitigation capability or a complete integrated service. Those are different purchases. Start with the customer’s decision: become aware of an aircraft, investigate an alert, coordinate a response, or obtain an authorized mitigation capability. Identify the missing layer before making a company shortlist.

For a founder, this also defines the partnership opportunity. A new sensor might fit inside an integrator’s system; a software application might consume an existing track feed. Neither relationship requires pretending your company supplies the entire counter-drone chain. Write the work package and the interface you will own.

Separate detection, assessment, coordination and mitigation

Five company examples with different roles

Resolve the authority and intended setting early

A product brochure does not establish that your organization can use every function it describes. The FAA’s counter-UAS resource links the interagency advisory on laws that may apply to detection and mitigation. Record the customer, location, proposed function and responsible authority; obtain the applicable review before treating a deployment or demonstration as ready.

Do not combine an airport, a military installation and a private facility into one assumed purchasing scenario. Permissions, integration responsibilities and the operator’s response process must be resolved for the actual engagement. Compare the sensing purchase and any mitigation purchase as separately defined scopes.

Ask what the demonstration proves

Agree on what counts as a detection, a continuous track, an assessed alert and a completed operator handoff. Ask for the configuration, conditions, trial attempts and excluded cases behind the results. Record nuisance alerts, interrupted tracks and the workload involved in resolving them, rather than evaluating only a successful video.

Keep supplier-supported, demonstrated and untested-for-this-site statements separate. Ask which sensors and software versions produced the evidence. If a component changes, identify which result still applies and which test must be repeated. A stated maximum range alone does not answer whether a particular customer workflow will function.

Compare an installed service, not just hardware

Write who performs the survey, installation, network integration, training, updates and fault support. Request the output format, alert routing, access controls and logs needed by the customer’s existing process. Confirm whether integration engineering, recurring software, sensor replacement and on-site support are included.

Use the same planning period and exclusions for each quote. A low sensor price can leave substantial installation and integration work with your team. A broader managed service may cover those tasks, but ask exactly what is delivered and who accepts it.

Prepare a common evaluation brief

Customer and intended site:
User decision and required layer:
Our product and missing work package:
Responsible authority and review dependencies:
Sensor / software / interface deliverable:
Deployment and support responsibilities:
Demonstration conditions and acceptance criteria:
Evidence, excluded cases and unresolved findings:
Recurring costs and planning period:
Open question, owner and next action:

Download the editable brief and evidence log.

A worked example: connect a sensor to an existing workflow

Fictional situation: a startup supplies a detection sensor and wants to integrate it with a customer’s existing alert console. The initial demonstration evaluates whether the feed arrives, labels and uncertainty remain visible, and operators can investigate the alert. It does not assume a mitigation authorization or require a mitigation purchase.

Next action: agree on the message format, interface owner, representative test cases and evidence to retain. If the customer later seeks an additional response capability, scope its authority, supplier and acceptance requirements separately.