This video walks through the core concepts for this module. Watch it first, then use the slides below to go deeper.
A Small Business Specialist at a Texas state agency described her week: 40–60 capability statements received. Average 12–15 seconds per document. The ones that go in the "follow up" pile have three things in common.
Here's a useful frame: imagine your capability statement as a billboard on I-35. A driver has 3–4 seconds. They can't stop. They can't ask questions. They either get it or they don't.
Your capability statement gives a contracting officer 15 seconds — which sounds like more time, but they're doing it 40 times in a row on a Tuesday afternoon. The same rule applies: if a stranger can't understand what you do, who you've done it for, and why you're worth a follow-up in one fast scan — the document isn't ready. Every word should earn its place on that billboard.
Clearly states what the company does in the first sentence. Has specific numbers — project sizes, years of experience, contract values. Looks professional and scannable.
Doesn't say what the company actually does. Uses vague language like "experienced team" and "quality work." Looks like a default Word template with no visual identity.
Your capability statement is the first sales conversation you'll ever have with a contracting officer — and you won't be there when it happens. It has to work without you.
Government capability statements have a standard structure. Contracting officers see hundreds — when yours follows the expected format, they can extract what they need in seconds.
Contracting officers routinely verify capability statements against SAM.gov. If your legal name is slightly different, your CAGE code doesn't pull up your record, or a NAICS code on your document doesn't match your registration — you've created doubt. Not just about the document. About you.
The most common mistakes: using your DBA (trade name) instead of your legal entity name, listing a NAICS code you registered for but then removed, or forgetting to update your capability statement after renewing your SAM.gov registration. Pull up your SAM.gov profile before you finalize anything.
Your core competencies must match the NAICS codes and PSC codes you've registered with. Vague descriptions are the most common mistake. A good test: if you replaced your company name with a competitor's name, would the competencies still be true? If yes, they're not specific enough.
• IT Services
• Consulting
• Project Management
• Support
• Cybersecurity assessments, FISMA compliance (NIST 800-53)
• Network infrastructure design (LAN/WAN/SD-WAN)
• Help desk, tier 1–3 support (SLA-backed)
• Cloud migration, Azure/AWS managed services
This is the most common situation for new contractors — and the one most capability statement guides don't address. Here's the reality: contracting officers know that every contractor starts somewhere. What they're actually evaluating is proof you can execute. That proof can come from commercial work.
The rule: format commercial experience exactly like government experience. Client name (or "[Fortune 500 Logistics Client]" if confidential) | service type | dollar value | duration — one-sentence outcome. A $340,000 commercial facilities contract formatted cleanly reads as credible. A paragraph of vague narrative about "extensive industry experience" reads as someone trying to hide the absence of evidence.
If you're brand new with no commercial performance either: document your team's individual experience. A former TxDOT employee on your staff, a principal with 12 years of IT infrastructure work — these belong in past performance, formatted the same way, with the previous employer named. You're not fabricating experience. You're surfacing the experience that's actually there.
3–5 specific, verifiable reasons your business is different from competitors. Must be real and provable — not claims every business could make.
Everyone says these — they carry zero weight with contracting officers who've seen them 60 times this week.
• Experienced team
• Client-focused approach
• High quality work
• Committed to excellence
• All staff hold active Secret clearances — no onboarding delays
• Bilingual service delivery (English/Spanish) for Texas border agencies
• Average project delivery 11% under budget across 14 contracts
• 7 contracts with HHSC and TxDOT — deep familiarity with their processes
For each differentiator, ask: "Could 90% of my competitors say this?" If yes, it's not a differentiator. Replace it with something only you can say — or something you can prove with a specific number.
Most contractors struggle with this section because they're trying to write differentiators from scratch. The better approach is to excavate what's already there. Work through these questions — the answers will contain your differentiators:
If none of your current differentiators came from this list — go back and answer the questions. Then replace what you have.
Legal business name · UEI number · CAGE code · Primary NAICS code(s) · Business address · Phone and website · Primary point of contact (name, email, phone) · Active certifications (SDVOSB, 8(a), WOSB, HUBZone, Texas HUB — only list verified, active certifications)
Every field in your company data block — legal name, UEI, CAGE code, NAICS codes — must be an exact copy of what's in your sam.gov registration. Contracting officers verify this when they receive your document. One discrepancy creates doubt. Use your sam.gov profile as the source of truth, not your memory.
Your capability statement may be the first thing a contracting officer sees. If they search for your UEI and the name on the document doesn't exactly match what SAM.gov shows — even a subtle difference like "LLC" vs "L.L.C." or a missing comma — it creates friction. Some COs will ask you to fix it. Others will move on.
Equally common: a business registers on SAM.gov with 6 NAICS codes during setup, then prunes the list later. But the capability statement still lists all 6. Now you're claiming capability in codes your registration doesn't support. Update your document every time you update SAM.gov — treat them as the same document in two formats.
[YourCompanyName]_CapabilityStatement.pdf — not "cap_statement_v3_FINAL.docx."Most businesses have one generic capability statement they send everywhere. The businesses that win have 3–5 tailored versions. The company data block stays the same. The core competencies, past performance examples, and differentiators are customized per agency or work type.
The company data block never changes. Everything else is fair game. Here's what a targeted version looks like in practice:
| Section | Generic version | TxDOT-targeted version |
|---|---|---|
| Core Competencies | Lists all 6 capabilities including healthcare IT, network infrastructure, help desk, cybersecurity, cloud, AV systems | Leads with network infrastructure, field communications, and project management — most relevant to TxDOT operations |
| Past Performance | 3 examples: HHSC (healthcare), Dallas ISD (education), commercial logistics client | 2 examples: TxDOT regional office project (if any), transportation-adjacent infrastructure work highlighted first |
| Differentiators | Lists 5 differentiators including bilingual staff, clearances, and TxDOT familiarity | TxDOT familiarity and relevant certifications moved to top two slots |
| Company Data | Unchanged | Unchanged — never touch this |
This takes 15–20 minutes once you have a solid base document. The increase in follow-up rate is significant because the CO immediately sees "this vendor understands our work" rather than "this is a generalist I might call someday."
Read your capability statement once and answer three questions:
1. Does it tell me, in plain language, exactly what this company does?
2. Does it give me specific evidence that they've done this work before?
3. Does it tell me exactly who to contact and how?
If any answer is "no" or "kind of," revise until all three are clear yes answers.
Send your capability statement to your APEX Accelerator counselor for review before it goes to any agency. They've seen hundreds of them and will immediately spot what's not working. This is one of the highest-value ways to use your free APEX access.
A real scenario from the field. No answer permanently locks you out — but the consequences below are real. Choose one, then see what unfolds.
A contracting officer from TxDOT reaches out after seeing your CMBL listing. She asks you to send your capability statement before an upcoming small business outreach event. You have a 4-page document covering your full company history, team bios, all 12 service areas, and your equipment list.
Make a choice above, then continue to the knowledge check.
Three quick questions to lock in what you just learned. Click any answer — right or wrong, you'll see the full explanation. The goal is retrieval, not a grade.
Module 8 is about finding and qualifying opportunities — how to build a pipeline of the right opportunities before you ever write a proposal.
[YourCompanyName]_CapabilityStatement.pdfWant feedback on your capability statement before you send it anywhere? Alex can review it and tell you exactly what's working and what isn't.
Your capability statement needs real target agencies, not hypothetical ones. Use BidWatchHQ to find the agencies actively buying in your NAICS — then tailor a version of your cap statement to each one. Real agency intel, not guesswork.
Module 8 is about building your opportunity pipeline — finding the right contracts, qualifying them before you invest time, and positioning yourself before the solicitation even releases.
Module 8: Building Your Pipeline →