Contents
Fixed price vs. time and material – this decision shapes the budget, risk and collaboration of your app project. A fixed price gives planning certainty when the scope is clear; time and material gives flexibility when requirements only emerge along the way. In practice, combinations often work best.
Fixed price and time and material: the models compared
Fixed price: Client and provider agree on a defined scope at a fixed price. The provider carries the risk if implementation takes longer than calculated. Scope changes are agreed separately via change requests.
Time and material: The time actually spent is billed at agreed hourly or daily rates, often with an estimate for orientation. The client carries the volume risk but can shift priorities at any time.
Neither model is a matter of belief; both are tools for distributing risk. The key question is: who knows more about the real effort at the start of the project – and who is better placed to carry the risk? An experienced provider can estimate known building blocks such as login, payments or push notifications well. Unknown business logic, new technologies or unclear interfaces to your existing systems, on the other hand, are hard to price upfront. The higher that share, the more worthwhile at least a preceding analysis becomes.
| Criterion | Fixed price | Time and material |
|---|---|---|
| Budget certainty | high | low to medium (a cap is possible) |
| Flexibility for changes | limited, via change requests | high |
| Who bears the overrun risk? | provider | client |
| Preparation effort | higher – requirements must be clear | lower – faster start |
| Steering effort for the client | lower during the project | higher – continuous prioritisation needed |
| Typical use | MVPs, well-scoped apps, sub-projects | ongoing development, exploration, unclear requirements |
When a fixed price makes sense
A fixed price is the right choice when these conditions are largely met:
- You can describe the core features and user flows.
- The budget is fixed, for example by grants, investors or an internal annual budget.
- You want to focus on your core business instead of negotiating priorities every week.
- There is a clear deadline, such as a trade fair or a product launch.
Important: a serious fixed price requires a thorough analysis. Providers who quote a fixed price without asking questions either add a large risk premium or plan to renegotiate later through change requests. How AI speeds up the analysis and makes quotes more precise is described in How AI makes fixed-price app quotes cheaper and more accurate.
When time and material is the better fit
- The product idea is still evolving and you want to decide afresh after each sprint.
- The work is technical exploration, for example testing the feasibility of an AI feature or a hardware integration.
- The app is live and the focus is continuous development with changing priorities.
- You have an internal product owner with time to steer the work.
Time and material fits well with agile approaches such as Scrum. How to stay in control as a client in this model is explained in Agile app development: Scrum explained for clients.
Hybrid models: the best of both worlds
In practice, combinations that balance certainty and flexibility have proven themselves:
- Analysis plus fixed price: A short analysis phase clarifies requirements and risks, followed by a fixed price for implementation. We use this model for app projects: free analysis, then a fixed-price offer.
- Fixed price per milestone: The project is split into stages (e.g. MVP, version 1.0, extension), and each stage is agreed separately at a fixed price.
- Time and material with a budget cap: Billing by effort, but with a ceiling at which both sides decide together how to proceed.
- Fixed price for version 1, then a maintenance or retainer agreement: A predictable start, flexible further development.
Common traps – and how to avoid them
| Trap | Model | Countermeasure |
|---|---|---|
| Vague scope leads to disputes | fixed price | define written acceptance criteria per feature |
| Expensive change requests for minor things | fixed price | agree on the change process and terms in advance |
| "Cheap" fixed price with quality cuts | fixed price | define tests, code quality and documentation as deliverables |
| Budget runs away without visible progress | time and material | regular demos, time reports, budget cap |
| Endless feature creep | time and material | clear product goal and prioritised backlog |
Some of these traps are among the classic cost risks we describe in Hidden costs of app development. And if you have several very different quotes in front of you, Why app quotes vary so much helps you compare them.
One more point that is often overlooked: even with a fixed price, you need a contact person on your side with decision-making authority. If questions remain unanswered for days or approvals are delayed, the project slips – and delays caused by the client are, in most contracts, not covered by the fixed price.
Checklist for your contract
- Is the scope described with features, platforms and acceptance criteria?
- Is it defined how changes are requested, assessed and billed?
- Do you receive the complete source code and all usage rights?
- Are there milestones with interim acceptance and linked payments?
- Are warranty, bug fixing and maintenance after launch covered?
- Is it specified where data is processed and hosted (GDPR)?
Conclusion
For most first projects – MVPs and apps with a clearly describable core – a fixed price after careful analysis is the more sensible model: you know your budget and the overrun risk lies with the provider. Time and material shows its strengths in ongoing development and exploratory phases. Hybrid models combine both. If you would like a fixed price for your app, you can request a free analysis via our offer wizard.
Frequently Asked Questions
Is a fixed price more expensive than time and material?
Not necessarily. A fixed price usually includes a buffer for the risk the provider takes on; in return, you avoid surprises from extra effort. For well-analysed projects, this buffer is small.
Can I still make changes under a fixed price?
Yes, via change requests. What matters is that the process and terms for changes are defined in the contract upfront.
Which model suits agile development?
Time and material fits Scrum particularly well, but fixed prices per milestone or sprint package can also be run in an agile way. Clear prioritisation is the key.
What should be clarified before a fixed-price offer?
Core features, user roles, platforms, interfaces and acceptance criteria. The clearer these points are, the more accurately and cheaply a fixed price can be calculated.