A federal capability statement is one page. One page that a contracting officer or BD manager will scan for about fifteen seconds before deciding whether to keep reading or file it.
Most of them don't survive those fifteen seconds. Not because the company can't do the work, but because the document fails to communicate that fact quickly.
Here's what actually goes on a cap statement that gets read.
Every effective capability statement has the same four elements. The order matters less than the clarity.
What you do. Not in marketing language — in the language of the work. "Custom software development for defense logistics systems" is useful. "Innovative technology solutions for a digital future" is not.
Aim for six to eight bullet points. Each one should be a real capability, specific enough that someone could evaluate whether it matches a requirement. Include relevant technologies, methodologies, security clearance levels if applicable, and domain expertise.
Bad: "Full-spectrum IT support and consulting"
Better: "DevSecOps pipeline implementation for AWS GovCloud-hosted applications"
Why you, specifically. This is the section most companies write wrong, usually because they haven't actually thought about what makes them different from the forty other small IT firms pursuing the same prime.
Real differentiators are specific and defensible. "Experienced team with a proven track record" is neither. Consider: cleared personnel, specific agency relationships, proprietary tools or processes, unusual domain expertise, geographic proximity to a key installation, or certifications that are genuinely hard to get.
Three to five bullet points. If you can't list three specific reasons why a prime should choose you over a comparable firm, you need to do more thinking before you do more marketing.
What you've done for the government before. Three to five examples, each with: the agency, the contract vehicle if applicable, a one-sentence description of the work, and the dollar value or period of performance.
If you're new to federal work, this is the hardest section. Your options: relevant commercial work with comparable complexity, subcontract performance you can reference (with the prime's permission), or — honestly — lead with your capabilities and differentiators and be upfront that you're building your federal past performance.
Don't pad this section with tangentially related work. Contracting officers can smell resume inflation.
This is the section that determines whether the document is useful at all. It must include:
Missing any of these is disqualifying. A contracting officer who wants to route your cap statement to a program office needs the CAGE code. A prime who wants to list you on a proposal needs your UEI. Put all of it on the page.
One page. That's the standard, and it's a real constraint, not a guideline. If your cap statement is two pages, primes won't read the second one. If it's three pages, you've told them something unflattering about your ability to communicate clearly.
Design matters modestly. It should look professional and be easy to scan — a clean layout, readable font size (no smaller than 10pt for body text), and your logo. It does not need to be a design showcase. A PDF with a clean column layout beats a cluttered attempt at visual branding.
Color is fine. Infographics are usually not — this isn't a pitch deck, it's a reference document.
No NAICS codes. Somehow this is still common. Without NAICS codes and the corresponding size standards, your document can't be used for anything that requires confirming your small business status.
Generic differentiators. "Commitment to excellence" and "customer-centric approach" aren't differentiators. They're the minimum expectations. Saying them out loud signals that you haven't identified what actually makes you different.
Past performance that doesn't match the target. If you're pursuing defense health IT work and your past performance section is all commercial retail projects, you're working against yourself. Lead with the most relevant experience, even if it's smaller.
Outdated contact information. A surprising number of cap statements circulate with dead email addresses or former employees listed as POCs. Review yours every six months.
No tailoring. The same cap statement for every pursuit is fine for general distribution, but for active teaming conversations, tailor the core competencies and differentiators to the specific opportunity. Two hours of work can substantially change how a prime evaluates your fit.
Usually nothing, immediately. Capability statements that go to generic BD inboxes are often read weeks later, if at all. The cap statement's job is to be useful when someone already interested in you wants to know more — not to generate interest on its own.
The most effective use of a cap statement is in an active teaming conversation: after you've connected with a BD manager, they ask you to send your cap statement, and you send one tailored to the opportunity they're pursuing. That's when it earns its place.
Sending unsolicited cap statements to cold contacts rarely works. The call or email comes first. The cap statement confirms what you said on the call.
A great capability statement matters most when you're already in a real BD conversation. PrimeFinder helps you identify primes actively winning in your space — so you're reaching out to people who have reason to care.
Get Charter Access — Free for 1 Year →