How to Build a Competitive Battlecard for a Federal IT Recompete Using Spend Data

Every capture manager has sat through a color-team review where the “competitive analysis” slide was three bullet points about the incumbent’s past performance and a line reading “strong relationships with the customer.” That slide doesn’t win or lose anything. It’s filler dressed up as strategy.

A federal recompete battlecard built on actual obligations data does something a capabilities narrative can’t: it shows you where the incumbent is already losing ground, before you write a single word of the proposal. The trick isn’t finding the data — USAspending.gov is free and public. The trick is knowing which numbers in that pull actually predict vulnerability and which are noise.

Why a Spend-Based Battlecard Beats a Capabilities-Only Battlecard

A capabilities-only battlecard repeats what the incumbent already says about itself; a spend-based one measures what they can’t spin. Marketing language, past-performance narratives, and reference quotes are curated by the company being evaluated. Obligation trends, award cadence, and PSC/NAICS concentration are recorded by the government, independent of anyone’s messaging.

This isn’t an either/or. The spend layer sits underneath the capabilities layer and tells you which of the incumbent’s claimed strengths are actually holding up.

Step 1: Pull the Incumbent’s Historical Obligations on the Contract and Agency

Start with the base contract’s obligation history, year over year, and read it next to transaction count. Total dollars alone can mislead — a single large modification can make a struggling contract look healthy for one fiscal year. Pair the dollar figure with how many individual transactions produced it. Rising obligations with a shrinking transaction count can mean consolidation into fewer, larger task orders. Flat obligations with a rising transaction count can mean the incumbent is scraping together smaller work to mask a stalled core.

Context matters here, and this is where agency-level trends help you calibrate. The table below uses the Department of the Air Force’s published obligations as an illustration of the kind of multi-year pattern you’re looking for — it’s agency-wide, not any single incumbent’s book, but it shows the method.

Dollars and transactions moving up together, as in this Air Force IT pattern, is what a growing book looks like. If your target incumbent’s single contract shows the opposite — obligations declining while the agency’s overall IT spend in that same PSC lane is climbing — that gap is your opening sentence in the vulnerabilities section. The award data platform is built to pull this comparison without a week of spreadsheet reconciliation.

Step 2: Map Past Performance Patterns by PSC and NAICS Code

The PSC and NAICS mix tells you whether the incumbent is expanding its footprint with the customer or getting boxed into a single lane. An incumbent that started on a help-desk labor code and has since picked up application development, cloud migration, and cybersecurity support codes within the same agency has grown the relationship. One that’s still sitting on the exact same PSC it won five years ago, with no adjacent codes added, has either chosen to stay narrow or been kept narrow by the customer.

Pull the incumbent’s full award history, bucket every task order and mod by PSC code, and plot the mix across fiscal years. Look specifically for scope creep — new codes appearing — versus scope narrowing, where codes the incumbent used to hold have disappeared from their award history and show up instead under a competitor’s name. That second pattern is a direct signal the customer has already started hedging.

Step 3: Identify Where the Incumbent May Be Vulnerable

Three spend signals consistently correlate with an incumbent that’s lost delivery capacity or customer trust: declining obligations against flat transaction count, heavy concentration in one PSC code, and a slowing award cadence. None of these are proof. All three are hypotheses worth testing against public news and past-performance records before they go anywhere near a proposal.

• Declining obligations, flat or rising transaction count: often reads as understaffing or rate pressure — the incumbent is doing more transactions for less money, which usually means smaller task orders or discounting to hold the account.
• Heavy reliance on one PSC code: overexposure. If 80% of the incumbent’s obligations on the contract sit in a single code, they have no diversified relationship to fall back on if that one workstream gets re-scoped.
• Slowing award cadence: fewer task orders issued per year than the contract’s history suggests, which can point to delivery friction or a cooling relationship with the program office.

The translation step matters as much as the detection step. A declining-obligations signal becomes a legitimate win theme around staffing depth or modernization — not a claim that the incumbent is “failing,” which you can’t support and shouldn’t write. Large contract modifications are a useful reminder of how fast a trajectory can actually shift: Washington Technology reported in August 2026 that the VA raised Oracle’s EHR modernization contract ceiling by $17 billion, pushing the total to nearly $27 billion — a reminder that a contract’s ceiling and its actual obligations are two different numbers, and the gap between them is often where the real story about an incumbent’s trajectory lives.

Step 4: Assemble the One-Page Battlecard

A battlecard that doesn’t fit on one page won’t survive a ten-minute pursuit review, so the discipline is in what you leave out. Every section below should be a defensible claim, not a paragraph of hedging.

1. Incumbent snapshot: contract vehicle, ceiling vs. current obligations, period of performance, teaming structure if known.
2. Obligation trend summary: three-year chart or table, dollars and transaction count side by side.
3. PSC/NAICS footprint: what codes they hold now versus three years ago, flagged as expanding or narrowing.
4. Identified vulnerabilities: each one labeled explicitly as a hypothesis, with the data point and the public signal (if any) that supports it.
5. Your counter-positioning: the one or two win themes this vulnerability analysis actually supports — not a wish list.

Treat this as a living document. If you flagged your pursuit through recompete radar tracking months before the solicitation drops, update the battlecard every time new obligations post, not once at kickoff and never again.

Common Mistakes That Undermine a Battlecard

The most common failure is treating spend data as the whole story instead of one input among several. Personnel, past relationships, teaming arrangements, and agency politics still decide most recompetes — spend data narrows where to look, it doesn’t replace judgment.

The second failure is using a stale pull. An obligations table built on last fiscal year’s numbers, presented as current, will get caught by anyone on the review team who’s looked at the award more recently than you have. The third is overstating a vulnerability as a certainty in the proposal itself — writing “the incumbent is understaffed” when your evidence is a declining obligations trend and nothing else. That’s a hypothesis, and proposal reviewers who’ve seen it backfire will flag it immediately.

Turning the Battlecard Into Action

The battlecard only earns its keep if it changes a decision — bid/no-bid, price-to-win, or a specific win theme in the proposal. If the vulnerabilities you found don’t shift any of those three things, the exercise was academic. Feed the obligation trend directly into your price-to-win model: a contract with declining obligations and shrinking transaction count usually means the incumbent has room to be underbid, not that the ceiling price is the number to chase.

This is also where the manual-versus-platform question actually matters. Teams without a dedicated capture analyst often default to building this in a spreadsheet pulled from whatever public tool they already have access to, which works until the recompete timeline compresses and nobody has three days to rebuild the pull.

The Battlecard Is Only as Honest as Its Caveats

Most capture teams that skip this analysis aren’t lazy — they’re intimidated by the data pull, so they default to the capabilities slide because it’s faster to build. That’s a mistake worth naming plainly: a battlecard built entirely on marketing claims tells you nothing the incumbent hasn’t already chosen to reveal. The version built on obligation trends, PSC concentration, and award cadence tells you something the incumbent can’t control — and that’s the version worth the extra afternoon it takes to build. Skip the caveats at your own risk; a vulnerability hypothesis dressed up as a certainty in front of a color team is how good capture teams lose credibility before they’ve even submitted.