• Home
  • Who we support
Who we support

Industry, civilian, defense and law enforcement.


Four audiences, one subject, and four genuinely different conversations. The technical problem is often identical; what differs is who owns the risk, what authority they hold, and what a useful document looks like to them.

Industry

Commercial and critical-infrastructure operators

Energy, transport, logistics, large venues, mining and heavy industry, organizations that hold explosive-threat risk as one line in a much larger risk register and do not employ anyone who has run the mission.

The deliverable that lands here is usually a written assessment plus a board-level briefing: what the exposure is, what it would cost to reduce it, and what happens if it is accepted instead.

Civilian

Municipal, emergency management and public safety

Cities, counties, emergency managers, event authorities and public venues. Typically strong on response and thin on the planning layer above it, with mutual-aid arrangements that have not been tested against a realistic sequence.

The work here is usually coordination and authority mapping, exercise objectives, and an honest account of which shortfalls are organizational rather than technical.

Defense

Department of Defense and defense industry

Program offices, units and the contractors supporting them. The conversation here usually starts at the organizational layer: qualification, currency, command relationships, risk governance and sustainment, because that is where a senior EOD career is hardest to substitute.

Everything delivered into this channel is handled in the channel appropriate to it. It is not summarized on a public page.

Law enforcement

Federal, state, tribal and local

Bomb squads, tactical units and the commands above them. Almost always technically capable and almost always short of the program layer: currency records, continuation training, risk decisions held at the right level, and an assessment written by someone outside the unit.

Engagements here are frequently a program evaluation rather than a new program.

The same discipline in all four

The audience changes. The standard does not.

A commercial client, a city, a program office and a bomb squad get the same honesty about what is known, what is inferred, and what has not been verified. The only thing that changes is the vocabulary and the document it arrives in.

Where a finding is unflattering it is written down as unflattering. Where a number has not been verified, the assessment says so rather than reaching for a plausible figure. That is not a stylistic preference; in this subject an assessment that overstates its own confidence is worse than no assessment.

What crosses between clients

Nothing. No client is named, no engagement is used as a case study, and no finding from one organization is carried into another. In this subject the deliverable is frequently a description of how to hurt the client. It is not marketing material and it will never be treated as such.

Where the line is

Protective and programmatic work only. No engagement whose purpose is to build, improve, exploit or defeat a device or a protective measure, and no work that would require publishing controlled technical data.

Which of the four are you?

It changes the first question, and it is worth saying up front.

Start a conversation