Fixed-price = vendor commits to deliver agreed scope for agreed price. Risk shifts to vendor; reward is predictability for client.
Why fixed-price fails:
- Underestimated initial scope.
- Scope creep without renegotiation.
- Quality cuts to make budget.
- Client demands beyond scope.
- Burnout from compressed timelines.
Practices that make fixed-price work:
1. Tight scope definition.
- Detailed Statement of Work (SOW) — every deliverable enumerated.
- Out-of-scope explicitly listed.
- Assumptions documented (X sandboxes, Y profiles, Z integrations, etc.).
- Acceptance criteria per deliverable.
2. Conservative estimation.
- Add buffer (20-30%) for unknowns.
- Estimate top-down and bottom-up; reconcile.
- Validate with similar past projects.
- Don't bid optimistically to win — you'll lose money.
3. Aggressive change control.
- Every new ask = formal change order.
- Change orders = additional time / money.
- "I just need this small thing" — politely route to change control.
- Document everything.
4. Phased structure.
- Even fixed-price projects can be phased: Phase 1 fixed-price for X scope; Phase 2 separately scoped.
- Avoids one giant fixed-price commitment for a project that should evolve.
5. Sponsor alignment.
- Sponsor understands the trade-off: predictable price requires fixed scope.
- Sponsor backs the change control process when their team pushes for changes.
- Without sponsor backing, change control collapses.
6. Quality preservation.
- Don't cut testing, training, or documentation to make budget.
- Save by reducing scope, not skipping necessary work.
7. Risk reserves.
- Allocate 15-20% of budget as risk reserve.
- Use only when needed; don't pad estimates.
8. Transparency.
- Share progress regularly.
- Surface risks early.
- Hidden problems become catastrophic.
9. Strong project management.
- Daily standup, weekly status, monthly steering.
- Track burn rate vs budget weekly.
- Course-correct early if deviations.
Common pitfalls:
- "We'll just absorb the change" — small absorptions accumulate.
- Overworking the team to compensate for poor scoping.
- Cutting corners on quality — eventually surfaces in defects, low adoption.
- Conflict with client when changes pile up — relationship damage exceeds project value.
When NOT to use fixed-price:
- Highly uncertain scope (Discovery still pending).
- Volatile requirements (industry changes, evolving regulations).
- Innovation projects (don't know what will work).
Time-and-materials is more honest for those.
Senior consultant insight: fixed-price requires discipline from BOTH sides. The vendor disciplines scope and execution; the client disciplines change requests. Without both, fixed-price collapses.
Many fixed-price projects are actually time-and-materials in disguise once change orders pile up. Plan for that with a strong change control process from day one.