We asked FedFathom where a cloud modernization firm fits in the $95.6 billion federal IT market

A $95.6 billion market is not a target list. To test how a contractor could move from market size to practical account research, I combined two different research methods: official USAspending aggregate analysis and a live FedFathom capability search.

The whole-market analysis began with NAICS 541512: Computer Systems Design Services . The FedFathom analysis began with what a company actually does:

Cloud modernization, cybersecurity, data integration, and DevSecOps.

That distinction matters. The API establishes the size and structure of the market. FedFathom searches imported award evidence for capability fit: which buyers, vendors, purchasing codes, contract descriptions, and individual awards deserve follow-up.

Two tools answered two different market-research questions

The 610 FedFathom matches are not a market total or market-share denominator. They are a relevance-ranked research set produced from the capability description and filters. The $95.554 billion figure comes from a separate, market-wide USAspending aggregation.

A durable market above $30 billion per year

Using the USAspending API, I filtered contract activity to NAICS 541512 for FY2023 through FY2025.

The same filter returned 33,202 contract awards.

Obligations rose 9.3% in FY2024, then fell 5.0% in FY2025. Even after that decline, FY2025 remained 3.8% above FY2023. The more useful conclusion is not that the category grows in a straight line. It is that demand remained above $30 billion in every fiscal year studied.

What we actually ran in FedFathom

On July 24, 2026, we ran the following production Market Research search against FedFathom's imported USAspending award corpus:

Cloud modernization, cybersecurity, data integration, and DevSecOps.

FedFathom returned 610 matching contract awards. It then summarized the matched evidence by agency, vendor, keyword, NAICS/PSC combination, and period-of-performance end date. Similarity percentages in the product are heuristic comparisons, not probabilities of fit or future award.

The buyer signals became a focused research list

These are counts inside the 610-award Search snapshot, not agency-wide totals. Their value is prioritization: DoD, GSA, and HHS emerged as the first buyer ecosystems to investigate for this capability wording.

The code map became more specific than one NAICS code

The aggregate API had already shown that DA01 is the largest PSC in the whole NAICS market. FedFathom added a capability-specific view: the same search also reached network operations, professional support, and engineering work. That is a better monitoring vocabulary than the phrase "cloud modernization" alone.

Representative awards made the signals auditable

FedFathom also surfaced established vendors throughout the matched set, including Leidos, HPI Federal, Deloitte Consulting, Accenture Federal Services, General Dynamics Information Technology, Peraton, and Booz Allen Hamilton. Those names are research signals—not a market-share ranking. Each result retains an official USAspending link so the underlying award can be checked before it informs a pursuit decision.

The agency administering the award may not fund the requirement

USAspending distinguishes between the organization that creates and administers an award and the organization that pays for it. Its official awarding-agency versus funding-agency explainer makes the difference explicit.

The largest contrast is GSA. It represents 18.3% of obligations when grouped by awarding agency, but only 0.8% when grouped by funding agency. The Federal Acquisition Service alone administered $17.244 billion in obligations under this filter.

That is strong evidence of GSA's role as an acquisition channel for demand funded by other agencies. The Federal Acquisition Regulation recognizes interagency acquisitions in which one agency uses another agency's contract or acquisition assistance.

For market research, the practical consequence is simple: the contracting office and mission customer may be different account targets. Researching only the awarding agency can misidentify who owns the requirement.

Five organizations control more than three-quarters of each map

The five largest awarding agencies account for 76.1% of obligations. The five largest funding agencies account for 78.4%.

The largest funding-subagency rows make the underlying mission demand more concrete:

Those are not interchangeable IT customers. Defense networks, veterans' health systems, Medicare operations, tax administration, diplomacy, and civilian cybersecurity imply different missions, security requirements, acquisition histories, and incumbent ecosystems.

The visible supplier field is concentrated too

The five largest recipient rows account for 29.0% of obligations. The ten largest rows account for 44.6%.

Recipient rows are not a perfect measure of independent-company concentration. Multiple UEIs, corporate parents, acquisitions, and joint ventures complicate the picture. But the contrast with the HVAC market in our first study is directionally clear: large established vendors hold a much larger visible share of this category.

For a smaller contractor, a $95.6 billion total addressable market is therefore less useful than a map of the subagency, acquisition channel, vehicle, incumbent, and specific capability niche.

One NAICS code contains many purchasing vocabularies

NAICS 541512 sounds like one service category. Its Product and Service Code distribution shows a much wider operating market:

DA01 alone accounts for 30.7% of obligations, but the five largest PSC rows together account for only 56.4%. The remaining market crosses network support, cybersecurity, service delivery, data centers, help desks, systems development, software, program management, and other categories.

A contractor searching only "computer systems design" would miss much of the language agencies use to buy work inside the NAICS boundary.

The set-aside field needs careful interpretation

An initial set-aside analysis found $12.029 billion in obligations matching explicit, recognized small-business, 8(a), SDVOSB, HUBZone, WOSB/EDWOSB, and related set-aside categories. Another $5.135 billion matched the explicit "No Set Aside Used" value.

Together, those populated categories account for only $17.164 billion of the $95.554 billion market. The remaining obligations did not match the recognized USAspending advanced-search categories used in this analysis.

This does not mean the remaining work was or was not available to small businesses. It means set-aside coding alone cannot answer the market-share question. Orders under larger vehicles, recipient status, award-level competition fields, and current solicitation evidence need separate review.

What an IT contractor should do with this information

1. Separate the mission customer from the acquisition channel

Record both the funding organization and the awarding organization. If GSA or another servicing agency administers the award, identify the office that owns and funds the requirement.

2. Choose a mission-and-capability intersection

"Federal IT" is too broad. A more useful target might be VA health-system application modernization, Air Force network operations, CMS program systems, IRS data platforms, or CISA security operations.

3. Map vehicles and established recipients

Determine how the customer has bought similar work and who already performs it. Concentrated recipient obligations make teaming, subcontracting, and vehicle access part of the market map, not afterthoughts.

4. Build a multi-code vocabulary

Connect capability language to NAICS, PSCs, agency terminology, award descriptions, and current notices. Codes are useful boundaries, but the evidence is in the underlying awards and requirements.

5. Verify current opportunities in official systems

Use SAM.gov for current contract opportunities. Historical analysis should narrow and improve that monitoring, not replace it.

What FedFathom added to the market brief

The USAspending aggregate analysis established market scale, concentration, and the awarding-versus-funding distinction. It did not begin with a contractor's capability or identify which individual awards were linguistically relevant.

FedFathom supplied that second layer. It translated a short capability description into a 610-award evidence set, highlighted buyer and vendor signals, identified adjacent PSC vocabulary, grouped related award modifications, and preserved links to official records.

The practical workflow is therefore:

1. Use aggregate data to decide whether the market is large and durable enough to study.
2. Describe the actual capability in FedFathom and constrain the search where appropriate.
3. Use matched agencies, vendors, PSCs, and representative awards to form a research shortlist.
4. Open the linked official records and verify the facts that matter to the intended pursuit.
5. Use SAM.gov and agency procurement channels to investigate current opportunities.

FedFathom is a research aid, not an official government source or a guarantee of future awards. Verify material information through linked official records.