SBIR Capture Strategy: The Work That Decides Whether You Can Win

Capture strategy is the discipline of deciding whether and how to compete for a federal opportunity — before you commit to writing a proposal. In the defense and aerospace primes, capture is a named function with dedicated leaders, multi-month budgets, and gate reviews. In the SBIR small-business world, it is most often skipped.

That asymmetry is why the win rate at most SBIR-only firms looks the way it does. The proposal is the deliverable. The capture is the strategy. Confuse them and you write a lot of proposals that never had a real chance.

What Capture Strategy Actually Is

Capture strategy answers four questions, in order:

1. Should we compete for this? The bid/no-bid decision. Most firms make this implicitly — by writing the proposal. Disciplined firms make it explicitly, with a documented rationale and a no-bid threshold.

2. Who is the customer? Not the agency — the named program manager, topic author, or program officer who controls the funding decision. If you do not know who that person is by name, you are not running a capture; you are running a content production exercise.

3. What is our position? Why your firm, your team, your technology, against this specific opportunity. The Position-To-Win is one paragraph. Most firms cannot articulate it because they have not done the work.

4. What is the path to award? The sequence of conversations, demonstrations, and documents that move you from ‘identified an opportunity’ to ‘awarded.’ This is a calendar with names, not a writing schedule.

How Capture Differs Across Agencies

The capture frame is universal. Its application varies sharply by agency.

DoD Capture

DoD capture is topic-author driven. The pre-release window — typically three to four weeks — is when the topic author is allowed to take direct technical questions. That conversation is the single highest-leverage event in the entire capture cycle. By the time the solicitation opens, the strongest respondents have already had two or three exchanges with the topic author and understand what ‘good’ looks like in their answer. Capture begins months earlier with topic-forecast monitoring through DSIP and component-specific calendars.

NIH Capture

NIH capture is program-officer driven. The single most underused asset in NIH SBIR is the program officer call — a thirty-minute conversation that confirms institute fit, study section assignment, and whether the work is responsive to current priorities. The call is free, available by email, and almost always offered. Firms that skip it write proposals into the wrong study section and lose for reasons unrelated to the science.

DOE Capture

DOE capture is national-laboratory driven. National lab partnerships, CRADA agreements, and conference engagement at venues like ARPA-E Energy Innovation Summit or DOE Office of Science user facility meetings are the substrate on which winning DOE proposals are built. By the time a topic appears on a Funding Opportunity Announcement, the strongest respondents have already had multiple conversations with the sponsoring program office. DOE capture happens at conferences, not at desks.

The Four Artifacts of a Disciplined Capture

If you cannot produce these four documents for a given opportunity, you are not running a capture. You are improvising.

1. The Bid/No-Bid Memo

One page. The opportunity, the customer, the win probability estimate, the cost to compete, and the explicit decision. Signed and dated. The point is not the document; it is the discipline of having to write it down.

2. The Customer Map

The named individuals who influence the funding decision: the topic author or program officer, their immediate superior, the contracting officer, the technical evaluation panel chair if known. With each name: the most recent date of contact, the substance of that contact, and the next planned touch.

3. The Position-To-Win

One paragraph that answers: why your firm, why now, why this technology against this requirement. The Position-To-Win is the discriminator that makes a reviewer choose your proposal over equally credible alternatives. Most proposals never articulate one. Reviewers notice.

4. The Capture Calendar

A dated sequence of touches: the topic-author call, the lab visit, the white paper, the demo, the proposal kick-off, the red-team review, the submission. Most firms have a writing calendar. Capture-disciplined firms have a customer-engagement calendar that the writing calendar feeds into.

Why Most SBIR Firms Skip Capture

Three reasons, all rational from inside the firm and all wrong from outside it. First, capture work is invisible until it pays off; founders feel busy when they are writing and feel idle when they are doing customer discovery, even though the latter is what wins. Second, the proposal deadline is concrete and the capture timeline is fuzzy; deadlines beat strategies. Third, capture requires picking up the phone and engaging human beings inside the federal government, which most engineers and scientists are not trained to do.

The fix is not motivational. It is structural: build capture as a separate function, with its own calendar, its own gate reviews, and its own success metrics that have nothing to do with proposal page counts.

What CovertEntity Does

We run capture as a discipline that begins six to nine months before submission, not three weeks before. We map customers, document positions, and run gate reviews. We turn down opportunities where the customer map has no real names on it and the position-to-win cannot be articulated. The work upstream of the proposal is what makes the proposal worth writing.

If your firm has been submitting proposals without an articulated capture process — or if your last submissions came back without an award and the technical critique seemed thin — the constraint is rarely the writing. It is the work that should have happened before the writing began.