Pricing · 7 min read
Retainer or project: which one fits
Most of the friction in an ongoing working relationship traces back to one decision made at the start: whether this was a project or a retainer, and whether both sides agreed.
Updated 30 August 2026 · GoDesign build team

The short version
- A project buys an outcome. A retainer buys availability. Confusing the two is the source of most disputes.
- Retainers work when the need is continuous and unpredictable in shape but predictable in volume.
- The most common failure is a retainer that is really a discount on project work with no defined scope.
- Both models need an explicit answer to what happens to unused capacity.
Almost every awkward conversation in a long-running client relationship traces back to a single unexamined decision: whether the arrangement was a project or a retainer, and whether both parties understood it the same way.
The distinction is not about duration or size. It is about what is being bought. A project buys a defined outcome — this exists at the end, and it did not before. A retainer buys availability: a certain amount of capacity, reserved, applied to whatever turns out to matter.
When each one fits
| Situation | Model | Why |
|---|---|---|
| A website that does not exist yet | Project | Clear outcome, definable end |
| Ongoing changes to a site that does | Retainer | Continuous need, unknowable in detail |
| A migration | Project | Finite, with an obvious completion |
| Someone available when things break | Retainer | Availability is the product |
| A rebrand | Project | One outcome, then done |
| Content published monthly | Retainer | Predictable volume, variable subject |
The pattern in the right column: projects suit work whose shape is known in advance, retainers suit work whose volume is known but whose shape is not.
The retainer that is really a discount
This is the most common failure mode in the category. A client and a supplier agree a monthly fee without defining what it buys, on the shared assumption that it will roughly work out. It roughly works out for a few months and then does not.
It fails in one of two directions and both are bad. Either the client uses very little and starts to feel the fee is unearned, or the client uses a great deal and the supplier starts to feel the fee is inadequate. Neither party did anything wrong; the agreement simply had no shape.
The unused capacity question
This deserves its own treatment because instinct points the wrong way. The intuitive answer is that unused hours should roll over, since the client paid for them. In practice rolling hours reliably breaks retainers.
What happens is that a balance accumulates over several quiet months, then gets spent in one demanding month — at which point the supplier is delivering three months of work in one while receiving one month's fee, and has no capacity left for anyone else. The arrangement that was meant to smooth demand has amplified it instead.
The workable positions are: hours do not roll over, and the fee is understood as buying reserved availability rather than a quantity of output; or hours roll over with a hard cap and an expiry, which limits the accumulation. What does not work is unlimited rollover, however reasonable it sounds when the agreement is signed.

What each side is actually getting
It helps to name the trade honestly, because the value is real on both sides and is often left implicit.
- The client gets a supplier who already knows the system, responds faster because there is no requoting cycle, and can be asked small questions without a commercial conversation attached to each one.
- The supplier gets predictable income, which lowers the cost of sale substantially and shows up as a better rate for the same work.
- Both get accumulated context, which is genuinely valuable and never appears on an invoice — the second year of any relationship is more efficient than the first.
That second point is why retainers can be priced better than the equivalent project work without either side losing. Predictability is worth real money to a supplier, and some of that saving can reasonably be passed on.
The simple test
Ask what happens if nothing needs doing next month. If the honest answer is that the fee is still fair because availability was the product, a retainer is right. If the answer is that it would feel like paying for nothing, the work is project-shaped and should be bought that way, however continuous the relationship feels.
Questions people ask
What is the difference between a retainer and project work?
A project buys a defined outcome — something exists at the end that did not before. A retainer buys availability: reserved capacity applied to whatever turns out to matter. The distinction is not about size or duration, and confusing the two causes most of the friction in ongoing relationships.
When does a retainer make sense?
When the need is continuous and its volume is predictable but its shape is not — ongoing site changes, someone available when things break, content published monthly. Work whose shape is known in advance, such as a build, a migration or a rebrand, is project-shaped even if the relationship is long-running.
Should unused retainer hours roll over?
Not without a cap. Unlimited rollover accumulates a balance over quiet months that gets spent in one demanding month, leaving the supplier delivering three months of work for one month's fee with no capacity for anyone else. Either hours do not roll over and the fee buys reserved availability, or they roll with a hard cap and an expiry.
What should a retainer agreement specify?
How much capacity, over what period, what it can be spent on, what is out of scope, and what happens to unused capacity. Four sentences. A retainer missing any of them produces an argument eventually, in one of two directions — the client feeling the fee is unearned, or the supplier feeling it is inadequate.
How do I decide which model to use?
Ask what happens if nothing needs doing next month. If the fee still feels fair because availability was the product, a retainer fits. If it would feel like paying for nothing, the work is project-shaped and should be bought that way regardless of how continuous the relationship feels.
Built by GoDesign FZE, who build WhatsApp and CRM automation for UAE businesses.
Get in touch
Want someone to just do this part?
The tool is free and stays free. If you would rather hand the work over, tell us what you are dealing with and you get a straight answer on scope, cost and timeline.
- You own everythingRepository, hosting and domain credentials sit in your name from day one, not handed over at the end.
- A written timelineMilestone dates are agreed in writing before work starts, so you always know what ships next.
- One business dayEvery enquiry gets a reply from the person who would scope the work, not a sales sequence.
Media City, Dubai, UAE · DHA Phase 2, Islamabad, Pakistan
Would rather type than fill in a form?
Message on WhatsApp