A capability statement is a one-page document that summarizes who your firm is, what it does, and why a federal agency should care. It is the most widely requested piece of collateral in federal small business BD, and the vast majority of them are useless.

Not useless in the sense of containing false information. Useless in the sense that they tell a contracting officer or small business specialist nothing they could not find by pulling your SAM.gov registration. Company name, CAGE code, NAICS codes, SDVOSB status — this is not differentiation. It is registration data.

The capability statement that earns a second conversation does something different. It answers, quickly and specifically, the question every contracting officer is actually asking: "Can this firm solve the problem I have, and do they have proof?"

What goes on the page and in what order

A capability statement has one page to work with. There is no room for padding, mission statements about "delivering excellence," or corporate values that every other firm on the planet also claims to have. Every line must carry weight.

Core competencies — lead with what you actually do. Not your industry category. Not your NAICS codes. The specific services or solutions you deliver. If you do cybersecurity, say exactly what kind: penetration testing, CMMC compliance implementation, cloud security architecture for FedRAMP environments. Specificity here is the first filter. A contracting officer with a specific requirement is scanning for a match. If your competencies are generic, you are invisible.

Limit yourself to four or five competencies. More than that and none of them read as genuine specialization. If your firm does ten different things, you need different versions of this document for different audiences.

Past performance — proof that you have done it before. List three to five contracts. For each one include: the agency name, the contract type and dollar value, the NAICS code if relevant, and one sentence describing what was delivered and what the outcome was. Contract numbers are optional but credible. CPARS ratings, if strong, can be noted.

The mistake most firms make here is listing contracts without context. "USAF IT Services, $2.3M" tells the reader almost nothing. "U.S. Air Force, $2.3M — Deployed zero-trust network architecture across three installations, completing 14 months ahead of schedule" tells them what you did and that you did it well.

Differentiators — why you specifically. Three bullet points that answer the question a busy contracting officer asks before they agree to a meeting: what makes this firm different from the other SDVOSB with the same NAICS code? Your differentiators should be specific, verifiable, and genuinely rare. "Deep federal experience" is not a differentiator. "Four of our five senior engineers hold active TS/SCI clearances with CI polygraph" is a differentiator. "Certified CMMC Third Party Assessment Organization (C3PAO)" is a differentiator.

If you cannot identify three genuine differentiators, that is a BD signal worth taking seriously. It does not mean you cannot win contracts. It means you need to be more deliberate about which contracts to target.

Company data — the registration block. This goes last. CAGE code, UEI, NAICS codes, business size designation, SDVOSB certification, active SAM.gov registration. Contact information for a named person, not an info@ address. This section exists so the reader can act on the document without having to search anywhere else.

Format and design

One page. No exceptions. A two-page capability statement signals that the firm does not know how to communicate efficiently. That is not the impression you want to create with a source selection official.

Use a clean layout with clear section headings. Color is fine and can help with visual organization. Avoid stock imagery. If you use your logo, use it once. The document should be readable when printed in grayscale — many government offices still print.

Save and distribute as a PDF. Protect it from editing but not from printing or copying text — some contracting officers will paste your CAGE code or NAICS codes into their systems.

Version control matters: Maintain separate versions tailored to different agencies or requirement types. A capability statement you send to an Army IT acquisition office should emphasize different past performance than one you send to a civilian health IT program. One generic version sent everywhere is the second most common mistake, after writing it once and never updating it.
Digital tablet displaying an editable federal capability statement template
A well-structured capability statement maps your strengths directly to the evaluation criteria the contracting officer is scoring.

When and how to use it

A capability statement is not a cold outreach tool in isolation. It is a leave-behind. You bring it to agency industry days, OSDBU office meetings, and small business conferences. You attach it to Sources Sought responses. You include it in introductory emails after you have made a human connection — not instead of one.

The sequence that works: research the agency, identify a specific requirement or program, reach out to the small business office or program office with a specific question relevant to their work, attach the capability statement as supporting context. The statement supports the conversation. It does not replace it.

Cold emailing a capability statement to a general agency inbox produces approximately nothing. The document only does its job when the person reading it has a reason to care about your firm before they open it.

Common mistakes worth avoiding

Listing every NAICS code you have registered. This signals that you are trying to be eligible for everything rather than expert in anything. List the three to five codes that represent your actual work.

Using classified contracts as past performance. You can note that you have classified program experience if you hold relevant clearances, but you cannot detail classified contracts. Leaving a vague reference to "classified programs" without any context is generally less useful than a concrete unclassified example.

Not updating it. A capability statement with a contract from 2019 as the most recent past performance and no contracts since 2021 raises questions. Update it every time you complete a significant contract or add a meaningful capability.

Putting your SDVOSB status in the headline. Your set-aside status is important data but it is not a differentiator in the context of a set-aside procurement where every bidder is SDVOSB. Lead with what you do, not what you are.

The test

Before you finalize any version of this document, apply this test: hand it to someone who does not know your firm and ask them to tell you, in one sentence, what your company does and why an agency would choose you over a competitor. If they cannot answer both parts of that question from the document alone, revise it.

The capability statement is not a marketing document. It is a qualification document. It exists to answer one question — can you do what I need — quickly enough that a contracting officer who is reading ten of them in an afternoon reaches yours and thinks: this one is worth a conversation.