- High vendor concentration signals locked accounts, not proven demand
- Army's 10% top-PSC concentration makes it more contestable than VA
- Rising obligations in consecutive years signal recompetes before solicitations
- Filter by your catalog's NAICS code, not total agency IT budgets
- Quarterly spend reviews beat broad canvasses for lean BD teams
A five-person channel team doesn’t need to know that the Air Force obligated $12.0 billion against IT and telecom contracts in fiscal 2025. It needs to know that $2.39 billion of it landed in a single labor code that’s grown every year since FY2023 — an incumbent’s name is already on it. That’s the number capture teams at the big primes fight over. The number that matters to a reseller sits a few agencies down the list, where obligations split across a dozen codes and none claims even a fifth of the total. That’s not a smaller opportunity. It’s an open door.
Why Federal IT Reselling Is Getting Harder (And More Cold Outreach Won’t Fix It)
Margin compression and thin BD benches are squeezing resellers from both directions, and the usual response — more calls, more emails — makes the math worse, not better. Distributor markups keep shrinking, OEM rules limit who you’re allowed to chase, and most reseller shops run BD with one or two people wearing three hats each. Every hour spent canvassing an agency where a prime already owns the account is an hour lost.
The fix isn’t a bigger call list. It’s a shorter one. Lean teams that already treat spend data as a substitute for headcount outperform teams running broad canvasses, because they spend scarce hours on accounts already flagged as open.
| Prospecting Method | Signal Used | Fit for a 2-3 Person Team |
|---|---|---|
| Broad agency canvass | None — same list every competitor has | Poor; burns hours on locked incumbents |
| Incumbent relationship-building | Past performance, not current spend | Slow; takes years to pay off |
| Spend-data-targeted outreach | Obligation concentration, transaction trend | Strong; wins go to whoever moves first |
What Does Federal Spend Data Actually Tell a Reseller That a Capture Team Doesn’t Need?
Reseller-focused spend analysis cares less about an agency’s total IT budget and more about how locked-up that budget already is. A capture team chasing a nine-figure bid needs the full agency picture; a reseller closing a six- or seven-figure refresh needs something narrower — which PSC and NAICS-level obligations are fragmented enough for a new vendor relationship to take root.
Headline agency totals are close to useless here. A $10 billion agency says nothing about whether that money splits across fifty vendors or locks to three. Vendor concentration is the real signal, and it cuts the opposite way from most pitch decks: high concentration means a market that’s closed, not proven. The same logic applies to mapping which vendors already sell into an agency before you pitch it — a crowded roster is a warning, not proof of demand.
How to Spot Fragmented Vendor Bases Using Agency Spend Data
The clearest fragmentation signal is a PSC category that keeps changing identity year over year — no single vendor relationship has had time to calcify. Look at the Army. Per FedSpend’s agency-spend dataset (as of September 2026), its top PSC was 5895 (Miscellaneous Communication Equipment) in FY2020, then 5810 (Communications Security Equipment) by FY2024 and FY2025 — though that leading code shrank from $1.44 billion to $962 million, just 10% of the Army’s $9.4 billion IT/telecom total. Compare that to the Air Force and VA, where one code — DA01, application development support labor — has topped the list three years running.
| Agency | FY2025 Top PSC Category | Obligations | Share of Total IT/Telecom Spend |
|---|---|---|---|
| Department of the Army | 5810 — Communications Security Equipment | $962.2M | ~10% |
| Department of the Air Force | DA01 — App Dev Support Services (Labor) | $2.39B | ~20% |
| Department of Veterans Affairs | DA01 — App Dev Support Services (Labor) | $2.83B | ~30% |
That’s the target list writing itself. Agencies with obligations spread across a wider range of codes, with no single category running away from the pack, are where a new reseller relationship can still get a foothold. VA at 30% concentration is a market that’s already decided. Army at 10% is still being decided.
Explore $492B in federal IT spend
Try FedSpend free for 14 days. Full dashboard access, no credit card required.
Using Obligation Trends and Transaction Counts to Time Recompete Outreach
Rising obligations in one PSC code across consecutive fiscal years isn’t a recompete date — it’s the best early signal you’ll get before one exists. Air Force DA01 climbed from $1.57 billion in FY2023 to $2.02 billion in FY2024 to $2.39 billion in FY2025 — a program expanding, not winding down. Navy shows a variant: DA01 rose from $1.63 billion to $2.00 billion between FY2024 and FY2025 while transaction count fell from 48,063 to 44,472 — fewer, bigger actions, the usual sign of consolidation ahead of a recompete.
None of this confirms a solicitation date. Even a contract that looks untouchably large can still move — Washington Technology reported in August 2026 that VA raised its Oracle EHR ceiling by $17 billion, to nearly $27 billion. Pair obligation trends with actual signals that an incumbent’s period of performance is running out before committing outreach hours to a timing bet.
Matching Spend Categories to Your Product Line Without Wasting BD Time
Filter by the codes you actually sell into, not the agency’s whole budget — the NAICS code your catalog maps to tells you more than any total-obligations figure ever will.
- 334220 — Radio/TV/Comms Equipment: hardware resellers, radio and network gear refreshes
- 511210 — Software Publishers: license resale, SaaS renewals, ELA management
- 541511 — Custom Computer Programming: integration and services-heavy VARs
This turns a broad canvass into a short, high-confidence list. Cross-reference your GSA Schedule category or SEWP group against agencies showing fragmentation in that exact code, filtered through a tool like FedSpend’s Award Data Platform, and skip the ones already sewn up.
Building a Lightweight, Repeatable Spend-Data Workflow
Treat this as a standing input to pipeline planning, not a one-time research sprint.
- Pull top PSC and NAICS obligations for five to ten target agencies each quarter.
- Flag agencies where a leading code’s share of total spend is falling, not rising.
- Cross-check flagged agencies against known GSA Schedule refreshes and open SEWP task orders.
- Build a short target list — five accounts you can work beats fifty you can’t.
- Revisit quarterly; obligation patterns shift faster than most BD calendars assume.
Instead of manually re-pulling numbers every ninety days, a standing alert tool like Sentry can flag PSC-level shifts automatically — a bigger win for a two-person BD team than for a capture shop with analysts to spare. It also surfaces the smaller, sub-threshold purchase activity many resellers actually live on.
The Agencies With the Messiest Vendor Base Are the Ones Worth Calling First
Most reseller BD still chases the biggest number on the budget chart, and most of them lose to whoever already owns that account. The agencies worth a Tuesday-morning call are the ones where spend is scattered and the top code keeps changing names. That’s not a consolation prize — it’s the only opening a lean team can actually win before someone bigger notices it too.