A capability statement is the single most important document in government contracting that most small businesses get wrong. It is a one-page summary of your company — what you do, what you have done, and why a buyer should pick you — and it is the first thing a contracting officer or program manager asks for after a good conversation. Get it right and it opens doors at industry days, sources-sought responses, and small-business offices. Get it wrong, or show up without one, and you look unprepared. This guide walks through every section, the mistakes that sink most drafts, and a reusable template you can fill in today.
What a capability statement is (and when you’ll need one)
Think of a capability statement as a resume for your company, written for a government audience. It is not a brochure and not a proposal. It is a fast, scannable, one-page answer to the buyer’s only real question: can this company do the work, and have they done it before?
You’ll be asked for one constantly once you start pursuing government work:
- Responding to a sources-sought notice — agencies use these to find capable small businesses before writing a solicitation, and a capability statement is the expected reply.
- Meeting a contracting officer or small-business specialist — at an OSDBU office, an industry day, or a matchmaking event.
- Introducing yourself to a prime contractor as a potential subcontractor or teaming partner.
- Following up after any of the above, attached to the thank-you email.

The standard one-pager has six sections. Here is what each does and how much room to give it.
| Section | What it does | Keep it to |
|---|---|---|
| Company overview | Who you are, what you do, structure | 2–3 sentences |
| Core competencies | What you do best, keyword-rich | 4–6 bullets |
| Differentiators | Why you over a competitor | 3–5 bullets |
| Past performance | Proof you’ve done the work | 3–5 short entries |
| Company data | UEI, CAGE, NAICS, certifications | A compact block |
| Contact | How to reach the decision-maker | 1 line + email/phone |
Laid out on the page, it looks like this:
The SBA’s guidance for small contractors stresses the same thing the best capture managers do: a capability statement is a marketing tool, not a data dump. Every line has to earn its place on the page.
Pro Tip: Design it like a one-page flyer, not a Word memo. A clean two-column layout with your logo, scannable headers, and white space reads as “professional” before a buyer has read a single word.
What should a capability statement include, section by section?
Work through these in order. The first draft is always too long — that is normal, and cutting is where the document gets good.
- Company overview. Two or three sentences: your legal entity name, what you do, who you serve, and your business structure. Lead with the work, not your founding story. “We provide network modernization for federal agencies in classified environments” beats “Founded in 2014, we are a passionate team…”
- Core competencies. Four to six bullets naming what you actually do, in the buyer’s language. Mirror the verbs and nouns agencies use in solicitations — this is also where your NAICS codes should be reflected. (Not sure which codes describe you? See our guide to picking the right NAICS codes.)
- Differentiators. Three to five bullets answering “why you over the other small business down the road?” Be specific and, where you can, quantifiable: “Only Red Hat partner in Region 4,” “98% on-time delivery across 40 task orders,” “Cleared staff available within 30 days.”
- Past performance. Three to five short entries, each with the client, contract scope, value or scale, and the outcome. This is the section buyers trust most, so make it concrete. Our deeper guide on building a past-performance portfolio covers how to present work you’re proud of.
- Company data (identifiers). A compact block with your UEI and CAGE code (both assigned during SAM.gov registration — the UEI replaced the DUNS number in 2022), your NAICS codes, and any socioeconomic certifications (8(a), WOSB, HUBZone, SDVOSB, CMMC level, etc.).
- Contact. One named decision-maker, their title, email, phone, and website. Not “info@” — a real person.
Pro Tip: Put your most relevant past-performance entry first, not your biggest. A $200K contract with the exact agency you’re targeting beats a $5M contract in an unrelated sector.
You can assemble all six sections in a few minutes with RFPHawk’s capability statement builder — it has a guided field for each one and renders a clean, formatted one-pager you can export.
How do you avoid the most common capability statement mistakes?
Most weak capability statements fail in one of three ways. Each is easy to fix once you see it.
It’s too long or too dense. The cardinal sin. If it spills onto a second page, or the page is a wall of text, a busy contracting officer simply won’t read it. Fix: one page, ruthless bullets, white space. Cut every adjective that isn’t doing work.
It’s generic. A capability statement that could belong to any company in your industry persuades no one. “High-quality, customer-focused solutions” is noise. Fix: replace every vague claim with a specific, ideally quantified one — named clients, real metrics, concrete certifications.
It’s missing the data buyers actually need. No UEI, no CAGE code, no NAICS codes, no set-aside status. Without these, a buyer can’t verify you or route you to the right set-aside, so you get filtered out before the conversation starts. Fix: include the full identifier block, current and correct.
A few habits keep your statement sharp:
- Update past performance and certifications every quarter, not once a year.
- Keep your logo, fonts, and contact details consistent with your website and proposals.
- Save it as a PDF so the formatting never breaks in someone else’s email client.
- Keep a master version, then tailor a copy per agency (more on that next).
“The capability statement isn’t where you tell your whole story. It’s where you earn the meeting where you get to tell it. Anything that doesn’t move a buyer toward that meeting is clutter.” — a common principle among small-business capture coaches
How do you tailor a capability statement to a specific agency?
The biggest jump in results comes from killing the one-size-fits-all version. A tailored capability statement reorders and rewrites the top of the page to match the agency or opportunity in front of you — without rebuilding the whole thing each time.
- Reorder competencies so the ones relevant to this agency come first.
- Swap the lead past-performance entry to the most similar contract — same agency, same NAICS, or same type of work.
- Echo the agency’s language and the specific NAICS/PSC codes from their forecast or solicitation.
- Front-load the set-aside that applies (if it’s a WOSB set-aside, your WOSB status belongs near the top, not buried in the data block).
| Generic capability statement | Tailored capability statement | |
|---|---|---|
| Competencies order | Same for everyone | Most-relevant first |
| Lead past performance | Biggest contract | Most-similar contract |
| Language | Your words | The agency’s words + codes |
| Set-aside emphasis | In the data block | Surfaced up top when it applies |
| Result | Skimmed and filed | Read and remembered |
Keep one master version current, and tailoring a copy takes ten minutes — most of the page stays the same.
Key Takeaways
A capability statement is a one-page marketing document that earns you the meeting; the winners are short, specific, and tailored to the buyer in front of you.
| Point | Details |
|---|---|
| One page, always | Two at most. Buyers skim; everything important fits on a single scannable page. |
| Six standard sections | Overview, competencies, differentiators, past performance, company data, contact. |
| Specific beats generic | Named clients and real metrics persuade; “high-quality solutions” does not. |
| Include the identifiers | UEI, CAGE, NAICS, and certifications — buyers can’t route or verify you without them. |
| Tailor per agency | Reorder competencies and past performance to match; echo the agency’s codes and language. |
Why a one-page document outperforms a 20-page pitch
We’ve seen a lot of small businesses pour days into a glossy capabilities deck — twenty slides, company history, mission statement, stock photos of handshakes — and then wonder why it goes nowhere. The problem isn’t effort. It’s that government buyers don’t read decks. They skim one-pagers, looking for two things: can you do the work, and is there proof.
The discipline of fitting everything onto one page is exactly what makes a capability statement effective. It forces you to decide what actually matters to this buyer and cut everything else. The company that shows up to an industry day with a tight, tailored one-pager — right NAICS codes, relevant past performance up top, UEI and certifications right there — looks like it understands how government buying works. The company with the twenty-slide deck looks like it’s still selling to the commercial market.
That’s the whole game early on: not impressing anyone, just making it effortless for a contracting officer to see that you fit and reach the next conversation. A great capability statement does that in under a minute.
— The RFPHawk Team
Build your capability statement in minutes with RFPHawk
Writing the content is the hard part — the formatting shouldn’t be. RFPHawk’s capability statement builder gives you a guided field for each of the six sections (company overview, core competencies, differentiators, past performance, identifiers, and contact) and renders a clean, professional one-pager you can export and attach.
Pair it with a feed of opportunities actually worth tailoring for: browse live RFPs free to see what’s open in your niche. The capability statement builder, match scoring, and saved searches are part of RFPHawk Pro, which you can try free for 14 days (cancel anytime before it bills). Spend your time on the work you do best, not on wrestling with a text box in Word.
FAQ
What is a capability statement?
A capability statement is a one-page marketing document that summarizes your company for government buyers. It covers what you do, your past performance, your differentiators, and key identifiers like your UEI, CAGE code, NAICS codes, and certifications.
How long should a capability statement be?
One page. Two at the absolute most. Contracting officers skim dozens of these, so everything that matters — competencies, past performance, identifiers, and contact info — needs to fit on a single page they can read in under a minute.
What should a capability statement include?
Six things: a short company overview, core competencies, differentiators, relevant past performance, company data (UEI, CAGE, NAICS, certifications), and contact information. Each should be tight, specific, and easy to scan.
Do I need a UEI and CAGE code on my capability statement?
Yes for federal work. The Unique Entity ID (UEI) replaced the DUNS number in 2022 and is assigned during SAM.gov registration; the CAGE code is assigned at the same time. Buyers expect both, plus your NAICS codes and any set-aside certifications.
Should I tailor my capability statement for each agency?
Yes. The strongest capability statements lead with the competencies and past performance most relevant to the specific agency or opportunity, and echo the agency’s own NAICS codes and language. A generic one-size-fits-all version converts far worse.
Put RFPHawk to work on your pipeline.
Federal SAM.gov plus a growing list of state portals, refreshed daily and scored against your profile so you see the bids worth pursuing first.
Start free — no credit card