AI Podcast Studios

Your capability statement gets seven seconds. That's it. In this episode, Hailey sits down with Brian McAllister, a veteran federal contracting officer, to decode the one-page document that either opens doors to federal contracts or quietly closes them forever. Brian breaks down the three critical mistakes he saw repeatedly in thousands of capability statements: vendor-speak that sounds professional but says nothing, differentiators buried too deep to be found, and past performance written as project lists instead of proven outcomes. You'll learn exactly what contracting officers are scanning for in those seven seconds, why your company history doesn't belong at the top, and how to structure past performance so it actually proves you can deliver. Whether you're new to federal contracting or struggling to win bids, this episode cuts through the noise and gives you the framework to write a capability statement that gets read—not skimmed. TranscriptHailey:This is The Set-Aside Playbook — built for veteran-owned businesses working the federal market. I'm Hailey, and today we're talking about the one document that either opens the door to a federal contract or quietly closes it. Brian McAllister spent years on the other side of that door as a federal contracting officer, and he's here to tell us exactly what he saw. Brian, good to have you.Brian:Hailey, glad to be here. Let's get into it.Hailey:I want to start with something that stopped me when I first heard it. How long does a contracting officer actually spend looking at a capability statement before they decide whether to keep reading?Brian:Seven seconds. That's the average. You get one scan — top to bottom — and if nothing catches, it goes in the pile and stays there.Hailey:Seven seconds. For a document that could be worth a multi-million dollar contract.Brian:That's right. And the problem isn't that COs are lazy. They're moving through dozens of these. The problem is that most capability statements give them no reason to slow down.Hailey:So for anyone who hasn't been through this process — what is a capability statement, and what's it actually supposed to do?Brian:It's a one-page document that answers three questions fast: do you have the right NAICS code for this opportunity, are you eligible for the set-aside, and have you done this exact work for someone credible. That's it. Everything else is noise.Hailey:Okay, so if the job is that focused — why are so many of them getting ignored?Brian:Because most people write them like a resume. They list services, credentials, company history — all in language that sounds impressive but tells the CO absolutely nothing about whether you can solve their problem.Hailey:You've called that vendor-speak. What does that actually look like on the page?Brian:Something like — and I've read this sentence a hundred times in different fonts — 'We provide comprehensive logistics support services to federal and commercial clients nationwide.' There is no information in that sentence. None.Hailey:Okay, but I'll be honest — that sentence sounds professional. It sounds like something you'd put on a document.Brian:It sounds like every other document in the pile. That's the problem. Professional is not the same as useful. A CO scanning for seven seconds needs to know what you've done, for whom, and with what result. That sentence answers none of those.Hailey:So that's pattern one — vendor-speak. What's the second pattern you see killing these documents?Brian:Buried differentiators. The business owner knows exactly what makes them different from the other forty SDVOSBs with the same NAICS code — but that reason is sitting in paragraph four, after two paragraphs of company history nobody asked for.Hailey:And by the time a CO gets to paragraph four—Brian:They don't. They've already moved on. If your differentiator isn't above the fold — meaning visible before a single scroll or page turn — it doesn't exist for that reader.Hailey:Okay, I think I've written that before. The company history paragraph at the top — 'founded in 2018 by a retired Army officer with a passion for...' — yeah. That's buried differentiator territory, isn't it.Brian:That's exactly it. The founder's background can be compelling — but it belongs in the differentiator section, framed as a reason to hire you, not as an origin story. The CO doesn't need the narrative. They need the proof.Hailey:What's the third pattern?Brian:Past performance written as a project list. 'Supported XYZ contract, 2019 to 2022.' That tells me duration. It tells me nothing about what you delivered, at what scale, and whether it worked.Hailey:So how do you fix past performance? What does a strong entry actually look like?Brian:You lead with the outcome. What changed because you were there — in numbers if you have them. Then the client, then the contract value or scale. Thirty percent downtime reduction. Eighty-second Airborne motor pool. Four-point-two million delivered eleven percent under budget. Three data points, one line.Hailey:And you lead with your strongest performance — not your oldest, not your first.Brian:Strongest first, always. COs aren't reading chronologically. They're scanning for credibility, and credibility comes from the most impressive thing you've done, not the thing you did first.Hailey:Let's talk about the rewrite framework. If someone is sitting with a capability statement right now that has all three of these problems, where do they start?Brian:Start with the competencies. Take every service you've listed and rewrite it as a buyer outcome. Not 'we provide fleet maintenance services' — 'we reduce fleet downtime for federal motor pools.' One sentence, one outcome, one reader.Hailey:Then move differentiators to the top — you said three bullets above the fold.Brian:Three is the right number. More than three and none of them land. Less than three and you look like you couldn't find a third. Three tight bullets — why you over the competition — visible before anything else on the page.Hailey:And the format itself matters too, right? This isn't just about what you say.Brian:Format for the skim, not the read. Short blocks, white space, bullets where possible. A CO should be able to extract your NAICS, your set-aside status, your top past performance, and your contact in seven seconds. If the layout makes that hard, the content doesn't matter.Hailey:I want to walk through a real example — fictional, but built from real patterns. This is Summit Defense Logistics. Brian, read me the before version.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. Our team of experienced professionals brings decades of combined experience in delivering quality solutions tailored to mission-cr...

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.