Retainer or fixed project: how to decide
A decision rule for agencies and teams choosing between monthly capacity, fixed scope or ongoing support.
7 min · Updated 2026-07-14
There is no universally better model. The right choice depends on how often priorities change, whether the outcome can be accepted objectively and who carries uncertainty.
01
Fixed project
Use it when there is a concrete piece, a date, known dependencies and an acceptance criterion. The price covers defined scope and assumptions.
- Landing, integration, API or release with a defined outcome.
- An owner available to accept milestones.
- Changes handled as scope changes.
02
Monthly retainer
Use it when several small or medium fronts exist and priority changes during the month. It buys capacity and judgment, not an unlimited task list.
- Agency peaks and technical presales.
- Variable evolutives, QA and integrations.
- Visible priority and consumption.
03
Support and evolution
Use it when a live product needs continuity. It should distinguish emergencies, fixes, improvements and out-of-window work; it is not the same as 24/7 availability.
04
The deciding question
If you can describe what counts as done, a fixed project probably fits. If you can only prioritize work as it appears, you need monthly capacity. If the system is already live and needs continuity, you need support rules.
A short diagnostic can also reduce uncertainty before selecting the longer-term model.
Useful next step
See the full comparison