Jackson SenczyszynCapture management is the work between business development and the proposal: qualifying the specific pursuit, understanding the competition, shaping what can lawfully be shaped, deciding teaming and price posture, and making an honest go or no-go call. It happens months before a solicitation drops. Done well, the proposal becomes a writing exercise instead of a strategy exercise.
The word gets used loosely enough that it has almost stopped meaning anything. Plenty of firms describe proposal support as capture. It is not, and the difference is expensive.
Business development answers the question “which offices should we be talking to at all?” Capture answers “are we going to win this specific one, and what do we have to do differently to make that true?” The proposal answers “how do we say it so an evaluator can score it?” Three different jobs, three different skill sets, and only the last one is visible from outside.
What capture actually involves
Qualification, which mostly means finding reasons to walk away
Every pursuit begins with four questions, and any one of them can end it.
- Is the money real? Not “is there interest,” but is there an identified funding line, in a fiscal year you can survive to, in an appropriation that can legally buy what you sell.
- Is the requirement already shaped? If the technical description reads like a particular competitor’s architecture, someone else did the work eighteen months ago.
- Can we actually perform? Including the parts that are not technical: clearances, accreditation, accounting system, the capacity to hire.
- Do we have a discriminator an evaluator can write down? Not a feature we like. A difference that maps to a stated evaluation factor.
Qualifying out is the most valuable thing capture produces, and the hardest thing to sell, because it looks like doing nothing. It is not. A no-go decision made three months early returns a quarter of your engineering capacity to the product.
Competitive assessment
Who else will bid, who is incumbent, and what does the award history say about how this office actually buys. Federal award data is public, and reading it tells you a great deal: whether an office prefers a particular vehicle, whether they have sole-sourced before, whether they split awards, whether the incumbent has ever lost.
The output is not a competitor list. It is a realistic answer to “why would they pick us over the obvious choice,” written in a sentence you would be willing to say out loud to the program office.
Shaping, within the rules
Shaping is the part people get nervous about, and the nervousness is misplaced as long as you understand where the line is. Before a solicitation is released, the government does market research. It asks industry what is possible. It publishes requests for information and sources sought notices specifically to learn. Responding thoughtfully to those, and giving a program office an accurate picture of what current technology can do, is exactly what that process is for.
What you cannot do is obtain competitive information you are not entitled to, or help write the solicitation you intend to bid. Organizational conflict of interest rules exist and they are enforced. The practical guidance is simple: participate openly in the government’s market research, keep your communications on the record, and if something feels like an advantage nobody else could have had, stop and ask.
If the way you obtained an advantage would embarrass the program office when it appeared in the award file, it is not an advantage. It is a protest waiting to happen, and protests fall on the government employee who trusted you.
Teaming and the honest prime or sub question
Companies default to priming because it sounds better. Sometimes it is wrong. If the requirement is larger than your past performance can support, if it demands functions you would have to subcontract anyway, or if the incumbent relationship is strong, being a meaningful subcontractor can produce revenue this year and the past performance that lets you prime next time.
Capture is where that decision gets made deliberately, rather than by default at proposal time when it is too late to build the team properly.
Price posture
Not the cost volume, which comes later. The question capture answers is what kind of price this competition rewards, and whether you can be that. A best-value tradeoff and a lowest-price competition demand almost opposite behavior. Discovering which one you are in at proposal time is how companies end up sharpening pencils on a bid they should never have entered.
What good capture produces
By the time a solicitation drops, a well-run capture has already delivered:
- A go or no-go decision made weeks earlier, with the reasoning written down.
- A win strategy in one paragraph: why us, why now, and what an evaluator will write in the strengths column.
- A team, with agreements in place rather than in negotiation.
- A price posture, and the cost data to support it.
- Draft technical content for the parts that never change, so the writing period is spent on the parts that do.
That last one is why capture pays for itself even on pursuits you win narrowly. A proposal period spent executing a decided strategy is calm. A proposal period spent deciding strategy is the reason your engineers are writing boilerplate at midnight.
How to tell whether you have capture or just proposal support
Three questions. When did work start on the last pursuit you lost: before or after the solicitation posted? Can anyone in your company state the win strategy for your current top pursuit in one sentence? When was the last time somebody recommended not bidding something?
If the answers are after, no, and never, you have proposal support. It might be excellent proposal support. It is just not the thing that decides whether you win.