The Buy

Federal Tail Spend: The Data Behind Long-Tail Government IT Procurement

FedSpend

Key Takeaways
  • Agency IT totals hide multiple separately competable PSC markets.
  • DHS averages $1M per IT transaction; Navy averages $226K.
  • Air Force DA01 obligations grew 53% from FY2023 to FY2025.
  • Four-step decomposition moves from agency total to bureau-level buyer.
  • Tail spend data expires monthly; static snapshots become stale quickly.

Most of what gets published about “federal tail spend” is actually about purchase cards — sub-$250K micro-transactions and office supplies flying under a contracting officer’s radar. That’s real, but it’s the wrong tail for an IT capture team to chase. The tail that matters isn’t defined by transaction size — it’s defined by what an awarding office’s total hides once decomposed to the bureau and the specific PSC lane consuming the money.

Here’s the proof: Air Force IT obligations hit $12.02 billion in FY2025 across 22,517 transactions, and the top five PSC categories underneath that number span application development labor, SaaS, perpetual licenses, engineering support, and network services. That’s five separately competable lanes bundled under one agency total, and most capture teams never split them apart.

What Federal Tail Spend Actually Means

Federal tail spend, in the IT capture context, is the obligation volume below the awarding office total — decomposed to the end-user bureau and the specific PSC or NAICS lane, not one undifferentiated agency number. An agency total is a rollup. It tells you VA obligated real money against IT contracts; it tells you nothing about which program office signed the check.

Scope matters, too. IT spend follows the OMB/GSA Category Management IT definition — IT-coded NAICS and PSC categories plus a curated allowlist, not every dollar an agency spends. The table below shows what stopping at the total costs you: obligations per transaction, five agencies, latest reported fiscal year.

AgencyFiscal YearTotal IT ObligationsTransactionsAvg. Obligation per Transaction
Department of the Air ForceFY2025$12.02B22,517$533,631
Department of Veterans AffairsFY2026 YTD$11.29B16,161$698,508
Department of Homeland SecurityFY2026 YTD$10.90B10,606$1,028,073
Department of the NavyFY2025$10.07B44,509$226,276
Department of the ArmyFY2025$9.41B19,926$472,093

The last column tells a story the totals alone can’t. DHS averages over $1 million per IT transaction while the Navy averages $226,276 — the Navy’s $10B spreads across roughly four times as many buying events. That’s where a VAR or smaller integrator finds room that a headline-chasing team walks past.

Top 5 Agency IT Obligations — Latest Reported Fiscal Year
Top 5 Agency IT Obligations — Latest Reported Fiscal Year

Why the Tail Gets Overlooked in Most Procurement Research

The tail gets ignored because agency-level totals are easiest to pull from raw USAspending and FPDS exports, and easy data shapes strategy whether or not it should. Most research stops at “Agency X obligated $Y billion” because a PSC-and-bureau breakdown means reconciling thousands of records by hand. The result, as prior analysis of agency spending intelligence has pointed out: a hundred capture teams chase the same handful of visible awards while adjacent, similarly sized PSC lanes go unaddressed. Nobody shows up for the lane three rows down the spreadsheet.

Decomposing the Tail: Agency Obligations by PSC and NAICS

Breaking an agency’s IT total into its top PSC and NAICS codes reveals four or five distinct markets, not one. Take the Air Force’s FY2025 numbers at the PSC level:

PSC CodeCategoryFY2025 Obligations
DA01Application development support (labor)$2.39B
DA10Application development SaaS$1.06B
7A21Business application software (perpetual license)$830M
R425Engineering/technical support$696M
DG01Network support services (labor)$401M

Labor services and software licensing are different sales motions and competitor sets, even inside one agency total. The NAICS breakdown confirms it: 541512, 541519, and 541511 dominate the Air Force’s $12B, while 334220 (hardware manufacturing) still pulls $930M — services-heavy agencies still carry a hardware tail.

VA and Navy Show the Same Pattern, Different Shape

VA obligated $11.29B in FY2026 YTD, and NAICS 541512 alone accounts for nearly $5 billion of it — concentration defines VA’s tail. The Navy runs the opposite pattern: at $10.07B across 44,509 transactions, a larger share flows through hardware-coded PSCs than most teams assume.

Explore federal IT spending patterns free

