FFP has been an available option for federal contracting officers for as long as anyone in this industry can remember. It's not a new invention. What the new executive order actually does is invert the default. Instead of agencies choosing FFP when conditions warrant it, they now have to justify going the other direction. That inversion sounds minor. In practice, it changes the institutional pressure inside every acquisition office in the federal government, and that pressure eventually reaches every contractor that depends on T&M and cost-reimbursement vehicles for the majority of their revenue.
The order also pushes toward outcomes-based performance standards, which is worth dwelling on separately from the contract type question. Outcomes-based contracting means a contractor has to define what they will deliver, not just how many people they will bring to bear on the problem. These two shifts together — fixed price and defined outcomes — constitute a fairly fundamental rethinking of how the Government buys technology services. And understanding why that's difficult for most of the industry requires being honest about what the old model actually rewarded.
What T&M Actually Incentivizes
Under a Time and Materials contract, a contractor's revenue scales with hours billed. This is not a subtle point, but it gets obscured in industry discussions because stating it plainly makes everyone uncomfortable. The contractor earns more money by billing more hours. The fastest path to revenue growth is not delivering better outcomes faster — it's maintaining a larger workforce billing against the contract over a longer period of performance. This doesn't require bad intent on anyone's part. It's just what the incentive structure produces when it's left to run.
The government historically accepted this arrangement for a reasonable reason: T&M provides flexibility. When requirements change mid-program — and in complex national security programs, they always do — a T&M contract can absorb that change without triggering a formal modification cycle. The cost of that flexibility is that nobody has a strong structural reason to finish the work. Programs that were scoped for 18 months run for five years. Deliverables that were supposed to modernize a capability become perpetual support arrangements. The contractor grows the team not because the work demands it, but because growth is how you signal investment and the Government program manager feels appropriately supported.
The result, visible in most large Government programs if you look honestly at the staffing, is teams that are significantly larger than the mission requires, with a meaningful share of effort going toward overhead activities — coordination meetings, status reporting, program management layers — that exist to manage the complexity of a large team rather than to advance the work itself. The people are usually qualified. The problem is that nobody ever asked how few people it would actually take to deliver the outcome. That question wasn't relevant under the old model.
Why Repricing Doesn't Solve It
The industry's instinctive response to the FFP mandate will be to treat it as a pricing problem. The work is the same; we'll restructure the billing. This misunderstands what FFP actually requires. Fixed-price contracting transfers scope risk from the Government to the contractor. That means you have to be able to define scope precisely before you start, staff to what the work genuinely requires rather than what the contract ceiling allows, and build delivery processes that can absorb requirement changes without blowing a fixed price you already committed to. For organizations that have spent three decades building the opposite muscle — staying flexible, growing headcount, keeping the work in motion — that's a capability they don't have.
The talent dimension compounds this. The professionals who have built careers in large T&M programs tend to be good at different things than the ones who thrive under fixed-price delivery. Large T&M environments reward thoroughness, process adherence, institutional knowledge, and careful documentation. Fixed-price delivery rewards precise scoping, rapid iteration, and the capacity to do more with a smaller team. Those are learnable skills, but they're not the skills that get you promoted in a system optimized around billable hours, and organizations don't retrain their workforces quickly.
There's also a structural financial problem for the large system integrators specifically. A significant portion of their overhead — facilities, program management infrastructure, recruiting pipelines, BD apparatus — is built to support large headcount programs billed at cost. When the Government signals it wants smaller, outcome-focused teams on fixed-price vehicles, that overhead structure becomes a liability. You can't price competitively against a leaner contractor while carrying an overhead rate calibrated for a T&M world.
What the Shift Actually Demands
If you think through what FFP and outcomes-based contracting require from a contractor, a picture emerges that looks very different from the traditional GovCon delivery model. You need to be able to scope work precisely. You need teams that are assembled around the mission rather than around a labor category table. You need delivery processes that compress timelines, because time is your cost exposure on a fixed-price engagement. And increasingly, you need AI-enabled workflows and human-machine teams, because those are what make it economically viable to deliver at the pace and price point that competitive FFP pricing demands. Efficiency isn't something you sacrifice to stay flexible. It becomes the primary competitive lever.
- Precise scoping — You must define deliverables before work begins, not discover them through months of engagement.
- Mission-assembled teams — Staffing to what the work requires, not what the ceiling allows or what signals commitment to a program manager.
- Compressed timelines — Time is your cost exposure on FFP. Speed and discipline are structural advantages, not nice-to-haves.
- AI-enabled delivery — Human-machine teams that can deliver what a larger traditional team would take twice as long to finish, at a price point that pencils out on fixed price.
This matters because it changes what kind of contractor performs well in the new environment. The differentiator isn't scale or breadth of contract vehicles or how many program managers you can put on-site. It's the ability to define an outcome clearly, assemble a small team with the right combination of domain expertise and technical capability, and move from problem to delivered solution faster than a larger organization can. That combination — mission SMEs working alongside engineers and AI tooling in a tight, accountable unit — is what our MAX Factory model is built around.
We didn't design it for the FFP mandate. We built it because we thought it was the right way to serve government customers, and because the bloated alternative consistently leaves customers with solutions that are expensive to sustain and hard to evolve without calling the contractor back in. It is also a direct outgrowth of our founders' small operational unit mindset, where close-knit collaboration under pressure delivers results for high-consequence missions.
The mandate doesn't change how we work. But it does clarify why the way we work matters, and it changes the competitive environment for customers who are now empowered to ask different questions when they evaluate proposals. Questions like: what exactly will you deliver, and by when? How many people does this actually require? What happens if scope shifts? Those are better questions than what most Government acquisitions have historically been structured to ask, and they tend to produce better answers from contractors who have been operating with those constraints all along.
See if MAX Factory fits your next acquisition
If you're working through what your next acquisition looks like under the new environment — or trying to understand whether your current contractor structure is positioned to perform under it — we'd welcome the conversation.