How to Build a Capability Statement That Actually Wins Contracts
Your capability statement is the one-page sales sheet contracting officers screen before they ever open your proposal. Get it wrong and you're filtered out before the conversation starts. Here's how to build one that gets you in the room.
What a capability statement actually is
A capability statement is a one-page (occasionally two-page) PDF that tells a federal, state, or local buyer who you are, what you do, who you've done it for, and how to reach you. It is not a brochure, not a resume, and not a proposal. It exists so a contracting officer can decide in 30 seconds whether to keep reading.
The six sections every capability statement needs
Core competencies
A focused list of what you actually deliver — written in the buyer's language, not your internal jargon. Five to eight bullets, each tied to a NAICS or PSC code you can support with past performance.
Past performance
Three to five recent, relevant contracts. Each one names the customer, period of performance, contract value, and the outcome — not just the scope. Quantify results: dollars saved, uptime, on-time delivery, awards.
Differentiators
Why you, not the incumbent? Certifications, clearances, proprietary methods, response times, geographic coverage, niche tools. Cut anything every competitor also has — generic isn't a differentiator.
Corporate data
UEI, CAGE code, DUNS (if still listed), primary and secondary NAICS, socioeconomic certifications (8(a), WOSB, HUBZone, SDVOSB, MBE), bonding capacity, accepted contract vehicles (GSA, SEWP, OASIS).
Key personnel (optional)
For service businesses, name one or two principals with credentials. For product or trades businesses, skip it and use that space for a stronger past-performance block.
Branded contact block
Logo, primary contact name, title, phone, email, website, physical address. Same fonts and colors as your proposals — your capability statement is a sales tool, not an org chart.
A step-by-step build process
Gather your inputs in one place
Pull every artifact you'll need before you start writing: SAM.gov registration, certifications, last three years of contracts, customer references, financial summary, logo files. Putting them in one capability vault now saves rebuilding the statement every six months.
Write core competencies to the buyer, not the mirror
Open a recent solicitation in your target market and read how the agency describes the work. Mirror that language in your competencies. If the buyer says 'environmental remediation' and you say 'green services,' you lose the keyword match in their screening tools.
Quantify past performance
Replace every adjective with a number. 'Large federal contract' becomes '$2.4M, 18-month task order, 99.2% on-time delivery.' Numbers are the only thing a contracting officer can defend to their reviewer.
Sharpen differentiators against the incumbent
Pick the top one or two opportunities you're chasing and ask: what does the incumbent do badly? Build your differentiators against those weak spots. A capability statement aimed at everyone wins nothing.
Format on one page, two only if you must
Two columns, header band with logo and contact, body split between competencies/past performance/differentiators, footer with corporate data. PDF only. Buyers print these. Filename: CompanyName_Capability_Statement_v2026.pdf.
Version it and keep it current in your vault
A capability statement is a living document. Update it every quarter — new contract awards, new certifications, fresh numbers. Store every version in your capability vault so the latest is always the one going out the door with a proposal.
Mistakes that get small businesses screened out
- Generic bullets like 'high quality' and 'customer focused' — every competitor wrote the same thing.
- Missing UEI, CAGE, or primary NAICS — the buyer can't validate you and moves on.
- Past performance without numbers, dates, or customer names — unverifiable equals unbelievable.
- Three pages of dense paragraphs — buyers skim, they don't read.
- Stale stats from a contract that ended four years ago — currency is credibility.
- Different fonts and colors than your proposals — the brand mismatch reads as amateur.
Store it where every proposal can pull from it
BidCommand's capability vault keeps your statement, past performance write-ups, certifications, and key personnel bios in one approved library — so the latest version goes out with every proposal, and updates happen in one place.
Start free