The federal capability statement, built backward from the reader

A capability statement is the one-page document that decides whether a contracting officer or a prime keeps reading or moves on. Most small contractors treat it as a brochure. It is not a brochure. It is a targeting document, and the ones that work are built backward from a specific reader with a specific decision to make.

What a capability statement is for

It exists to answer, in about ten seconds, three questions for the person holding it: what does this company do, can they do it for me specifically, and how do I act on that. Everything that does not serve those three questions is taking up space that should be serving them. The generic capability statement that lists every service the company has ever performed answers none of them well.

The blocks that have to be there

Core competencies. Not a list of everything. The three to six things you want this reader to associate with your name, written in the language the reader uses — which for federal work means the language of the NAICS codes and the work statements they buy against, not your internal marketing terms.

Differentiators. Why you and not the other small business with the same NAICS codes. A clearance you hold, a contract vehicle you are on, a certification, a past performance profile in exactly this domain. If your differentiator could be claimed verbatim by any competitor, it is not a differentiator.

Past performance. Two to four relevant contracts with the customer, the scope, the period, the value, and your role. Relevance to the reader beats impressiveness in the abstract — a $2M contract doing exactly their work beats a $50M contract doing something adjacent. This is the same selection discipline as a full proposal, just compressed.

Company data. UEI, CAGE code, NAICS and PSC codes, socioeconomic certifications (8(a), SDVOSB, WOSB, HUBZone), DUNS-era identifiers where still referenced, accepted payment vehicles, point of contact. This is the block that lets a contracting officer actually act, and the block most often left incomplete.

Where they go wrong

The first failure is one statement for every reader. A capability statement aimed at a prime looking for a subcontractor is a different document than one aimed at a contracting officer considering a sole-source set-aside. Same company, different targeting. Maintain a base and tailor the core competencies and past performance to the reader.

The second failure is verbosity. If it does not fit on one page and survive a ten-second skim, it has failed at its actual job. The reader is not going to read paragraphs. They are going to scan for fit.

The third failure is stale data. A CAGE code that points to an old address, a certification that lapsed, a point of contact who left. The data block is the part the reader trusts to act on; if it is wrong, you do not get the call.

How it connects to the rest of the pursuit

A good capability statement is downstream of knowing your own past performance cold — the same evidence base that feeds your proposals. The companies that keep this current as a living asset, rather than rebuilding it in a panic the night before a match-making event, are the ones that look ready when an opportunity appears. The discipline that produces a sharp capability statement is the same discipline that produces a responsive proposal: know your relevant past performance, write to a specific reader, and keep the data clean. If you want to see how that evidence base feeds an actual pursuit, start with the RFP shred and the ten-stage workflow that reads from it.