Capability Statement Template: What Federal Buyers Actually Read

A capability statement is the federal contractor's resume. It lives on your website, travels with you to industry days, and gets forwarded by small-business specialists who are trying to fill a set-aside. A strong one takes about 30 seconds to read and leaves no doubt about what you do, who you do it for, and why a contracting officer should call you.

Most capability statements fail for the same reasons. They are too long. They use vague marketing language. They omit the federal-specific data a contracting officer needs at a glance. This post shows what a winning statement includes, what to cut, and gives you the skeleton to start from.

The five mandatory sections

A one-page capability statement should have exactly five sections. Two are text. Three are data.

1. Company overview (2–3 sentences)

Open with the elevator pitch. Be specific about what you do, for whom, and what differentiates you.

Weak: "ABC Services is a world-class provider of innovative IT solutions serving public- and private-sector clients nationwide."

Strong: "ABC Services delivers FedRAMP Moderate cloud migration and Zero Trust architecture implementation for civilian agencies. We have moved 14 agency workloads to AWS GovCloud since 2019 under OASIS+ and the Department of Homeland Security EAGLE II vehicles."

The strong version tells a contracting officer exactly what to buy from you and signals credibility through specific vehicles and counts.

2. Core competencies (3–5 bullets)

Core competencies are what you do, not what you aspire to do. Each bullet should map to a NAICS or PSC code you work under. Three to five bullets is the sweet spot; more and the reader stops scanning, fewer and you look narrow.

Example:

• Cloud migration (AWS GovCloud, Azure Government) — lift-and-shift through full refactor
• Zero Trust architecture — NIST SP 800-207 aligned design, implementation, operations
• DevSecOps pipelines — CI/CD with built-in security scanning and ATO acceleration
• 24/7 SOC services — Tier 1–3 staffing, SIEM engineering, incident response

3. Differentiators (3–4 bullets)

Differentiators are why you, specifically, over the thirty other small businesses in the contracting officer's inbox. Good differentiators are verifiable facts: certifications, clearances, past performance metrics, specific vendor partnerships.

Avoid: "innovative," "world-class," "best-in-class," "customer-focused."

Use: "93% CPARS ratings of Exceptional or Very Good across 12 contracts since 2020," or "14 cleared engineers with active Top Secret clearances," or "AWS Advanced Consulting Partner with Government Competency."

4. Past performance (3–5 entries)

For each entry: Customer · Contract type · Period · Dollar value · What you did. One line each.

Example:

• U.S. Army PEO-EIS · FFP · 2022–present · $4.8M — Cloud migration for four enterprise systems to AWS GovCloud
• DHS CISA · T&M · 2021–2023 · $2.1M — Zero Trust architecture assessment and reference design
• VA OI&T · FFP · 2020–2022 · $1.6M — DevSecOps pipeline standup and ATO support

Contracting officers use past performance for two things: to check that you can do the work, and to look up your CPARS ratings. Make it easy for them.

5. Corporate data (the stamp)

The top band or bottom band (designer's choice) carries the structured data every federal buyer needs:

• Legal business name
• UEI (12-char)
• CAGE code (5-char)
• Primary NAICS and up to 5 secondary NAICS codes
• Socioeconomic certifications (8(a), WOSB, HUBZone, SDVOSB, etc.)
• Key contract vehicles (GSA Schedule SIN, OASIS+, CIO-SP4, GWACs)
• Point of contact: name, title, email, phone
• Website and office location

What to cut

The most common cuts that make a capability statement dramatically better:

• The mission statement. Contracting officers are not buying your mission; they are buying your services.
• "About Us" history. Year founded is fine as a data point in the stamp; a paragraph about the founder's journey does not belong here.
• Generic stock photos. The U.S. Capitol, server racks, anonymous teams-around-a-laptop — they say nothing. Cut them.
• Full-color branding gradients. You want to read well in black-and-white on a printer somewhere on a federal base. Test print your statement.
• QR codes to LinkedIn. Federal networks often block LinkedIn. Use your .com email and your website URL.

Design guidance

Keep it one page unless you have genuinely unique depth that requires two. Use clean sans-serif (Inter, Helvetica, Arial). Ensure 10-point minimum body text. Anchor the corporate-data band in a contrasting block that separates it visually from the narrative.

Export as PDF. Include your company name and UEI in the file name: ABC-Services-CapabilityStatement-ABC123DEF456.pdf.

A skeleton you can start from

[Logo]   COMPANY NAME
         UEI · CAGE · Primary NAICS · Certs · POC

[2–3-sentence company overview that names the services, customers, and differentiation specifically.]

CORE COMPETENCIES
• [Capability 1 tied to NAICS/PSC]
• [Capability 2 tied to NAICS/PSC]
• [Capability 3 tied to NAICS/PSC]

DIFFERENTIATORS
• [Verifiable fact 1]
• [Verifiable fact 2]
• [Verifiable fact 3]

PAST PERFORMANCE
• [Customer · Type · Period · $Value · Scope]
• [Customer · Type · Period · $Value · Scope]
• [Customer · Type · Period · $Value · Scope]

CORPORATE DATA
Legal Name:           [Exact SAM.gov name]
UEI:                  [12 chars]
CAGE Code:            [5 chars]
Primary NAICS:        [code] — [description]
Secondary NAICS:      [list]
Certifications:       [8(a), WOSB, HUBZone, SDVOSB, etc.]
Contract Vehicles:    [GSA Schedule SIN, OASIS+, etc.]
Point of Contact:     [Name, Title, Email, Phone]
Address:              [City, State]
Website:              [URL]

Iteration cadence

Update your capability statement:

• Annually, regardless of whether anything changed, so dates are current
• After any new award that meaningfully changes past performance
• After any new certification — new set-asides broaden your eligibility
• Before every industry day, tailored to the agency and topics being presented

Distribution

A capability statement only works if it is seen. Distribute it to:

• Your agency small-business specialists (every agency has OSBDU — Office of Small and Disadvantaged Business Utilization)
• PTAC/APEX Accelerator counselors in your state
• Prime contractors you are targeting as teaming partners
• The contracting officer on any sources-sought or RFI you respond to
• Your own website footer — make it one click from your homepage

Common mistakes

1. Two pages when the content needed one. If you are padding, cut.
2. No dollar values in past performance. The dollar signal is how federal buyers assess whether your scale fits their requirement.
3. Claiming certifications you do not hold. Do not write "pending 8(a)" as if it were "8(a)." Claim only what is active.
4. Missing UEI. If you do not show your UEI, you look like you are not in SAM.gov.
5. Outdated website URL. Click every link in your own document before every distribution.

What strong capability statements have in common

Strong statements read more like a data sheet than a brochure. They deliver federal-specific facts in a scannable layout, let past performance do the talking, and put certifications and NAICS where buyers can see them in two seconds. Follow the skeleton above, cut the marketing adjectives, and your statement will outperform most of what sits in contracting officers' inboxes today.