US Federal Readiness
Capability statement.
A capability statement is your one-page seller's resume for government buyers. Get it right and a contracting officer can see what you do, that you've done it before, and how to reach you — in under a minute.
There's no single mandated form, but the convention is settled. Below: the four sections every strong statement has, the company data that has to be on it, and how to keep it to a page.
The four sections.
The structure contracting officers expect. Each section earns its space — cut anything that doesn't help them decide to call you.
Core competencies
What your business does best, in the buyer's words. Lead with the few services you actually want to win, stated plainly and backed by specifics — not a catch-all list. Four to six is the usual guidance.
Past performance
Recent, relevant contracts that prove you can deliver. The common format is a short list: customer, contract number, period of performance, value, and a one-line outcome. Three recent examples is the typical baseline.
Differentiators
Why you over the other vendors who could also do the work. Concrete advantages — certifications, a niche, a clearance, a track record — not adjectives. This is the line a contracting officer remembers.
Company data
The identifiers and codes a contracting officer needs to act: your UEI and CAGE code, your top NAICS and PSC codes, any socioeconomic certifications, and contact details. This is what lets them verify and reach you.
Keep it to one page.
One page is the convention for a reason: contracting officers screen many vendors fast and won't read a brochure during first contact. A single page forces you to lead with your strongest qualifications and drop the filler.
Make it skimmable — clear headers, short lines, the company data easy to find. The goal isn't to say everything; it's to say enough that the right buyer keeps reading.
Aim it at work you can win.
A capability statement only works when it's pointed at real demand — the NAICS codes, agencies, and contract types where you actually have a shot. Generic statements get ignored.
Sell to State shows you that demand. Search government tenders in plain English, see which agencies buy what you sell and who's won before, and sharpen your core competencies and differentiators against what buyers are actually purchasing.
Keep going
Get contract-ready
- SAM.gov registration — Register and get the UEI and CAGE code your statement needs
- UEI lookup — Find and verify a Unique Entity ID on SAM.gov
- Find tenders — See the real demand your statement should target
- Tender alerts — Get notified the moment a matching contract posts
- Government procurement software — How the full discovery stack fits together
Frequently asked questions
What is a capability statement?
A capability statement is a concise, usually one-page document that summarizes what a business does for government buyers. It functions as a federal seller's resume: core competencies, past performance, differentiators, and the company data (UEI, CAGE, NAICS codes, certifications) a contracting officer needs to evaluate and contact you.
What should a capability statement include?
By common convention: core competencies (what you do best), past performance (recent relevant contracts), differentiators (why you over competitors), and company data — your UEI, CAGE code, top NAICS/PSC codes, socioeconomic certifications, and contact information. There is no single government-mandated form, but contracting officers expect these elements.
How long should a capability statement be?
One page is the widely-recommended length. Contracting officers scan many vendors quickly during initial screening, so a single page forces you to prioritize your strongest qualifications and cut filler. Keep it skimmable.
What company data goes on a capability statement?
Your Unique Entity ID (UEI) and CAGE code from SAM.gov, your top NAICS and PSC codes, any socioeconomic certifications (such as small business, 8(a), HUBZone, SDVOSB, or WOSB where applicable), and how to reach you. The DUNS number is no longer used — it was replaced by the UEI in 2022.
Do I need a SAM registration before I write a capability statement?
Effectively yes — your capability statement should carry your UEI and CAGE code, and those come from SAM.gov registration. Register first so the IDs on your statement are real and verifiable, then build the statement around them.
How does Sell to State help me write a stronger capability statement?
A strong statement is targeted at the work you can win. Sell to State helps you see which NAICS codes and agencies match your business, who's won similar contracts before, and what those buyers actually purchase — so your core competencies and differentiators speak to real demand rather than guesses.
Find the tender before your competitor does.
Free to browse the entity graph across 194 countries. One subscription unlocks the full dataset, the API, the CLI and the MCP server.