Writing a Capability Statement That Actually Gets Read

A capability statement is not a brochure. It is a one-page answer to a specific question a buyer is asking: if I need this thing, can these people do it, and can I verify that quickly?

It gets about twenty seconds. Build for twenty seconds.

The four blocks

1. Core competencies. What you do, in the buyer's vocabulary, not yours. If they buy "instructor-led workforce training," do not write "transformational learning journeys." Three to six items, each one a phrase rather than a paragraph.

2. Differentiators. The hardest block, and the one most people fill with adjectives. A differentiator is something a competitor cannot honestly write on their own page. Certifications, a method you actually use, a credential, response time you can commit to, a niche you genuinely dominate. "Committed to excellence" is not a differentiator. Neither is "customer focused."

3. Past performance. Two to four engagements: who, what, when, and the outcome in one line. Real ones only. If you are new, name what you have delivered in another context and describe it accurately rather than inflating it — the inflation is what gets caught, not the inexperience.

4. Company data. Legal name exactly as registered, DBA if you use one, Unique Entity ID, CAGE code if you have one, NAICS codes, certifications with their issuing bodies, insurance limits, physical address, one phone number, one email, one website. This is the block that makes you findable in a procurement system.

Rules that matter more than design

• One page. Non-negotiable.
• Legal name that matches your registrations. If it does not match SAM.gov or the state's vendor system, you look like a different company.
• NAICS codes visible. This is often literally what a buyer searches by.
• Only certifications you currently hold. An expired certification on a live document is the fastest way to lose credibility with the one audience that checks.
• A person's name and a direct phone number. Not "info@". The point is that someone can call you.

Make versions

One general version, and then one per market you actually sell to. A school district and a state agency are buying different things and using different words for them. The company data block stays identical; the competencies and past performance get reordered so the relevant items are at the top. This takes fifteen minutes per version and noticeably improves response rates.

The version you email should be a PDF named for your company and the date. Buyers save these to a folder. Make yours findable in six weeks.

What it is for

Attach it to introductions. Bring it to matchmaking events. Send it when a buyer says "send me something." Include it in bids where the solicitation allows supporting documents. It is not a proposal and it will not win a contract on its own — its whole job is to get you into the small group of vendors someone remembers when a need appears.

The test

Hand it to someone who does not know your business. Give them twenty seconds. Then ask them what you do and who you have done it for. If they cannot answer both, the page is not finished — and the fix is almost always removing things, not adding them.

Questions people ask

How long should a capability statement be?
One page. Two is a brochure and it will not be read. If you cannot fit it, you are describing what you could do instead of what you have done.

What has to be on it?
Core competencies, differentiators, past performance, and company data: legal name, UEI, CAGE code if you have one, NAICS codes, certifications, contact information, and address.

Should I send it as a PDF or a Word file?
PDF, so the layout survives. Name the file with your company name and the date so it is findable in a buyer's downloads folder six weeks later.

How often should I update it?
Every time you finish a project worth citing, and any time a certification, insurance limit, or contact detail changes. A stale statement with an expired certification date does more damage than no statement.