How to Size a New Federal IT Product Category Before You Build a Go-to-Market Plan

A product leader at a 60-person GovTech company once told me their entire TAM slide rested on one data point: three prospects at a conference said they’d “definitely consider it.” That’s a hallway poll, not a federal TAM analysis. To size a federal IT market for a new product before building a go-to-market plan, the durable signal sits in years of federal obligations data, coded transaction by transaction, long before anyone posts a solicitation for a product that doesn’t fully exist yet.

Why “Is Anyone Buying This?” Is the Wrong First Question

The right question isn’t whether anyone is buying your product — it’s how much agencies have already obligated toward the capability it replaces. Most vendors validate a new federal category like a consumer app: conference chatter, RFP alerts, a few friendly contracting officers. That’s a single moment in time, filtered through whoever picked up the phone.

Historical obligations data is a multi-year record of what agencies actually paid for, under which codes, at what scale — before a line item matching your marketing copy appears. This walkthrough is federal product category validation done properly: a repeatable five-step method for federal market sizing with spend data, ahead of a go-to-market plan.

Step 1: Define the Category by PSC and NAICS Codes, Not Marketing Language

Your product’s marketing language almost never matches how agencies code the money. Federal spend data doesn’t know what “AI-powered compliance monitoring” means — it knows Product Service Codes and NAICS codes, and one capability routinely gets coded three different ways depending on the contracting officer.

Take application development. An agency might buy it as labor-heavy support under DA01, as a subscription under the SaaS-specific code DA10, or as a one-time purchase under the legacy perpetual-license code 7A21. Same capability, three codes. Pull all three, not just the one matching your pitch deck.

How Do You Pull Total Obligations Across a Multi-Year Window?

Sum obligations against your mapped codes across at least three fiscal years, because a single-year snapshot tells you nothing about direction. This is the core of a real federal obligations data analysis: a category flat at $1 billion for three years is a different opportunity than one that just crossed $1 billion after growing every year.

FedSpend’s agency-spend dataset (as of September 1, 2026) shows the Air Force’s obligations under DA01 and DA10 climbing from $1.57 billion and $703 million in fiscal 2023, to $2.02 billion and $926 million in fiscal 2024, to $2.39 billion and $1.07 billion in fiscal 2025 — based on 22,460 tracked transactions that year. That’s growth on both the labor and SaaS side, in one service branch, three years running — a stronger signal than a hot RFP that closes in six weeks and disappears.

Which Agencies Are Already Buying Adjacent Capability?

Rank agencies by total obligations in your mapped codes, then weigh transaction count against dollar total. Two agencies can post similar totals and still run on different sales motions.

FedSpend’s agency-spend dataset (as of September 1, 2026, FY2025 figures) puts four agencies within striking distance of each other: the Air Force at $12.01 billion across 22,460 transactions, the Navy at $10.07 billion across 44,472, the Army at $9.41 billion across 19,914, and the VA at $9.40 billion across 12,975.

Dollar totals alone say chase the Air Force and ignore the rest. Transaction counts tell a sharper story: the Navy buys the same category almost twice as often at similar total spend, signaling a high-volume, smaller-deal environment rather than a few program offices controlling the budget. That distinction changes who you knock on first — a pattern a searchable award-data platform surfaces faster than parsing raw FPDS extracts by hand.

How Do You Estimate Price Bands Before Setting a Pricing Strategy?

Break out the top PSC lines within your target agencies to see whether the category is priced as labor, license, or subscription. This is where pricing assumptions fall apart.

Inside FedSpend’s FY2025 Department of Veterans Affairs data, DA01 obligations reached roughly $2.83 billion against DA10’s roughly $2.16 billion — two adjacent codes for similar application-development work, carrying different obligation profiles. Is VA still paying for staffed labor because incumbents haven’t offered a SaaS alternative, or because the mission genuinely requires custom work a subscription can’t replace?

Treat these totals as directional signals, not a substitute for pricing comparable awards. The federal shift away from perpetual licensing toward subscription-based delivery is real but uneven — some agencies moved decisively, others are still riding out license renewals nobody’s re-competed in years.

Step 5: Decide — Build, Reposition, or Walk Away

Three outcomes fall out of this exercise, and only one means “start building a GTM plan.” This is a go/no-go checkpoint, not a strategy document.

1. Multi-year growth plus multiple buying agencies: proceed to territory and pipeline planning.
2. Flat obligations concentrated in one agency: reposition against a different code before committing budget.
3. Near-zero presence across every code mapping: the category is premature for federal investment right now.

A near-zero reading doesn’t mean automatic retreat — it often means your product description hasn’t found its code yet, and the fix is reframing the pitch. Before locking in a verdict, check for:

• Three-plus fiscal years of data, not one lump-sum year that could be a single mega-contract.
• Two or more agencies buying adjacent capability, not a single outlier program office.

Turning a Market-Sizing Exercise Into a Go/No-Go Decision

Five steps, one output: a defensible answer to “should we build this,” backed by data instead of anecdote. Map the category to real codes, pull the multi-year trend, rank the buying agencies, break out price bands, then apply the decision framework.

Once the answer is “build,” the work changes shape. Sizing a category isn’t building a BD motion without a full capture team, nor the pipeline work that turns a target list into warm conversations. Vendors who skip straight to cold outreach often rediscover, expensively, that the biggest obligations don’t sit with agencies that have room for a new vendor — the lesson that applies to resellers hunting underserved agency contracts. A sizing pass built on an obligations-based intelligence report is a starting line, not a finish line.