When does a retainer beat paying per project?

When the work is continuous and unpredictable in shape but steady in volume, and when the cost of re-explaining context each time is material. Where work is genuinely occasional and self-contained, per-project — or a marketplace — is cheaper and simpler.

What usually goes wrong with them?

Three things, all avoidable in writing: unclear rollover of unused hours, no definition of what falls outside the retainer and gets quoted separately, and no review cadence, so a figure set for one workload quietly persists through a very different one. Agree all three up front and review on a fixed schedule.

Retainers — capacity vs availability | Getting Digital glossary

Retainer

Also: monthly retainer, ongoing engagement, retained work

A retainer is a recurring fee that reserves a supplier's capacity or guarantees their availability over a period, buying continuity and access rather than a specific delivered artefact.

Two different things sold under one word

A capacity retainer buys an agreed block of work each month — say two days — with the client deciding what fills it. An availability retainer buys priority access and a guaranteed response time, whether or not any work is requested. They price differently and fail differently, and most retainer disputes come from the two sides having assumed different models.

For the supplier the appeal is predictable income and the end of constant repricing. For the client it is a person who already holds the context — which is the genuinely valuable part, and the thing a per-task marketplace cannot supply, because context does not survive being re-explained to a new contractor every time.

Decide the rollover rule before month two

Do unused hours roll over? If yes, you can accumulate an unbounded liability and a client who "banks" months then expects them all in December. If no, say so plainly at the outset — discovering that policy retrospectively, in a quiet month, is how otherwise good retainers end.

Key takeaways

→Capacity and availability retainers are different products; agree which one you are in before the first invoice.
→The real asset is retained context — someone who already knows the system, which is exactly what per-task hiring cannot provide.

FAQ

When does a retainer beat paying per project?: When the work is continuous and unpredictable in shape but steady in volume, and when the cost of re-explaining context each time is material. Where work is genuinely occasional and self-contained, per-project — or a marketplace — is cheaper and simpler.
What usually goes wrong with them?: Three things, all avoidable in writing: unclear rollover of unused hours, no definition of what falls outside the retainer and gets quoted separately, and no review cadence, so a figure set for one workload quietly persists through a very different one. Agree all three up front and review on a fixed schedule.