Once you’ve chosen a vendor, there’s a second decision that gets less attention than it deserves: how the contract charges you. Most software work is sold one of two ways. A fixed price is one agreed number for an agreed scope. Time and materials means you pay for the hours worked, at agreed rates, for as long as the work continues.
Each model puts the risk in a different place. Neither one is the honest choice by default, and each tends to go wrong in its own predictable way.
Here’s how to tell which one fits your project, what to watch for with each, and how we combine them at CS2.
1. The real difference is who carries the risk
With a fixed price, the vendor carries the risk of the work taking longer than planned. With time and materials, you carry it. That’s the whole trade, and almost everything else follows from it.
Vendors know this, so a fixed price usually includes some margin for the unknown. That margin is what it costs to move risk from your side to theirs, and it’s fair as long as it stays small. It stays small when the scope is clear.
For managers: Ask yourself how well you can describe the work today. The clearer the scope, the better a fixed price works in your favour.
2. When a fixed price is the right call
Fixed price fits work you can write down: a defined set of users and workflows, known integrations and an agreed definition of done. A customer portal, an internal tool that replaces a spreadsheet, or a website with a CRM behind it usually falls into this group.
It also suits buyers who need one number to get approval. A board, a funder or a public-sector budget line rarely wants an hourly estimate with a range attached. Our small business packages work this way: Foundation at CAD $4,500 setup plus $650 a month, Growth at $8,500 plus $1,200 a month, and Scale at $15,000 plus $2,250 a month, all before tax. The scope is defined, so the price can be too.
For managers: If you need a single approved number and can describe the outcome, push for a fixed price against a written scope.
3. When time and materials makes more sense
Some work can’t be scoped honestly up front. Think of a research-heavy feature, an AI capability where nobody knows yet which approach will hold up, or an old system no one fully understands. Forcing a fixed price onto that kind of work usually produces a heavily padded number or an argument later.
Ongoing work belongs here as well. When an experienced engineer or architect joins your team on a fractional or full-time basis, you’re buying capacity rather than a defined deliverable, and time-based billing tends to fit that better than a fixed number.
For managers: If the honest answer to “what exactly are we building?” is “we’ll find out,” time and materials is the more truthful contract.
4. How fixed price goes wrong, and how to prevent it
The weak spot of a fixed price is the edge of the scope. Anything that isn’t written down turns into a debate: is it a bug the vendor fixes for free, or a new feature that costs extra? Vague scopes produce a lot of those debates, and they wear a working relationship down.
What prevents it is a precise written scope plus a change process agreed before work starts. We price every change before it’s built, so you decide with the cost in front of you and nothing lands on an invoice you didn’t approve.
For managers: Before signing a fixed-price contract, read the scope as if you wanted to argue about it. Anything you could argue about should be settled now.
5. How time and materials goes wrong, and how to prevent it
Here the weak spot is the open end. Hours pile up, progress is hard to judge from a timesheet, and the budget can drift without anyone making a single bad decision.
Controls make the difference. Agree a spending ceiling for each period, ask for working software on a real environment at the end of every short increment, and compare what was delivered with what was spent. If progress only ever shows up in status reports, treat that as your warning sign.
For managers: Don’t run time and materials without a spending cap and regular demos of working software.
6. The hybrid we use: assess first, then fix the price
For most clients we combine the two. When the scope is unclear, the first step is a fixed-scope technical assessment with a written report. It turns unknowns into things you can plan around, and you can act on the report with us or with another team.
Once the scope is in writing, we quote a fixed price. The work then runs in four phases: scoping, architecture with a first working slice, short build increments with demos, and handover. Each phase is signed off in writing before the next begins, so you always know where the project stands before more work starts.
For managers: If a project feels too uncertain for a fixed price, pay for a short assessment first instead of signing an open-ended contract.
7. Questions to ask any vendor, whichever model you pick
Who owns the code and the cloud accounts? With us, the repository sits in your organization and the infrastructure runs in your account from day one. What happens when the scope changes, and who approves the cost? What’s included after launch, such as hosting, monitoring and maintenance, and what does that cost each month?
Then ask who actually does the work once the contract is signed. That answer often matters more than the pricing model. At CS2, the senior engineers who scope a project lead its delivery, and the team scales with the work.
For managers: The pricing model matters less than a clear scope, a fair change process and ownership in your name.
The short version
A fixed price moves the risk to the vendor and works when the scope can be written down. Time and materials keeps the risk with you and fits work that can’t be fully defined yet. When you’re unsure, start with a short fixed-scope assessment, then fix the price against a written scope and sign off each phase as you go.