Agile vs Fixed-Price Contracts: Which Protects You Better?
Key takeaway
Fixed price transfers risk to the vendor, who prices it in and defends scope; time and materials transfers risk to you. A phased, capped agile contract — fixed scope and price per phase, re-planned between phases — gives most buyers the budget certainty they want without freezing decisions they can't yet make.
Contract structure is usually treated as procurement's problem and then quietly determines how the project runs. A fixed-price agreement makes every change a negotiation; an open time-and-materials one makes every week a leap of faith.
Fixed price
- Good for: genuinely well-defined, bounded work — a migration, an integration, a redesign with agreed screens.
- Reality: the vendor adds a risk premium, typically 20–40%, and has a commercial incentive to interpret scope narrowly.
- Fails when: requirements will evolve, because every discovery becomes a change request with its own approval cycle.
Time and materials
- Good for: exploratory work, ongoing product development, and teams with strong internal product ownership.
- Reality: you carry the estimating risk and need real visibility to keep it honest.
- Fails when: nobody on the client side is actively prioritising — spend continues whether or not value is produced.
Capped agile — the structure most projects should use
Break the engagement into phases of six to ten weeks. Each phase has a fixed scope, a fixed price, and a defined deliverable. Between phases you re-plan with everything you learned. You get budget certainty in the increment that matters, and the freedom to change direction at every boundary.
- Phase one is usually discovery, priced separately — and should leave you with a plan you could take elsewhere.
- Include an explicit change mechanism: swaps of equal size within a phase need no contract amendment.
- Define acceptance per phase in testable terms, not by adjectives.
Clauses worth more than the rate card
- IP assignment on payment — unambiguous, covering code, designs, and documentation.
- Source control in your own organisation from day one, not handed over at the end.
- Key-person continuity, and notice if a named lead is replaced.
- Exit terms: knowledge transfer, documentation standard, and a defined handover period.
- Warranty period for defects after each phase's acceptance.