Fixed-price contracts are the federal government's way of telling you: "We're done absorbing surprises." The problem is that someone has to absorb them — and if you bid, that someone is you.
Federal News Network has been covering the fixed-price expansion closely, with one procurement professional recently putting it plainly: the hardest part is defining "done" before a contract is signed and money starts changing hands. That's a polite way of saying most agencies don't actually know what they want — they just want you to be financially responsible for figuring it out.
This isn't an argument against ever bidding fixed-price. It's an argument for knowing exactly when the risk profile makes sense for your firm, and when you're pricing yourself into a loss.
Why the Government Loves Fixed-Price Right Now
The push toward firm-fixed-price (FFP) contracts isn't new, but it's accelerating. Acquisition policy under FAR 16.202 encourages FFP when requirements are well-defined and risk is manageable. The reality on the ground is that contracting officers are under pressure to reduce cost overrun optics — which means pushing price risk downstream to contractors regardless of whether requirements are actually stable.
The GAO has documented this pattern repeatedly in defense acquisition contexts: programs with poorly defined requirements get awarded as fixed-price anyway, and cost growth shows up later as modifications, scope disputes, and protests.
For small businesses, this matters more than it does for large primes. A large integrator can absorb a $2M overrun on a $40M contract. A small business at $3M total contract value cannot absorb the same proportional hit.
The Risk Variables You Have to Price In
Before you commit to a fixed-price bid, you need to quantify four variables — and be honest about what you don't know.
1. Requirements stability. How likely is the scope to shift post-award? Look at the agency's modification history on comparable contracts. If their last three similar efforts averaged two or more significant modifications each, the requirements weren't actually stable — and you'll spend money negotiating mods you shouldn't need.
2. Your cost floor. What's the absolute minimum this effort costs if everything goes right? Not your target cost — your floor. FFP means that if you miss your cost floor estimate, you eat the difference. Build your bid around the floor, not the midpoint.
3. Performance uncertainty. Is there any technical work in this scope you've never done before? Any dependency on a third party, a government-furnished system, or a subcontractor you haven't worked with? Every unknown is unpriced risk on a fixed-price vehicle.
4. Modification leverage. Once you're on contract, how easy is it to get a mod approved? Some agencies have responsive CO teams; others treat modifications as admissions of failure. If you're likely to need mods and the agency culture resists them, your cost floor just went up.
Running the Actual Bid/No-Bid Math
Let's say [Example Federal Solutions] is looking at a $1.8M fixed-price IT services contract. Their estimated cost to perform: $1.4M at the low end, $1.7M if anything goes sideways. That's a $100K–$400K margin range before overhead and G&A.
On the surface, this looks viable. But now apply the variables:
- Requirements stability: The PWS references a system migration that hasn't been fully scoped internally. Risk premium: +$80K minimum.
- Performance uncertainty: The work involves integrating with a legacy system the agency hasn't fully documented. Risk premium: +$60K.
- Modification leverage: This agency has a track record of slow mod approvals based on comparable vehicle history. Risk premium: another $40K in carrying cost.
Suddenly that $100K floor margin has been consumed by unpriced risk. You're bidding breakeven on optimistic assumptions, and a loss on realistic ones.
Plug your own contract parameters into the expected value framework — the math on whether a fixed-price bid is worth the proposal investment changes fast when you stress-test the margins.
This contract has strong expected value at your stated PWin.
Want the realistic PWin for your specific RFP?
RFP Recon analyzes wired-RFP signals, capability fit, and incumbent vulnerability to produce a defensible PWin estimate — not a guess.
Start your first analysis for $75Where Fixed-Price Can Actually Work for Small Business
This isn't a blanket indictment of FFP. There are scenarios where fixed-price favors you.
Mature, repeatable service lines. If you've delivered the same type of work five times and you know your cost structure cold, FFP is a pricing advantage — not a risk. You can underprice competitors who are guessing while you're calculating.
Short performance periods. A six-month FFP task order limits your exposure window. Labor rates don't shift dramatically, inflation risk is minimal, and unknowns have less time to compound. The longer the period of performance, the more FFP punishes you for assumptions that drift.
Tight PWS with acceptance criteria. When the deliverables are genuinely binary — either the software passes UAT or it doesn't — you have a defensible exit. The danger is open-ended service work where the government can always find something more to ask for.
Where you have incumbent knowledge. If you have detailed insight into how the work actually runs — because you're the incumbent or you have a strong teaming relationship with someone who is — your cost estimate is grounded in reality rather than estimation. That's a competitive moat, not just a data advantage. This is the dynamic that drives wired RFP patterns and explains why incumbents win fixed-price rebids at disproportionate rates.
What to Do When the RFP Is Fixed-Price and You're Not Sure
The first move is a pre-solicitation due diligence pass. Before you decide to bid, answer three questions:
-
Has this agency awarded this type of work as cost-reimbursable or T&M before? If yes, why are they switching? A contract type change mid-program-history is a signal worth investigating — it may mean they had cost overruns they want to push to the next contractor.
-
How did the last contractor do? FPDS data on the predecessor contract — specifically whether it was completed on time and whether there were significant modifications — tells you more about the actual difficulty of the work than the PWS will.
-
What's the agency's BD track record on small business contract modifications? Some agencies are genuinely collaborative; others treat modifications as zero-sum negotiations. Talk to anyone who's worked that CO shop.
If after that diligence the math still works, bid it. If the diligence reveals unknowns you can't price, either raise your number to absorb them or walk away. The government's fixed-price preference doesn't obligate you to take on uncompensated risk.
The Walk-Away Calculus
There's a version of this decision that BD teams get wrong consistently: they treat the no-bid option as a failure. It isn't. Walking away from a $2M contract that has a realistic probability of losing $200K is not conservative — it's arithmetic.
The opportunity cost argument cuts both ways. The same proposal team that spends three weeks writing a doomed fixed-price bid could have spent those weeks building a real capture position on a T&M or cost-plus vehicle where their cost structure is competitive and the risk is shared.
Fixed-price contracts punish optimism and reward firms that know their numbers. If you don't know your numbers on this specific requirement, that's your answer.
Frequently Asked Questions
How do I know if a fixed-price contract has poorly defined requirements before the RFP drops?
Look at pre-solicitation activity: RFIs, industry days, and draft PWS language. Vague questions in the RFI and heavy government reliance on contractor input to scope the work are both signals. If the agency is asking industry to help define what "done" looks like, the requirements aren't ready for a fixed-price award.
Is it possible to negotiate contract type on a federal solicitation?
Rarely, but it does happen through the questions-and-answers process. You can submit a formal question arguing that the work scope warrants a different contract type given documented uncertainty. Most COs won't change it, but the question creates a record and occasionally surfaces a draft amendment. More practically, if you can identify specific areas of scope uncertainty, you can request clarification that reduces your risk even if the contract type stays fixed.
How do modifications work on a firm-fixed-price contract when scope changes?
A modification under FAR 43 can adjust the contract price, but the CO has to agree the change is outside the original scope. In practice, the burden is on the contractor to demonstrate the delta — and agencies vary widely in how receptive they are. On FFP contracts, always document every government-directed activity that looks like it might be out-of-scope in real time, not retroactively.
What's the difference between FFP and fixed-price with economic price adjustment (FPEA)?
FPEA contracts (FAR 16.203) include provisions that allow price adjustments tied to specific indices — labor rates, material costs, or published price lists. For multi-year contracts with significant labor or material exposure, FPEA is substantially less risky than pure FFP. If the solicitation doesn't include an economic adjustment clause and the performance period runs two years or more, that's a risk item worth flagging explicitly in your cost model.
Field notes for federal small business contractors. Sharp, direct, and free of the consultant-speak that dominates the GovCon trade press. We help BD leaders allocate proposal capacity better — fewer wasted bids, more wins on the bids that matter.