The Real Question Isn't the Contract Type. It's Who Eats the Surprise.
Every acquisition class eventually gets to the moment where someone says "cost-plus" and someone else says "fixed-price" and the room gets quiet, because everyone senses this matters but not everyone can say exactly why. Here's the plain version: a contract type is really just an answer to one question. If this thing costs more than we thought, who pays for the difference?
That's it. That's the whole ballgame. Everything else, the fee structures, the incentive arrangements, the audit requirements, is just plumbing built around that one decision. Get the risk allocation wrong and you either overpay for certainty you didn't need, or you hand a contractor an impossible bet and watch the program collapse when reality shows up.
Get the Acqlerate Acquisition Starter Kit (Free)
Key terms, ACAT levels, career roadmaps, and the 5 most common acquisition mistakes. Tailored to your role, USG, contractor, or career changer.
The Menu: What You're Actually Choosing Between
Strip away the acronyms and there are really two families, with some hybrids in between.
- Firm-fixed-price (FFP): You agree on a price up front. The government pays that price no matter what it actually costs the contractor to deliver. If the contractor is efficient, they keep the difference as profit. If they blow the estimate, that's their problem, not yours.
- Cost-plus-fixed-fee (CPFF): The government reimburses the contractor's actual allowable costs, plus a fee that was agreed to in advance and doesn't change much regardless of how the costs shake out. If costs run higher than expected, the government pays more. The contractor's fee stays roughly flat either way.
- Cost-plus-incentive-fee (CPIF): Same reimbursement of actual costs, but the fee slides up or down based on how actual costs compare to the target. Underrun the target and the contractor's fee grows. Overrun it and the fee shrinks. Risk is shared, on a formula both sides agreed to ahead of time.
- Fixed-price-incentive-firm (FPIF): A fixed ceiling price with a share line underneath it. Costs below target get split between government and contractor at an agreed ratio. Above the ceiling, the contractor is fully on the hook. It's the middle child of the family, part fixed-price discipline, part cost-plus flexibility.
| Contract Type | Who Bears Overrun Risk | Best Fit For |
|---|---|---|
| Firm-Fixed-Price | Contractor, almost entirely | Mature tech, production runs, well-understood requirements |
| Fixed-Price-Incentive | Shared, contractor pays past ceiling | Moderate uncertainty, some cost history to anchor a target |
| Cost-Plus-Incentive-Fee | Shared via fee formula, government pays actual cost | Real technical risk, but a target estimate is still credible |
| Cost-Plus-Fixed-Fee | Government, almost entirely | Early R&D, prototyping, requirements nobody can price yet |
Why the Government Doesn't Just Always Pick Fixed-Price
Every acquisition professional has heard someone insist "just make it fixed-price, that protects the taxpayer." It sounds right. It's also wrong often enough to matter. Fixed-price only works when someone can actually estimate the cost with confidence. Ask a contractor to commit to a firm number for something that's never been built before, and one of two things happens. Either they pad the price so heavily to cover their risk that you overpay for certainty, or they lowball it to win, then either eat a brutal loss, cut corners, or come back begging for a modification. None of those outcomes serve the mission.
This is why the rules push contracting officers to match the contract type to how well-understood the work is, not to some blanket preference. Early-stage research, where nobody knows if the physics even cooperates, sits naturally in cost-plus territory. A production run of a design that's flown for five years belongs in fixed-price territory. The mistake is treating contract type as a values statement ("fixed-price is disciplined, cost-plus is wasteful") instead of a risk-transfer tool matched to actual uncertainty.
The single biggest tell that a contract type is mismatched to reality: constant contract modifications. If a "firm" fixed-price contract keeps getting re-priced through change orders, that's not a pricing failure, that's a sign the requirement was never mature enough for fixed-price in the first place.
The Political Pressure Toward Fixed-Price (and Why It's Not That Simple)
If you've been in this field more than a few years, you've watched the pendulum swing hard toward "fixed-price whenever possible." That instinct isn't new, it's been Pentagon orthodoxy in one form or another for over a decade, and it's picked up fresh energy from newer commercial entrants who build software and hardware fast and simply refuse to run their books the way traditional cost-plus accounting demands. Their argument, roughly: why should a company with a clean product and a real price tag submit to the audit overhead built for defense-only cost-reimbursement contractors?
That argument has real merit for mature, well-understood work. It falls apart the moment you apply it to genuine frontier R&D. You cannot firm-fixed-price your way through a problem nobody has solved yet, no matter how confident the sales pitch sounds. The honest version of this debate isn't "cost-plus bad, fixed-price good." It's "we've been defaulting to cost-plus out of habit on things that are actually mature enough for fixed-price, and we should stop doing that." Those are very different claims, and conflating them leads to bad contract decisions in both directions.
Module: Defense Contracting Fundamentals
This post touches on concepts covered in depth in the Defense Contracting Fundamentals module. Contract types, source selection, IDIQs, GWACs, modifications, and the COR role.
Start This Module Free →What This Actually Means for You
- If you're on the government side: Resist both the reflex to default to cost-plus because "that's how we've always done this program" and the political pressure to slap fixed-price on something genuinely uncertain just to look disciplined. Ask honestly: can this be priced with confidence right now? The answer, not the mood of the moment, should drive the choice.
- If you're on the contractor side: Understand that a cost-plus award isn't a blank check, it comes with real accounting system scrutiny and audit exposure you need to be built for. And a fixed-price award isn't free money either, it means you own the downside if your estimate is wrong. Know which bet you're actually making before you sign.
- For both: Watch how a program's contract type evolves over its life cycle. A smart acquisition strategy often starts cost-plus during design and shifts toward fixed-price as the design matures and the unknowns shrink. If that shift never happens, that's worth asking about.
The contract type on the cover page tells you more about a program's actual risk posture than almost any other single data point. Learn to read it, and you'll understand what's really going on long before the budget briefings catch up.
Contract Type Selection Summary
| Contract Type | Risk Allocation | Best Used When | Contractor Upside/Downside |
|---|---|---|---|
| Firm Fixed Price (FFP) | All on contractor | Well-defined scope; low technical risk | Full profit if efficient; loss if over budget |
| Fixed Price Incentive (FPIF) | Shared up to ceiling | Moderate risk; want to incentivize efficiency | Earn more if under target cost |
| Cost Plus Fixed Fee (CPFF) | All on government | High tech risk; R&D; requirements unclear | Low profit; no downside; DCAA oversight |
| Cost Plus Incentive Fee (CPIF) | Shared via share ratio | High risk with measurable outcomes | Earn more fee for better performance |
| Time & Materials (T&M) | Mostly on government | Uncertain hours; labor-intensive services | Billed at ceiling rates; ceiling is max |