Choosing between a fixed-price contract and a time-and-materials agreement is not a choice between “certain cost” and “uncontrolled cost.” The two models allocate risk differently between buyer and delivery team. Fixed price is dependable when outcomes, scope boundaries, acceptance criteria and dependencies are clear. Time and materials is better suited to work where the problem, solution or priorities still need discovery, provided budget, team capacity and each delivery period remain transparent.
This guide is for executives, product leaders, technology managers and business owners preparing to contract for custom software. It is not legal advice; final terms should reflect the project and receive appropriate legal review. The focus here is commercial logic, cost visibility and delivery control.
The short answer: which model should you choose?
Use fixed price for a defined scope when you can describe requirements with examples, data, user roles, exceptions and testable acceptance criteria, and later change is expected to be limited. Choose time and materials, or a capped variant, when the team must still learn from real users, integrations or legacy data and priorities may change as evidence appears.
In practice, a hybrid is often more responsible. Discovery and prototyping can run under capped time and materials, after which well-understood packages receive fixed prices. Another option fixes the price of the essential core and reserves a controlled monthly capacity for changes and improvements. The model should follow the uncertainty of each work package rather than organizational habit.
What does a fixed-price contract actually fix?
Under fixed price, the supplier agrees a price for a defined scope and outcome. The official US Federal Acquisition Regulation description of a firm-fixed-price contract states that price is not adjusted based on the contractor's cost experience, except where contract clauses explicitly provide otherwise. That regulation does not govern every private software agreement, but it illustrates the economic logic: the supplier carries more estimating and delivery-efficiency risk for the defined work.
Fixed price does not mean every fact about the initiative is fixed. The agreement should distinguish:
- deliverables included in the base price;
- assumptions supporting the estimate;
- data, access and decisions the buyer must supply;
- acceptance criteria for each deliverable;
- review limits or design boundaries;
- the method for pricing changes;
- the effect of external dependency delays;
- defect-resolution and support boundaries.
A document containing only one amount and one date is not a controlled fixed-price contract. It is a fixed expectation attached to ambiguous scope.
How does time and materials work?
In a time-and-materials model, payment reflects actual time from agreed roles plus approved direct costs. Rates, roles, time-recording rules and reporting periods should be defined before work starts. The model does not remove delivery responsibility: every period still needs an objective, prioritized work, visible outputs and quality standards.
The official time-and-materials contract definition uses agreed hourly rates and direct materials. In a private software project, materials may be minimal and specialist team capacity will represent most cost. The important difference is that the buyer accepts more risk over the quantity of work required and therefore needs stronger visibility and prioritization rights.
A healthy T&M agreement should specify at least:
- team composition and rates by role;
- minimum and maximum capacity per period;
- time recording and approval method;
- a spending cap or budget review point;
- product demonstration and reporting cadence;
- backlog ownership and prioritization rules;
- definition of Done and quality expectations;
- the right to change capacity or stop with clear notice.
The central trade-off: scope risk versus cost risk
With fixed price, the supplier accepts more risk over the time and cost of delivering an agreed scope. When uncertainty is high, suppliers may add a risk margin, narrow scope conservatively or route changes through a formal and separately priced process.
With time and materials, the buyer accepts more risk over the final quantity of work but can change priorities each cycle and direct funding toward the most valuable features. That flexibility creates value only when the buyer can make decisions quickly, maintain a ranked backlog, inspect progress and stop or reshape work. Without those controls, flexibility can become drift.
The right question is not simply which party “takes the risk.” Ask which party can best control each risk. A supplier can usually control engineering productivity. The buyer usually controls user access, data availability and decision speed. Risk should sit with the party that has practical authority to reduce it.
When is fixed price appropriate?
Fixed price is better suited to conditions such as:
- a small or medium outcome with a clear boundary;
- a stable, documented business process;
- testable acceptance criteria;
- representative data and access available from the start;
- limited or understood external dependencies;
- familiar technology and delivery patterns;
- low probability of reprioritization during the contract.
A limited portal with known forms, a content website migration with an agreed page inventory, or a report built on a stable data source may fit this model. Even then, exceptions, authorization, performance, security and responsive behavior belong in acceptance criteria.
Before asking suppliers to price the work, use the custom software RFP checklist to describe scope, responsibilities and deliverables in comparable terms.
When is time and materials appropriate?
T&M is generally more suitable when:
- the business problem is known but the best solution is not;
- user behavior must be tested through prototypes or limited releases;
- legacy data quality is uncertain;
- integrations cannot be estimated before real access exists;
- requirements will evolve with regulation, market feedback or product learning;
- the buyer has an active product owner able to prioritize weekly;
- the goal is continuous improvement of a live product.
For example, an organization may want to digitize a complex process while departments disagree about exceptions. A fixed estimate for the whole initiative will either contain a large safety margin or enter change disputes quickly. A capped discovery period can produce a shared process map, sample data, architecture and a backlog that later becomes priceable.
Benefits and limits of fixed price
Benefits
- the budget for a defined outcome is more predictable at approval time;
- acceptance connects to explicit deliverables;
- the supplier has a stronger incentive to manage delivery efficiency;
- proposals are easier to compare when they genuinely cover the same scope.
Limitations
- uncertainty enters the price as risk margin;
- a valuable change may wait behind change-control administration;
- focus can shift from business outcome to completing a feature list;
- ambiguous scope creates conflict about included and excluded work;
- price pressure can weaken testing, documentation or invisible quality unless these are explicit deliverables.
Fixed price works best around small, acceptable outcomes, not a long document attempting to predict the entire future of a product.
Benefits and limits of time and materials
Benefits
- priorities can change in response to evidence;
- work can start sooner under genuine uncertainty;
- team composition and capacity costs are visible;
- the buyer can stop after a period without renegotiating the entire scope;
- the model suits maintenance and continuous product growth.
Limitations
- final spend is not predictable without caps and active control;
- the buyer must allocate real time to product decisions;
- timesheets alone do not prove delivered value;
- a standing team without period objectives can remain busy without meaningful progress;
- comparing only day rates ignores quality and delivery speed.
A more expensive team that solves the problem faster and creates less rework may produce a lower total cost. Compare rates alongside team composition, relevant experience, QA practice and outputs per period.
Capped T&M: flexibility with a spending boundary
Under capped time and materials, invoices reflect actual effort but do not exceed an agreed ceiling without a new decision. The ceiling should be a stop-and-review point rather than a hidden promise to complete any scope regardless of work required.
Define what report appears when spending reaches 70 or 80 percent of the cap, how the backlog is reforecast and which minimum usable outcome is expected within the ceiling. If scope remains fully fixed while the price is capped, the model transfers a portion of fixed-price risk back to the supplier and that must be reflected in price or scope.
Hybrid models for real software initiatives
Many projects contain several kinds of uncertainty, so one commercial model is not optimal for every phase. A practical hybrid can use:
1. capped T&M for discovery and analysis; 2. a defined prototype or architecture output; 3. fixed-price packages for understood features; 4. separately reported T&M capacity for uncertain integrations; 5. monthly capacity and an independent SLA for post-launch improvement and support.
The UK government's official Contracting for Agile guidance discusses the limitations of rigid fixed pricing under high uncertainty and the option of fixed-price sprints or blended approaches. It is not a legal template for your contract; it is evidence that the commercial model should match uncertainty and delivery method.
Use the phased software delivery guide to turn a large initiative into outcomes that can be priced and accepted separately.
What should you compare in proposals?
Do not place only total price or day rate in the comparison table. Compare:
- scope and explicit exclusions;
- assumptions about data, access and buyer participation;
- team composition and actual availability by role;
- deliverables and acceptance criteria per phase;
- environments, deployment and data migration included;
- security, performance and browser or mobile QA;
- documentation, training and knowledge transfer;
- ownership of code and infrastructure accounts;
- warranty and support boundaries;
- change, pause and termination procedures.
For the components behind an estimate, read the custom software cost guide. That page explains cost drivers; this one addresses payment mechanics and risk allocation.
Controlling cost in a T&M engagement
Transparency means more than receiving a list of hours. Effective control operates at three levels.
Capacity
Show the budget, team mix, available days and forecast cost for each period. Extra roles or overtime should not enter invoices without approval.
Output
For each sprint or month, record the objective, completed items, moved items and reasons for change. Regular demonstrations and acceptance stop disagreements from accumulating.
Value
Measure an outcome appropriate to the problem: less processing time, reduced duplicate entry, higher workflow completion or fewer measurable errors. Story points and hours support planning; they are not business value.
Report remaining budget alongside a forecast of achievable scope. A decision-maker should learn early what the current trend will deliver before the ceiling is exhausted.
Controlling change under fixed price
Change control should not be punitive or vague. A request should show its effect on scope, schedule, price and risk. Options can include exchanging a feature of similar effort, moving it to another phase or adding budget.
A useful change request records:
- business reason for the change;
- difference from the contractual baseline;
- technical and data effects;
- effect on acceptance criteria;
- lower-cost alternatives;
- the decision and approval from both parties.
Without a clear baseline, every correction looks like normal delivery to one side and expanded scope to the other. The contract must make that boundary visible before a dispute appears.
Decision example: after-sales service software
Imagine a company that wants to combine request intake, expert assignment, scheduling, spare parts and SLA reporting. Core forms and roles are clear, but integration with an old inventory system and the quality of part codes are uncertain.
A fully fixed-price agreement must either price the integration risk conservatively or process later changes. A completely open T&M agreement may leave total budget unclear. A hybrid can use capped discovery for integration, fixed price for the intake and assignment core, and monthly capacity for reports and improvements after real use begins.
The buyer gains predictable cost around understood work and the right to learn or stop around uncertainty. The supplier does not need to hide an uncontrollable unknown inside an apparently precise figure.
Questions to answer before signing
- Which assumption would change price or schedule if it proved false?
- Which scenarios and data will determine acceptance?
- Who owns backlog approval and priority?
- How often are time, progress and budget reported?
- What is the spending cap and warning point?
- Under fixed price, how are scope changes estimated and approved?
- Under T&M, how is unfinished work handed over if the engagement stops?
- Who controls code, documentation, accounts and database versions?
- How are defects, support and new development distinguished?
- What business outcome defines success beyond feature delivery?
Clear answers matter more than the label applied to the contract.
Conclusion: match the contract to uncertainty
Fixed price is effective for clear, acceptable scope. Time and materials provides flexibility for discovery, reprioritization and continuous development. Neither automatically guarantees quality, speed or cost control. Those outcomes come from visible assumptions, testable acceptance, decision rights and operational transparency.
Divide the initiative into work packages with similar risk. Reduce unknowns through bounded discovery, contract understood outcomes as acceptable packages and reserve controlled capacity for product change. Then connect payment to evidence appropriate to the model: accepted deliverables for fixed price, and transparent capacity plus period outcomes for T&M.
If your project needs a defensible commercial structure, the EasySaz custom software team can review scope, uncertainty and delivery options before estimating. Start through the EasySaz contact page.