Project work creates income spikes — good months and empty ones. A retainer agreement smooths that out by securing recurring work at a fixed monthly rate. But a retainer that isn’t structured properly can create more problems than it solves: clients who expect unlimited access, disputes about what’s covered, and cancellations at exactly the wrong time.
Here’s what a fee retainer agreement should contain, and how to set one up so it actually works.
What a fee retainer agreement is
A fee retainer agreement is a contract that establishes an ongoing working relationship between a freelancer and a client, typically on a monthly basis. In exchange for a fixed monthly fee, the freelancer provides a defined scope of services, a defined number of hours, or dedicated availability.
There are two main structures:
Hours-based retainer: The client pays for a defined number of hours per month (e.g., 20 hours). The client directs how those hours are used within an agreed service area. Any work beyond the monthly allocation is billed at the freelancer’s standard rate.
Scope-based retainer: The client pays a fixed fee for a defined set of recurring deliverables (e.g., 4 blog posts + 1 monthly email campaign). The deliverables are the same each month. Hours aren’t tracked; the fee covers the output.
Both structures work. Hours-based retainers give the client more flexibility. Scope-based retainers give the freelancer more predictability. Choose based on your service type and how variable the client’s needs are.
The terms that matter most
Monthly fee and payment timing. Define both explicitly. The fee should be stated as a number ($X/month), not an hourly rate applied to estimated hours — the point of a retainer is a predictable cost for both parties.
Payment timing is where retainers often create cash flow problems. If the client pays at the end of the month after the work is delivered, you’re essentially extending credit. Paying in advance — on the 1st of the month before work begins — is standard for retainers and the professional default. State this clearly in the agreement.
What’s included. Define the scope in the same specific terms you’d use in a project proposal. If it’s hours-based: the number of hours, the service category, and what counts against the hours (calls, revisions, research). If it’s scope-based: each deliverable, its format, and its revision limit.
What’s excluded. Add a short “not included” section. If you’re a developer on a monthly retainer for feature work, clarify that DevOps, on-call support, and emergency bug fixes are separate. This prevents the retainer from expanding into unlimited availability.
The most common retainer dispute is a client who treats a scope-based retainer as unlimited access. A clear “not included” section in the agreement, signed before work begins, prevents this from becoming a mid-engagement argument.
Unused hours or deliverables. If it’s an hours-based retainer, state whether unused hours roll over, expire, or can be banked. The cleanest policy: hours expire at the end of the month and don’t roll over. This removes the accounting complexity of tracking balances and reinforces that the fee is for availability, not just output.
Cancellation notice. Both parties should be able to exit the retainer with reasonable notice — typically 30 days. This matters for both sides: the freelancer needs enough time to fill the income gap, and the client needs enough time to transition the work. A retainer with no cancellation clause can create legal ambiguity about when it ends.
What out-of-scope requests look like in a retainer
Even within a retainer, clients will sometimes request work that falls outside the defined scope. Handle this the same way you’d handle a project scope change: acknowledge it as out of scope, provide an estimate, and proceed only after written approval.
The retainer agreement should reference this process explicitly: “Requests outside the defined scope will be handled as separate work orders at [rate or fixed price].”
How to propose a retainer to an existing client
The easiest time to set up a retainer is after a successful project. The client already knows your work quality, and you’ve established trust. The transition can be as simple as: “I have availability to continue working with you on [service area]. If it would be useful to have dedicated capacity each month, I can put together a retainer proposal.”
Then treat the retainer proposal the same way you’d treat a project proposal — specific scope, clear pricing, defined terms. A tool like Waco3 lets you build the retainer proposal as a structured quote with recurring line items, so the terms are in writing. Use DocuSign or HelloSign for the digital sign-off so you have a formal record.
Common mistakes to avoid
Retainers without payment-in-advance terms. If you wait until month-end to invoice, you’ve delivered 30 days of work before seeing a cent. Always pay in advance.
Scope defined as “ongoing support.” This is an open invitation to scope creep. Define what support means: response within 24 hours, up to X requests per week, covering these service areas.
No cancellation notice period. A client who cancels with a week’s notice on a $3,000/month retainer creates a significant income gap. Thirty days is standard and reasonable.
Forgetting to review the retainer annually. Retainers that were set at your rates from two years ago may no longer reflect the current scope of work or your current pricing. Schedule an annual review when the agreement is signed.
A fee retainer agreement, properly structured, is one of the most valuable arrangements a freelancer can have. Predictable income, a defined working relationship, and a client who’s committed to the engagement — that’s worth the time it takes to write a clear agreement.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
