SDR in intelligence means a route, not a rep

Where the term comes from

Cold War field practice, Moscow station, against the KGB's surveillance service — tradecraft that hardened through the 1960s and 1970s, when CIA officers in Moscow worked under effectively continuous coverage. The surveillance detection route belongs to the cluster of habits later packaged as the "Moscow Rules" — never a formally issued document, which is why no two published versions of the list agree (Moscow rules); Antonio and Jonna Mendez's 2019 book The Moscow Rules gives one insider account of them. Officers working a city under permanent hostile coverage needed one question answered before servicing a dead drop or meeting an agent: am I being watched right now?

The route answers it. You also see "surveillance detection run" — same thing, and SDR covers both.

The route's job is not to escape. It is to force a yes or no, early enough that the operational act can still be called off.

What an SDR is not

The term people collapse it with is anti-surveillance — "dry cleaning" — which is the opposite behaviour. Counter-surveillance is a third practice entirely (Tradecraft).

The third one leaks. Doubling back, sudden transfers, entering a building and leaving by another door — all of it tells anyone watching that the person has training and something to hide. A correctly run SDR produces information and gives away nothing. Mislabel the two and you build the wrong route.

The other SDRs that answer to "intelligence"

Three senses compete for this query. Two of them are legitimate intelligence usage.

1. Surveillance detection route — human intelligence. The sense defined above. If your source is a HUMINT memoir, a security-officer briefing, or a State Department travel brief, this is it.

2. Software-defined radio — signals intelligence. A radio where filtering, demodulation and decoding happen in software on general-purpose compute rather than in fixed analogue hardware. "Software radio" dates to 1984 at E-Systems in Garland, Texas; Joseph Mitola's 1992 IEEE paper put "software defined radio" into general circulation (Wikipedia). In a SIGINT context, "we put an SDR on it" means hardware, not a route.

3. Sales development representative — "sales intelligence." The prospecting half of a sales team, split off from closing in the outbound model Aaron Ross built at Salesforce and published as Predictable Revenue in 2011 (Predictable Revenue). Anyone searching "SDR in intelligence" from a GTM seat means this one sitting on top of a data product — ZoomInfo, Apollo, Clay — and has conflated "sales intelligence platform" with "intelligence."

Then there is the IMF's Special Drawing Right, a reserve asset created in 1969 (IMF). Not intelligence at all. It owns a large share of the acronym's search results, so learn to recognise it on sight and move on.

Worked example: a $25 SDR, sense two

The cheapest real instance of sense two is an RTL-SDR: a USB dongle built around the Realtek RTL2832U demodulator chip, sold originally as a DVB-T television tuner, which turned out to pass raw I/Q samples to a host computer. The RTL-SDR project documents the resulting capability — roughly 500 kHz to 1.75 GHz of tuning range depending on tuner chip, 8-bit samples, about 2.4 MS/s of stable bandwidth. Around $25.

You point it at a signal, run a GNU Radio flowgraph on the samples, and demodulation that used to require a dedicated receiver becomes a software block you can change in an afternoon. The radio is defined by the code, not the circuit. A collection discipline that used to cost a lab bench now costs a dongle and a laptop, which is why the acronym shows up in every amateur SIGINT write-up on the internet.

How to tell whether a route genuinely qualifies

Three tests, and a route has to pass all three.

It runs before the act, not instead of it — a path walked after the drop is serviced produces nothing you can use, because detection has to happen while abort is still free. Someone on that route needs the standing to call it off; if the meeting is happening regardless of what the officer sees, the route is a commute with extra steps. And it gives the opposition nothing. Every turn, stop and reversal needs a reason that survives being watched: a natural stop, a platform where trains arrive from both directions, a shop with a long window and a legitimate reason to be standing in it. The moment the route only makes sense as evasion, it has become anti-surveillance, and it is now reporting on you.

Why this entry sits in an agentic GTM glossary

The thing worth stealing from sense one is the abort gate. A detection pass that cannot stop the action is decoration — which is exactly what most "human in the loop" review steps are in an agent pipeline that was always going to send. If you are building outbound agents, the question is not whether there is a verification step. It is whether that step has the standing to drop the record and end the run. Unbounded action without an enforced stop is the most common production failure in agent systems, and the fix lives outside the model: a hard cap and a kill path in the orchestration layer, not a politely worded instruction in the prompt.

Practitioner guidance on agent design converges on the same separation of duties: a prospecting agent should not hold send authority over contacts it enriched in the same pass. Verify separately, with the power to discard. The mechanics of that pass are in build a lead triage agent that scores inbound in one pass, and what it looks like when the agent speaks out loud is in how AI outbound sales calls actually work in production.

For the same two-senses-one-word problem applied to the word everyone now uses daily, see what a computer agent is, and the three things people mean by it.