Fixed Price vs Time and Materials: Choosing a Software Contract Model

Two men at a meeting table reviewing a printed software contract with a laptop and coffee cups

Before a line of code is written, every custom software project needs a commercial agreement, and the contract model you choose shapes everything that follows: how risk is shared, how changes are handled and how much flexibility you have along the way. For most NZ businesses, the decision comes down to fixed price vs time and materials software contracts. Both can work well, and both can go badly if they are used in the wrong situation.

This guide explains how each model works, where each one fits, the risks to watch for and the hybrid options many teams use in practice. The aim is to help you choose an agreement that protects your business while still giving the project room to succeed.

What is a fixed price software contract?

Under a fixed price contract, you and the development partner agree on a defined scope, a set price and a delivery schedule before work starts. The supplier commits to delivering that scope for that price, usually in NZD excl. GST, and payments are often tied to milestones.

The appeal is obvious: you know the cost up front, which makes budgeting and board approval simpler. The catch is that the price is only as reliable as the scope it is based on. If requirements are vague or change during the project, the contract needs a change process, and those changes cost extra.

When fixed price works well

  • The scope is small, clear and unlikely to change.
  • Requirements are documented in detail, ideally after a discovery phase.
  • The project replicates something well understood, such as a defined integration or a website rebuild with known features.
  • Your organisation needs a firm budget figure for approval or funding.

Risks of fixed price contracts

  • Built-in contingency. Suppliers carry the risk of overruns, so quotes typically include a buffer to cover uncertainty.
  • Rigid scope. Good ideas that emerge mid-project trigger change requests, paperwork and extra costs.
  • Misaligned incentives. Under pressure, a supplier may deliver the letter of the specification rather than what you actually need.
  • Long upfront specification. Writing a detailed enough spec takes time before any building begins.

What is a time and materials contract?

Under a time and materials (T&M) contract, you pay for the actual time the team spends, at agreed hourly or daily rates, plus any direct costs such as third-party licences or hosting. Work is usually planned in sprints, with priorities reviewed regularly.

T&M gives you flexibility. You can change priorities as you learn, drop features that turn out to be unnecessary and add ones that prove valuable. The trade-off is less certainty about the final cost, so it relies on good reporting, trust and active involvement from your side.

When time and materials works well

  • The product is new, and requirements will evolve as users give feedback.
  • You are building an MVP and want to learn quickly.
  • The project is ongoing, such as continuous improvement of an existing platform.
  • You want to be closely involved in setting priorities.

Risks of time and materials contracts

  • Budget uncertainty. Without discipline, costs can creep as scope grows.
  • Requires oversight. You need someone available to review progress and make decisions.
  • Depends on trust. You are relying on the supplier to work efficiently and report honestly.

Fixed price vs time and materials: a side-by-side comparison

Factor Fixed price Time and materials
Cost certainty High, if scope does not change Lower, managed through budgets and caps
Flexibility Low; changes need formal requests High; priorities can shift each sprint
Who carries the risk Mostly the supplier, priced into the quote Mostly the client, with full visibility
Upfront effort Detailed specification required Lighter planning, refined as you go
Best suited to Small, well-defined projects New products, MVPs, evolving requirements
Your involvement Heavy at the start and at acceptance Regular, throughout the project

Hybrid models that combine the best of both

In practice, many software projects use a combination rather than a pure model. Common hybrids include:

Fixed price discovery, then time and materials

A short, fixed price discovery phase defines requirements, designs and an estimate. The build then proceeds on T&M with a clear backlog. You get early cost clarity and a well-informed estimate without locking in every detail too soon.

Capped time and materials

The team works on T&M, but with an agreed budget cap or “not to exceed” amount. If the cap is approached, both parties review scope before going further. This gives flexibility with a safety net.

Fixed price per phase or milestone

The project is split into smaller stages, each with its own fixed price. Later stages are priced once earlier ones are complete and more is known. This reduces the risk of a large fixed quote based on guesswork.

