Fixed-Price vs Retainer — Choosing the Right Engagement
Risk lives somewhere — pick where
Fixed-price puts scope risk on the vendor (good for defined builds) and change friction on you. Retainers put roadmap flexibility with you and utilization risk on the vendor. Neither is universally better; each fits different uncertainty levels.
The decision rule
Locked scope with acceptance criteria: fixed-price with milestone payments (30/40/30). Evolving roadmap with continuous delivery: monthly pods, pausable with notice. Most relationships start fixed (build trust on a bounded outcome) and graduate to retainers (velocity on the roadmap).
Change handling in both
Fixed-price: change requests priced in 48 hours with swap/extend/defer options — no silent creep either direction. Retainers: reprioritize any sprint; the backlog absorbs change by design. The failure mode to avoid is fixed-price billing with retainer-style evolving scope — ambiguity both sides resent.
Related Articles
Discovery Process for Software Projects — The Two-Week Blueprint
Stakeholder maps, technical specs, and fixed quotes: what paid discovery delivers.
Remote Team Rituals — Stand-ups, Demos & Trust at Distance
The five rituals that make distributed teams outperform colocated ones.
Technical Debt Paydown — The 20% Rule That Actually Works
Debt registers, interest pricing, and sprint allocation that keep velocity from collapsing.
Written by Agile Lead
Specialized engineering teams at Omnetra focus on writing high-performance code, ensuring API security, and optimizing layouts for client success.