Start a FedSpend trial to discover growth opportunities in $675B+ of federal IT awards.

Start trial

Where the Tail Signals Recompete and Growth Opportunity

Tracking the same PSC category across multiple fiscal years turns a static snapshot into a leading indicator of upcoming recompetes. A lane that’s grown three straight years isn’t an accident — it signals a vehicle expanding scope or approaching a renewal with new money attached.

Air Force PSC code DA01 — application development labor — is the clearest example:

Fiscal YearDA01 ObligationsTrend
FY2023$1.56B—
FY2024$2.02B+29%
FY2025$2.39B+19%
FY2026 (YTD)$1.58Bpartial year

DA01 grew nearly 53% from FY2023 to FY2025 before the FY2026 figure, reflecting only a partial year, reset the base. Three straight years of expansion beats any single headline award as a signal. Teams tracking ordering-period expirations around that growth position ahead of the solicitation instead of reacting once it hits SAM.gov — the premise behind a recompete-timing view rather than a static award list.

Turning Tail Spend Data Into a Capture Strategy

A workable tail-spend workflow moves from agency total to bureau-level consumer in four steps, not one lookup. Skipping straight from “the Air Force spent $12B” to a proposal wastes cycles chasing a market that isn’t one.

  1. Start from agency-level IT obligations to set the fiscal-year ceiling.
  2. Filter to PSC and NAICS lanes matching your delivery capability.
  3. Decompose that lane to the end-user bureau consuming the spend.
  4. Cross-reference FSRS subaward data to see which primes already subcontract there.

That fourth step matters most. A lane saturated with sub relationships usually rewards a reseller or OEM better by finding the underserved agency pocket than by displacing an incumbent. The Award Data platform is built around this exact drill-down — agency to PSC to bureau to subaward.

Building This Into an Ongoing Process

Tail spend analysis expires fast because obligations post monthly and a PSC lane’s picture shifts with every new transaction. A decomposition accurate in July can be stale by October — a one-time sprint guarantees stale assumptions by the next solicitation.

  • New transactions change which bureau looks like the active buyer within a quarter.
  • Growing PSC lanes can plateau once a multi-year IDIQ ceiling is reached.
  • Subaward flows shift as primes rotate subs between option periods.

Agency quarterly Intelligence Reports carry this forward without forcing a re-pull of raw FPDS exports every quarter, and a weekly digest like Dispatch keeps policy and budget context attached to the numbers instead of floating in a separate browser tab.

The Tail Isn’t a Rounding Error — It’s Where the Market Actually Lives

Call it what it is: most “tail spend” content online is written for commercial teams worried about rogue purchase-card buys, and it doesn’t map onto federal IT capture at all. The real tail — the PSC lanes and bureau-level consumers hiding under a $10 billion headline — isn’t a footnote to the big award. It’s five or six competable markets disguised as one number, and the teams willing to decompose it show up to the recompete a year before everyone else notices it’s coming.

Frequently Asked Questions

What distinguishes federal tail spend from commercial tail spend?
In federal IT capture, tail spend refers to obligation volume hidden beneath an agency headline total once broken down by PSC, NAICS, and end-user bureau — not the small-dollar purchase-card spend the term typically means in commercial procurement.
Why do most capture teams miss PSC-level opportunities?
Agency-level totals are the easiest data to pull from USAspending and FPDS exports, so most teams stop there, leaving adjacent PSC lanes unaddressed while competitors chase the same handful of visible awards.
How do I decompose agency IT obligations down to the bureau level?
Filter the agency total to PSC or NAICS codes matching your capability, drill into award-level detail to identify the actual end-user program office, then cross-check FSRS subaward records for existing team structures.
What does average obligation per transaction reveal about an agency?
It shows how concentrated or spread out buying events are — DHS averages over $1M per IT transaction while the Navy's $10B spreads across 44,509 transactions at $226K each, indicating very different competitive entry points.
How often should tail spend decompositions be refreshed?
At least quarterly, since obligations post monthly and a PSC lane's picture can shift within a quarter — a decomposition accurate in July can be stale by October.
Get content like this in your inbox
Tips from our team — once a week, no spam, unsubscribe anytime.

Tagged: Federal IT · FPDS Visibility · Tail Spend

About the Author

FedSpend