The bid you can win is the one you helped write

Small shops new to government work treat the RFP as the starting gun. The experienced ones know it is closer to the finish line. By the time a solicitation is final, the government has usually spent months deciding what it wants, how it will evaluate offers, and — informally — which kind of company it expects to win. A team that shows up at RFP release is reacting to a requirement that someone else helped shape. The whole point of capture management is to be that someone else, and the legal, public tools for doing it are RFIs, sources sought notices, and draft RFPs.

None of this is back-room influence. These are formal, on-the-record steps the government uses to learn what industry can do before it commits to a final requirement. Responding to them well is how a capable small business gets its strengths reflected in the language an RFP is eventually scored against — and how it learns, early, whether the requirement is being quietly written around an incumbent it can never beat.

Sources sought: prove you exist and you can do the work

A sources sought notice is the government asking a simple question: are there capable companies — especially small businesses — that could do this work? The answer shapes how the contract gets set aside. If enough qualified small businesses respond, the agency may reserve the work for small business or a specific socioeconomic category; if only large primes answer, it goes full and open. Your response is a vote, and a no-show is a vote against your own category.

A strong response does two jobs. It establishes that you are real and qualified — your relevant past performance, your size status, your specific capabilities mapped to the described work — and it subtly demonstrates that the requirement as described fits companies like you. Treat it as a short, sharp capabilities statement aimed at one reader making one decision, not a marketing brochure. The discipline of mapping your strengths to the customer’s described need is the same one you will use later when shredding the RFP into a compliance matrix; you are just doing it before the requirement is locked.

RFIs: trade real information for influence

A request for information goes further than sources sought. The government is genuinely trying to understand its options — what approaches exist, what they cost, what is and is not feasible — and your RFI response is a chance to educate the customer in a direction that favors your strengths. If your discriminator is a faster delivery method or a capability most competitors lack, an RFI is where you can put that idea in front of the people writing the requirement, framed as helpful market intelligence rather than a sales pitch.

The give-and-take is real: a good RFI response shares genuine substance, and in return your thinking can end up reflected in the eventual requirement. Be careful not to hand competitors your whole solution — RFI responses can be shared internally — but do plant the ideas that, if the government adopts them, become evaluation factors you are already built to win. Every signal you pick up in return, every hint about budget, timeline, or priorities, is intelligence worth logging on the pursuit record so it sharpens your eventual price-to-win.

Draft RFPs: the last legal chance to fix the rules

When the government releases a draft RFP and asks for comments, it is showing you the rules of the contest before they are final — and inviting you to object. This is the most direct shaping tool of the three, and the most underused. A draft RFP review reads like a compliance matrix done in advance: walk Section L and Section M line by line and ask where the requirements are ambiguous, where an evaluation factor seems written around one competitor’s strengths, where a constraint is needlessly narrow, or where a page limit makes a required answer impossible.

Submitting thoughtful comments does two things. It can genuinely improve or open up a requirement that was tilting away from you, and it signals to the program office that you are a serious, engaged bidder who understands the work. Even when your comments do not change the final RFP, the exercise hands your proposal team a head start: you have already read and dissected the requirement weeks before release.

Reading the signals you get back

Shaping activity is also intelligence-gathering, and sometimes the most valuable thing you learn is that you should not bid. If the sources sought results suggest the work will go full and open against primes you cannot match, if your RFI ideas land with silence while a competitor’s approach shows up in the draft, or if the draft RFP is plainly built around an incumbent’s solution, those are early, cheap signals feeding your bid/no-bid decision. Catching a lost cause during shaping saves the proposal team you would otherwise have burned, which is exactly the kind of early call a gate review is built to force.

Where the CRM fits

Shaping a requirement happens over months and across several touch points — a sources sought response in the spring, an RFI in the summer, draft RFP comments in the fall — and the value compounds only if each one builds on the last instead of starting cold. When the pursuit lives as a single record in Hitt CRM, every shaping touch, every program-office contact, and every signal you read back sits on one timeline, so the person drafting your RFI response can see what you told the customer in the sources sought reply. Tasks keep you ahead of the response deadlines that the government rarely extends, automations can flag a pursuit whose shaping window is closing, and a report across pursuits shows which requirements you actually helped shape versus the ones you only reacted to — which, over time, is the clearest predictor of which bids you win.

The one-sentence version

The federal contest is usually decided before the RFP drops, so use the legal, public shaping tools — sources sought to set how the work gets competed, RFIs to educate the customer toward your strengths, and draft RFP comments to fix the rules while you still can — and treat every signal you get back as early intelligence that sharpens your bid/no-bid call, all of it banked on one pursuit record so each shaping move builds on the last.