If you're chasing federal contracts, your capability statement is the most important single page you will ever produce. It's what contracting officers, prime contractors, and small business specialists look at to decide whether to invite you to bid, add you to a teaming arrangement, or skip you entirely. Most are bad. The good ones take maybe two hours to write and pay for themselves on the first contract they unlock.
This guide explains exactly what belongs on a capability statement, gives you a template you can adapt today, and walks through the most common mistakes that get small businesses ignored.
A capability statement is a one-page summary of your business formatted for federal contracting officers. It tells them, in under two minutes of skim time, what you do, who you've done it for, why you're different, and how to reach you. It is not a brochure, not a marketing flyer, and not a corporate "About" page. It's a vendor evaluation tool.
Contracting officers receive dozens of these every week. They read the headline, scan the bullets, and either save the document to a "consider" pile or hit delete. Your job is to make the "consider" pile decision happen on a six-second skim.
Federal contracting moves on volume. A small business specialist at a single agency may receive several hundred capability statements per quarter. The one-page convention exists so they can build a usable shortlist without reading a stack of brochures. A two-page statement signals you don't understand the medium. Treat the one-page constraint as a forcing function for clarity.
The header. Company name, logo, one-sentence description of what you do, your UEI (formerly DUNS), CAGE code, and primary contact. Two lines maximum.
A bulleted list of 5–8 specific capabilities. Use the CO's language, not yours: "cybersecurity assessment and authorization" beats "cyber stuff." Each bullet should map to a real NAICS code you've registered.
2–4 specific contracts you've delivered. For each: customer name (or "Federal civilian agency" if confidentiality applies), period of performance, contract value, brief scope, and outcome. If you've never had a federal contract, use commercial work and label it accurately.
3–5 things that genuinely set you apart. Not "we care about quality" — every contractor says that. Real differentiators look like "FedRAMP-authorized SaaS platform," "all engineers hold active TS/SCI clearances," or "average 11-year tenure on contract leadership." If a competitor could honestly write the same line, it's not a differentiator.
List your formal certifications: 8(a), HUBZone, WOSB/EDWOSB, SDVOSB, ISO 9001, CMMI Level 3, FedRAMP, etc. Use the official acronyms. If you don't have any, omit this section rather than padding it.
List your primary code first, then your top secondary codes. Don't list all 15. Pick the 5–8 that matter for the audience you're targeting. If you're sending the statement to a Navy small business specialist, your DoD-relevant codes go first.
One line: "Brennan Sweeney, Founder & CEO — 12 years experience, federal contracting since 2018, M.S. in Computer Science." Resumes belong in proposals, not capability statements.
Phone, email, website, and a single sentence CTA: "Contact us to discuss small business set-asides under [NAICS]." Make it impossible to miss.
[YOUR COMPANY NAME]
[One-sentence description of what you do for the federal government]
UEI: [12-character ID] · CAGE: [5-character code] · DUNS: [legacy, optional]
[primary contact name] · [phone] · [email] · [website]
• [Competency 1 — use CO language]
• [Competency 2]
• [Competency 3]
• [Competency 4]
• [Competency 5]
[Customer] — [contract name or scope], [period of performance], [value]. [One sentence on outcome.]
[Customer] — [contract name or scope], [period of performance], [value]. [One sentence on outcome.]
[Customer] — [contract name or scope], [period of performance], [value]. [One sentence on outcome.]
• [Specific, verifiable advantage 1]
• [Specific, verifiable advantage 2]
• [Specific, verifiable advantage 3]
[8(a) / HUBZone / WOSB / SDVOSB / ISO 9001 / CMMI / FedRAMP / etc.]
Primary: [code] — [title]
Secondary: [code], [code], [code], [code]
To discuss a current opportunity or add us to your vendor list, contact [name] at [phone] or [email].
A one-page summary of your business that federal contracting officers use to decide whether to consider you for a contract. It includes core competencies, past performance, differentiators, certifications, NAICS codes, and contact information.
One page. Federal contracting officers receive dozens per week and won't read longer documents during initial vendor evaluation. If you can't fit your story on one page, tighten it.
Eight elements: company snapshot, core competencies, past performance, differentiators, certifications/set-asides, NAICS codes, key personnel, and a call to action with contact information.
No. SAM.gov registration doesn't require one. But you do need a capability statement to be taken seriously by contracting officers and primes once your registration is active.
Both. The PDF is what you attach to emails and upload to vendor portals. The webpage is what a CO finds when they search for your business name online. You need both.
Get AI-curated SAM.gov opportunities delivered every weekday at 6 AM ET — filtered by set-aside type and NAICS code.
Subscribe FreeRelated reading: NAICS Codes for Government Contracting · SAM.gov Registration Guide · Federal Set-Aside Programs Explained