5 Smart Lessons from the FAR Part 10 Rewrite: What Contractors Need to Know About Market Research

Most government contractors think market research is something that happens to them. They wait for a sources sought notice, submit a capability statement, and hope for the best. But here's the problem: by the time you're responding to that notice, the contracting officer has already started forming opinions about what the requirement should look like, who can do the work, and how much it should cost. If you're not positioned early, you're not recovering lost ground during the proposal phase. You're starting from behind.

Recent updates to FAR Part 10 guidance have fundamentally changed how contracting officers are expected to conduct market research. The emphasis is now on earlier engagement, more rigorous documentation, and better-informed acquisition decisions. For contractors, this isn't just a procedural update. It's a strategic opening. If you understand what contracting officers are now required to do and why, you can align your business development strategy to meet them exactly where they need help.

This article reverse-engineers those changes. Instead of listing what's new in FAR Part 10, we're translating government-side obligations into contractor-side actions. Think of it this way: if you know what test questions the teacher has to answer, you can study smarter. The same logic applies here.

Lesson 1: Understand What Changed and Why Contracting Officers Are Under New Pressure

FAR Part 10 has always required market research, but updated guidance now emphasizes depth, timing, and documentation. Agencies are pushing contracting officers to conduct market research earlier in the acquisition lifecycle, gather more detailed capability and pricing data, and document their findings in ways that support downstream decisions like contract type selection and evaluation criteria.

Why the push? Because poor market research leads to bad requirements, unrealistic budgets, failed competitions, and protests. Agencies want contracting officers to make defensible, data-driven decisions before they ever draft a solicitation. That means COs need industry input that's clear, accurate, and useful.

Here's what this means for you: if a contracting officer is under pressure to gather better data, your job is to provide it. When you help the CO build a smarter acquisition strategy, you're not just being helpful. You're positioning your firm as the logical solution before anyone else even knows the opportunity exists.

Lesson 2: Move Your Capture Timeline Earlier Than You Think

Updated FAR Part 10 guidance encourages market research before requirements are finalized. That's the key phrase: before finalization. By the time a request for proposals hits the street, the scope, budget, and evaluation priorities are already locked in. The opportunity to shape those decisions happens during market research, not after.

Think of it like house hunting. By the time you walk into an open house, the seller has already decided on the price, what stays and what goes, and what kind of buyer they're hoping to attract. If you want to influence those terms, you need to show up earlier—maybe during the pre-listing consultation. Market research is that pre-listing phase for government contracts.

Start monitoring for sources sought notices, requests for information, and industry day announcements as early as possible. Set up automated alerts using SAM.gov and agency forecast tools. If you wait until the RFP drops, you're reacting to decisions that were made weeks or months earlier. Early engagement allows you to help shape the requirement in ways that align with your capabilities.

Lesson 3: Stop Treating RFIs Like Mini-Proposals

Contracting officers issue RFIs and sources sought notices to answer specific questions. Can anyone actually do this work? What will it realistically cost? What's the right contract type? Are there enough small businesses with relevant experience? They're not evaluating your marketing materials. They're testing assumptions and gathering data.

Yet many contractors respond with generic capability statements, boilerplate corporate overviews, and sales language that doesn't answer the government's actual questions. This wastes everyone's time and, more importantly, it makes you invisible. If your response doesn't help the CO make a better decision, it won't be remembered.

Here's what to include instead. Answer the real questions directly. If the RFI asks about your technical approach, describe it in plain terms with realistic timelines. If it asks about pricing, provide rough order of magnitude estimates with clear assumptions. If it asks about past performance, cite specific contracts with relevant scope, not every contract you've ever won. Be concise, be honest, and be useful. That's what gets remembered when the acquisition strategy is being written.

Lesson 4: If You Are a Small Business, Use New Documentation Requirements to Your Advantage

One of the most significant changes in updated FAR Part 10 guidance is the emphasis on documenting small business considerations. Contracting officers are now expected to clearly justify their socioeconomic set-aside decisions, including why they did or did not pursue an 8(a), HUBZone, SDVOSB, or WOSB set-aside.

This creates an opportunity. If you're a small business, your job during market research is to make it easy for the contracting officer to justify a set-aside in your favor. That means providing clear, specific evidence that you can perform the work at a fair and reasonable price, on schedule, and with acceptable risk.

