How to Read and Respond to Sources Sought Notices
How to Read and Respond to Sources Sought Notices: Your Intelligence-Gathering Mission
Listen up. If you’re treating Sources Sought Notices (SSNs) as just another email alert to skim and delete, you’re leaving money on the table and partnerships on the cutting room floor.
I’ve spent twenty-five years in Air Force acquisition—from the flightline to the Pentagon—and I’ve watched thousands of companies miss the boat because they didn’t understand what was actually happening when that “Request for Information” hit the street. You’re not looking at a procurement. You’re looking at reconnaissance. The government is reconning the battlefield, and they want to know if you’re worth fighting beside before they ever write the contracting strategy.
This is tactical execution—the “Do” tier—but it only works if you understand the strategic game being played above it. Let me show you how to read these notices like a Program Manager and respond like a strategic partner.
Strategic Foundations (Think): Understanding the Battlefield
Before you open that SAM.gov link, you need to understand why this notice exists in the first place. Under FAR 10.002,contracting officers conduct market research to determine whether capable sources exist to fulfill requirements—particularly for small business set-asides, socio-economic programs, or innovative commercial solutions.
Here’s the reality: By the time you see a Sources Sought, the government has already decided they have a problem. They haven’t decided how to solve it, who should solve it, or whether industry can even solve it within their constraints. This is the sweet spot. This is where requirements are still clay, not concrete.
From my doctoral work in strategic leadership at Regent University and decades watching requirements evolve, I can tell you this: Influence flows to those who show up early with value. The Sources Sought is your invitation to the requirements development table—if you know how to accept it.
The strategic principle at play here is partnership over product. The government isn’t asking you to sell them something yet. They’re asking, “Can you dance?” Your job isn’t to pitch. Your job is to demonstrate capability, credibility, and commitment to their mission.
Operational Leadership (Lead): Positioning Before the Fight
Before you type a single word in response, you need to lead your organization through the operational preparation. This isn’t about drafting a response—it’s about building relationships that make your response matter.
Map the stakeholders. Who issued this notice? Which Program Office? Who’s the contracting officer? Is there an assigned Small Business Technical Advisor (SBTA)? In my Air Force days, we watched which companies showed up to pre-solicitation conferences and industry days. Those faces became familiar. Familiarity breeds trust, and trust gets you the phone call when the requirement changes—which it will.
Conduct your own market research. Who else is likely to respond? What’s the incumbent situation? If this is a recompete, why is the government looking at other sources? Are there capability gaps they’re trying to fill? This is where strategic patience matters. Don’t just look at this notice in isolation. Look at the last three years of contracts in this space. Look at the agency’s strategic plan. Understand the why behind the what.
Align your internal capabilities. Before you promise the moon in your response, have you talked to your engineers? Your contracts people? Your capture manager? Operational leadership means ensuring your left hand knows what your right hand is offering. Nothing destroys credibility faster than promising capabilities in an SSN response that you can’t deliver in the actual RFP.
Tactical Execution (Do): Reading and Responding
Now we get to the floor. Here’s how you actually execute.
Step 1: Parse the Notice Like a Contracting Officer
When you open that Sources Sought, read it three times with three different lenses:
First read: The Compliance Lens
- What’s the NAICS code? Is it accurate for the work described?
- What’s the size standard? Are you small or large under that standard?
- When is it due? (Government means business on these deadlines.)
- How do they want the response formatted? (Email, portal, specific forms?)
Second read: The Capability Lens
- What are they actually asking for? Look past the buzzwords. Are they seeking IT services? Engineering support? Logistics? Maintenance?
- What’s the scope? Dollar estimate, period of performance, place of performance?
- Are there security clearance requirements? Contract vehicle preferences?
Third read: The Strategic Lens
- Why are they issuing this? Is this headed for a small business set-aside? (If they mention “8(a)” or “SDVOSB” or “HUBZone,” they’re testing the pool.)
- Is this a capabilities assessment for an Other Transaction Authority (OTA) or P-20 agreement?
- Are they fishing for innovative commercial solutions versus traditional defense contracting?
Red Flag Alert: If the notice asks for “white papers” or “technical approaches” but doesn’t specify page limits, that’s a test of your discipline. Can you be concise? Program Managers are drowning in paperwork. Show them you respect their time.
Step 2: Craft the Response
Your response has one job: Prove you exist and you’re capable. It is not a sales pitch. It is a capability statement backed by evidence.
The Structure That Works:
1. Executive Summary (One Page)
- Who you are
- Relevant past performance (cite contract numbers if unclassified)
- Why you’re responding (mission alignment)
- Your socioeconomic status (if applicable to the notice)
2. Technical Capability (Two Pages Max)
- Direct response to their stated needs
- Innovation within constraints: How you solve their problem within the FAR/DFARS framework they must operate in
- Differentiation: What makes your approach unique, not just different
3. Corporate Qualification (One Page)
- Size status certification
- Relevant certifications (ISO, CMMI, etc.)
- Facility clearances if applicable
4. Past Performance (One Page)
- Three relevant contracts
- Points of contact (ask permission first)
- Brief description of scope similarity
Critical Tactical Points:
- Answer the mail. If they ask for capability to support C-130s, don’t tell them about your F-16 work unless it directly translates. Connect the dots for them.
- Use their language. If the notice mentions “Agile DevSecOps,” use that terminology. Don’t force them to translate your commercial speak into government speak.
- Be honest about gaps. If you can’t do 100% of the requirement but can do 80% with a partner, say so. Values-based decision-making means not wasting their time—or yours. In my acquisition career, I remembered the companies that shot straight more than the ones who overpromised.
Step 3:Questions and Engagement
Most SSNs allow questions. Use them strategically. Don’t ask, “When is the RFP coming out?” (They don’t know yet—that’s why they’re doing market research.) Instead ask: “Are you seeking commercial items or developmental solutions?” or “What are the primary performance risks you’re trying to mitigate through this market research?”
If there’s an industry day or one-on-one sessions available, go. Dress appropriately. Bring business cards. Don’t bring swag—it looks desperate. Bring intelligent questions and a notepad.
Step 4: Follow-Up
After submission, send a brief email to the contracting officer: “Submitted our capabilities statement per your Sources Sought notice [ number]. Happy to elaborate on any points or discuss how we might support your mission requirements.”
Then wait. Strategic patience means not calling every three days. They’ll contact you if they’re interested or if the requirement moves to formal solicitation.
The Air Force Buyer’s Perspective
From the other side of the desk, here’s what we’re thinking when we issue these notices:
We’re trying to satisfy our market research requirements to justify a set-aside or validate that full and open competition makes sense. When you respond with generic marketing brochures, you’re wasting everyone’s time. When you respond with specific capabilities aligned to our mission (Air Force, not just “DoD”), you’re entering our Rolodex.
We also watch for innovation within constraints. Can you deliver cutting-edge capability within our funding and regulatory environment? If you suggest something that requires changing the FAR, unless you’re working a Middle Tier Acquisition or OTA pathway, you’re showing you don’t understand our world.
And remember: Program Managers talk. Contracting officers talk. If you submit a sloppy response full of errors, that reputation follows you. If you submit a thoughtful, concise capability statement that demonstrates you read the notice and understand the mission, that follows you too.
Strategic Takeaways: Your SSN Playbook
1. Partners, Not Products You’re not responding to sell a product. You’re responding to establish a relationship. The government is interviewing potential dance partners before the music starts. Show them you can lead when needed and follow when required.
2. Strategic Patience One Sources Sought does not a pipeline make. Build a system to track these, respond consistently over time, and understand that today’s “no capability match” becomes tomorrow’s sole source justification if you’ve maintained contact and demonstrated value.
3. Innovation Within Constraints Don’t propose solutions that require the government to change their procurement regulations unless specifically asked. Show them how to win within the rules they have to play by. That’s true innovation in defense acquisition.
4. Values-Based Positioning If you see that the requirement is poorly written, the NAICS code is wrong, or the scope is unrealistic, say so—professionally. “We note that NAICS code XXXXX may not accurately capture the technical scope described, which appears to align more closely with YYYYY.” That kind of honesty earns respect and positions you as a trusted advisor, not a desperate vendor.
5. Document Everything Every response is a capability statement for your next response. Build a library. Track what works. The companies that win consistently treat government contracting as a craft, not a lottery.
Sources Sought Notices are your early warning radar. They tell you where the government is looking before they commit to a path. Read them strategically, respond operationally, and execute tactically with precision.
Remember: In this business, you’re not just competing for contracts. You’re competing to become indispensable. The Sources Sought is your first chance to prove you’ve got the right stuff.
Now get to work. The acquisition clock is ticking, and your future partners are waiting to see if you’re paying attention.
— Dr. Jesse W. Johnson, DSL, MAOM Founder, Craftsman Leadership