- Small IT shops fail BD by treating all postings equally
- Use timing and bureau-level fit as the two core filters
- A 180-plus-day recompete window is where positioning happens
- Quarterly shortlist of 2-3 targets beats continuous scanning
- Elimination is the core BD strategy, not accumulation
Ask a five-person IT reseller why it skipped a winnable recompete, and you’ll get the wrong answer first: “we didn’t have the data.” That’s rarely true. Every award, every incumbent, every obligation on that contract already sits in USAspending.gov, free and searchable. The real answer, the one founders don’t like saying out loud, is nobody on staff had six hours to go find it.
A data problem is solved by buying a subscription; a time problem by changing the method. Most small federal IT shops do neither: they chase every SAM.gov posting with their NAICS code, or chase nothing and wait for referrals. Both lose the same math: a one-person BD function spread across forty opportunities produces forty shallow reads, zero strong proposals.
Why Small IT Businesses Lose the BD Math Before They Start
Small federal IT shops don’t fail at business development because they lack information; they fail because they treat every posting as equally worth their time. A 40-person managed services provider has the same public data as a 4,000-person integrator. What it lacks is a team to read every solicitation and decide what’s contestable before the clock starts.
| Approach | What It Looks Like | Where It Breaks Down |
|---|---|---|
| Chase everything | Capability statement for every NAICS hit on SAM.gov | Bandwidth too thin for real competitive analysis |
| Chase nothing systematic | Wait on referrals, react only when one lands | Misses recompetes months before they post |
| Quarterly shortlist | Filter by timing and bureau fit, land on 2-3 targets | Requires saying no to the other 37 |
What a BD Department Actually Does (and Why One Person Can Replicate It)
A BD department’s real output isn’t a pipeline of opportunities, it’s a pile of eliminated ones. Most of a capture analyst’s day is disqualification: read a notice, check the incumbent, check the size, move on. Discovery is the easy 10%; elimination is the job.
- Triage incoming notices against NAICS, PSC, and set-aside fit
- Check recompete timing against available proposal bandwidth
- Research incumbent strength and teaming history before committing resources
- Decide prime, sub, or pass within days of a notice landing
A solo generalist can run all four with two filters instead of covering the whole universe: recompete timing, and who actually uses the IT below the contracting office.
Filter One: Recompete Timing as a Prioritization Tool
A recompete is only worth your time if there’s a realistic entry point, not simply because the base period is expiring. Expiring and contestable are different facts. Conflating them wastes quarters chasing contracts where the incumbent owns the relationship, the past performance, and the cleared staff.
A contract inside a 30-day window is almost never winnable cold; a 180-day-or-further window is where positioning happens — the logic behind tools like Recompete Radar, which scores contracts on size, timing, and contestability rather than just an expiration date. Small businesses also miscalculate size by looking only at the base IDV: an IDV child-order rollup can hide real money in task orders issued years later, up to ordering-period end.
| Window | What It Signals | Solo BD Action |
|---|---|---|
| 0-30 days | Decision locked in | Skip unless already teamed |
| 31-90 days | RFP likely imminent | Confirm fit fast — last entry window |
| 91-180 days | Positioning window open | Begin incumbent and bureau research |
| 180+ days / ordering-period end | Early enough to build past performance | Add to quarterly shortlist |
Filter Two: Bureau-Level Spend Decomposition to Judge Fit and Incumbent Strength
The office that signs a contract is rarely the office that uses it, and that gap is where small businesses misjudge fit. A department-level contracting shop might serve one bureau’s help desk, or a different component’s cybersecurity program entirely. Decomposing spend to the end-user bureau, layered with PSC and NAICS classification per the GSA Category Management IT definition, collapses a multibillion-dollar budget to the handful of contracts in your lane.
Explore federal IT spending patterns free
Start a FedSpend trial to discover growth opportunities in $675B+ of federal IT awards.
Subaward data from the federal FSRS feed shows what transaction history can’t: which subcontractors and OEMs sit underneath the prime — the difference between chasing a prime slot you’ll never win and finding the open teaming slot, a judgment the Reseller Landscape view surfaces, since the goal is the contract where the incumbent’s grip is weakest.
Building the Quarterly Shortlist: A Workflow for One Person
A repeatable quarterly block beats continuous ad hoc searching, and it fits inside an afternoon. Timing first, since it eliminates fastest; fit second; incumbent research last, for survivors only.
- Pull everything in your NAICS/PSC lane inside the 90-180+ day recompete windows.
- Cross-reference each against bureau-level fit — does the end user match what you deliver?
- Check incumbent concentration and subaward history on anything that survives.
- Rank survivors by realistic entry point — prime, sub, or pass — and commit to 2-3 targets for the quarter.
Fewer, better pursuits protect proposal bandwidth, which is why capture managers stop guessing which contracts are coming up for recompete: the decision is usually made before the RFP posts. One caution: classified spending, OTA member-project dollars, and micro-purchases are structurally invisible in public data, so your shortlist covers most of the visible IT market, not all of it.
What This Looks Like in Practice
A two-person reseller pulling 40 SAM.gov postings a month doesn’t need 40 capability statements. Timing leaves a dozen inside the 90-180 day window; bureau fit drops that to four or five; subaward history usually shows two with a locked incumbent OEM relationship, and one or two with a prime that’s never subcontracted.
That’s the shortlist: 2-3 targets, repeated every quarter — the same habit behind finding long-tail federal IT contracts, where the real opportunity sits below the headline awards everyone else is fighting over.
Getting Started Without Hiring a BD Department
The mindset shift is elimination over accumulation: stop trying to see every opportunity and start ruling most of them out fast. A BD department was never a discovery engine; it was a filter with enough headcount to run in parallel. A disciplined generalist with two signals — timing and bureau-level fit — runs the same filter serially, in a few hours a quarter instead of a few desks all year. See the broader case for why spend data matters more without a BD department.
Elimination Is the Strategy, Not the Consolation Prize
Nobody builds a BD department at a 30-person IT shop, and nobody should. One capture analyst’s salary can exceed what most small recompete wins are worth in year one. What works is treating triage as the job itself, not a prelude to the real work. Two filters, run on a quarterly cadence, do what a team used to do by headcount. The businesses that get this right aren’t the ones with the most data — they’re the ones willing to say no to 37 out of 40 postings before lunch.
