The White House just made cost-reimbursement contracts politically toxic. Before you celebrate, understand what the shift actually costs you.
Trump's executive order directing agencies to move away from cost-reimbursement toward fixed-price contract structures isn't a procurement technicality. It's a risk transfer — from the government to contractors — and small businesses are the least equipped to absorb that transfer at scale. The question isn't whether this policy will reshape the pipeline. It will. The question is whether you're positioned to benefit or get crushed.
What the Order Actually Does
The directive requires agencies to default toward fixed-price contract types when acquiring goods and services, treating cost-reimbursement as the exception rather than the norm. The stated rationale is budget predictability and accountability — government pays what was agreed, not whatever the contractor spent.
From an acquisition policy standpoint, this isn't novel. FAR Part 16 already establishes a preference hierarchy that favors firm-fixed-price when risk and cost are reasonably estimable. What changes is the political pressure on contracting officers to justify any deviation from that hierarchy. CO discretion on contract type hasn't disappeared — it's just become more expensive to exercise.
That matters because contracting officers will now think twice before writing a cost-plus justification, even when the work genuinely warrants it. The chilling effect on CO judgment is real, and it will show up in solicitations over the next 12-18 months.
Why Small Businesses Should Read This Carefully
The GovCon trade press has generally framed this as a taxpayer-friendly reform. That framing misses the structural implications for smaller contractors.
Cost-reimbursement contracts exist because some work — particularly R&D, system integration, and early-stage program development — has genuinely uncertain scope. When you price fixed-price on uncertain scope, one of three things happens: the contractor pads the estimate to cover risk, the contractor wins low and eats losses, or the contractor wins low and delivers degraded work. None of those outcomes serve the government well, but they're particularly dangerous for small businesses without capital reserves to absorb a bad job.
Fixed-price contracts shift schedule and cost risk to the contractor. Large primes with diverse portfolios can absorb a bad contract. A small business running 3-4 active task orders cannot. One underpriced FFP on a complex integration effort can wipe out margin from your other work.
Consider the scenario: a [Civilian Agency] issues an FFP solicitation for a system modernization effort that historically would have been cost-plus. The scope is ambiguous — legacy architecture isn't fully documented, data migration complexity is unknown. You estimate 8,000 hours. The work takes 12,000. Under cost-reimbursement, you'd recover actual costs. Under FFP, you just donated 4,000 hours to the federal government.
This scenario is not hypothetical. It's the predictable outcome when acquisition policy mandates contract type before the scope is understood.
Where the Real Risk Concentrates
Not all work is equally affected. The shift hits hardest in three areas:
IT modernization and integration. Scope uncertainty is endemic. Legacy systems are often undocumented. Data quality is unknown until you're in it. Cost-reimbursement has historically been the appropriate vehicle for this work. Expect agencies to try to FFP it anyway, and expect contractors to either pad bids heavily or underestimate and suffer.
Research and advisory services. When the deliverable is analysis, recommendations, or emerging technology work, outcomes are genuinely hard to specify in advance. FFP forces artificial specificity into PWS language that doesn't match how the work actually flows.
Rapid response and surge work. Task orders under IDIQs that get pulled for urgent agency needs — where timelines and scope are compressed — carry inherent execution risk that fixed pricing doesn't accommodate well.
Work that is already well-suited to fixed-price — commodity IT, staffing augmentation with defined hours, defined deliverables with stable requirements — will see less disruption. If your business is concentrated in those categories, this order may actually work in your favor by standardizing what was already your operating model.
The Bid/No-Bid Signal This Creates
Here's the contrarian read: this order actually makes wired RFP signals easier to spot in certain acquisition categories.
When an agency issues an FFP solicitation for work that is clearly unsuitable for FFP — complex integration, undefined requirements, novel technology — that's a signal. Either the contracting officer doesn't understand the work, or the incumbent has already scoped it and the RFP is a formality. In the first case, the risk to you is execution. In the second case, the risk is wasted proposal spend.
Either way, your bid/no-bid calculus just got a new filter: Is this work actually priceable at a fixed amount by anyone who doesn't already know the environment? If the answer is no, and the solicitation is FFP anyway, you have two likely explanations — neither of them good for a non-incumbent bidder.
Add contract type mismatch to your qualification checklist. If an FFP solicitation covers work with high scope uncertainty and you're not the incumbent, the pricing risk and the structural disadvantage compound each other. That's two strikes before you write a word.
How to Position for the New Environment
Get good at scope decomposition. The contractors who will win and survive in an FFP-dominant environment are the ones who can slice ambiguous work into defensible fixed-price components. That's a skill set — in proposal writing, in program management, and in how you structure your teams. If your capture process doesn't include a serious scope risk assessment before pricing, build one now.
Use the pre-solicitation window harder. When you see an RFI or Sources Sought for work that you suspect will go FFP, engage aggressively. Attend industry days. Submit detailed questions. The more you know about the actual environment before the RFP drops, the better your pricing will be relative to competitors who are estimating blind. This is where federal BD tactics around pre-solicitation engagement pay direct financial dividends — not just relationship-building, but risk reduction.
Price risk explicitly, not emotionally. A lot of small business pricing is optimistic by default — teams want to win, so they shade estimates low. In a cost-reimbursement world, that optimism is partially protected by the contract type. In an FFP world, optimism is a liability. Build contingency into your estimates with documented rationale. If you lose on price to a competitor who priced with unrealistic optimism, that's their problem, not yours.
Watch the deviation patterns. As this policy takes effect, track which agencies are still writing cost-reimbursement justifications and for which work types. According to usaspending.gov, you can filter awards by contract type. The agencies that continue to use cost-reimbursement after the order — and the contract vehicles they use to do it — are telling you something about where scope uncertainty is acknowledged by the acquisition community. That's where your particular expertise may be better valued.
The Inconvenient Truth About Who Benefits
Large integrators benefit most from this shift. Not because FFP is inherently better for primes — it isn't — but because they have the capital reserves, subcontractor management infrastructure, and historical cost data to price fixed-price work more accurately than smaller competitors. When a prime has run twenty similar integration projects, their FFP estimates are calibrated. When a small business is estimating a new customer environment from scratch, they're guessing more than they know.
The policy is framed as accountability and efficiency. The structural effect in competitive acquisitions may be to further entrench firms with deep cost history on similar work. That's not an argument against the policy. It's an argument for being clear-eyed about how it changes your competitive position — and for being selective about which FFP opportunities you're actually equipped to price and execute.
The fixed-price shift is real, it's accelerating, and it will separate contractors who understand their own cost structures from those who don't. Know which one you are before the next solicitation lands.
Frequently Asked Questions
Does the executive order eliminate cost-reimbursement contracts entirely?
No. The order creates a default preference for fixed-price, not a ban. Contracting officers retain authority to use cost-reimbursement when justified. What changes is the political and administrative cost of making that justification — expect COs to default to FFP more often even when cost-reimbursement would be technically appropriate.
Which contract types are most affected by this shift?
Cost-plus-fixed-fee (CPFF) and cost-plus-incentive-fee (CPIF) vehicles for services and IT work face the most pressure. Time-and-materials contracts are also likely to come under scrutiny, as they share some characteristics with cost-reimbursement in terms of cost risk transfer to the government.
If I'm an incumbent on a cost-reimbursement contract, what happens at recompete?
Your recompete may be structured as FFP even if the current contract is cost-plus. That means you need to convert your historical cost data into a defensible fixed-price estimate — which you're better positioned to do than any competitor, since you know the environment. Use that advantage aggressively in your pricing and in your technical approach to show you've already mitigated the unknowns.
Is this shift permanent or likely to reverse with the next administration?
Executive orders on acquisition policy can be rescinded, modified, or ignored in practice faster than FAR rule changes. But the underlying political logic — fixed-price as accountability signal — has bipartisan appeal and responds to real frustrations with cost overruns. Treat it as durable enough to shape your pipeline strategy for the next 2-3 years, while staying alert to how strictly individual agencies actually implement it.