Skip to content
Auctoritas IntelligenceAuctoritasIntelligence
Practice 02 · Workforce & growth

Finding people, and reaching buyers.

Talent acquisition, business development and digital modernization for organizations in the defense and federal supply chain — including the part that is still communications.

Why this sits inside a security company

Hiring and selling both put an organization in public view.

A job advert names the tools, the stack and the clearance level. A capability brief dates a program. A team page maps an organization. A pursuit announced early confirms a guess somebody had already made.

None of that is a growth problem to most agencies, because it has never been their problem. They are measured on reach and volume, and both are improved by saying more.

We are measured differently. The work is to make an organization legible to the people it wants to hire and to sell to, and no more legible than that to anyone else. It is the same discipline as the rest of this company, applied to hiring and pipeline instead of to systems.

What the practice does

Six areas.

  1. 01
    Talent acquisitionTechnical and cleared-role recruiting: candidate discovery, engagement, pipeline development and the analytics underneath. The constraint in this sector is rarely the job advert; it is that the people who can do the work are already employed.
  2. 02
    Employer brandHow an organization is seen by the people it needs to hire, which is a different audience from the one it sells to and is usually served with the same material. Built so the organization can apply it without us in the room.
  3. 03
    Business developmentOpportunity research, positioning, capability materials and the pipeline discipline behind them. Knowing which programs and partners are worth pursuing is most of the work; the deck is the smallest part of it.
  4. 04
    Digital modernizationThe systems underneath the above — customer and candidate records, automation, analytics, digital presence — assembled so they produce evidence rather than activity.
  5. 05
    CommunicationsMessaging and public material, including the part most often skipped: what is deliberately not said. This was the whole of the practice and is now one part of it.
  6. 06
    Disclosure reviewReading planned material for what it reveals: capability, timing, structure, relationships. A second pair of eyes trained on exposure rather than on tone.
How a disclosure review runs

Read what is already public before writing anything new.

Most reviews start at the draft. By then the organization has usually said the thing already, somewhere else, and nobody has gone looking.

  1. 01

    Inventory what is already out

    Site, decks, job adverts, conference talks, press, team profiles, contract notices. Assembled in one place, because the risk is almost never in a single item.

  2. 02

    Read it for what it reveals

    Capability, timing, structure, relationships. Not tone and not grammar — the question is what a reader could reconstruct that nobody meant to publish.

  3. 03

    Mark what should not have gone out

    With the reason attached, so it is a judgment someone can argue with rather than an instruction they have to take on faith.

  4. 04

    Write the standard

    The point is that the next piece does not need us. A review that has to be repeated forever was a service; a standard the organization can apply itself is a capability.

What we read for

The things that leak without anyone deciding to leak them.

None of these are secrets. Each is ordinary material that becomes informative once it is put beside the rest.

  1. 01
    Job advertsThe most reliably overlooked disclosure in any organization, and the one this practice touches most directly. They name the tools, the stack, the clearance level and the direction of travel.
  2. 02
    Capability detail that dates a programA feature described in the present tense tells a reader when the work started.
  3. 03
    Team pages that map an organizationRoles and reporting lines are a structure diagram assembled from public parts.
  4. 04
    Timing that confirms a guessAn announcement is rarely news on its own. It is news because it dates something somebody had already inferred.
  5. 05
    Third parties named without agreementNaming a partner, a client or a supplier discloses their position as well as yours.
  6. 06
    Language that implies proof that does not existWording that suggests customers, scale or accreditation the organization cannot produce on request. It is the failure we watch for hardest, including in our own copy.

This is a practice, not a platform. There is no product to license and we are not going to imply otherwise.

No client list, no case studies, no portfolio, no awards. The work described above is done by people, with the systems the client already has or the ones we build for them.

If any of it is ever productized, that will be announced when it exists and not before — which is the same rule the rest of this site runs on.