A capability statement is often the first thing a contracting officer, or a prime contractor's small business liaison, sees from you. It's one page, sometimes two, and it gets read fast. Usually that happens at an industry day, after a matchmaking session or when someone is building a list of companies to invite to bid. Most of the ones we see read like a brochure. Our read is that a capability statement works best when it answers one question. Why should this agency, or this prime, put you on the list?
Who reads a capability statement
There are mostly three kinds of readers. Contracting officers and specialists who are doing market research before a solicitation goes out. Small business specialists at agencies who match companies to opportunities. And business development leads at larger prime contractors who need subcontractors to fill a gap on a bid.
None of them have much time. They're scanning for fit. Can you do the work they need? Have you done it before? Are you set up to be paid by the government? A page that answers those three questions in under a minute does its job.
What goes on it
The core sections are close to standard, and readers expect to find them in roughly the same places.
Core competencies. What you do, stated as the work the government buys. Use the language agencies use in their own solicitations rather than your internal service names. Four to six lines is plenty.
Past performance. Two or three contracts or projects that look like the work this reader buys. Name the agency or client, what you delivered and the size if you can share it. If you're new to government work, commercial projects count. Say what they were and why they're relevant.
Differentiators. What makes you the safer or better choice. This is where most statements fall apart, because "quality," "integrity" and "customer focus" say nothing. A specific differentiator sounds like "cleared staff in the region," "a 24-hour emergency response crew" or "the same project manager from kickoff to closeout."
Company data. Your Unique Entity ID (UEI) from SAM.gov, your CAGE code, the NAICS codes you work under, any socioeconomic certifications like 8(a), HUBZone, women-owned or service-disabled veteran-owned, and any contract vehicles you hold. Contracting officers use this block to check that you can be awarded work. Make it easy to find.
Contact. One named person, a direct phone number and an email that someone answers.
What to cut
Mission statements. Long company history. A list of every service you've ever offered. Stock photos. Logos of clients you can't name with permission. Every line on the page should help a reader decide whether you belong on their list, and anything that doesn't is taking space from something that does.
Tailor it every time
The biggest mistake we see is one capability statement for every agency. The company data stays the same, but the competencies and past performance should change based on who's reading. A version for a defense facilities office and a version for a health agency's IT team should lead with different work.
Keep a master file, then cut a version for each agency or opportunity. It takes about an hour, and it changes how the whole page reads.
Design that helps a fast reader
A capability statement is read in seconds, so the layout does a lot of the work. Use clear section labels. Put the company data in a consistent block, often down one side. Leave enough white space that a reader can find past performance without hunting. Use your brand colors and logo with restraint. Save it as a PDF small enough that it won't bounce off an email filter.
Our read is that a well-designed capability statement does one more thing. It signals that your proposals will be just as easy to read when the time comes, and contracting officers notice that.
A capability statement, before and after
Here's a typical case. A 30-person facilities maintenance company wants to get on the radar of a regional federal building office.
The first draft opened with a mission statement and a paragraph on the founder's story. Competencies were a list of 14 services, from HVAC to grounds work. The company data sat at the bottom in small type, and past performance was a strip of logos.
The rewrite led with four competencies written in the agency's own terms, like preventive maintenance for occupied federal buildings. Past performance became three short lines, each with the building type, the scope and the contract length. The differentiator was specific, an emergency response time already written into their existing contracts. The company data moved to a clean block on the right, with the UEI, CAGE code, NAICS codes and small business status where a reader looks first.
Same company, same work. The second page tells a contracting officer in under a minute whether to keep reading.
Questions we hear about capability statements
How long should a capability statement be?
One page is the norm. Two is fine if past performance needs the room. Anything longer stops being a capability statement and starts being a proposal nobody asked for.
Do I need a different one for each agency?
You should have a version for each type of buyer you pursue. The company data stays the same, while the competencies and past performance shift to match what that reader buys.
Where does a capability statement fit with a proposal?
It comes first. A capability statement gets you on the list. The proposal, once the solicitation comes out, is what wins the work. For that stage, see how to write a government RFP response evaluators can score and what to look for in government proposal writing services.
The short version
Write a capability statement for a reader who has a minute. Lead with the work they buy, prove it with two or three relevant jobs, make one specific differentiator clear and put your company data where they can check it fast. Then tailor it for each agency you pursue.
When the solicitation comes out and the bid matters, start a proposal or see how our Board build works on the pricing page.
