- FAR 2.101's threshold rose to $15,000, erasing award data below it
- Navy averages $226K per IT action; Air Force averages $536K
- GAO found 13% of federal obligations went to one-offer competed contracts
- Sub-threshold buys generate no PIID, NAICS code, or vendor record
- Capture teams need program-office intelligence, not queries, below the threshold
Every capture team repeats the same FY27 advice: land a foothold contract, build past performance, then go win the big recompete. Almost nobody says which side of a single line in the Federal Acquisition Regulation that foothold should sit on. That line — the micro-purchase threshold defined in FAR 2.101 — is not a compliance footnote. It is the border between the federal market you can measure and the one that disappears from every dashboard the instant a transaction clears it. And the side you can see is thinner than the pitch decks admit.
The Line Nobody Budgets Around
The micro-purchase threshold is a data-existence boundary, not just a spending rule.
Below it, a buy stops behaving like a contract in the data. No PIID gets minted, no NAICS-coded competition record, no offers-received count — the transaction usually rides a government purchase card into a ledger nobody outside the agency can query. Clear the line, and the same action reports to FPDS and enters the public record.
For years that line sat at $10,000. On October 1, 2025, the FAR Council’s inflation adjustment moved it to $15,000 and pushed the Simplified Acquisition Threshold from $250,000 to $350,000 the same day. The exact figure keeps drifting. The principle does not: wherever the threshold lands, visibility ends there.
That is the part the advice skips. When someone says “get a foothold,” they rarely name a dollar tier — and the tier decides whether the win is even legible to the tools your competitors use. A $9,000 task that seeds a relationship with a program office never enters the same dataset as the recompete you are eventually chasing. This is the quiet mechanics of federal tail spend, and it is why the small-dollar layer matters far more than its size suggests.
How Much of the Visible Market Is Actually Small Buys?
Most of it — agencies fragment their IT spend into thousands of modest actions, and how aggressively they do it swings wildly from one agency to the next.
According to federal spending data compiled from usaspending.gov, the services run opposite playbooks even inside the visible tier.
| Agency | Fiscal Year | Total Obligations | Transaction Count | Avg. $ per Transaction |
|---|---|---|---|---|
| Department of the Navy | 2,025 | $10.1B | 44.4K | $226.3K |
| Department of the Navy | 2,024 | $9.6B | 48K | $199K |
| General Services Administration | 2,024 | $9B | 74.9K | $119.7K |
| Department of the Air Force | 2,025 | $11.9B | 22.1K | $536.1K |
| Department of the Air Force | 2,024 | $11.1B | 21.8K | $511.3K |
| Department of the Army | 2,020 | $9.2B | 25K | $366.8K |
| Department of the Army | 2,025 | $9.3B | 19.7K | $470.7K |
| Department of Veterans Affairs | 2,024 | $9.5B | 12.4K | $761.6K |
| Department of Health and Human Services | 2,024 | $9.2B | 14.7K | $626.9K |
The Navy, whose 44.4K logged IT actions in FY2025 averaged just $226.3K apiece, breaks its spend into a swarm of smaller awards. The Air Force ran the other direction — a comparable $11.9B in total dollars but an average of $536.1K per action, more than double the Navy’s. Both counts are FPDS-reportable actions only; anything under the micro-purchase threshold sits outside this table and everywhere else in public data.
Read that spread as a behavioral tell. A fragmenting agency does far more of its buying near or below the SAT — the Navy’s average action already fell under the old $250,000 line — which is precisely where a foothold might live. Building a real read on an agency’s federal IT spending intelligence profile starts with knowing whether it fragments or consolidates, because the two demand different pursuit strategies.
Why Competition Above the SAT Isn’t What It Looks Like
Because “full and open competition” on the label routinely means one company actually bid.
The comfortable assumption runs: above the SAT, real data exists, so a real market with real competition exists. The award records puncture it.
| Recipient | Agency | Total Value | Extent Competed | Offers Received |
|---|---|---|---|---|
| CACI, INC. – FEDERAL | Department of Homeland Security | $13.2M | FULL AND OPEN COMPETITION | 1 |
| ASRC FEDERAL TECHNOLOGY SOLUTIONS, LLC | Department of Defense (Army) | $10.8M | NOT AVAILABLE FOR COMPETITION | 1 |
| AMAZON WEB SERVICES, INC. | Department of Justice | $10.3M | NOT COMPETED UNDER SAP | 1 |
| OASYS INTERNATIONAL LLC | Department of Homeland Security | $18.9M | FULL AND OPEN COMPETITION AFTER EXCLUSION OF SOURCES | 1 |
| BOOZ ALLEN HAMILTON INC | Department of the Treasury | $13M | FULL AND OPEN COMPETITION | 1 |
| FOUR POINTS TECHNOLOGY, L.L.C. | Social Security Administration | $17.4M | FULL AND OPEN COMPETITION | 2 |
| CYBERDATA TECHNOLOGIES, INC. | Department of Health and Human Services | $25.9M | FULL AND OPEN COMPETITION AFTER EXCLUSION OF SOURCES | 5 |
| TRUVETA INC | Department of Health and Human Services | $10.2M | FULL AND OPEN COMPETITION AFTER EXCLUSION OF SOURCES | 5 |
| TRIDENT SYSTEMS LLC | Department of Defense (Air Force) | $18.3M | NOT COMPETED | 1 |
| MANAGEMENT SERVICES GROUP, INC. | Department of Defense (Navy) | $68.1M | FULL AND OPEN COMPETITION | 2 |
Look at the Homeland Security order to CACI: $13.2M, coded full and open, and exactly one offer received. The label promised a contest; the record shows a walkover. Down the table, an Army DevSecOps award to ASRC Federal — $10.8M, marked “not available for competition” — makes the same point from the other side: eight-figure work with no contest at all.
This is not a small-dollar quirk. GAO has been flagging it for more than a decade. Its 2010 review found that contracts competed with only one offer held steady at roughly 13% of total federal obligations across fiscal years 2005 through 2009, even as outright noncompetitive awards fell. A later GAO look at defense buying put one-offer awards near $20.9B in FY2014 obligations alone. When one in eight competed dollars draws a single bidder, “competed” is a procedural status, not a market condition.
The implication for capture teams is uncomfortable. If the market you can measure is already this thin, the offers-received field you mine through an award-data platform tells you who showed up, not where a real opening sits. Thin competition is not the exception above the SAT. On plenty of awards, it is the baseline.
The Market No Award Platform Can See
The sub-SAT foothold market is a structural blind spot, not a platform failure.
Here is where the argument turns. If competition is already an illusion where the data exists, then the tier below the micro-purchase threshold — where no award record exists at all — is not just harder to measure. It may not resemble the visible market in any way that lets you reason from one to the other.
Explore $492B in federal IT spend
Try FedSpend free for 14 days. Full dashboard access, no credit card required.
The reason is plumbing. Micro-purchases move on government purchase cards, and those ledgers are organized around card accounts and reconciliation, not competition or capture intelligence. You cannot query them by vendor, by product line, or by winning incumbent. What FPDS gives you for a $13M order simply does not exist for a $9,000 one:
- No PIID to track, protest, or tie to a recompete.
- No NAICS code to filter the buy by market.
- No offers-received field to gauge who competed.
- No recipient name you can search by product or program.
So when a BD lead says the foothold strategy is to win small and grow, understand what that means for measurement: the very contracts meant to seed the relationship are the ones no dashboard — ours, GovWin’s, or anyone’s — can show you your competitors already hold. The blind spot is designed into the reporting rules, not into any one tool.
Rebuilding Past-Performance Strategy Around the Blind Spot
Capture teams need relationship and program-office intelligence for sub-SAT pursuit, because award-database mining cannot reach that tier.
The standard past-performance playbook — scrape award history, find adjacent wins, model the recompete — works only where records exist. Below the threshold, that method returns nothing, and nothing is not the same as no activity. It just looks identical in a spreadsheet.
The fix is not a better query. It is a different source of truth: the humans and program offices making small buys, tracked directly rather than inferred from filings. That is slower, less scalable, and far more accurate than pretending the data covers the tier it structurally excludes.
It also means retiring “get a foothold” as standalone advice. A useful foothold instruction specifies four things:
- The dollar tier. Sub-SAT and SAT-to-seven-figures behave like different markets; name which one.
- The contract vehicle. A BPA call, a schedule order, and a standalone SAP buy each carry different odds and different follow-on paths.
- The agency’s buying pattern. A fragmenter like the Navy rewards a different approach than a consolidator like the Air Force.
- The program office, not just the agency. Sub-SAT decisions live at the office level, which is where the relationship has to land.
Mapping pursuit to the actual programs and offices driving the buy — rather than to the award records they eventually generate — is the only way to build past performance in a tier the public record refuses to describe.
Common Questions About Federal Tail Spend and the SAT
What is the simplified acquisition threshold in federal contracting?
The Simplified Acquisition Threshold is the dollar ceiling under which agencies may use streamlined procedures instead of full RFP processes. As of October 1, 2025, it rose from $250,000 to $350,000 under the FAR Council’s inflation adjustment.
Where does federal spending data become invisible below the threshold?
Data effectively disappears below the FAR 2.101 micro-purchase threshold, now $15,000. Buys under that line typically move on purchase cards and never generate an FPDS record, so they cannot be queried by vendor, product, or competition.
Why is competition thin above the SAT?
Because a “competed” label does not guarantee more than one bidder. GAO found roughly 13% of federal obligations went to contracts competed with only a single offer received, a share that held steady for years.
How should a foothold strategy account for sub-SAT contracts?
By treating them as relationship targets, not data targets. Because sub-SAT wins leave no award trail, pursuit has to run through program offices and direct contact rather than through award-history platforms.
Treat FPDS as a Map, Not a Census
Visible award data is a partial map of the federal market, not a complete count of it.
Two facts sit uneasily together, and FY27 planning has to hold both. The competition you can see is thinner than the “full and open” labels claim — sometimes a single bidder on an eight-figure order. And the foothold tier everyone is quietly building strategy around sits below the line where any of that data exists.
The takeaway is not that FPDS-derived tools are useless. They are the best available map of the tier they cover. The mistake is reading a map as a census — assuming the market ends where the records do.
Here is the position I will defend: any FY27 pipeline built purely on visible award history is optimizing against a dataset that silently omits the exact segment its own foothold strategy depends on. Fix that by pairing the visible record with structured intelligence below the SAT — the kind that flags an agency’s buying drift before the solicitation posts, the way disciplined teams already track budget signals ahead of the market. The number on the award is real. It is just not the whole story, and it never was.