Capability statements: what they are and a simple outline

A capability statement is a one-page summary of what your business does, what it has done before, and why a government buyer should trust it with real work. It is not required by law, and plenty of small contracts get won without one, but it is one of the fastest ways to look credible to a contracting officer who has never heard of your business, and it becomes close to essential once you are bidding on anything larger or more competitive than a routine, small, local job.

Think of it as the single document you can hand, email, or attach to anyone who asks "what does your company do and why should we trust you with this," a question that comes up constantly in government contracting outside of the formal bid process itself, at a networking event, in a cold email to a contracting officer, or in a conversation with a prime contractor sizing up potential subcontractors.

What a capability statement actually is

Think of it as a resume for your business, not a brochure. A contracting officer or a prime contractor looking for a subcontractor should be able to read it in under a minute and walk away knowing exactly what you do, what you have already done for a government (or comparable) client, and how to reach you. It is not the place for marketing language or a long company history. It is the place for specific, verifiable facts.

Why it matters even for a small, informal bid

Even when a listing does not explicitly ask for one, having a capability statement ready signals that you have done this before, or at least prepared properly. It gives you something concrete to attach to an email introducing your business to a contracting officer, or to hand to a prime contractor looking for small business subcontractors to round out their own team, which is a real, separate path into government work worth knowing about. Prime contractors on large awards are frequently required to subcontract a share of the work to small businesses, and they are actively looking for exactly this kind of one-page introduction, often well before a specific subcontracting opportunity even exists, so having a capability statement ready ahead of time is what lets you actually respond when one comes up.

A simple one-page outline

• Core competencies. A short, specific list of what you do (not a paragraph of marketing copy). Three to six bullet points is plenty.
• Differentiators. What makes your business a better choice than the next bidder, stated as fact, not superlative. Certifications, response time, a specialty piece of equipment, a track record in a specific niche.
• Past performance. Two to four real, specific examples: the client (government or comparable private-sector, if you have no government history yet), the scope, and the outcome. Specific numbers (square footage, contract value, duration) read as more credible than vague claims.
• Corporate data. Your business's legal name, SAM.gov unique entity ID, CAGE code, relevant NAICS codes, and any small business certifications (set-aside categories you qualify for), kept current as your registration changes.
• Contact information. A real name, phone number, and email, not just a general company inbox.

What not to put in one

Skip generic mission statements, stock photography, and anything that reads like it was written for a website rather than a specific, skeptical reader who is deciding whether to trust you with real money. Do not overstate past performance either; a contracting officer who checks a claimed reference and finds it does not hold up will remember that far longer than a modest, accurate one. A short, honest, accurate document beats a padded, impressive-sounding one every single time, especially with a reader who has seen a lot of both.

Keep it current

A capability statement built once and never updated goes stale fast, especially the past performance section. Revisit it every time you complete a new contract worth including, and every time your certifications or NAICS codes change. A one-page document that still lists your very first small job three years after you have completed a dozen larger ones undersells you.

Format matters less than accuracy

Do not spend hours agonizing over the design. A clean, well-organized one-page PDF using your logo and basic brand colors is entirely sufficient; contracting officers are reading for information, not evaluating your graphic design. What matters far more is that every claim on the page is accurate and specific enough to survive a follow-up question. A vague capability statement full of unverifiable claims does more harm than a plain, honest, specific one.

If you do not have a website yet either, read our take on whether you actually need one before assuming a capability statement alone is not enough. Otherwise, browse live opportunities by field and start putting your capability statement to use.