Why Your Capability Statement Dies in 7 Seconds (And How to Fix It)

Most veteran-owned small businesses never hear back on their capability statements. In this episode, Brian, a former federal contracting officer, explains why: it's not about qualifications, it's about framing. Discover the three patterns that sabotage proposals every single time: vendor-speak that could describe any company, buried differentiators hidden in paragraph four, and past performance listed as timestamps instead of outcomes. Learn why contracting officers spend just seven seconds deciding whether your submission stays in the pile — and what that means for how you should structure your document. Walk away with a battle-tested framework for above-the-fold content, how to rewrite past performance as proof of outcomes, and why your strongest contract example should be your opening sentence. If you're a VOSB or SDVOSB serious about federal contracts, this episode is essential. TranscriptHailey:If you're a veteran-owned small business and you've sent out capability statements that never got a response, I'm going to tell you exactly why — and it has nothing to do with your qualifications. Welcome to The Set-Aside Playbook, the show for VOSBs and SDVOSBs serious about winning federal contracts. I've got Brian with me today — former federal contracting officer, the guy who was literally on the other side of the desk. Brian, how much time did you actually spend reading a capability statement before deciding whether to keep going?Brian:Seven seconds. That's not a figure of speech — that's about how long it took to decide whether a cap statement stayed in the pile or got set aside. You're looking at a stack of them, you've got a solicitation deadline, and you need one sentence to tell you whether this vendor has solved your problem before. Most of them don't have that sentence anywhere on the page.Hailey:Wait — seven seconds. So the veteran who spent two weeks writing that document, listing every service they offer, every certification they've earned, every contract they've ever touched — that person lost in under a decade of a full minute. Brian, what are they doing wrong? Because I don't think it's laziness.Brian:It's not laziness. It's a framing problem. They're writing a resume when they should be writing a solution brief. The three patterns I saw kill capability statements, over and over: vendor-speak that says nothing — 'we provide comprehensive logistics support services' could describe a thousand companies. Buried differentiators — the one thing that actually sets them apart is sitting in paragraph four, after the CO has already moved on. And past performance that reads like a project list — contract number, period of performance, dollar value, no outcome. That's not proof. That's a timestamp.Hailey:Okay, I have to stop you there because I've seen that third one constantly — and honestly, I think I've written that before. Just a list of contracts with dates and dollar amounts like that's supposed to impress someone. But you're saying the CO doesn't care what you did, they care what happened because you did it.Brian:Exactly right. The question a contracting officer is unconsciously asking is: has this company already solved my problem for someone credible? If your past performance section doesn't answer that in one sentence, it's not doing its job. 'Reduced fleet downtime 30% for 82nd Airborne motor pool, $4.2 million contract delivered 11% under budget' — that's a sentence that earns a second look. 'Provided logistics support services to DoD client, 2021 to 2023' tells me almost nothing.Hailey:So let's talk about the fix, because I want people to walk away from this with something they can actually use today. You've got one page. What goes above the fold, and in what order?Brian:Three things above the fold, no exceptions. Your strongest past performance first — one sentence, specific outcome, credible client. Then your core competencies written as buyer outcomes, not service lists. Not 'fleet maintenance services,' but 'we keep federal motor pools running on schedule.' Then three differentiators as bullets — why you over the forty other SDVOSBs with overlapping NAICS codes. Below the fold: your company data, UEI, CAGE, NAICS codes, socioeconomic certifications. Contact info at the bottom, direct line to a decision-maker, not a general inbox. Format the whole thing for the skim, not the read.Hailey:I want to run the before-and-after on this, because I think hearing it is more powerful than explaining it. Read me the before version — a real-sounding cap statement opening the way most people write them.Brian:'Summit Defense Logistics is a service-disabled veteran-owned small business providing comprehensive logistics, supply chain, and maintenance support services to federal and commercial clients nationwide.' That's the before. Now the after: 'Summit Defense Logistics cuts fleet downtime for federal motor pools. Past performance: 30% downtime reduction for 82nd Airborne, 2023, $4.2 million contract delivered 11% under budget. SDVOSB, NAICS 488490, UEI: ABC123XYZ.' Same company. Same facts. Completely different document.Hailey:Same facts. Completely different read. And that's the thing that gets me — nothing was invented, nothing was exaggerated. You just led with the outcome instead of the biography. The set-aside gets you into the pool, but the capability statement decides whether you get the call. That's the line I want every listener to write on a sticky note.Brian:That's the whole thing. Your capability statement is not a document about you. It's a document about the contracting officer's problem — with you as the answer. Most veteran founders come from operational backgrounds, not marketing. Writing in buyer-outcome language feels unnatural at first. That's the skill gap closing the pipeline. Not eligibility, not network, not contracting knowledge. Just that one reframe on a single page.