Fixed price, time and materials or a dedicated team?
Fixed price, time and materials or a dedicated team: which should you choose?
Choose a fixed price when you can write down what the first version must do and you need one number and one date; choose time and materials or a dedicated team when the scope will keep moving. With us, a fixed-scope build starts from $12k, a dedicated team from $6k per developer per month with 30 days' notice either way, and a care plan for software that is already live from $900 a month. The real difference between the models is who carries which risk, and how a change of mind gets paid for.
This article explains how each model works, who carries the risk, when each fits, how change requests work in each, and the red flags to look for before you sign.
How does a fixed-price software contract work?
You agree a written scope — what will be built, by when and for how much — and the vendor delivers it for that price. Ours is one price, one date, one deliverable, with the scope written in plain language before you sign anything. If we don't believe it can be done for that price and date, we say so first.
The scope is the contract: what is in it is in the price, and what isn't, isn't. That makes the scope document the most important thing you will read, and a clear software project brief the best way to get a good one. Our fixed-scope builds also include a clickable demo every Friday and 30 days of fixes once real users are in the product.
For a sense of size: in our MVP cost calculator, the typical MVP — a web app for customers and staff with an admin panel, payments, notifications and file uploads, connected to one or two other systems — comes to $23k–$34k as a fixed-scope build, about ten weeks with two developers.
How does a time and materials contract work?
You pay for the time actually spent, at an agreed rate per hour or per day, plus the 'materials' — licences, paid services, hosting. There is no fixed total: the scope can change from week to week and the bill follows it. A good time and materials contract reports the hours and what they produced every week or month, and sets a budget cap that can't be passed without your written approval.
Of our three models, the dedicated team is the closest to time and materials: you pay for people's time, counted in developer-months rather than hours, so the conversation stays on what ships rather than on timesheets.
How does a dedicated development team work?
You hire a team by the month: developers who work on your product, in your tools, to your priorities. Ours are senior engineers from $6k per developer per month — two to six people with a tech lead included, working your board and your standups — and you scale the team up or down with 30 days' notice either way.
You decide what gets built in each two-week slice; the team decides how. Nothing is re-scoped, because there is no fixed scope to protect: a change of plan is a change in the order of the board. The typical MVP above, built by a dedicated team of two, is $12k a month for about two and a half months. A marketplace on the web and in both app stores is three developers at $18k a month for about four months, against $58k–$85k as a fixed-scope build. See how we run dedicated teams and custom platforms.
Who carries the risk in each contract model?
Every software project has two big risks: that the work takes longer than estimated, and that what was asked for turns out to be wrong. Each model hands them to a different side:
- Fixed price. The vendor carries the estimate: if the work takes longer, that is their cost. You carry the scope: if the written scope misses something, adding it is a change. Vendors price the first risk in, so a fixed price includes a margin for the unknown.
- Time and materials. You carry both. You pay for the time it actually takes, false starts included, and in return you can change course whenever you like. The vendor's main risk is that you stop.
- Dedicated team. You carry the cost and the direction; the vendor carries the team — keeping the right people on it, replacing anyone who leaves, and keeping the quality up. The notice period limits how much either side has committed at any moment: with us, 30 days.
- Care plan. For software that is already live, the vendor carries the routine — monitoring, backups, security patches and a named engineer on call — for a known monthly price, which grows with how much change work you want on top.
When does each model fit?
Match the model to how well you can describe the work today:
- Fixed price fits an MVP or a well-understood system: you can write down what the first version must do, and you need a number for a budget, an investor or a board. Our MVP development builds are priced this way.
- Time and materials fits short, exploratory work where nobody can write the scope yet — an investigation, a prototype, a fix in a system nobody understands — as long as there is a cap.
- A dedicated team fits a product that will keep growing, or a scope you expect real users to change. It also suits large builds: our calculators recommend a team when you say the scope will change, or when the work passes about 60 developer-weeks. A marketplace on the web and both app stores with a custom design, sensitive data and three or more integrations comes to $83k–$123k as a fixed-scope build, or four developers at $24k a month for about four months — and the calculator suggests the team.
- A care plan fits software that is already live and needs looking after more than it needs new features — whether we built it or somebody else did. Ours start from $900 a month: see software support and maintenance.
How do change requests work in each model?
Change is normal in software. What differs between the models is how a change is agreed and paid for:
- Fixed price. Anything outside the written scope is a change. With us, work moves in two-week slices with a clickable demo every Friday, so changes made early stay cheap; bigger changes are re-scoped in writing — a new price and a new date — before any work on them starts. You should always hear the cost of a change before it is made, never after.
- Time and materials. A change is simply more time. There is no paperwork, which is both the attraction and the danger: without a cap and a regular report, many small changes add up unnoticed.
- Dedicated team. A change is a new priority on the board. The month costs the same either way, so the only question is what moves down the list to make room.
- Care plan. Small changes can sit inside the plan. In our software maintenance cost calculator, small tweaks — about two developer-days a month — are priced at $600 a month on top of the care, and a product that needs new features every month is better served by a dedicated developer.
What are the red flags in a software development contract?
Whatever the model, these should make you slow down before signing:
- A fixed price with no written scope. The price is fixed but the product isn't, and every disagreement becomes a change request.
- A price far below every other quote. Either something has been left out, or the difference comes back later as changes.
- No working software until the end. You should be clicking real software within weeks, not reading status reports for months.
- Time and materials with no cap and no regular report of the hours and what they produced.
- A dedicated team with a long lock-in, or no named people. You should know who is on your team, hear before anyone changes, and be able to leave on a notice period you can live with.
- Code in the vendor's account. Your code should live in your repository and your cloud account from the first commit — see who owns the code in software development.
- A vague change process. 'We'll be flexible' is not a process. Ask how a change is priced, who approves it and when you hear the cost.
- Nothing about what happens after launch. Fixes, support and handover belong in the contract, not in a surprise invoice.
Can you combine fixed price, a dedicated team and a care plan?
Yes, and it is often the right path: a fixed-scope build for the first version, a dedicated team while the product grows, and a care plan once it is stable. Our fixed-scope builds include 30 days of fixes after launch; after that you can keep us on a care plan or take the keys, with documentation and a walkthrough for your own team.
What a care plan costs depends on the system. The worked example in our software maintenance cost calculator — a $50k web app with a few thousand users, one or two outside systems, next-working-day response and small tweaks each month — comes to $1,950–$2,800 a month for the engineering, plus the hosting bill.
Which is cheaper, fixed price or time and materials?
Neither by default. A fixed price includes a margin for the risk the vendor takes on; time and materials has no margin but passes every surprise to you. For a clear, modest scope a fixed price is usually the safer number; for a scope that will change anyway, paying for time avoids a stream of change requests.
Can the scope change on a fixed-price project?
Yes, through a change request. With us, bigger changes are re-scoped in writing — a new price and a new date — before any work on them starts. The two-week slices and the Friday demo mean most changes are spotted early, while they are still cheap.
How much notice does a dedicated team need?
With us, 30 days either way, and the same notice scales the team up or down. Be wary of much longer notice periods or long minimum terms: the point of a dedicated team is that it follows the work, not the contract.
How much does a dedicated developer cost?
Ours start from $6k per developer per month, with a tech lead included in the team. The typical MVP built by two developers is $12k a month for about two and a half months. Our MVP cost calculator shows both the fixed price and the team cost for your own product.
How do I decide which model fits my project?
Write down what the first version must do. If that fits on a page and you would be happy to sign it, ask for a fixed price; if it doesn't, or you expect real users to change it, ask for a team. Send us the brief and we reply within one working day; you get the model we'd recommend and a written scope with a price and a date.