Here's the thing nobody tells small businesses: by the time a government contract is posted as a formal RFP, it's often already decided in the buyer's mind. Not officially — the competition is real and the rules are followed — but the contracting office usually already has a company (or a short list) it trusts to do the work. The winner is frequently a vendor the office met months earlier. So the real question isn't "how do I write a better proposal?" It's "how do I become the company they already know?" And the answer is: show up before the RFP, during a phase called market research.
The federal buying timeline (and where you can actually influence it)
Most small businesses only ever engage at the very last step. Here's the whole arc, so you can see how much happens before the part everyone fights over:
1. Budget & planning. The agency decides it needs something and sets aside money. (Often visible months ahead in a procurement forecast.)
2. Market research. The office publicly asks the market who can do the work — usually via a Sources Sought notice or a Request for Information (RFI). This is your window.
3. Draft RFP / industry day. Sometimes the office shares a draft and invites feedback or holds an event.
4. The RFP (solicitation). The formal request for proposals drops. The requirements, evaluation criteria, and often the preferred approach are now locked.
5. Evaluation & award. Proposals are scored; the contract is awarded.
By step 4, the game is largely set. The requirement is written — sometimes shaped by whichever vendors engaged at step 2. Steps 2 and 3 are where winners get made. Yet that's exactly where most small businesses are absent.
What is a "Sources Sought" notice?
A Sources Sought notice is the government publicly asking: "Who out there can do this work?" An office posts it on SAM.gov when it has a funded requirement and is doing homework before it competes the contract. There is no bid to win yet and no proposal to write. The office is trying to answer practical questions: Does a healthy field of capable companies exist? Are enough of them small businesses (or veteran-, women-, or HUBZone-owned) to justify a set-aside? How should the contract be structured and priced?
When you respond, you're not bidding — you're raising your hand and saying "we exist, we're capable, and here's proof." That single act puts your company on the buyer's radar while the requirement is still soft clay.
Sources Sought vs RFI vs Presolicitation vs RFP
These notice types confuse everyone. In plain terms:
- Sources Sought — "Who can do this?" Pure market research; the office is gauging capability and small-business interest. Respond with a capability statement.
- Request for Information (RFI) — Similar to Sources Sought, but often asks more detailed questions about approach, pricing ranges, or technical feasibility. Still not a bid.
- Presolicitation — A heads-up that a solicitation is coming soon, usually with a description and expected timeline. Your late-but-still-useful chance to engage the office before the RFP.
- RFP / RFQ (Solicitation) — The real thing: submit a proposal or quote to win. By now, the requirement is fixed.
If you only ever act on RFPs, you're arriving after the requirement — and the relationships — are already formed.
Why responding is the highest-leverage move you can make
- *The buyer wants to hear from you.* This is the one moment in the whole process when a contracting office is actively soliciting introductions. Cold outreach is unwelcome during an open solicitation; during market research it's exactly what they asked for.
- You can shape the requirement. If you flag that plenty of qualified small (or veteran-owned) businesses can do the work, the office may set the contract aside for that group — turning a wide-open fight into one you're positioned to win. Your capabilities can also nudge the technical requirements toward your strengths.
- You start a relationship early. When the RFP finally drops, you're not a stranger — you're the company that was helpful and credible months ago. That familiarity is worth more than any single line in a proposal.
- You learn what's coming. Even if nothing else happens, you now know a real, funded opportunity is on the way, and you can prepare instead of scrambling.
Experienced contractors and their consultants spend real money chasing this exact signal. Most small businesses never see it — because Sources Sought notices are buried in SAM.gov alongside everything else, with short windows and little fanfare.
How to find them on SAM.gov
On SAM.gov's Contract Opportunities search, filter the notice type to "Sources Sought" and "Presolicitation," then narrow by your NAICS and PSC codes and your location. Save the search so new ones alert you. The challenge is volume and timing: there are hundreds across every industry, each with a short response window, and you have to check constantly not to miss the ones in your lane. (This is precisely the kind of monitoring worth automating — more on that below.)
How to respond: the capability statement
A Sources Sought response is not a proposal — don't over-build it. What the office wants is a short, credible capability statement, usually one page, sent by email before the deadline. Include:
- Who you are — company name, UEI/CAGE, location, and your business size and any certifications (veteran-owned, women-owned, 8(a), HUBZone, small business).
- Core capabilities — what you do, stated in the same language as the requirement. Mirror their words.
- Relevant past performance — two or three examples of similar work, ideally for government or comparable clients, with scope and dollar value.
- A clear statement that you can perform this requirement — say it plainly.
- Differentiators — certifications, clearances, contract vehicles, key personnel, or specialized experience.
- Answers to any questions they asked — some notices include specific questions; answer them directly.
Keep the tone factual and confident, not salesy. And if the notice asks questions, answer the questions — officers notice when you don't.
A simple response structure
1. One-line intro: who you are and that you're responding to the specific notice (reference its number).
2. Capability summary matched to the requirement.
3. Two or three past-performance examples.
4. Your size and certifications, and how the office might set the work aside.
5. One or two smart questions that open a conversation.
6. Contact details and a one-page capability statement attached.
Common mistakes to avoid
- Treating it like a bid. It's not. Don't send a 20-page proposal; send a crisp one-pager.
- Being generic. A boilerplate statement that ignores the specific requirement gets ignored back. Mirror their language.
- Skipping the questions. If the notice asks specific questions and you don't answer them, you look like you didn't read it.
- Missing the window. These deadlines are short. Late is the same as absent.
- Never following up. A brief, professional note after you respond keeps you memorable.
What happens after you respond
Sometimes you'll get a reply or a question; often you'll just hear nothing — and that's normal. The value is that you're now known. Watch for the presolicitation and RFP that follow, keep a light relationship with the office where appropriate, and be ready to move fast when the solicitation drops. Occasionally, strong market-research responses even lead the office to a sole-source or set-aside award — the best outcome of all.
How early is "early," and how long does this take?
Be honest with yourself about the timeline. From a Sources Sought notice to a contract award, six to eighteen months is normal, sometimes longer. That's not a reason to skip it — it's the reason it works. The companies that win are the ones who planted the seed months ago while everyone else waited for the RFP. Treat market-research responses as pipeline-building, not lottery tickets: you're investing an hour now for a shot at a contract two or three quarters out. The ones who do this consistently always have something maturing in the pipeline, so they're never dependent on a single bid.
The bigger picture: build a pre-RFP habit
Winning federal work consistently is less about heroics on any one proposal and more about a steady habit: watch procurement forecasts, respond to the Sources Sought notices in your lane, engage the offices that buy what you sell, and be the known quantity when the RFP arrives. It's a longer game — but it's the game the winners are playing. Pair it with disciplined bid/no-bid decisions so your effort goes to the opportunities you actually influenced, and the odds compound in your favor over time.
The catch: seeing them in time, every time
The whole strategy depends on catching the right notices before the window closes — across all your NAICS and PSC codes, every day. That's the part that breaks down when you're running a business. It's exactly what AskTuvo's Buyer Radar automates: it watches SAM.gov for Sources Sought and pre-solicitation notices matched to your industry, surfaces the ones in your lane, and shows you the buyer's contact and how to respond — so you can get in early, the way the pros do.