Capability Statement for Federal Contractors: Template and Guide

Every federal contractor needs a capability statement — a one-to-two page document that tells government buyers, prime contractors, and procurement officials what you do, who you serve, and why you win. It is your federal contracting business card.

A generic capability statement that could describe any contractor in your industry is almost worthless. A targeted, well-designed capability statement that speaks directly to a specific agency's needs will open doors that cold calls never will.

This guide covers the required sections, how to tailor your statement, and the common mistakes that make capability statements forgettable.

What Is a Capability Statement?

A capability statement is a concise marketing document (typically 1–2 pages) that federal buyers, contracting officers, and prime contractor business development managers use to quickly assess whether your firm has relevant capabilities and qualifications.

It is not a proposal — it is a door-opener. Government buyers receive capability statements in:

• Agency small business outreach sessions
• One-on-one matchmaking events
• SBA and PTAC events
• Cold outreach and email introductions
• Industry days and site visits

A good capability statement prompts a follow-up meeting. A weak one is filed and forgotten.

The Six Required Sections

Every effective federal capability statement includes these six sections, in this order:

1. Company Overview and Contact Information

The header of your capability statement should immediately identify:

• Company name and logo
• Primary point of contact name, title, email, phone
• Company website
• SAM.gov UEI number

Do not bury contact information. Many capabilities statements lose business because a busy contracting officer can't find the phone number.

Example header block:

Apex Technology Solutions, LLC123 Innovation Drive, Suite 400 | Arlington, VA 22201Contact: Sarah Chen, VP Business Development[email protected] | (703) 555-0192 | apextech.comUEI: ABCD1234567E | CAGE: 7XY89

2. Core Competencies

This is the most important section — a clear, concise statement of what your company does best, organized around 3–6 specific competencies directly relevant to your target market.

Don't list generic capabilities:

• ✗ "IT Support Services"
• ✗ "Program Management"
• ✗ "Consulting"

Do list specific, differentiated capabilities:

• ✓ "Zero Trust Architecture Design and Implementation (NIST SP 800-207)"
• ✓ "FedRAMP Authority to Operate (ATO) Preparation and Advisory"
• ✓ "Legacy COBOL System Modernization to Cloud-Native Microservices"

Each core competency should be specific enough that a reader can immediately assess relevance to their procurement.

3. Past Performance (2–4 Projects)

List 2–4 recent, relevant past performance examples. For each project include:

• Agency/customer name
• Contract number (if federal)
• Contract value (or range: "$1.2M–$3M")
• Period of performance
• One-to-two sentence description of what you delivered
• Outcome or metric that demonstrates success

Example:

U.S. Department of Veterans Affairs — IT Infrastructure Modernization Contract: VA-2022-1234 | $2.8M | 2022–2024 Migrated 47 legacy VA applications to AWS GovCloud, reducing annual maintenance cost by $840K and improving system uptime from 97.1% to 99.6%.

Keep past performance examples recent (within 3–5 years) and as relevant as possible to the target agency. See our past performance guide for how to frame these descriptions.

4. Differentiators

What makes your company different from every other contractor claiming the same capabilities? Your differentiators section articulates the 2–4 things that make your firm distinctly qualified.

Weak differentiators:

• "20 years of experience" (so does everyone)
• "Dedicated customer service" (every contractor says this)
• "Innovative solutions" (meaningless)

Strong differentiators:

• Specific certifications (ISO 27001 certified, DoE Q-clearance team members, CMMC Level 3 certified)
• Proprietary methodologies or tools with documented outcomes
• Unique subject matter expertise (former DoD program manager with direct Pentagon relationships)
• Specific technology partnerships (AWS Premier Partner, Microsoft Gold Partner)
• Geographic presence (offices at or near the target installation)

Be specific. "Our team includes three former AFMC contracting officers who know acquisition from the inside" is a differentiator. "Quality service" is not.

5. Company Data and Socioeconomic Status

This is the section contracting officers use to check your eligibility for set-asides and to complete their market research. Include:

• Business size: Small Business (confirm against your primary NAICS)
• NAICS codes: List your 3–5 primary codes with size standards
• Socioeconomic certifications: 8(a) (with expiration date), HUBZone, SDVOSB, VOSB, WOSB, EDWOSB
• CAGE code
• Entity type: LLC, corporation, etc.
• Year founded
• Number of employees

Make this section easy to scan — a table or two-column list format works well.

6. GSA/Contract Vehicles

If you hold contract vehicles, list them:

• GSA MAS Schedule number and SINs
• GWAC vehicles (OASIS+, STARS III, CIO-SP4, SEWP V, etc.)
• Agency-specific IDIQ vehicles

Contracting officers often want to know: can I order from you right now without a new competition? If you have vehicles, this section answers that question instantly.

Design and Format

One Page vs. Two Pages

One page is the standard for most capability statements and is preferred for:

• Cold outreach situations
• Industry days with short attention spans
• Agency small business events where you hand it to a busy CO

Two pages is acceptable when:

• You have a deep past performance record to showcase
• The agency you're targeting has specific requirements
• You are presenting at a one-on-one matchmaking where both parties have 30 minutes

Visual Design Principles

• Use your brand colors and logo consistently
• White space matters — a cluttered capability statement is harder to scan than a clean one
• Use bullet points and headers, not dense paragraphs
• Font size: Minimum 10pt body text; 11–12pt is more readable
• File format: Always provide as PDF; never send an editable Word document

Professional design significantly increases the perceived credibility of your firm. If you do not have a designer, hire one for this document — it is worth the investment.

Tailoring Your Capability Statement by Agency

A single generic capability statement is less effective than tailored versions for each target agency. If you are pursuing VA, DoD, and HHS contracts:

• VA version: Lead with healthcare IT and facility management capabilities; emphasize SDVOSB/VOSB if applicable
• DoD version: Lead with security clearances, CMMC compliance, DFARS experience; include Berry Amendment compliance if relevant
• HHS version: Lead with public health, life sciences, or healthcare program management capabilities

Keep the base document consistent but swap out:

• The target agency's logo (where appropriate) or mission language
• The most relevant past performance examples
• The core competencies most aligned with that agency's needs

Distributing Your Capability Statement

Where to share it:

• DSBS profile on SAM.gov (upload as supporting document)
• Email to agency Small Business Offices (directories on agency websites)
• Hand-deliver at industry days, matchmaking events, and site visits
• Share with prime contractor small business liaison officers
• Upload to state/local PTAC procurement portals

Follow up: Always follow a capability statement with a request for a 30-minute capability briefing. The capability statement gets the meeting; the briefing gets the relationship.

Key Takeaways

• Six required sections: Company overview and contact, core competencies, past performance, differentiators, company data, and contract vehicles.
• Core competencies must be specific — generic capabilities are forgettable; specific, demonstrable expertise is memorable.
• Past performance examples need contract numbers, dollar values, periods, and outcome metrics — not just project names.
• Tailored versions by agency outperform generic one-size-fits-all capability statements.
• Design matters — a well-designed, easy-to-scan document conveys professionalism and attention to detail.
• The capability statement gets the meeting — it is not the end of the business development process; it is the beginning.

Use RFxNerd to find the right agencies and buyers to target with your capability statement →