Time and Materials vs Fixed Price IT Projects: When to Use Which
Choosing the wrong pricing model for an IT project is one of the most reliable ways to create friction between a client and a provider, blow a budget, miss a deadline, or end up with something that does not do what you needed. Fixed price and time and materials are the two dominant models. Each has a legitimate use case. Each produces bad outcomes when applied to the wrong type of project or the wrong client relationship. Understanding which model is appropriate for what you are trying to build, buy, or implement matters more than negotiating the price itself.
This article covers how each model works, what it is good for, what can go wrong with each, and how to decide which one applies to your situation. The goal is not to declare one model superior. It is to give you the framework to make the right call for each specific project.
How Fixed Price Works
In a fixed price engagement, the provider quotes a specific amount for a defined scope of work. The scope is documented in a statement of work or project brief. The client pays the agreed amount regardless of how many hours the provider actually spends, as long as the scope is delivered. If the provider underestimated the work, they absorb the additional cost. If they overestimated, they keep the difference.
The fixed price model requires the scope to be defined with a high degree of precision before the price is set. This means the client needs to know what they want in enough detail to write it down, and the provider needs to understand the requirements well enough to estimate them accurately. For well-defined, known work with clear requirements, this is achievable. For exploratory or evolving work, it is not.
The pricing mechanism also matters. A fixed price that is set too low will result in a provider who is reluctant to do the work properly because it is costing them money. A fixed price set too high means the client is paying more than the work was worth. The price reflects the provider's estimate, which reflects their understanding of the risk. If the client has not been clear about requirements, the provider prices in uncertainty, which makes the price higher than it needs to be for well-scoped work.
Before committing to any pricing structure, it is worth reviewing what your contract actually covers, including deliverables, warranties, and what happens when requirements change mid-project. A clear contract protects both parties regardless of which model you choose.
What Fixed Price Is Good For
Fixed price works well for projects with well-defined, stable requirements where the client knows what they want and the provider has done similar work before. Website migrations where the source and destination are known, hardware refreshes where the new equipment is specified, standard software installations with documented configuration steps, and office network setups where the site survey has been completed are all good fixed price candidates.
The model also works well when the client has a strict budget that cannot be exceeded. If you have a board-approved IT budget of £15,000 for a project, a fixed price contract with clear deliverables gives you certainty about whether the project fits within that budget. Time and materials gives you an estimate, not a ceiling.
Fixed price also provides protection when the relationship between client and provider is new or has limited trust. With a fixed price, both sides know exactly what the financial exposure is. The provider cannot come back six months later and say the project actually cost three times as much as quoted. The client cannot claim the provider should have done more than the agreed scope without additional payment. The ambiguity that causes disputes in IT projects is reduced because the financial terms are clear and fixed.
If you are hiring an external IT specialist for the first time, a fixed price structure can help establish expectations on both sides before moving to more flexible arrangements.
What Can Go Wrong With Fixed Price
The most common failure mode for fixed price projects is scope ambiguity. If the statement of work says "configure the firewall" but does not specify how many rules, which zones, what logging is required, or what the changeover process looks like, the provider will interpret "configure the firewall" in the most economical way they can justify. The client will expect something more comprehensive. This gap is where disputes live.
A related failure mode is the addition of requirements after the price is set. Clients frequently discover new needs during a project that they would like to include. With fixed price, adding scope requires a change order and often a change order price that the client feels is excessive. The provider's incentive is to resist scope changes because they affect the price. This creates a tension that can damage the relationship, particularly if the client expected flexibility as part of a good working relationship.
Fixed price also creates an incentive for the provider to cut corners on quality to protect their margin. If the estimate was wrong and the project is running over, the provider faces a choice between absorbing the loss or reducing the quality of deliverables. Clients rarely notice reduced quality until after the project is delivered and they start encountering edge cases or maintenance problems that should have been handled differently.
Documentation matters in fixed price projects. When scope is contested, clear records of what was agreed, what was delivered, and what was changed can be the difference between resolving a disagreement quickly and a prolonged dispute that costs more than the original project.
How Time and Materials Works
In a time and materials engagement, the client pays for the actual time spent by the provider's staff, at agreed hourly or daily rates, plus the cost of any materials, software licenses, or third-party services required. There is no fixed total price. The scope may be defined, but the final cost depends on how long the work takes.
The model requires the client to trust the provider, because the client is taking on the cost uncertainty. To manage this risk, the client typically sets a budget ceiling or approval threshold. Work above a certain cost requires additional approval before proceeding. The provider sends regular timesheets or progress reports that the client can review to track spend against budget.
Hourly rates in time and materials engagements are usually lower than the effective rates embedded in a fixed price quote, because the provider does not need to price in the contingency for scope uncertainty. A fixed price quote for a project the provider has not done before will include a contingency for scope variation. Time and materials pricing does not include that contingency, which can make it appear cheaper even when the final total is higher.
Ongoing IT support arrangements often use time and materials or a variation called a retainer. In a retainer, the client pays a fixed monthly amount for a set number of hours or a defined scope of availability. This is different from true fixed price because the client is buying access to the provider rather than a specific deliverable.
What Time and Materials Is Good For
Time and materials is the correct model for work where the scope cannot be defined precisely in advance. Software development projects, particularly those involving new or experimental features, are the canonical example. You cannot know how long it will take to build something that has not been built before. Trying to force a fixed price on an unknown software development project produces either an inflated contingency-laden quote or a provider who underestimates and absorbs losses until they can no longer continue.
Time and materials also works well for ongoing operational support and improvement work. A retainer arrangement where the provider handles all IT improvement requests as they arise is a time and materials model. The scope changes month to month and cannot be predicted a year in advance. Trying to define it as a fixed price produces either a retainer so high it covers all possible eventualities, or one that is regularly exceeded and causes friction.
For clients who want to maintain flexibility and control over the direction of a project, time and materials provides that flexibility without requiring scope to be locked down before the work begins. The client can change direction mid-project, add new requirements, or stop work at any point without being bound by a fixed scope that no longer reflects what they need.
If you are considering whether to hire a part-time IT specialist or a full-time member of staff, understanding how different pricing models work can help you evaluate whether contracting work makes more sense for your situation than a permanent hire.
What Can Go Wrong With Time and Materials
The primary failure mode for time and materials is scope creep that drives cost beyond what the project was worth. Without a fixed price creating a boundary, it is easy for a project to expand incrementally until the cost has exceeded the original estimate by a significant margin. Clients who did not set a clear budget ceiling or approval threshold are particularly exposed to this.
A subtler failure mode is reduced provider urgency. When the client is paying by the hour, there is less incentive for the provider to be efficient. This is not about provider dishonesty, though that can happen. It is about the natural tendency of any service provider to do thorough work when they are being paid by the hour in a way that they do not when they have already agreed a fixed price. Fixed price creates an efficiency incentive. Time and materials can remove it.
Time and materials also requires more client engagement. The client needs to review timesheets, approve additional spend, and make timely decisions about scope changes. Clients who prefer to hand a project over and wait for the result often find that time and materials projects drift without adequate oversight because no one is actively watching the budget.
Regular progress reviews and budget checkpoints are essential in time and materials arrangements. Scheduling these reviews at the start of the engagement and treating them as mandatory rather than optional helps keep the project on track.
The Hybrid Approach
In practice, many engagements use a hybrid model that captures the benefits of both approaches while limiting the drawbacks. A common hybrid structure is to fix the price for the known, defined portions of a project and use time and materials for the portions that are uncertain or exploratory.
For a website rebuild, the design phase might be fixed price because the deliverables are well-defined. The development phase might be time and materials with a budget ceiling because the exact features and complexity are not known until the design is approved and the development work is underway. The hosting setup might be fixed price because it is routine. This structure gives the client cost certainty where it matters most while retaining flexibility where it is needed.
The hybrid approach requires more upfront planning than either pure model, but it often produces the best outcomes for projects that have a mix of routine and uncertain elements. The key is to identify upfront which parts of the work are truly predictable and which are likely to change, and to structure pricing accordingly.
How to Decide Which Model to Use
The decision tree is straightforward. Can you write a precise statement of work that defines the entire scope before the project starts? If yes, fixed price is appropriate. If the work involves research, experimentation, or requirements that will only become clear once the work has started, time and materials is appropriate.
Is the relationship new or does it involve a provider you have not worked with before? Fixed price provides better protection for both sides against scope and estimate disputes in new relationships. Established relationships with high trust can use time and materials more effectively because both sides know how the other works.
Do you have a hard budget ceiling? Fixed price is the only model that gives you a guaranteed ceiling. Time and materials requires budget monitoring and approval processes to avoid overruns.
Do you want to be involved in technical decisions as the project progresses? Time and materials allows you to redirect the work based on what you learn. Fixed price requires change orders for significant direction changes.
Do you have a clear technical specification already, or will requirements emerge through the work? If the specification is complete and verified against the actual system, fixed price works. If the specification is an approximation that will need testing against reality, time and materials or a hybrid approach is more appropriate.
Taking time to answer these questions before you engage a provider will save you from the most common disputes that arise from mismatched pricing models and expectations.
What to Include in Your Contract Regardless of Model
Whether you choose fixed price or time and materials, certain elements should be present in any IT contract. Clear definitions of scope prevent most disputes before they start. A change control process that specifies how scope changes are requested, priced, and approved keeps both sides aligned when requirements evolve.
Acceptance criteria define when the work is considered complete. Without agreed acceptance criteria, fixed price projects can stall indefinitely while the provider and client disagree on whether the deliverables meet expectations. Timesheets and progress reports, while less critical in fixed price work, become essential in time and materials arrangements for budget tracking.
A dispute resolution process, even a simple one that specifies how disagreements are escalated before legal action, can save significant time and cost if problems arise. Good IT documentation practices support whatever pricing model you choose by creating a clear record of what was agreed, what was delivered, and why decisions were made.
Making the Right Call for Your Project
The choice between fixed price and time and materials is not about which model is better in the abstract. It is about which model fits the nature of your work, the maturity of your requirements, and the relationship you have with your provider. Fixed price rewards clear thinking upfront. Time and materials rewards flexibility and ongoing engagement. Most real-world projects benefit from understanding both models and applying them where each fits best.
If you are planning an IT project and want help working through which pricing model suits your situation, it is worth discussing your specific requirements before committing to a contract structure. Preparing a short description of what you need to achieve, what systems are involved, and what your timeline looks like gives you a solid foundation for that conversation.