Before a software project starts, you and the developer have to agree how the bill will be worked out. The two common answers are fixed price, where you agree a total for a defined scope, and time and materials, where you pay for the effort actually spent at agreed rates.
Neither model removes uncertainty from a software project. It only decides who carries it and how changes get paid for. This guide explains how each model works, when each suits, how milestones and change requests should run, and the clauses to put in writing whichever you choose.
Quick answer: Choose a fixed-price contract when the scope can be written down clearly before work starts and budget certainty matters most. The vendor carries the effort risk, and changes go through priced change requests. Choose time and materials when requirements will evolve and you can take part every week. You pay for hours used, controlled with a rate card, caps and timesheets. Many projects combine both.
How a fixed-price contract works
The vendor studies your requirements, writes a specification and agrees a total price for it. The work is split into milestones, and you pay a portion as each milestone is delivered and accepted. If the work takes longer than the vendor estimated, that is the vendor's problem, not yours.
That certainty has a cost. Because the vendor carries the risk of underestimating, a fixed quote usually includes a margin for the unknown. And because the scope is the basis of the price, anything outside it becomes a change request with its own price and schedule. Fixed price works well when you know what you want. It gets uncomfortable when you discover what you want during the project.
How a time-and-materials contract works
You agree rates for each role, such as developer, designer or tester, per hour, day or month. The team works through a prioritised list of features, and you are billed for the time actually spent, usually monthly, backed by timesheets or a work log.
You gain flexibility. You can change priorities every sprint, drop features that no longer matter and add ones you discover you need. In return, you carry the risk that the work takes longer than hoped. Time and materials needs someone on your side who joins sprint reviews, makes decisions quickly and watches spending against the budget.
Fixed price vs time and materials at a glance
| Aspect | Fixed price | Time and materials |
|---|---|---|
| Scope | Agreed in writing before work starts | Evolves through a prioritised backlog |
| Budget certainty | High for the agreed scope | Depends on caps and how you manage priorities |
| Who carries the effort risk | The vendor | You |
| Handling changes | Formal change requests, priced separately | Reprioritise the backlog; cost follows effort |
| Your time needed | Heavy at the start, lighter during the build | Regular, throughout the project |
| Suits | Defined projects, a clear first version, integrations with known APIs | New products, unclear requirements, ongoing enhancement |
| Main risk | Disputes about what was in scope | Budget drift without caps and reporting |
Hybrid models
Many projects run well on a mix. A common pattern is a short, paid discovery phase that produces a specification, followed by a fixed price for the first version, then time and materials with a monthly cap for enhancements after launch. Another is capped time and materials: you pay for actual effort, but the contract sets a ceiling that cannot be crossed without your written approval.
How milestones and change requests should work
Arguments on software projects often come down to two questions: is this milestone really finished, and is this request a bug fix or a new feature? Settle both in the contract, before work starts.
- Define each milestone by what you can test, such as "invoice module working on the test server with GST calculation", not by a date or a percentage of work done.
- Attach acceptance criteria to each milestone, plus an acceptance window in working days, after which silence counts as acceptance.
- Link payment to acceptance, with an advance at the start if agreed and the final payment on handover of source code and documentation.
- Use a written change request for anything outside the specification: what changes, why, the effort, the price, the effect on the schedule and your sign-off before work begins.
- Keep a change log that both sides can see, so the final invoice holds no surprises.
- Separate bugs from changes: something that does not match the specification is a defect, fixed at no extra cost. Something the specification never described is a change.
A clear specification makes all of this easier. Our guide on writing a software requirements document explains what it should contain.
What to put in the contract
- Scope annexure: the specification, its assumptions and an explicit list of what is out of scope.
- Commercial model: the fixed price per milestone, or the rate card with a monthly or total cap.
- Reporting: for time and materials, weekly or monthly timesheets showing who worked on what.
- Payment and tax: the payment schedule, GST invoices from the contracting entity and how TDS will be handled. Check the TDS treatment with your CA.
- Change process: the change request steps above, including who on your side can approve a change.
- IP and source code: assignment of source code, database schema and documentation to you on payment, delivered through a repository in your name.
- Confidentiality: a mutual NDA covering your data and business processes.
- Warranty: a period after go-live during which defects against the specification are fixed at no charge.
- Support: post-warranty support as a separate, priced agreement rather than an open-ended promise.
- Exit terms: how either side can end the contract, what is paid for work done and how code and credentials are handed over.
To see how scope drives the budget under either model, try our software development cost estimator.
How EthicsComputer can help
EthicsComputer works under both models. On a fixed-scope project, discovery typically takes 1–2 weeks and produces a written specification, an architecture and a milestone roadmap with a fixed quote before you commit to the build. For evolving products, a dedicated team works in two-week sprints on your roadmap and is billed monthly. Every software development project includes a mutual NDA, milestone sign-off and full source code and IP handover, and custom software and MVPs start from ₹45,000 for a modern frontend and secure backend, role-based access, REST APIs and webhooks, and database design.
Not sure which contract model fits your project?
Share your requirement and we will suggest a contract model, a scope and a milestone plan you can review before you commit.
About the author
Vinay Grover founded EthicsComputer in Rohtak, Haryana in 2018 and leads its cybersecurity, software and AI work for clients across India and abroad. EthicsComputer is ISO 9001, ISO/IEC 27001 and ISO 20000-1 certified.