Fixed Price vs Time and Materials for Custom Software
Match the commercial model to how much you know about scope and how often you expect to revisit priorities.

Choose fixed price when the software scope and acceptance criteria are stable enough to estimate. Choose time and materials when priorities are likely to change as the team learns. Under either model, agree on spending controls, change approval and handover.
Key takeaways
- Compare proposals using the same scope and assumptions.
- Define how changes affect cost or schedule.
- Review progress and remaining spend at agreed intervals.
What changes under each model?
| Decision | Fixed price | Time and materials |
|---|---|---|
| Scope | Defined deliverables with agreed acceptance | Prioritised backlog reviewed as evidence changes |
| Price basis | Agreed price for the defined work | Actual approved effort and other charges at agreed rates |
| Change | Written change request with cost or date impact | Reprioritisation within agreed capacity, with approval to raise it |
| Budget control | Milestones, payment terms and defined exclusions | Forecast to complete, burn review and explicit approval for extra spend |
| Main uncertainty | What counts as included and who owns client or vendor dependencies | How much work the budget will buy and when priorities change |
Which would fit two fictional projects?
Repeatable import. A buyer can supply sample data, known mappings and pass/fail acceptance cases. Fixed price may fit after the vendor has verified access and representative files, including malformed rows. Agree who owns subsequent format changes.
New service portal. Staff are still testing which intake steps they need and which records the existing platform exposes. A time-and-materials discovery phase with a spend ceiling and review date allows the team to test assumptions. Once a release is defined, the buyer can ask for a fixed proposal or continue with a controlled backlog.
What should you ask regardless of the model?
Agree who can request and approve changes, how often you review progress, what evidence is required for acceptance, and how work is handed over if delivery stops. In time and materials, separate a spend ceiling from a guarantee of specific scope. In fixed price, ask how assumptions and dependencies can change the price or date.
Start with a shortlist of acceptance cases, known dependencies and unresolved questions. Use the custom software scoping brief to prepare a conversation with vendors. Discuss a software project with Wizy.
Frequently asked questions
Can discovery and development use different pricing models?
Yes. A buyer can use a time-and-materials discovery phase with a spending cap, then ask for a fixed-price proposal once requirements and dependencies are better understood.
Does a time-and-materials cap guarantee all requested features?
A cap limits the authorized spending under the agreed terms. Ask which backlog items fit the available capacity and how the team will adjust priorities if the estimate changes.
How should you handle a scope change in a fixed-price project?
Document the proposed change, verify why it falls outside the agreed scope and record its impact on cost, dates and acceptance before approving it.
