GovCon Academy · Intermediate
The Capability Statement
8 min read
What it is — and why it matters
A capability statement is a one-page (sometimes two) marketing document that tells a government buyer or prime contractor who you are, what you do, and why you're worth a conversation. It is the single most-requested document in early GovCon relationships — you'll attach it to sources-sought responses, hand it out at industry days, and email it to small-business specialists.
Think of it as a resume for your business, written for a reader who has 30 seconds and a specific need. Clarity beats cleverness every time.
The sections it should include
Company overview
A 2–3 sentence description of who you are and what you do — plainly. Lead with your core service, not your history.
Core competencies
A short, scannable list of what you actually deliver. Use the language agencies use (map it to your NAICS/PSC codes).
Differentiators
Why you over the next vendor: certifications, clearances, past performance, proprietary methods, geography, surge capacity.
Past performance
A few relevant contracts or projects — customer, scope, value range, outcome. Commercial and subcontract work counts when you are new.
Company data
UEI, CAGE code, primary and secondary NAICS codes, socio-economic certifications (SDVOSB, 8(a), WOSB, HUBZone), DUNS is retired.
Contact block
A named point of contact, email, phone, and website. Make it effortless to reach a human.
What separates a strong one
- ✓ One page. If it runs to three, you haven’t prioritized.
- ✓ Tailored per opportunity — swap the core competencies and past performance to match the agency’s need.
- ✓ Keyword-aligned to the NAICS/PSC codes and terms in the notice, so it reads as “on target.”
- ✓ Concrete past performance (customer, scope, value, result) beats adjectives.
- ✓ Clean, readable design — the buyer should find your UEI, CAGE, and set-asides in seconds.
Common mistakes to avoid
- ✕ A generic statement sent to every agency unchanged.
- ✕ Burying your certifications and codes in a wall of text.
- ✕ Listing services you can’t actually staff or deliver.
- ✕ No named contact — “info@” with no human is a red flag.
- ✕ Claiming or implying a government endorsement you don’t have.
Put it into practice
Grab the capability-statement template in the resource library, then — on GovCon Professional — request a human review before you send it out.