How to write a capability statement for government contracts
A capability statement is a one-page summary of what your company does for government buyers. Contracting officers and prime contractors ask for it at industry days, after a sources-sought notice, and before they add you to a list of suppliers. A good one is short, specific and written for the agency reading it.
The five sections
- Core competencies. Three to six services you are best at, in the buyer's words: "accessible website design and development (WCAG 2.2 AA)", "cloud migration to AWS GovCloud", not "digital excellence".
- Past performance. Two to four short projects with the client, what you delivered and a measurable result. Commercial and subcontract work count if you have no federal contracts yet.
- Differentiators. Why you rather than the next firm: a specialism, certifications, speed, security clearances, local presence, a tool or method.
- Company data. Unique Entity ID and CAGE code, NAICS codes (primary first), small business status and any SBA certifications (8(a), HUBZone, WOSB, SDVOSB), contract vehicles you hold, and accepted payment methods (for example the government purchase card).
- Contact. One named person, phone, e-mail and website.
Template for a digital or IT company
[Company name] — [one sentence: who you help and how, e.g. "We build accessible, secure websites and web applications for public agencies."]
Core competencies: [service 1] · [service 2] · [service 3] · [service 4]
Past performance
[Client] — [what you delivered], [year]. [Result: e.g. "page load time halved, WCAG 2.2 AA audit passed"].
[Client] — [what you delivered], [year]. [Result].
Differentiators: [e.g. in-house accessibility testing with assistive technology users; FedRAMP-authorised hosting; 48-hour response time]
Company data: UEI [ ] · CAGE [ ] · NAICS 541511 (primary), 541512, 541519 · Small business · [certifications] · Accepts government purchase card
Contact: [name, title] · [phone] · [e-mail] · [website]
For the right codes see NAICS codes for websites, software and IT; for the UEI and CAGE code, SAM.gov registration step by step.
Make it fit the agency
- Tailor it. Keep a master version and adjust the competencies and past performance for each agency or opportunity. Use the language of their mission and of the notice.
- One page, readable in a minute, as a PDF. Your logo and brand colours are fine; dense paragraphs are not.
- Evidence over adjectives. Numbers, named clients (with permission) and standards met.
- Send it with a reason: answering a sources-sought notice, following up an industry day, or introducing yourself to a small business specialist (OSDBU) or a prime contractor looking for subcontractors.
Common mistakes
- Listing every service you could possibly offer.
- Missing UEI, CAGE or NAICS codes — the first things a contracting officer looks for.
- Past performance with no result or no date.
- A generic statement sent to every agency.
Where it is used
Many federal buys start with a sources-sought notice or a request for information on SAM.gov: the agency checks whether enough small businesses can do the work before deciding on a set-aside. Answering with a tailored capability statement can shape the competition in your favour. See US set-asides for small businesses and how to win US federal contracts.
Brieflist lists open US federal opportunities for digital work every day: open US contracts. Pro e-mails new matches each morning, with a 7-day free trial.