Federal IT Contracting Officers and Program Managers: What They’d Want From a Vendor Who’s Done the Homework

A contracting officer at the Department of the Air Force sits through three vendor meetings on an average Tuesday, and by the second slide of each one, she already knows how it ends. The test isn’t whether the vendor can do application development, cybersecurity, or network support — she assumes baseline competence from anyone who landed a meeting. The test is whether they looked at where her agency’s money actually went before they walked in the room. Most vendors fail that test in the first ninety seconds, and most of them never realize the test was happening.

That’s the gap this piece is about: the difference between selling to federal contracting officers with a generic capabilities deck and showing up having done the homework. It matters because how to pitch a federal contracting officer isn’t really a sales-technique question. It’s a research question, and most reps are still answering it like it’s 2015.

What Do Federal Contracting Officers Actually Listen for in the First 90 Seconds?

They’re listening for evidence that you’ve already looked at their spend history, not for a list of your certifications. A generic opener — “we do application development support,” “we’re a trusted partner in IT modernization” — reads as a signal of low preparation, not a neutral introduction. It sounds like the same sentence the last four vendors used, because it probably is.

A pitch that opens differently stands out immediately. The table below shows what separates the two in a CO’s or PM’s head, usually before either side has said more than two sentences.

What a Generic Capabilities Deck Actually Looks Like From the Inside

From the buyer’s chair, a generic deck is a stack of slides that could be presented to any agency in any fiscal year without changing a word. Past performance citations, certification logos, a mission statement slide, maybe an org chart. None of it says anything about this agency, this office, or this year’s buying pattern.

The recurring ingredients of the deck that gets tuned out tend to look like this:

• Past performance slides listing contracts won elsewhere, with no connection drawn to the buyer’s own category spend
• Certification and set-aside badges presented as differentiators rather than table stakes
• A capabilities matrix covering every service line the company offers, signaling breadth instead of relevance
• A closing “why us” slide built on company values rather than anything specific to the agency in the room

None of this is wrong, exactly. It’s just interchangeable — and interchangeable reads as spray-and-pray, the exact opposite of targeted. COs and PMs sit through enough of these to spot the pattern inside the first slide, the same way they can tell within a few lines whether a vendor actually mapped the competitive landscape before pitching or just pulled a template.

What Does Real Homework Actually Look Like in an Agency Pitch?

Real homework looks like a vendor citing the specific procurement category code an agency has been obligating money against, across more than one fiscal year. Not “IT services” — a PSC code, a NAICS code, a trend line.

Take the five agencies where this kind of data is easiest to pull. The Award Data Platform breaks obligations down to the PSC and NAICS level per fiscal year, and the patterns aren’t subtle once you look.

The Army Example Nobody Pitches Correctly

Here’s where it gets interesting. Four of these five agencies lead with the same application-development labor category. The Army doesn’t. Its top obligation code is communications security equipment and components, not software labor — a vendor who walks into an Army meeting with the same software-labor opener they used at the VA is reciting a script that doesn’t match the buyer’s actual spend. That mismatch is instantly visible to anyone on the other side of the table.

Why the Multi-Year Trend Matters More Than One Year’s Number

A single year of data can be a fluke. A trend is a pattern. Air Force obligations in application-development support labor ran $1.57 billion in FY2023, $2.02 billion in FY2024, and $2.39 billion in FY2025 — three straight years of growth in the same category. Citing that trajectory, instead of one snapshot, is what separates a vendor who checked once from one doing sustained competitive research the way a capture team builds a battlecard.

Why Does Spend Context Build Trust Faster Than Past Performance Alone?

Past performance proves you can do the work somewhere; spend-specific framing proves you understand what this agency needs right now. Those are different claims, and contracting officers know it.

A CO managing a source selection isn’t just scoring capability. She’s managing risk — the risk that a vendor overpromises, misreads the requirement, or doesn’t understand how the money actually moves inside her organization. Specificity is a risk-reduction signal. When a vendor references NAICS 541512, Computer Systems Design Services — the top code across all five agencies in this dataset — and then explains how that plays out differently at HHS versus the Navy, it tells the buyer this person isn’t guessing. Past performance says “trust my resume.” Spend context says “trust that I read yours first.”

Which Questions Can a Prepared Vendor Answer That an Unprepared One Can’t?

A prepared vendor can answer three questions cold, and an unprepared one stalls on all three. These aren’t trick questions. They’re the basic diligence a CO expects anyone serious about the account to have already done.

1. Which categories has this agency actually obligated money toward over the past few fiscal years? Not a guess based on the mission statement — the actual PSC breakdown, by dollar.
2. Is this a growing or shrinking area of spend for them? HHS obligated $2.33 billion into application-development labor in FY2024 alone; a vendor who can say whether that line is expanding or flattening is operating on information, not hope.
3. Which NAICS codes define the competitive field here? Knowing that 541512 and 541519 dominate the landscape at an agency tells a vendor who they’re actually up against, not just who they’re pitching to.

A rep who can’t answer any of these is, functionally, pitching blind — and sitting across from someone who can tell.

How Much Spend Data Is Too Much in a Vendor Pitch?

One or two sharp data points beat a spreadsheet every time. The goal of bringing agency spend context into a pitch isn’t to perform analysis in front of the buyer — it’s to earn the right to ask a better discovery question.

A rep who opens with a single relevant obligation figure, then pivots to “how does that line up with what you’re seeing on the ground,” reads as curious and credible. A rep who opens by narrating six slides of PSC trend charts reads as someone who built a deck instead of a conversation. The data is a door-opener, not the pitch itself — the same discipline that turns a cold open into a warm pipeline conversation rather than a monologue.

The Homework Isn’t Optional Anymore

The bar for “prepared” has moved, and most sales organizations haven’t noticed. Agency-specific spend context used to be a differentiator; among the vendors actually winning recompetes and new task orders in 2026, it’s table stakes. The reps who are still leading with a capabilities slide are competing for the CO’s patience against reps who already know what her building spent last year — and losing, quietly, without ever finding out why.

This is less about having a better slide deck and more about having looked at the right data before building one. The agency profiles on FedSpend’s Award Data Platform exist for exactly that ninety seconds — the part of the meeting where a CO decides, often before you’ve finished your second sentence, whether you’re worth the rest of the hour.