How to Write a Capability Statement That Actually Wins Government Contracts
Short answer: A government contracting capability statement is a one-page document with four required sections: Core Competencies (what you do), Past Performance (contracts you’ve completed with full details), Differentiators (why you specifically), and Company Data (your UEI, CAGE code, NAICS, set-aside status, and contact info). Tailor it to each opportunity by reordering content so the most relevant past performance and competencies appear first.
A capability statement is basically your business’s one-page resume for the government. When a contracting officer is deciding who to consider, or when a prime contractor is looking for a subcontractor, this is the document that gets you in the door or gets you ignored. Most small businesses either don’t have one or have a bad one, which is honestly good news for you — a strong capability statement makes you stand out fast.
Here’s exactly what goes in one, what to leave out, and the mistakes I see kill them.
What a Capability Statement Is (and Isn’t)
It’s one page. Sometimes two, but one is better. It’s a focused snapshot of what your business does, who you’ve done it for, and why a government buyer should pick you.
It is not a brochure. It’s not your company history. It’s not a list of your values. Contracting officers skim these in about 15 seconds, and anything that isn’t directly useful to them is wasted space. Think dense and relevant, not pretty and vague.
The Sections That Have to Be There
A capability statement has a fairly standard structure, and you should follow it because that’s what contracting officers expect to see. When something’s in the format they’re used to, they find what they need fast.
Core Competencies. A short, scannable list of what you actually do. Not paragraphs — bullet points or short phrases. If you do IT managed services, say “IT managed services, network security, help desk support,” not three sentences about your commitment to excellence.
Past Performance. The contracts you’ve completed that prove you can do the work. Include the customer, a one-line description, and ideally the contract value and dates. This is the single most important section, and it’s where most weak statements fall apart. We go deep on this in the past performance guide — it matters that much.
Differentiators. Why you, specifically, over the other businesses that do similar work. Certifications, specialized equipment, security clearances, a niche specialty, geographic coverage. This is your “so what” section. Be concrete: “Only firm in the region with X certification” beats “We provide superior quality.”
Company Data. The practical stuff a contracting officer needs to actually do business with you: your UEI, CAGE code, NAICS codes, business size and set-aside status (small business, WOSB, SDVOSB, HUBZone, 8a, whatever applies), and contact info. If you’re not sure about your codes, the NAICS and PSC guide covers how to pick them.
The Mistakes That Get You Ignored
I’ve seen a lot of capability statements. The ones that don’t work usually make at least one of these mistakes.
Too generic. “We deliver innovative, customer-focused solutions.” That sentence describes every business on earth and tells a contracting officer nothing. Cut all of it. Say what you actually do.
No relevant past performance. Listing commercial work that has nothing to do with the contract, or worse, listing nothing. If you’re new and don’t have federal past performance yet, lead with relevant commercial work and be honest about it. There are ways to build past performance, which we cover in the past performance guide.
Wrong codes or missing codes. If your NAICS codes don’t match the work, or your UEI and CAGE code aren’t there, you look like you don’t know what you’re doing. These details signal whether you’re a serious contractor.
Two pages of fluff. The longer it is, the less likely it gets read. One dense, relevant page beats two pages of padding every time.
One generic version for everything. The best capability statements get tailored. If you’re going after Department of Defense work, your DoD-relevant past performance goes up top. We get into why DoD is different in the DoD contracting guide. Sending the same generic statement to every opportunity is a missed chance to look like the obvious fit.
How to Actually Tailor It
This is where capability statements go from “fine” to “winning.” You don’t need a totally different document for every opportunity, but you should adjust the emphasis.
Read the opportunity. What does the buyer care about most? Reorder your core competencies and past performance so the most relevant stuff is first. If the contract is for cybersecurity work, your cyber past performance and any relevant certs should be the first thing they see, not buried at the bottom.
Match their language. If the solicitation uses specific terms, use those same terms in your statement (when they honestly apply to you). Contracting officers scan for the words that match what they’re buying.
It takes 15 minutes to tailor a statement per opportunity, and it dramatically improves your odds. Most businesses don’t bother, which is exactly why doing it makes you stand out.
Where to Use Your Capability Statement
A capability statement isn’t just for formal bids. Use it:
– Attached to bid submissions where the solicitation asks for one
– In your outreach to prime contractors when you’re pitching to be a subcontractor
– At matchmaking events and industry days
– Emailed to contracting officers after a “sources sought” notice
– On the capability statement field in your SAM.gov profile
The subcontracting use is underrated. Primes are constantly looking for qualified small-business partners, especially set-aside-eligible ones, and a sharp capability statement is how you get on their radar. We cover that path in [how to find government bids.
How SAMstream Helps
Writing a capability statement from scratch, and then tailoring it for each opportunity, is exactly the kind of repetitive document work that eats your time. SAMstream’s document generation builds capability statements formatted the way contracting officers expect, pulls in your past performance, and tailors the emphasis to the specific solicitation you’re targeting. What used to be a half-day of formatting and rewriting becomes a few minutes of review and tweaks.
The Archive Search side helps too: before you tailor a statement for a specific buyer, you can see what that agency has awarded before and what the winners looked like, so you know which of your differentiators to lead with.
FAQ
How long should a capability statement be?
One page is ideal. Two at most. Shorter and denser beats long and padded.
Do I need past performance to have a capability statement?
It’s much stronger with it, but if you’re new, lead with relevant commercial experience. Don’t fabricate federal past performance — contracting officers verify it.
What’s the difference between a capability statement and a proposal?
A capability statement is a one-page overview used to get considered. A proposal is the full response to a specific solicitation. The capability statement gets you in the room; the proposal wins the contract.
Should I have different versions?
You should tailor the emphasis per opportunity. You don’t need a completely different document each time, but reordering to put the most relevant content first makes a real difference.
Where do I put my UEI and CAGE code?
In the company data section, usually along the bottom or in a sidebar. They should be easy to find.
Next Steps
If you don’t have a capability statement yet, build one this week using the four-section structure above. If you have one, pull it up and check it against the mistakes list — most statements have at least one of them.
To generate and tailor capability statements automatically, formatted the way contracting officers expect, start a free 7-day SAMstream trial. No payment up front, cancel anytime.