Enquirer Consulting Group

Reachable Buyer Map

Prepared for Peter Thomson · NCS Technologies · August 2026
Here is the map. From the outside, this is a market reached through contract vehicles and incumbency, which is a strong position and a narrow channel: it reaches the buyers already looking for you and it is silent about the ones who have never heard the name. This page sets out the segments that can buy what NCS builds, who signs inside each one, and roughly how many organizations sit there. It describes the market rather than your business, and there is nothing to buy at the end of it.
Federal civilian agencies and their program offices
The buyers a contract vehicle is built for. They are reachable, they are enumerable, and the decision that matters is usually made in a program office long before anything reaches a contracting officer.
Who signs: agency or deputy CIO, end user computing lead, infrastructure director, program manager, and the contracting officer once the requirement exists.
400 to 450
US federal agencies, bureaus and sub-components; a large share run their own device and infrastructure buys rather than a single central one
Defense commands, services and program offices
The largest pool of mission computing money in the country and the one that cannot be worked from a list. Requirements are written years ahead inside program offices, so the useful contact happens well before a solicitation, or not at all.
Who signs: program executive officer, product manager, the communications and information staff at a command, and the integrator holding the prime seat.
No single public list
defense program offices are not published anywhere as one enumerable set; they are identified command by command, which is why incumbency counts for so much here
Federal systems integrators and defense primes
The channel buyer. They win the program and then need a manufacturer who can build, secure and ship at volume with a documented supply chain. A slower first sale and a much longer tail, because the work recurs with every task order.
Who signs: hardware engineering manager, supply chain and subcontracts lead, capture manager, program director.
4,000 to 5,000
US employers in computer systems design and related services carrying 50 or more people; the federal facing subset inside that is where hardware pull-through sits
Technology companies that ship a hardware appliance
The segment furthest from a federal channel and the easiest to define. Software, networking and security vendors reach a point where the product has to ship as a box, and almost none of them want to become a manufacturer to do it.
Who signs: VP of engineering or hardware, chief product officer, COO, head of operations, and the founder at the smaller ones.
1,200 to 1,800
US software, networking and security vendors at 50 or more people, the population that ships or is planning to ship a physical appliance
State, local and public safety agencies
Rugged and mobile computing bought for the field rather than the desk, on grant cycles and disaster funding rather than annual budgets. Fragmented, which is the reason it stays open: nobody can cover it by relationship alone.
Who signs: county or city CIO, emergency management director, public safety technology lead, procurement director.
4,000 to 4,800
US counties, cities above 50,000 people and state level agency technology offices; grant funded buys move faster than federal ones
Critical infrastructure and industrial operators
Utilities, energy, pipeline, rail and port operators running compute in places a commercial laptop does not survive. They buy on the same durability and security arguments as defense, without the clearance overhead.
Who signs: VP of operations technology, control systems manager, IT infrastructure director, plant or network engineering lead.
1,800 to 2,400
US utility, energy, pipeline, rail and port operators carrying 100 or more people

Where the openings are

1
A contract vehicle makes you buyable, not visible. It works on the buyers who already know to look, and it is silent on the ones writing a requirement for the first time. Those seats are reachable by name months before a solicitation exists, and that window is where the specification gets shaped.
2
The hardware and the lifecycle service do not share a buyer. A ruggedized build is specified by an engineer or a program manager against a requirement. A managed lifecycle model is bought by whoever owns the refresh budget and the headcount it saves. Two audiences, two arguments, and one channel today.
3
The appliance market never sees a federal supplier. A software company that needs its product shipped as hardware searches generically, buys from whoever answers, and then stays for a decade. That population is small, definable and reachable, and nothing about a government channel puts you in front of it.
4
Refresh runs on a clock you can read from outside. Fleets turn over on a three to five year cycle, program start dates are published, and end of support dates for the underlying platforms are public. Watching several thousand named organizations for those dates is mechanical work, and it is the part a relationship channel cannot do.
Built from public US registry data: the published structure of federal, state and local government, and employer filings that record sector and workforce size for private companies. Counts are banded deliberately. Sector codes are self-reported, so the private company bands describe established employers with payroll rather than every registered entity. Defense program offices are described rather than counted because no public register enumerates them.
ENQUIRER CONSULTING GROUP
enquirerconsulting.com