Key takeaways
A fixed price works when the scope can be described precisely before work starts. Time & materials works when the scope will change as needs become clearer.
A fixed price doesn’t remove risk, it prices it in: the vendor adds a buffer, and the dispute moves to the question of what falls within the scope.
Time & materials doesn’t have to mean a blank check — a budget cap, time reports, and regular reviews give you full control.
A hybrid model often works best: a fixed price for a well-defined stage and time-based billing for further development.
The two models in one sentence each
Fixed price is a contract for a defined scope at a defined amount. You know upfront what you’ll pay — as long as the scope doesn’t change.
Time & materials (T&M) is billing for time actually worked at an agreed rate. You pay for what’s been done and can change direction without renegotiating the contract. For reference: team hourly rates on the Polish market are around 150–180 PLN net per hour (Devstock, 2026, in Polish).
Both models are fair, and both can fail. They differ in who carries the risk of unforeseen work and how visible that risk is.
Fixed price and time & materials side by side
Fixed price — advantages
A predictable budget, easier internal approval, a clear moment of acceptance. Good for a small, well-defined scope.
Fixed price — risks
A risk buffer built into the price, a rigid scope, every change a negotiation. The vendor has an incentive to interpret the scope narrowly.
Time & materials — advantages
Flexibility, no buffer in the price, the ability to change priorities after every cycle. You pay for real work.
Time & materials — risks
The budget isn’t capped upfront. It requires involvement on your side: reviews, decisions, and checking reports.
A fixed price doesn’t remove risk — it prices it in
A vendor that accepts a fixed price takes on the risk that the work will turn out bigger than expected. To avoid losing money on it, they add a buffer to the quote. If the project goes smoothly, you paid that buffer for nothing. If it goes badly, the buffer may still turn out to be too small.
The second effect is less obvious. With a fixed price, every ambiguity in the scope description becomes a potential dispute: does “report export” include exporting to PDF, or only to CSV? The vendor has a natural incentive to read the scope narrowly, and you to read it broadly. Instead of talking about what’s good for the product, you end up talking about what was in the contract.
That doesn’t mean a fixed price is the wrong choice. It means it only works when the scope can be described truly precisely — with acceptance criteria, not general slogans.
Time & materials doesn’t mean a blank check
The most common worry about time-based billing is: “what if it never ends?” That worry is only justified when the contract has no control mechanisms at all. And those mechanisms are simple:
- A budget cap per month or per stage, after which work stops until you decide.
- An alert threshold, e.g. at 80% of the cap, so the decision is made before the budget runs out.
- Time reports describing what was worked on — weekly or with every invoice.
- A review after every cycle, where you see a working version and set priorities for the next one.
- The right to end the engagement with a reasonable notice period and a handover of the code.
With these clauses, T&M gives you more control than a fixed price, because you see the cost of every decision as you go, not only when the scope is renegotiated.
When a fixed price makes sense
Choose it when most of the following conditions are met:
The scope can be described precisely — You know the screens, features, and acceptance criteria before work starts.
The project is small — A few weeks of work, few integrations, a limited number of unknowns.
The budget has to be capped — For example, with co-funding or a rigid procurement procedure.
You don’t plan changes along the way — New ideas are collected for the next version rather than added on the fly.
When time & materials is the better choice
This model wins when there’s more uncertainty than certainty:
You’re building a new product — Some assumptions will only be verified by the first users — the scope has to change.
The project is large or long — Over many months of work, the risk buffer in a fixed price becomes very expensive.
There are difficult integrations — The state of external systems only becomes clear once work is under way.
It’s about development and maintenance — Tasks come up continuously and can’t be described upfront.
Hybrid models
In practice, many projects are best billed with a hybrid approach:
Fixed price per stage
Analysis and design for a fixed amount, with later stages quoted based on their results. The risk is lower, because each stage is described with knowledge of the previous one.
T&M with a cap
Time-based billing with an upper budget limit. You get flexibility and at the same time know the maximum you’ll spend.
Fixed budget, flexible scope
You agree on an amount and priorities, and the team delivers the most important features until the budget is used up. A good model for an MVP.
Not sure which model fits your project?
Describe the scope and your budget constraints. We’ll propose a pricing model that distributes risk fairly on both sides.
What to put in the contract regardless of the model
These clauses protect both sides, whether you choose a fixed price or time-based billing:
Scope definition and acceptance criteria — What exactly has to work and how you’ll know it does.
Change procedure — How you request a change, how quickly you get a quote for it, and who approves it.
Reporting — With T&M — time reports describing the work. With a fixed price — progress reports against milestones.
Cap and alert thresholds — Especially with T&M: an upper budget limit and the point at which the vendor has to warn you.
Milestones and payments — Payments tied to the acceptance of concrete outcomes, not to the passage of time.
Termination and handover — The notice period and the handover of code, documentation, and access.
How we bill projects at Just Site
We bill smaller, well-defined projects at a fixed price. Larger ones are billed for time worked, because with a large scope a fixed price means a risk buffer that the client always ends up paying. Infrastructure maintenance under our DevOps service is billed hourly, with no minimum, and unused hours roll over to the next month.
We write more about what drives the quote itself in our guide to custom software, and about the clauses that protect the ordering company in what a software development contract must include.
Frequently asked questions
Which is cheaper: fixed price or time & materials?+
Can I change the scope under a fixed price?+
How do I control the budget with time & materials?+
Which pricing model should I choose for an MVP?+
Does hourly billing require a long-term contract?+
Have a project in mind?
We’ll help you design and deliver it — from strategy to a finished solution.
