Fixed Price vs Time and Materials: Which Contract Fits Your Software Project?
The contract type decides who pays when the estimate turns out wrong. Five models compared, a decision table by the state of your project and the six clauses to write down before you sign.

Key takeaways
- Under a firm-fixed-price contract the contractor carries maximum risk and full responsibility for all costs (FAR 16.202-1); under time and materials the buyer carries it, because the contractor has no profit incentive to control cost (FAR 16.601).
- Executive Order 14402 of April 30, 2026 made fixed price the default for US federal contracts, while the 18F De-risking Guide (2024) advises time and materials with a not-to-exceed ceiling for custom software.
- In a sample of 1,471 IT projects the average cost overrun was 27%, and one project in six ran over by 200% on average (Flyvbjerg and Budzier, Harvard Business Review, 2011).
- A cap limits what you pay, not what you get: under FAR 52.232-7 the contractor warns the buyer before spend passes 85% of the ceiling and does not have to keep working above it.
- In a study of 785,326 small marketplace projects, choosing a bid 25% below the average came with a 9% increase in the frequency of failures at the same provider skill (Jørgensen, 2013).
Sign a fixed price when the scope is written, stable and testable. Pay for time and materials with a written ceiling when the scope will change once users see the product. The contract type decides who carries the risk of a wrong estimate: in US federal rules a firm-fixed-price contract "places upon the contractor maximum risk and full responsibility for all costs", while time and materials "provides no positive profit incentive to the contractor for cost control or labor efficiency" (FAR Part 16, sections 16.202-1 and 16.601). For a new product, the safer route is usually a mix: a small fixed-price discovery, then the build under the model its result supports.
This guide is for founders and business owners in the US and the UAE who are comparing quotes from studios and agencies. Inside: five pricing models, who carries which risk, a decision table, the hybrid route, six contract clauses and red flags. Definitions come from the Federal Acquisition Regulation (FAR), the US government's purchasing rulebook. Your contract is private, so read the FAR as a public dictionary, not as a law that applies to you.
Software development pricing models: the five you will be offered
- Fixed price. One price for an agreed result. The FAR calls it firm-fixed-price: "a price that is not subject to any adjustment" for what the work ended up costing.
- Time and materials (T&M). You pay for hours worked at fixed hourly rates that already include wages, overhead and profit, plus materials at cost: hosting, licenses, paid APIs.
- T&M with a cap (not-to-exceed, NTE). The same, with "a ceiling price that the contractor exceeds at its own risk".
- Milestone-based fixed price. The work is cut into pieces, each with its own price, result and acceptance. In the US government's guide to buying digital services, line items "may be structured by iterations (sprint cycles)" (TechFAR Hub).
- Retainer or dedicated team. A fixed monthly fee for named people or a block of hours. The closest FAR type is the level-of-effort contract: "a specified level of effort, over a stated period of time, on work that can be stated only in general terms".
Design is priced the same way: see our UI/UX design cost guide.
Fixed price vs time and materials: who carries the risk?
Under a fixed price, the studio pays for a wrong estimate. Under time and materials, you do. The other three models split that risk.
Five contract models by who carries the risk. Definitions from FAR Part 16 and the TechFAR Hub. Checked November 20, 2026.
| Model | Who pays if the estimate is wrong | What you must prepare | How a change is handled |
|---|---|---|---|
| Fixed price | The studio, inside the written scope | A detailed scope and acceptance criteria | A change request with a new price and date |
| Time and materials | You | A prioritized backlog and a person who decides weekly | You reorder the backlog |
| T&M with a cap | You, up to the cap; above it work stops until you agree | A scope and a cap per milestone | Above the cap, your written approval |
| Milestone fixed price | The studio inside a milestone; you for the number of milestones | A clear result for the next milestone | Changes wait for the next milestone |
| Retainer or dedicated team | You: the fee buys effort, not a result | A steady flow of tasks | You change priorities any day |
The same five models during the work. The middle column follows the same definitions; the last column is NextGenSoft's assessment. Checked November 20, 2026.
| Model | What you see during the work | Where it usually goes wrong |
|---|---|---|
| Fixed price | Results at acceptance, unless the contract adds demos | Disputes over what was in scope; quality cut to save margin |
| Time and materials | Timesheets, demos, the repository | The total drifts when nobody checks it |
| T&M with a cap | The same, plus spend against the cap | The cap is reached, the work is not finished |
| Milestone fixed price | A working result at every milestone | Milestones describe activity, not a result |
| Retainer or dedicated team | A monthly report of hours and tasks | Paid capacity sits idle, or unused hours expire |
The US government has argued both sides. On April 30, 2026, Executive Order 14402 said fixed-price contracts "should serve as the default and preferred method of procurement", and a time-and-materials contract now "must be justified in writing by the contracting officer to the agency head". The order covers all federal buying, not software in particular.
For custom software, the government's own digital team advised the opposite. 18F, part of the US General Services Administration until 2025, wrote that "a T&M contract protects the government's financial and performance interests better than other contract types" (18F De-risking Guide, 2024 edition, kept online as an archive). Its reasoning: the vendor bills only for time worked, and a buyer who stops will "still own the software that has been delivered up to that point". Both positions rest on one test: how well can the work be defined before it starts?
In a sample of 1,471 IT projects, the average cost overrun was 27%, but one project in six ran over by 200% on average, with a schedule overrun of almost 70% (Flyvbjerg and Budzier, Harvard Business Review, September 2011). The study covers IT projects in general, not startup builds, so read it as a direction. The contract model decides whose money that one-in-six case burns.
Nor does a fixed price buy a lower risk of failure. A 2017 paper found fixed-price contracts connected with a higher risk of failure than time-and-materials types, in small outsourced jobs worldwide and in Norwegian public-sector projects (Jørgensen, Mohagheghi and Grimstad, International Journal of Project Management). That is a connection, not proof of cause.
Fixed price contract for software development: when does it work?
It works when the studio can price the risk at the start. The FAR test: fixed price fits when "the risk involved is minimal or can be predicted with an acceptable degree of certainty". In software that means a marketing site with an agreed page list, a migration or an integration with documented APIs. Our website cost guide shows how such a scope is counted. Three things come with it.
The price is fixed for the written scope, not for the product in your head. Anything unwritten is a change. Even the government's standard fixed-price clause gives the contractor "an equitable adjustment in the contract price, the delivery schedule, or both" when the buyer changes the work (FAR 52.243-1). So the scope is your job; start with our one-page brief template.
You pay for the risk. A studio that fixes a price adds a buffer for what it cannot see. The TechFAR Hub warns that "forcing a FFP arrangement could force the contractor to build in unnecessary contingencies" (FFP is firm-fixed-price). Our iOS app cost guide shows how to read that buffer.
The incentive is to finish. When the hours run out, the studio's margin is at stake, and the cheapest savings are the ones you cannot see: fewer tests, no documentation. So write acceptance criteria you can check yourself.
Time and materials contract: what are you paying for?
You pay for hours at agreed rates and may change your mind without paperwork. The FAR allows this type only when it is "not possible at the time of placing the contract to estimate accurately the extent or duration of the work". That describes most new products.
The same section names the weakness: with no profit incentive to control cost, the FAR requires "appropriate Government surveillance". For a private buyer, that means three habits:
- Timesheets with every invoice. The federal payment clause makes the contractor substantiate each invoice; daily timekeeping records come first on its list (FAR 52.232-7).
- A demo of working software every one or two weeks.
- Access to the repository from day one.
T&M also needs a person on your side who sets priorities every week. Open T&M, with no ceiling, suits a team you already trust.
Capped time and materials (not-to-exceed): how does the ceiling work?
A cap limits what you pay. It does not promise a finished product. The federal payment clause says both halves: the buyer "will not be obligated to pay the Contractor any amount in excess of the ceiling price", and the contractor "shall not be obligated to continue performance if to do so would exceed the ceiling price" (FAR 52.232-7).
Write three things next to the number.
- What the cap covers. A named milestone with a result, not "development".
- An early warning. In the federal clause, the contractor must notify the buyer when it expects to pass 85% of the ceiling within the next 30 days, and send a revised estimate. Copy the idea.
- What happens at the cap. You choose: cut scope, raise the cap in writing or stop and keep everything delivered so far.
Milestone-based fixed price: can you fix the price sprint by sprint?
Yes. The TechFAR Hub describes it for agile work: the price of an iteration is fixed, and what it includes is defined in advance. The studio carries the risk inside a milestone; you carry the risk of how many milestones the product takes.
It works only if every milestone ends in something you can open and accept: a working sign-up flow, a live page. "Backend 50% done" is not a milestone.
Our Encore case does not describe its contract, so it is not proof of a model. What carries over is the cut. For Encore, a PR, media and events agency in Dubai, we shipped one system in three layers: the website, the CRM and the call notes tool. Two have their own dates: the new site went live 7 weeks after the first line of code, Asana data was in production in the CRM 9 days after the first CRM commit. A product that cuts this way can be priced by milestone.
Dedicated team vs fixed price: when does a retainer make sense?
A retainer makes sense when the product is live and work arrives as a stream: fixes, small features, content. The FAR's level-of-effort contract states the trade: "payment is based on the effort expended rather than on the results achieved". You get speed and no change requests, and you pay whether or not the month produced something.
Write into a retainer: the named people and their share of the week, the response time, a monthly report, what happens to unused hours and the notice period. Our websites page says this about ongoing work: a monthly block of hours and a response time, agreed in writing. Market ranges are in our app maintenance cost guide. For a first build, take a dedicated team only if your product manager can fill its week.
Which pricing model is best for a startup or a new product?
For most new products: T&M with a cap per milestone, after a fixed-price discovery. Check that against four questions. Is the scope written and stable? Is there a hard deadline? A budget ceiling? Will requirements change after users see the product?
Which model fits which project state. NextGenSoft's assessment, built on the definitions above. Checked November 20, 2026.
| Your project today | Model that fits | Why |
|---|---|---|
| Scope written, stable and testable | Fixed price | The studio can price the risk, and you get one number |
| Scope written, but large or with unknowns in later parts | Milestone fixed price | You fix what is clear and price the rest later |
| A new product with a budget ceiling; requirements will change | T&M with a cap per milestone | You change direction freely and still know the worst case |
| A hard date and an open scope | Capped T&M with a must, should and won't list | The date and the cap hold; the scope gives way |
| You do not know yet what to build | Fixed-price discovery first | A small, priced step turns unknowns into a scope |
| A live product with a steady flow of changes | Retainer or dedicated team | Speed matters more than pricing each task |
| An AI-built app whose code nobody has reviewed | A review first, then an estimate by step | Nobody can price repairs before reading the code |
The last row follows our vibe code rescue page: the estimate comes after the review, split by step, so you can stop after stabilizing. See also our guide to taking a vibe-coded app to production.
The hybrid route: a paid fixed-price discovery, then the build
Discovery is a small paid step with a fixed price and a written result that you keep. Ask for user flows, a clickable prototype, a data model, a list of integrations, a list of what is out, and an estimate by milestone with its assumptions. Our MVP cost guide covers when discovery is worth paying for.
Then let the result pick the model. If discovery closed the open questions, a fixed price is fair to both sides. If it left some, such as an untested integration, go with capped T&M by milestone.
The model can change later. The FAR tells contracting officers to "avoid protracted use of a cost-reimbursement or time-and-materials contract", so after two or three steady milestones, ask for a fixed price for the rest.
Two rules keep discovery honest: another studio could build from the result, and paying for it does not commit you to the build.
What to write into the contract under each model
Scope and acceptance criteria. Under a fixed price, the scope is the contract: screens, flows, integrations, languages and what is out, with criteria for each item and the days you have to test. Under T&M, write the goal, the first backlog and what "done" means.
Change requests. Under a fixed price: who may ask, how fast the studio prices the change, and that work starts only after written approval. Set a deadline: in the federal clause the contractor "must assert its right to an adjustment under this clause within 30 days". Under T&M, name who on your side may reorder the backlog.
Reporting and access. Under every model: the repository, the task board and the test version from day one. 18F's standard: "at the end of each sprint, all code is delivered to a government-owned repository".
Who owns the code, and when. Paying does not make you the owner by itself. In the US, commissioned software is not among the nine work-made-for-hire categories in US Copyright Office Circular 30, so the contract needs a written assignment. Set the moment: on payment of each milestone, not at the end, so a dispute over the last invoice cannot hold the whole product.
Payment schedule. Under a fixed price, tie payments to accepted milestones, not to dates. Under T&M, invoice every two weeks or monthly and show spend against the cap. In the UAE, ask whether the price includes value added tax: the standard rate is 5%, and it also applies to imported services (UAE Ministry of Finance).
Warranty period. Under a fixed price, the federal services clause lets the buyer require the work to be done again "at no increase in contract amount" (FAR 52.246-4). Under T&M the default is weaker: for 6 months after acceptance, unless the contract sets another period, the buyer may require a correction, and those hours are billed at a rate reduced "to exclude that portion of the rate attributable to profit" (FAR 52.246-6). So under T&M, write down the period and who pays.
Red flags in a quote under each model
Fixed price
- No written scope, acceptance criteria or procedure for changes.
- The lowest bid by far. In a study of 785,326 small projects on an online marketplace, choosing a bid 25% below the average came with a 9% increase in the frequency of failures at the same level of provider skill (Jørgensen, 2013). The tasks were small, so take the direction, not the number.
- Most of the money due before anything is accepted.
Time and materials, open or capped
- No estimate and no ceiling, or a cap over an undefined result.
- A blended rate with no names behind it.
- No timesheets, demos or repository access until the end.
- No early warning before the cap.
Retainer and milestones
- No named people, and unused hours that expire silently.
- Milestones that describe activity ("design in progress") instead of a result.
To score the companies behind the quotes, use our guide to choosing an app development company.
Before you sign: a checklist
- Write the scope on one page and mark every item must, should or won't.
- Answer the four questions above.
- Pick the model from the decision table and ask every bidder to quote under it.
- If nobody can price the scope, buy a fixed-price discovery first.
- Check the six clauses, and add an early warning to any cap.
- Give the draft to a lawyer before you sign.
Senior partners lead every project at NextGenSoft and staff it with vetted specialists. A partner goes through your scope on a call and gives an estimate and a timeline for that exact scope. See what we build, or send us your brief.
Questions we get asked
What is the difference between fixed price and time and materials?
Under a fixed price you agree one price for a written scope, and the studio pays if its estimate was wrong. Under time and materials you pay for the hours worked at agreed rates, so you carry that risk, but you can change the scope without a change request. The US Federal Acquisition Regulation defines both: firm-fixed-price in section 16.202 and time-and-materials in section 16.601.
What is a not-to-exceed (capped) time and materials contract?
It is time and materials with a ceiling price. You pay for actual hours up to the ceiling, and nothing above it without your written approval. The ceiling limits your spend, not the result: under the federal clause FAR 52.232-7 the contractor does not have to continue once the ceiling is reached. So set a cap for each milestone, an early warning and a rule for what happens at the cap.
Is fixed price cheaper than time and materials?
Not by default. A fixed price includes a buffer for the risk the studio takes on, and the TechFAR Hub warns that forcing a fixed price can make a contractor build in unnecessary contingencies. Time and materials has no buffer, but the total is open unless you add a ceiling. Fixed price tends to cost less only when the scope is stable enough that the buffer stays small.
Which pricing model is best for an MVP?
For most first versions, start with a small fixed-price discovery and then build under time and materials with a cap for each milestone. An MVP exists to learn from users, so its requirements will change, and every change under a fixed price is a change request. If discovery leaves no open questions and the scope is small, a fixed price per milestone also works.
Can I switch from time and materials to fixed price in the middle of a project?
Yes, and US federal guidance points the same way. FAR 16.103 tells contracting officers to avoid protracted use of time-and-materials contracts once experience gives a basis for firmer pricing, and the TechFAR Hub encourages a move to firm-fixed-price when pricing history is established. In practice, after two or three milestones at a steady pace you can ask the studio for a fixed price for the remaining scope.
Does a fixed-price contract mean the price will never change?
No. The price is fixed for the written scope only. When you change the work, the studio is entitled to a new price or date; even the US government's standard clause, FAR 52.243-1, gives the contractor an equitable adjustment in price, schedule or both. To keep the number stable, write the scope and acceptance criteria in detail and agree how changes are priced before you sign.
Sources
- FAR Part 16: Types of Contracts · Acquisition.gov, 2026
- FAR 52.232-7: Payments under Time-and-Materials and Labor-Hour Contracts · Acquisition.gov, 2021
- FAR 52.243-1: Changes-Fixed-Price · Acquisition.gov, 1987
- FAR 52.246-4: Inspection of Services-Fixed-Price · Acquisition.gov, 1996
- FAR 52.246-6: Inspection-Time-and-Material and Labor-Hour · Acquisition.gov, 2001
- Executive Order 14402: Promoting Efficiency, Accountability, and Performance in Federal Contracting · The White House, 2026
- De-risking Guide: Buying custom software development services · 18F, 2024
- Contract Types for Agile Development Contracts · TechFAR Hub, 2023
- Why Your IT Project May Be Riskier Than You Think (Harvard Business Review, September 2011), author copy · Bent Flyvbjerg, Alexander Budzier, 2011
- Direct and indirect connections between type of contract and software project outcome · International Journal of Project Management, 2017
- A Strong Focus on Low Price When Selecting Software Providers Increases the Likelihood of Failure in Software Outsourcing Projects · Magne Jørgensen, Simula Research Laboratory, 2013
- Circular 30: Works Made for Hire · U.S. Copyright Office, 2024
- Value Added Tax (VAT) · UAE Ministry of Finance, 2026
Share this article

About the author
Viacheslav Kasatkin
Co-founder & CEO
Sets direction on fintech, AI and business strategy.