Don't just say you're capable. Show it. Reference similar past performance. Explain your teaming strategy if you're using one. Provide enough detail that the CO can confidently write in the acquisition plan that a set-aside is appropriate because qualified small businesses exist and have demonstrated relevant experience. Silence or vague responses do the opposite: they give the CO a reason to go full and open because they can't document viable small business capability.

Lesson 5: Treat Industry Days and One-on-One Meetings as Intelligence Gathering, Not Sales Pitches

Market research events are two-way conversations. Yes, the government is learning about industry capabilities, but you should be learning just as much about the government's priorities, constraints, and concerns. If you show up to an industry day with a slide deck full of corporate achievements and zero questions, you're missing the point.

Listen for clues about scope uncertainty, budget realities, risk tolerance, and evaluation priorities. Pay attention to the questions other attendees ask and how the government responds. Notice what the program office emphasizes versus what the contracting officer emphasizes. These details reveal what matters most when the solicitation is drafted.

Ask questions that demonstrate expertise and help the government clarify its thinking. For example: "Have you considered a phased approach with an initial prototype period?" or "What's your biggest concern about transitioning from the incumbent?" These questions show you understand the complexity of the requirement and you're thinking strategically. They also help you gather intelligence that will sharpen your capture plan and proposal strategy later.

Lesson 6: Understand What the Government Is Documenting and Why It Matters

During market research, contracting officers are building documentation that feeds directly into the acquisition plan. That documentation includes capability assessments, pricing analysis, small business availability, commercial item determinations, and risk evaluations. Every piece of input you provide during market research can end up in that documentation, influencing contract type selection, evaluation criteria, and competitive strategy.

Here's the critical insight: your input during market research has more influence than your proposal narrative later. Once the solicitation is released, the rules are set. The evaluation criteria, the scope, the contract type—all of it is locked in. But during market research, those decisions are still being made. If you provide useful data that helps the CO choose a contract type that aligns with your strengths, or write evaluation criteria that emphasize your differentiators, you've already tilted the playing field before the competition officially begins.

When contractors are absent or unhelpful during market research, the government fills in the gaps with assumptions, outdated information, or input from competitors who did show up. You can't recover from that gap later. By the time you submit a proposal, you're fighting against a framework that someone else helped design.

Practical Application: A Real-World Scenario

Imagine a contracting officer at a Department of Defense installation is preparing to acquire IT infrastructure support services. She's required under updated FAR Part 10 guidance to conduct thorough market research before finalizing the acquisition strategy. She issues a sources sought notice asking for information about small business capabilities, realistic pricing, and technical approaches.

A small business responds with a detailed two-page summary. It includes three relevant past performance examples with contract numbers, period of performance, and scope. It provides a rough order of magnitude estimate with clear assumptions about labor categories and materials. It identifies a teaming arrangement with a subcontractor for specialized hardware support. It even suggests a hybrid contract type—firm-fixed-price for routine services and time-and-materials for on-call support—and explains why that structure reduces risk for both parties.

The contracting officer uses this input to draft the acquisition plan. She documents that qualified small businesses exist and can perform the work. She justifies a small business set-aside. She selects the hybrid contract type the contractor suggested because it makes sense. When the RFP is released, the small business that provided useful input is now competing under a structure it helped design. It's not a guarantee of winning, but it's a significant strategic advantage.

Now imagine the opposite. The same sources sought notice is issued, but this time the small business either ignores it or submits a generic capability statement with no pricing data, no relevant past performance details, and no thoughtful input. The contracting officer can't document viable small business capability. She defaults to a full and open competition because she has no evidence to justify a set-aside. When the RFP drops, the small business is now competing against large businesses, under evaluation criteria it had no hand in shaping, and with no early relationship with the government. It's an uphill battle that didn't have to be.

Why This Matters

Market research is not something that happens to you. It's a strategic phase where you can actively shape the outcome. The recent updates to FAR Part 10 have increased the pressure on contracting officers to conduct more rigorous, earlier, and better-documented market research. That pressure creates opportunity for contractors who understand what the government needs and are willing to provide it.

When you show up early, provide clear and useful information, and help contracting officers make defensible decisions, you do more than build goodwill. You position yourself as the solution the government is designing the requirement around. You influence contract type selection, evaluation criteria, and competitive strategy before your competitors even know the opportunity exists.

The contractors who win consistently aren't just good at writing proposals. They're good at shaping the conditions under which proposals are evaluated. They understand that the real competition doesn't start when the RFP drops. It starts during market research, when the rules of the game are still being written. If you're not playing at that stage, you're not playing to win.