When you buy software development from a vendor, the pricing model decides more than the invoice. It decides who carries the risk of a wrong estimate, how easily the scope can change, and how much you can see of what you pay for. This guide compares cost plus vs time and material, and both with fixed price, from the buyer's side: how each model works, where it helps, where it hurts, and which questions to ask before you sign.
None of the three is better in general. Each one fits a different kind of project, and many buyers use more than one over the life of a product.
Three pricing models
Fixed price. The vendor agrees to deliver a defined scope for a set price. If the work takes longer than estimated, the vendor absorbs the difference. If you want something that is not in the scope, it becomes a change request with its own price.
Time and material (T&M). You pay for the time the team actually works, at agreed rates per hour, day, or month, plus agreed expenses. The scope can change at any time; the cost follows the work.
Cost plus. You pay the vendor's actual costs plus an agreed margin, and the costs are shown to you. Like T&M, the cost follows the work. Unlike T&M, the price is split into what the work costs and what the vendor earns on it.
| Fixed price | Time and material | Cost plus | |
|---|---|---|---|
| Who carries the estimate risk | Vendor | Buyer | Buyer |
| Scope changes | Through change requests | At any time | At any time |
| Total known up front | Yes, for the agreed scope | No, unless capped | No, unless capped |
| What you see | The total | Hours and rates | Each cost line and the margin |
| Effort before the work starts | High: the scope must be specified | Low | Low to medium: cost lines are agreed |
When fixed price fits
Fixed price works when the scope is small, clear, and unlikely to change, and when someone needs one number before the work can be approved.
Good candidates are a first version of a product with a scope agreed in a workshop, a well-specified integration, or a migration with a known end state. In each case, both sides can describe what "done" means before the work starts.
The costs are less visible:
- A risk buffer. A vendor that carries the estimate risk prices it in. You pay for that buffer whether the risk happens or not.
- Change requests. Every change has to be specified, priced, and approved. On a project that learns as it goes, this slows decisions and can cost more than the original scope.
- Pressure on what is not written down. If the budget runs short, the vendor's incentive is to deliver the letter of the specification. Quality attributes that were not specified, such as test coverage or documentation, are the first to suffer.
- Specification work. The scope has to be written precisely enough to price. That work is useful, but it takes time and someone has to pay for it.
When time and material fits
Time and material works when the scope is still moving: product discovery, a product that is already live and changes every sprint, or work where the problem is only understood once you start.
Its strengths are flexibility and the lack of a risk buffer. You pay for the work that is done, and you can change priorities without renegotiating the contract.
Its weaknesses are on your side of the table:
- Budget uncertainty. The total depends on how the work goes. A cap, often called a not-to-exceed budget, limits that risk, but then you have to decide what happens when it is reached.
- You manage the scope. With no fixed scope, someone on your side must set priorities and say when a feature is good enough.
- One rate, little detail. A daily rate includes the vendor's salary costs, overheads, tools, and profit in one number. You see how many days were spent, not what they cost the vendor.
Cost plus vs time and material in practice
On a weekly basis, cost plus and time and material can look alike: a team works, the cost follows the work, and the scope can change. The difference is in what the price is made of and what you can check.
Under cost plus, the vendor's proposal lists the cost lines, typically developer costs, software licences, and infrastructure such as hosting or cloud services, and the margin is a separate, agreed line. When the team grows or shrinks, the cost lines change and the margin stays as agreed. When a licence is no longer needed, it disappears from the price.
That transparency has consequences you should plan for:
- Cost evidence. Agree up front what the vendor shows to support each cost line, and how often. Itemised invoices are only useful if both sides read them.
- Incentives. A margin on costs gives the vendor no reason to lower them. The usual answer is the same as for T&M: agreed team composition, regular reviews of the cost lines, and a budget the work is planned against.
- No fixed total. Cost plus does not tell you the final cost of a project on its own. If you need one number, combine it with a budget or a scope, or price a defined first phase at a fixed price and break that price down into the same cost lines.
Cost plus is a way to build a price, not a way to organise the work. It can be combined with an outsourced project, where the vendor delivers the outcome, or with team augmentation, where its developers join your team.
Which model for which situation
| Situation | Usually fits |
|---|---|
| Small, stable scope that needs one approved number | Fixed price |
| A first version whose scope is agreed in a workshop | Fixed price, ideally broken down into its cost lines |
| A live product with a changing backlog | Time and material or cost plus |
| A long-running team where you want to see what you pay for | Cost plus |
| Exploratory work with an unclear end state | Time and material or cost plus, with a cap |
Questions to ask a vendor
Whatever the model, these questions show quickly how a vendor works:
- What exactly is in the price? Ask for the parts: people, licences, infrastructure, and profit. A vendor that cannot or will not split the price is asking for trust without evidence.
- How are changes handled? Under fixed price, ask how change requests are estimated and approved. Under T&M or cost plus, ask how you will know when the budget is at risk.
- What do you report, and how often? Time spent, cost lines, progress against the budget, and the work that is done.
- Who is on the team, and what happens when someone leaves? Team composition drives the cost under T&M and cost plus, and quality under fixed price.
- What happens at the end? Who owns the code and the repositories, what documentation you receive, and how the work is handed over.
How we can help
We work with COST+ pricing for software development: your price is our actual cost plus a margin agreed up front. The proposal lists developer costs, licences, infrastructure, and the margin, and invoices can be itemised on request. COST+ works with both outsourcing and team augmentation.
