What is a capability statement for government contracting (and what should it include)?
Written by the team at Mansa Gov, a SAM.gov-registered small, minority-owned federal contractor (UEI G5CQFNE82EL7).
A capability statement is a one-page document that tells a federal buyer or prime contractor who you are, what you do, and why to pick you. It includes five blocks: core competencies, differentiators, relevant past performance, company data (UEI, CAGE, NAICS, certifications), and contact info. It's the single most-requested document in early federal business development.
Key takeaways
- A capability statement is a 30-second decision aid — not a brochure — that a prime forwards internally when deciding whether to add you to a team.
- It needs five blocks: core competencies, differentiators, past performance, company data (UEI, CAGE, NAICS), and a real contact.
- Keep it to one page, quantify outcomes, and tailor it to the specific agency or prime you're sending it to.
- Update it every time you win work or add a certification — a stale cap statement costs you opportunities you never hear about.
Why the capability statement matters more than a website
When a contracting officer or a prime's Small Business Liaison Officer asks "send me your cap statement," they're asking for a 30-second decision aid — not a brochure. It's the document that gets forwarded internally when someone decides whether to add you to a team. A vague or bloated cap statement quietly kills opportunities you never hear about.
What should a capability statement include? The five blocks
- Core competencies — 3–6 bullet points of what you actually do, in the buyer's language (use NAICS/PSC vocabulary, not marketing speak).
- Differentiators — why you over the next vendor. Quantify: certifications, clearances, tools, response time, niche expertise. "We do X" is weak; "We cut Y by Z%" is strong.
- Past performance — 2–4 relevant projects with client, scope, outcome, and value. Commercial work counts when you have no federal record yet — show you can deliver.
- Company data — legal name, UEI, CAGE code, NAICS codes, socioeconomic designations (small, minority-owned, WOSB, HUBZone, etc.). You get your UEI and CAGE by registering on SAM.gov.
- Contact — a real person, direct email, phone. Not "info@".
What a great capability statement does differently
- One page. Always. Two pages signals you can't prioritize.
- Buyer-specific. Tailor the competencies and past performance to the agency or prime you're sending it to. A generic cap statement reads as generic capability.
- Quantified. Numbers survive the forward-to-the-decision-maker test; adjectives don't.
- Visually scannable. Headers, bullets, your logo, and company data in a sidebar. The reader spends 20 seconds — design for the skim.
Common capability statement mistakes
- Listing every NAICS you registered instead of the 3–5 that fit the buyer.
- Burying your UEI/CAGE — primes need it to add you to a proposal.
- Past performance with no outcomes ("provided IT services") instead of results ("migrated 12 legacy SQL databases, zero downtime").
- Treating it as static. Update it every time you win work or add a certification.
How often should you update it?
Every new contract, certification, or capability. Keep a master version and tailor per-buyer. Many small businesses keep one general cap statement plus 2–3 agency-specific variants.
Keep reading
Want to team with Mansa Gov?
Mansa Gov is a SAM.gov-registered small, minority-owned contractor open to teaming with primes and supporting agencies directly. If you're a prime looking for a reliable subcontractor — or a small business sharpening your own capability statement — reach out.
Contact Mansa GovThis article is general information, not legal or contracting advice. Federal program rules and thresholds change — verify current requirements with SAM.gov and the SBA before relying on them.