The one-pager is a search artifact, not a brochure
A small business specialist asks for one at the end of a five-minute call. A prime's supplier lead asks for one in a two-line email. A contract specialist running market research on a sources-sought notice asks twelve companies at once and gets back twelve PDFs that read identically: a mission statement, a row of adjectives, a stock photo of a handshake, and a logo. The job of the document is to convince one specific reader that you solve one specific problem, and then to survive being forwarded twice inside an agency where nobody has met you. Most capability statements do neither.
The mental model that fixes most of them is simple. The document is a search artifact. It gets saved to a shared drive under a filename somebody else picks. It gets attached to an email whose entire body is "see below." Six weeks later a contract specialist searches an inbox for "records digitization" or "541715" or "Iowa small business," and either your PDF comes back in the results or it does not. Everything below follows from writing for that moment.
That moment is not incidental to how work gets awarded. FAR 10.001 requires agencies to conduct market research before soliciting most requirements. FAR 19.502-2(b) then says the contracting officer must set the acquisition aside for small business when there is a reasonable expectation that offers will come from at least two responsible small businesses and award can be made at fair market price. The evidence behind both of those decisions is often nothing more than the pile of capability statements a specialist collected. A one-pager that lands cleanly in that pile is doing real acquisition work, weeks before an RFP exists.
Four readers, four different jobs
A single page has to serve four people who want different things, and the reason most one-pagers fail is that they are written for none of them.
The small business specialist or OSDBU representative. Their job is routing. They need your size status, socioeconomic status, NAICS codes, and one repeatable sentence they can carry into a program office meeting. They will not read your third paragraph. If they cannot restate what you do in ten words, the document dies with them.
The prime's subcontracts or supplier diversity lead. They are managing a subcontracting plan, which is required under FAR 19.702 and clause FAR 52.219-9 for other-than-small primes on contracts expected to exceed $750,000 (higher for construction). They want to know whether adding you helps a goal category, whether you can actually staff the scope, and whether you will be a compliance problem. Certifications and registration facts matter to them more than your technical prose.
The technical lead, COR, or program engineer. This person skips the entire top half of your page and looks for evidence you have done the specific thing. They are the reader who generates the callback. Everything you write for them should be concrete enough that they could argue for you in a meeting they attend and you do not.
The contract specialist writing the market research report. They need your UEI, CAGE, NAICS, and size status in copyable text, plus one or two sentences that map to the language of their own requirement. Make that paste easy and you become the vendor who is quoted in the file.
Attention distribution across a 30-second skim
Editorial weighting from public sources and practitioner reading — illustrative, not a measured statistic.
The ten-second block
There is a fixed set of facts that must be findable without scrolling, hunting, or squinting. Put them in one place, keep them in live text, and never change their position between versions:
- Legal entity name and DBA. The legal name has to match SAM.gov exactly, because that is what a contract specialist searches.
- UEI and CAGE code. The Unique Entity ID replaced DUNS for federal award purposes on April 4, 2022. CAGE codes are assigned through DLA's CAGE program. Print both as text, never inside an image.
- NAICS codes with size status. Three to five, each one you would genuinely bid.
- Socioeconomic status and certifications. Named exactly as the certifying body names them, with the certification date.
- SAM registration status and expiration. Registration must be renewed annually to stay active and eligible for award.
- Place of performance and business address. Geography decides more than people expect, especially for state work and for HUBZone-adjacent requirements.
- A named human, a direct email, and a direct phone number. Not info@. Not a web form.
Any relevant facility or program credential belongs in this block too: a JCP / DD-2345 certification for access to militarily critical technical data, a CMMC assessment status, an active FedRAMP authorization, or a schedule or IDIQ contract number. These are the lines a specialist checks before scheduling anything, and their absence is read as absence of the credential.
Core competencies: write the problem, not the noun
The single most common failure on the page is a competency list made of category nouns. "Artificial Intelligence / Machine Learning. Data Analytics. Cloud Migration. Cybersecurity. Program Management." Every competitor's PDF says the same five things, and the reader learns nothing except that you own a thesaurus.
A competency should name an input, an output, and a constraint. "We take a program's twenty-year backlog of scanned correspondence and turn it into a searchable record set with a measured false-extraction rate the program can defend in an audit." That sentence tells the engineer what you touch, what they get, and what standard you hold yourself to. It also gives the specialist their ten-word restatement for free.
Use the verb test. Read each competency out loud. If there is no verb and no object, it is a category, not a competency, and it should be rewritten or cut. Three to five sentences is the right count. More than five and the reader concludes you do everything, which reads as doing nothing in particular.
Order matters as much as content. The first competency on the page should be the one that matches whatever brought this reader to you: the sources-sought scope, the prime's gap, the conference conversation. That is the one edit worth making before every send.
Differentiators only count if they are checkable
"Responsive." "Customer-focused." "Proven track record of excellence." None of these are differentiators, because the eleven other PDFs in the folder claim them word for word. A differentiator is a fact the reader can confirm without calling you. There are four kinds worth printing.
Registration facts. Active SAM registration, CAGE code, NAICS with size status, export-control or technical-data credentials. Verifiable in a public system in under a minute.
Credential facts. Licensed professional engineers on the team, cloud certifications held, competition rankings, clearance levels held by named staff. Specific, dated, and checkable.
Structural facts. Where the work is performed, whether you will work as a subcontractor, response time you commit to, whether your accounting system can carry a cost-reimbursement contract. Primes ask all four on the first call, so answering in advance saves the call.
Technical facts. The stack you deploy on, the accreditation boundary you have worked inside, the benchmark you measure against. Numbers beat adjectives every time.
NAICS codes and the size standard behind them
NAICS is not decoration. The contracting officer assigns one NAICS code to a solicitation, and that code's size standard in the SBA table at 13 CFR 121.201 decides whether you are small for that particular buy. A firm can be small under one code and large under another on the same day.
The mechanics are worth knowing before you print anything. Receipts-based standards in the professional services codes are calculated on a five-year average of annual receipts, a change made by the Small Business Runway Extension Act of 2018 and finalized by SBA in December 2019, with the five-year method mandatory from January 6, 2022. Employee-based standards work differently: NAICS 541715, research and development in the physical, engineering and life sciences, carries a 1,000-employee standard for the base code, with higher standards for specific aircraft and space vehicle exceptions. Look your own codes up in the table rather than trusting memory, because SBA adjusts the receipts thresholds for inflation on a recurring cycle.
Two practical rules follow. First, list three to five codes, not twenty. A page carrying twenty NAICS codes signals that the firm has not decided what it does, and specialists read it that way. Second, if a solicitation carries a NAICS code you believe is wrong for the work, you can appeal it to SBA's Office of Hearings and Appeals, and the window is short: 13 CFR 121.1103 sets ten calendar days after issuance of the solicitation. Knowing that deadline exists is worth more than most of the content on a typical one-pager.
Product Service Codes deserve a line as well. Many buying offices search their own opportunity and vendor data by PSC rather than NAICS. Adding the two or three PSCs that match your actual work costs you eight words and puts you in a second search index.
Socioeconomic status: use SBA's exact words
If you hold a certification, name it the way the certifying body names it and include the date. The 8(a) Business Development Program is governed by 13 CFR part 124. HUBZone certification sits at 13 CFR part 126. Service-disabled veteran-owned certification moved from VA to SBA under the 2021 NDAA and has been administered by SBA since January 1, 2023, under 13 CFR part 128. Women-owned and economically disadvantaged women-owned certification is at 13 CFR part 127.
If you hold none of them, write "Small Business" and move on. The temptation to manufacture adjacency, "veteran-friendly," "minority-supportive," "certification in progress," is the fastest way to lose a specialist, because they check, and a fuzzy claim in the socioeconomic block casts doubt on every other claim on the page. There is a legal edge here too: misrepresenting small business status carries penalties under 15 U.S.C. § 645(d). Precision in this block is not modesty. It is the cheapest credibility available.
A one-page structure that survives forwarding
Six blocks, fixed positions, roughly 350 to 450 words of live text on the page. The layout below is the one that reads fastest on a laptop screen and prints cleanly in grayscale, which is how a program office will actually see it.
| Block | Placement | What goes in it | Budget |
|---|---|---|---|
| Header bar | Top, full width | Legal name, DBA, and one line naming what the firm builds and for whom. | ~15 words |
| Core competencies | Upper left, ~55% width | Three to five problem-shaped sentences, ordered so the first matches this reader. | 90–120 words |
| Differentiators | Middle left | Three to five checkable facts, one line each, no adjectives. | 60–90 words |
| Relevant work | Lower left | Two to four entries: customer type, problem, what changed, measured where possible. | 80–120 words |
| Contracting data | Right rail, full height | UEI, CAGE, NAICS with size status, socioeconomic status, certifications, SAM status, vehicles. | 40–60 words |
| Contact | Bottom right | Named person, title, direct email, direct phone, website, city and state, document date. | ~20 words |
The right rail is the part that never changes. Fixing it in place has a practical benefit: a reader who has seen one of your pages before knows exactly where to look on the next one, and repeat familiarity is a real advantage in a field where most vendors are indistinguishable.
The cut list
Everything below has appeared on capability statements we have read, and none of it earns its space on a single page.
- Mission and vision statements
- The founding story, the year established as a headline, a leadership photograph
- "We deliver innovative solutions to complex challenges" and every sentence like it
- Stock photography of handshakes, globes, circuit boards and flag overlays
- Customer logos you do not have written permission to display
- An org chart, a capability wheel, or a maturity pyramid
- A second page
- A DUNS number, retired from federal award use since April 2022
- Any claim you could not document in a single reply email
Tailoring per agency without maintaining twenty files
Keep one source file with three variable blocks and one fixed rail. The variable blocks are the header descriptor, the competency order, and the relevant-work entries. The fixed rail is the contracting data, which is identical everywhere and should never be retyped. Editing three blocks takes ten minutes and is the difference between a page that reads as addressed to this office and a page that reads as mass mail.
When responding to a specific sources-sought or RFI, mirror the notice's own vocabulary in the first competency. If the notice says "records digitization and data migration," those words appear in your first sentence. Contract specialists assemble market research documentation by pasting from vendor submissions, and matching their language means your sentence is the one that survives into the file. That is also the reason to answer sources-sought notices at all when no dollars are attached: it is how a requirement becomes a small business set-aside months later.
Three variants cover almost every situation. An agency-facing version leads with set-aside status, NAICS and relevant federal work. A prime-facing version leads with subcontract posture, staffing depth and accounting readiness, since a prime's first question is whether you can carry scope without becoming their problem. A commercial or state-facing version drops the federal registration rail to a single line and leads with outcomes, because a state IT director does not know what a CAGE code is and does not need to.
Format conventions federal buyers expect
These are conventions, not regulations, and violating them still costs real reads.
One page, PDF, text-searchable. A flattened image PDF cannot be searched or copied, which defeats the entire search-artifact purpose and makes the file useless to anyone using a screen reader.
Under two megabytes. Federal mail gateways routinely quarantine large attachments, block archives, and strip anything that looks active. A 14 MB PDF with embedded video is a file that never arrives.
Ten-point minimum body text. Assume the reader prints at 90 percent scale or reads on a phone in a hallway.
Company name first in the filename, with a date. "PrecisionFederal_CapabilityStatement_202602.pdf" survives being dropped into a folder of forty files. "CapStatement_final_v3.pdf" does not.
Set the PDF title metadata field. It is what shows in the browser tab and in some search results, and almost nobody sets it.
Date the document. An undated capability statement is assumed stale, and the assumption is usually correct.
Avoid full-bleed dark backgrounds. They print badly, drain toner in offices that still print, and reduce contrast on projector screens during industry days.
What happens after it lands
Realistically, one of three things. It gets forwarded to a technical person, which is the win. It gets filed against a future requirement, which is a slower win and the reason the searchability details matter. Or it gets deleted, which is what happens to a page whose first competency did not match anything the reader had in mind.
Two follow-through moves raise the odds. First, put the same words in the places buyers search independently of email: the capabilities narrative field on your SAM entity record, your SBA small business profile, and any prime supplier portal you are registered in. When the one-pager and the SAM narrative say the same thing in the same language, a specialist who finds you two different ways gets a consistent answer, and consistency reads as competence. Second, follow up once, roughly ten business days later, with one new fact rather than a check-in. A new certification, a relevant piece of work, a specific comment on a notice they published. A follow-up that carries information is a second read; a follow-up that carries nothing is an unsubscribe.
Our team rebuilds this page for every agency conversation we are in, and the rebuild is always the same three edits: which problem goes first, which work example proves it, and which line of the rail the reader is most likely to check. The rail itself has not changed in a year, which is the point.
Common questions on the one-pager
Should rates or pricing appear on it?
No. A capability statement that prints rates invites a price conversation before a capability conversation, and it locks you into numbers before scope exists. Keep a separate rate sheet ready to send on request. The exception is a schedule or IDIQ contract number, which is a fact about how you can be bought and belongs in the contracting rail.
What goes in relevant work when the work was commercial?
Describe it by problem shape and label it plainly as commercial or state work. A federal reader can map "we reconciled twelve years of asset records across four incompatible systems" onto their own problem without being told it happened at an agency. Never imply a federal customer you do not have; that is the one error that ends the conversation permanently.
How often should it be updated?
At minimum every time SAM registration renews, which is annual. Also any time a certification is granted or lapses, a NAICS code changes, a point of contact changes, or a new piece of relevant work finishes. The date in the contact block makes the freshness visible, so an out-of-date page is visibly out of date.
Is a two-page version ever right?
The capability statement stays one page. When a sources-sought notice asks technical questions, answer them in a short response document and attach the one-pager behind it. Two artifacts with two jobs beat one hybrid document that does neither well.
Frequently asked questions
A one-page PDF that tells a federal buyer what problems your firm solves, what makes the claim checkable, and how to contract with you. It is the standard artifact requested during market research, at industry days, and by prime contractors screening potential subcontractors.
Legal name, UEI, CAGE code, NAICS codes with size status, socioeconomic status and certifications, SAM registration status, core competencies stated as problems solved, checkable differentiators, relevant work, and a named point of contact with a direct phone and email.
Three to five. Each one should be a code you would genuinely bid under, since the contracting officer assigns a single NAICS to each solicitation and that code's size standard at 13 CFR 121.201 determines whether you count as small for that buy.
No. Self-certified small business status is a legitimate status and is what most firms hold. State it plainly and accurately. Claiming or implying a certification you do not hold carries real exposure under 15 U.S.C. § 645(d) and destroys credibility with the specialist who checks.
A proposal answers a specific solicitation and is evaluated against stated criteria. A capability statement runs earlier, during market research and teaming conversations, and its only job is to get you into the group being considered when the requirement takes shape.