Most pursuits are lost before pen hits paper
Small federal contractors don't lose most pursuits at the proposal stage. They lose them during capture — or, more precisely, because capture never happened. The proposal was competent. The pricing was reasonable. The team was qualified. But the pursuit was structurally disadvantaged before the technical volume was drafted, because the capture work — scoring, incumbent research, competitive positioning, pricing benchmarks, compliance — either wasn't done or was done too late to matter.
Capture is the work that decides whether a pursuit is winnable, then positions you to win it. When the capture process has gaps, even strong proposals lose to weaker firms with stronger pre-proposal positioning. These are the five most common signals that a capture process is leaking wins.
Sign 1: You score opportunities by gut feel
"We always bid this agency" is not a strategy — it's a habit. Without weighted Pwin scoring across structured factors, every opportunity in the pipeline looks pursuable. Without a quantified GO/NO-GO recommendation, every opportunity gets some level of resource allocation, which means resources are spread thin across pursuits that shouldn't have been started.
The cost is concrete. A small contractor with a 10-opportunity pipeline and no scoring discipline ends up doing capture work on all 10. The contractor with disciplined scoring works 4 opportunities at full intensity and walks away from the other 6. Outcomes diverge fast.
What good looks like: quantified Pwin with factor breakdown. 78% because of strong set-aside fit, weak incumbent, favorable pricing position, and demonstrated past performance. 28% because of no customer relationship, strong incumbent, LPTA evaluation where you can't compete on price, and no relevant past performance. The score isn't an oracle — it's a forcing function for honest analysis.
Sign 2: You don't research the incumbent until after the RFP drops
By the time a solicitation hits SAM.gov, the contractor has lost six to twelve months of positioning opportunity. Incumbent contract history, past performance ratings, staffing patterns, and recompete signals shape your bid strategy, pricing, teaming arrangements, and win themes. None of that intelligence is useful in week three of proposal development — it should be in hand at qualification.
If your team cannot answer five questions — Who is the incumbent? What is their contract value? When did the period of performance start? What is their CPARS history? What are their known weaknesses? — without searching SAM.gov, the incumbent research is happening too late.
Sign 3: Your pricing is based on what feels right
Federal pricing is benchmarked. CALC+ ceiling rates, BLS Occupational Employment Statistics, historical award amounts at the agency, and FedScope wage data are all public. Bidding above CALC+ without justification is a self-inflicted wound in a best-value evaluation. Bidding below market without a defensible rationale triggers price realism concerns that can disqualify the bid before the technical evaluation.
What good looks like: labor rates benchmarked against federal data with a recommended bid range, a wrap rate calculation tied to specific overheads, and a pricing rationale that anticipates how the source selection authority will read the price volume. "It feels right" is not a defensible price-to-win position.
Sign 4: You skip compliance review until Red Team
By Red Team, the proposal structure is set. Discovering at that stage that you missed a Section L formatting requirement, an attachment, or a representation means rewriting under deadline — typically with the wrong people doing the rewrite, because the SMEs are gone and the proposal team is in production mode.
A compliance matrix should exist at the GO/NO-GO decision, not after the proposal draft. Mapping every Section L instruction, every Section M evaluation factor, and every required submission attachment at the beginning is structural work that takes hours. Doing it at Red Team is crisis work that takes days.
Sign 5: You chase every opportunity that matches your NAICS code
NAICS match is a minimum filter, not a pursuit decision. The volume trap is familiar: 20 opportunities show up in the weekly pipeline, 3 are actually qualified for the contractor's profile, but the team treats all 20 the same. The result is 17 light-touch capture efforts and 3 under-resourced ones — instead of 3 fully-resourced bids and 17 disciplined no-decisions.
The resource cost of one unqualified pursuit (20 to 40 hours of BD and proposal time, sometimes more) could fund complete capture on a high-Pwin bid. Volume in the pipeline is not the metric. Concentration of capture effort on the right pursuits is.
What good capture looks like
Strong capture processes do five things consistently: they score opportunities with weighted Pwin and produce explicit GO/NO-GO recommendations; they research incumbents months before the RFP drops; they benchmark pricing against published federal data with documented rationale; they build the compliance matrix at qualification, not at Red Team; and they run a disciplined pipeline that filters by Pwin, not by NAICS match alone.
Prime Recon Labs automates the capture work behind each of these signals — Pwin scoring, incumbent research, pricing benchmarks, compliance matrices, and opportunity qualification — and delivers it as a 13-document intelligence package per pursuit. The weekly pipeline digest flags the must-pursue bids and filters the noise. The capture intelligence arrives before the RFP drops, not after.