Fixed price or time and materials? Choosing a software contract
How you pay for software shapes how the project runs. A fixed price promises certainty. Time and materials promises flexibility. Each works well in the right setting and badly in the wrong one.
By the FocalID team in Colombo, , 2 min read

The two models
With a fixed price, the supplier agrees to deliver a defined scope for a set amount. With time and materials, you pay for the hours worked at agreed rates, and the scope can change as you go.
| Fixed price | Time and materials | |
|---|---|---|
| Budget | Known at the start | Estimated, then tracked |
| Scope | Must be defined in detail up front | Can change from week to week |
| Who carries the risk of overrun | Mostly the supplier | Mostly the client |
| Changes | Handled by change requests, each priced | Reprioritised without renegotiating |
| Your involvement | Heavy at the start and at acceptance | Steady throughout |
When a fixed price works
A fixed price suits work that is small, well understood and easy to describe: a pilot, a defined integration, a website, a first version with a short feature list. It works when both sides could write down what “done” means before starting.
It works badly when requirements are still being discovered. The supplier adds a margin for the unknown, every change becomes a negotiation, and the team is rewarded for delivering what the document says, not what you now know you need.
When time and materials works
Time and materials suits long-running products, work with real uncertainty and teams that extend your own. You can change direction when you learn something, and you pay only for what is done.
It needs trust and visibility. Ask for working software every week or two, a clear record of hours, and the right to stop at short notice. A monthly cap or a budget per phase keeps spending in check.
Combine them
Many projects start with a small fixed-price phase to prove the idea and learn how the two teams work together, then continue on time and materials once the direction is clear. That is why our own first step for AI work is a fixed-price, four-week pilot on one workflow.
Whatever you choose, put these in the contract
- Who owns the code and the data.
- What counts as accepted, and how long you have to test.
- How changes are requested, priced and approved.
- What support is included after go-live, and for how long.
Common questions
Is fixed price always cheaper?
No. The price includes a margin for risk. On uncertain work you may pay more than the hours it took.
How do we control cost on time and materials?
With a budget per phase, weekly reporting of hours against progress and working software to review at short intervals.
Can we switch models mid-project?
Yes, at a natural break such as the end of a phase, if both sides agree.