Fixed budget, flexible scope

You set the budget and timeframe, and the team delivers the most valuable features possible within it, prioritising together. This works well for MVPs where the deadline and spend are firm but the exact feature list is not.

How to choose the right model for your project

Ask yourself these questions:

  1. How clear is the scope? If you could write a detailed specification today and expect it to hold, fixed price is viable. If not, lean towards T&M or a hybrid.
  2. How much will you learn along the way? New products almost always change once real users try them.
  3. How firm is your budget? A hard limit suggests fixed price, capped T&M or fixed budget with flexible scope.
  4. How involved can you be? T&M works best when someone on your side can attend sprint reviews and make decisions.
  5. How well do you know the supplier? Trust matters for T&M. A small fixed price first project can be a good way to build it.

If you are unsure, an independent IT consulting session can help you scope the work and decide which model suits it.

What to include in any software contract

Whichever model you choose, a good agreement should cover:

  • Scope and deliverables, including what is explicitly out of scope.
  • Change process, describing how new requests are estimated and approved.
  • Intellectual property, making clear who owns the code, designs and data, and when ownership transfers.
  • Source code access and handover, so you are not locked in to one supplier.
  • Acceptance criteria that define when work is complete.
  • Warranty and support, including how defects are handled after launch.
  • Data protection, covering how personal information is handled in line with the Privacy Act 2020.
  • Payment terms, with rates or milestone amounts stated in NZD and whether GST is included.

It is wise to have significant contracts reviewed by a lawyer, particularly for larger projects or where IP ownership is important to your business.

Common mistakes to avoid

Whichever way you lean, a few mistakes come up again and again:

  • Choosing fixed price for an idea that is still forming. The quote ends up based on assumptions, and the change requests start in week two.
  • Comparing quotes on headline price alone. Two fixed quotes can cover very different scope, testing and support. Compare what is actually included.
  • Running T&M without a backlog or budget. Flexibility without priorities quickly becomes drift.
  • Leaving IP and handover until the end. Agree ownership and source code access before work starts, not when the relationship is under strain.
  • Skipping discovery to save money. A short discovery phase usually costs far less than the rework caused by misunderstood requirements.

How we approach contract models

As an Auckland software development company, we discuss the contract model openly at the start rather than defaulting to one. For well-defined work, a fixed quote can make sense. For new products and evolving platforms, we usually recommend a discovery phase followed by sprint-based delivery with regular demos and transparent reporting. You can read more about our team and how we work.

Frequently asked questions

Is fixed price always cheaper?

Not necessarily. Fixed price quotes typically include contingency for risk, and changes cost extra. For uncertain projects, T&M can work out better value because you only pay for work actually done.

Can we switch from fixed price to time and materials mid-project?

Yes, if both parties agree. It is common to move to T&M once the first release is live and the project shifts to ongoing improvement.

How do we control costs on a time and materials project?

Agree a budget or cap, prioritise the backlog, review progress at every sprint and ask for regular reports on hours spent against estimates.

Which model is better for an MVP?

MVPs usually suit T&M or a fixed budget with flexible scope, because requirements tend to change once early users give feedback.

Who owns the code under each model?

Ownership depends on the contract, not the pricing model. Make sure your agreement clearly assigns IP and includes source code handover.

Do prices include GST?

Business quotes in New Zealand are commonly stated excl. GST. Always check the contract so there are no surprises when invoices arrive.

Choose a contract that sets your project up to succeed

The right contract model matches how certain your scope is, how firm your budget is and how involved you want to be. Fixed price suits small, clear projects; time and materials suits products that will evolve; and hybrids often give the best balance. If you would like to talk through the options for your project, book a free 60-minute consultation with our Auckland team.

Share Article:
About Author

Consectetur sollicitudin cubilia facilisis lobortis lacus a ac phasellus. Mus pulvinar enim suspendisse pharetra id commodo platea nunc aliquet.