Writing a capability statement that gets read

A capability statement is a one-page PDF that answers, for a stranger with thirty seconds, three questions: what do you do, why you rather than someone else, and can I actually buy from you.

It is not a brochure. It is not a pitch deck. It is a reference document that gets skimmed once and then filed, and its job is to be findable and usable six months later when someone at that agency has a requirement and is trying to remember who does this.

Almost every bad capability statement fails the same way: it is written as marketing, aimed at nobody in particular, and it says things every competitor could also say.

Who reads it and why

• Contracting officers and contract specialists, during market research, deciding whether enough small businesses exist to justify a set-aside.
• Small business specialists and OSDBU staff, whose actual job is to connect capable small firms to requirements inside their agency.
• Program and technical staff, who describe what they need and are asked whether anyone can do it.
• Prime contractors, looking for subcontractors who fill a capability gap or a subcontracting-goal category.

None of these people are browsing. All of them are looking for a specific thing. Write for retrieval, not for persuasion.

The four blocks

1. Core competencies

Three to six bullets describing what you do, in the customer's vocabulary rather than yours.

The test: could a contracting officer read this and know which NAICS codes you belong under? If your bullet is "innovative technology solutions," the answer is no, and the document has already failed.

Weak: Cutting-edge IT services and digital transformation.

Better: Microsoft 365 and Azure tenant migrations for organisations of 100–2,000 users, including hybrid Exchange cutover, mailbox remediation, and post-migration support.

The second one is longer and it is better, because it is retrievable. Someone who needs exactly that will find it.

2. Differentiators

This is the block that separates a useful capability statement from the other ninety on the pile, and it is the one that is almost always wrong.

A differentiator is something a competitor cannot also claim. Apply that test ruthlessly:

• "Committed to quality" — every competitor claims this. Not a differentiator.
• "Responsive customer service" — same.
• "Experienced team" — same.
• "Cleared staff at Top Secret/SCI with polygraph, currently on contract at [agency]" — a competitor either has this or does not.
• "ISO 9001:2015 and CMMI-DEV Level 3 appraised" — verifiable, binary.
• "Completed 14 tenant migrations totalling 31,000 seats in the last 36 months, average cutover downtime under 4 hours" — specific, quantified, checkable.
• "Within 25 miles of the installation; two-hour on-site response" — geography is a real differentiator on many requirements.

If you cannot fill this block with things that pass the test, that is genuinely useful information about your market position — and better learned here than after losing five bids.

3. Past performance

Three to five relevant contracts. For each: customer, a one-line description of the work, contract value, period of performance, and a contact if you have permission to list one.

Lead with federal work if you have it. If you do not, lead with the work most relevant in size, scope and complexity to what you are chasing — that is the language evaluations use, so use it back. Commercial and state/local work counts more than new contractors assume when it is presented against those criteria. See building past performance.

Do not list a customer you cannot describe accurately, and do not list a reference who has not agreed to be one.

4. Company data

The block that makes you buyable. Put it where it can be found without reading a sentence:

• Legal business name and DBA
• UEI and CAGE code
• NAICS codes — primary first
• Socio-economic status — small business, 8(a), WOSB/EDWOSB, HUBZone, SDVOSB, and certification dates
• Contract vehicles you hold (GSA MAS schedule number, any IDIQs, BPAs)
• Bonding capacity, if you are in construction
• Clearance level, if relevant
• Point of contact: name, title, phone, email
• Website and physical address

Missing UEI and CAGE is the single most common defect. It signals — often correctly — that the company is not registered and cannot be awarded anything.

Format

One page. Two only if you are in construction with a substantial project list, and even then, page two is the project list and nothing else.

PDF, named so it survives a download folder: CompanyName_Capability_Statement_2026.pdf, not capstate_final_v3.pdf.

Readable at a glance. Real headings, real white space, 10pt minimum. It will be printed, emailed, and viewed on a phone.

Company data block visually distinct — sidebar or footer, so a reader can find your UEI without reading prose.

Dated. A capability statement with no date is assumed stale.

Tailor it, and use it as an opener

Keep one master version, then produce agency-specific variants for the three to five agencies you are actually targeting. Change the past performance you lead with, foreground the competencies that match that agency's buying pattern, and use their terminology. Ten minutes of work, and it is visible.

Research what the agency actually buys before you tailor — browse by agency to see current requirements and the NAICS codes they buy most under.

Then send it with a purpose. A capability statement attached to an email that says "please keep us in mind" produces nothing. Attached to a specific, short message — we saw you have recurring requirements in NAICS 541512; we have done this work at three comparable agencies; is there a sources sought or industry day coming up we should respond to? — it produces replies, because you have asked a question a small business specialist can actually answer.

The common failures, in order of frequency

1. No UEI or CAGE. Instantly signals you are not registered.
2. Differentiators that are not differentiators. Everyone is committed to excellence.
3. Marketing voice. Nobody in a procurement office is moved by "leveraging synergies."
4. Too long. Three pages is a document nobody reads to the end of.
5. Generic — one version for everybody. Visible immediately.
6. No date.
7. Stock photography and heavy graphics. It reduces the information density of a document whose only job is information density.

---

ContractBeam aggregates public federal opportunity data. This guide is general business advice. Certification claims on a capability statement should reflect current, verifiable status — misrepresenting size or socio-economic status is a serious matter.