The USDA just handed Palantir a $300M blanket purchase agreement described publicly as a "continuation" of existing work. That word — continuation — is doing a lot of heavy lifting. If you're a small business BD lead who saw that headline and thought "is there an opportunity here for us?", the honest answer is probably no. But the more useful question is what this deal tells you about how to allocate your time elsewhere.
"Continuation" Is Not Marketing Spin — It's a Legal Signal
When an agency describes a new award as a continuation of prior work, they're telling you something specific about how the requirement was scoped. Incumbents don't just have an advantage in these situations — they effectively authored the performance baseline. The technical approach in the solicitation often mirrors what the incumbent already does. The evaluation criteria reward demonstrated past performance on the exact system being extended.
Blanket purchase agreements under existing vehicles are one of the cleaner mechanisms for agencies to re-obligate to a preferred vendor without triggering the competitive scrutiny that a standalone procurement would attract. The ceiling goes up; the competition stays narrow.
That's not a criticism of Palantir or USDA — it's a description of how the federal procurement system actually works. Data-intensive agencies with complex operational environments rationally prefer continuity on mission-critical systems. The switching costs are real. The risk of disruption is real. Contracting officers know this, and they structure awards accordingly.
What's irrational is a small business spending six weeks on a capture effort for a requirement that was functionally decided before the solicitation dropped.
The Downstream Opportunity Map Is the Right Frame
Here's where small business BD should actually focus when a deal like this lands: not on the prime, but on the work it creates downstream.
A $300M BPA for IT and national security work at USDA will generate task orders. Some of those task orders will have subcontracting requirements — either because of small business goals tied to the BPA, or because the prime needs specific domain expertise it doesn't staff internally. FPDS and USASpending.gov will show you the subcontract and modification history on prior Palantir USDA work. That's your entry point for a partnership conversation, not a competitive one.
Specifically, look for:
- Task orders with specialized requirements in geospatial analysis, agricultural data systems, or food supply chain security where boutique domain expertise beats platform breadth
- Subcontracting plan obligations that large primes have to meet — if the BPA has SB participation requirements baked in, those become leverage points in teaming conversations
- Adjacent requirements at USDA that the BPA doesn't cover — every large platform deployment creates visibility gaps and integration needs that a separate procurement addresses
What This Pattern Looks Like Across Your Pipeline
The USDA-Palantir deal is one instance of a structural pattern that repeats constantly across federal IT. A platform vendor gets initial entry — sometimes through an Other Transaction Agreement, sometimes through a small pilot task order — delivers results, and then the agency builds its operational dependency around that vendor's architecture. Re-compete math becomes unfavorable for challengers, and eventually the agency formalizes what was already a de facto sole-source relationship through a competitive-looking BPA.
"We spent four months on a pursuit that an agency publicly called competitive. Debriefs made clear the incumbent's architecture was the technical baseline. We were graded against a standard they helped write."
— Hypothetical Capture Manager, Mid-Tier GovCon
This is the core argument behind paying attention to award history before you start a capture effort. If you look up an agency's prior obligations on a given NAICS code or program area and the same vendor appears across three to five consecutive years with expanding ceiling values, that's not a competitive market — it's a relationship with procurement paperwork around it.
I cover the mechanics of reading those signals in Wired RFPs. The short version: award continuity plus "continuation" language plus a BPA structure equals a near-zero probability of displacement for a small business without an existing relationship in that program office.
The CMMC Parallel — Platforms as Bid Filters
There's an underappreciated similarity between what Palantir does in the data platform space and what CMMC does in the defense industrial base: both function as barriers that look like requirements. CMMC compliance filters out companies that can't afford the certification burden. Proprietary platform dependencies filter out companies that aren't already integrated into the vendor's ecosystem.
The result in both cases is that agencies gradually narrow their viable vendor pool — not through explicit exclusion but through technical and compliance moats that compound over time. For small businesses, the strategic response is the same in both cases: get inside the moat early (through teaming, through subcontracts, through pilot work) or stop spending BD resources trying to assault it from outside.
Agencies that are earlier in their platform adoption curve — not yet locked into a single vendor — are where small businesses can still shape requirements. That window closes faster than most BD calendars account for.
What to Do With This Information Monday Morning
If USDA agriculture or national security IT is in your target market, the questions to answer this week are:
- Does your firm have an existing relationship with the prime through prior subcontracts or teaming?
- Are there adjacent USDA IT requirements — system integration, data migration, training, cybersecurity overlays — that fall outside the BPA's scope?
- What other civilian agencies have similar data-intensive missions where the platform consolidation hasn't happened yet?
The third question is where your BD investment actually pays off. Look at agencies with analogous missions — natural resources management, food safety inspection, agricultural export compliance — that are still in the market-research phase on their data platform strategy. That's where a small business can get in front of a requirement before an incumbent writes it.
Chasing a $300M BPA that's already been awarded is a case study in how small business BD budgets get consumed with nothing to show for it. The better move is using that deal as a market signal: this category of work is now locked up at USDA for the foreseeable future — where else does this requirement live, and how early can we get there?
As I lay out in Bid Strategy, the most expensive thing in federal BD isn't the proposal you lose — it's the six weeks you spend on the capture before you decide not to bid. Deals like the USDA-Palantir BPA are telling you to reallocate that time before it's spent.
Frequently Asked Questions
Can small businesses compete as primes on large BPAs like this one?
Rarely, and almost never when the BPA is structured as a continuation of incumbent work. The technical baseline, past performance requirements, and evaluation criteria all compound in the incumbent's favor. The better path is subcontract positioning or pursuing adjacent requirements on separate vehicles.
How do I find out if a large prime has small business subcontracting obligations on a BPA?
The solicitation and resulting award documents are the primary source — subcontracting plans are often included or referenced. USASpending.gov shows subcontract awards over $30K on federal contracts, which gives you a track record of how a prime actually performs against its SB commitments versus what it promised.
If "continuation" language appears in a pre-solicitation notice, is it worth pursuing?
It's worth a quick competitive landscape check — nothing more. Pull the award history for the program office on FPDS, identify the prior performer, and assess whether you have a direct relationship with that office or a disruptive technical differentiator. If neither is true, move the opportunity to your watch list and redirect active BD resources.
What's the best leading indicator that an agency is still early enough in platform adoption for a small business to shape a requirement?
Look for market research notices (RFIs, Sources Sought) where no single vendor dominates the prior award history for that NAICS code at that agency. Multiple small awards to different vendors signals an agency still evaluating. A single vendor with expanding task order ceilings signals consolidation is already underway.