A retainer is the same client with the sales cost removed. Decide whether you are selling availability, outcomes or a block of scope — and never mix them. Three shapes that work for a solo freelancer, when to have the conversation (not at the end), how to price from what the last project actually took, and the rollover rule to write before month one.
The hardest thing about freelancing is not the work. It is that every month begins with an empty pipeline and the unpaid effort of refilling it. A retainer fixes that specific problem: it is the same client, continuing, with the sales cost removed. But retainers also fail in a characteristic way — they get agreed warmly and vaguely, and six months later you are doing twice the work for a fixed fee and cannot say when that happened. This guide is about the mechanics: which shape to sell, when to raise it, how to price it from evidence, and the two clauses that keep it fair.
Why a retainer is worth more than its rate
Compare two freelancers with identical monthly income. One earns it from four new clients found each month; the other from two retainers and one project. The second is doing materially less work for the same money, because the first is paying a hidden tax: the hours spent finding, qualifying, proposing and onboarding, none of which anybody pays for. On a retainer that cost is near zero after month one.
There is a second, less obvious benefit. Continuity makes you better at the work. You already know the client's systems, their brand, their approval habits and who actually decides things, so a task that would take a stranger a day takes you two hours. That accumulated context is real value you are delivering and it is the honest justification for a retainer being good for the client too — you are faster and you make fewer mistakes than whoever they would hire instead.
And predictability changes decisions. Knowing a baseline of income is arriving lets you turn down badly-scoped work, take a week off without arithmetic, and raise your rates on new clients from a position of not needing them. That is worth more than the difference between a retainer rate and a project rate.
Decide what you are actually selling
This is the decision that determines whether the retainer works, and it is the one most people skip. There are three things you can sell monthly, and mixing them is precisely how retainers go underwater — because when the scope is ambiguous, both sides default to their own reading, and the client's reading is always more generous than yours.
| You are selling | The client is buying | Goes wrong when |
|---|---|---|
| Availability | The right to reach you, and a response time. Capacity reserved whether or not it is used. | You never state what the reserved capacity is, so a quiet month sets the expectation and a busy one feels like a betrayal. |
| Outcomes | A defined result each month: four articles, a monthly report, a working site with uptime maintained. | The outcome sounds fixed but the effort behind it is not — “four articles” quietly becomes four articles plus research plus five revision rounds. |
| A block of scope | A stated quantity of your time or work per month: a set number of hours or a set number of tasks. | Unused amounts roll over forever and you end up owing a quarter's work in one month. |
Pick one and name it in the agreement in a single sentence. “This retainer reserves 20 hours of my capacity per month with a one-working-day response time” is an availability retainer. “This retainer delivers four published articles per month” is an outcomes retainer. They are different products with different risks, and a sentence containing both — reserved hours and guaranteed deliverables and unlimited revisions — is a retainer that will end badly for you.
Three shapes that work for a solo freelancer
All three are variations on the choice above, sized for one person with no team to absorb overflow.
- Maintenance and support. A monthly fee for keeping something you built working: updates, backups, small changes, a stated response time for urgent problems. The natural follow-on to any build, and the easiest to justify because the client can see what happens without it. Cap the small changes at a number of hours or tasks so “small” does not expand.
- A capacity block. A set number of hours or working days per month, booked in advance, used on whatever the client needs. Works well for clients with genuinely varying needs, and it is honest about the fact that you are selling time. Requires a rollover rule, which is the next section.
- A recurring deliverable. A fixed output on a fixed rhythm: a monthly report, a weekly set of designs, four articles. The cleanest to sell because the client knows exactly what arrives, and the most important one to bound — state what a unit includes, how many revision rounds it carries, and what happens when a request is twice the usual size.
What does not work for a solo freelancer is an unbounded “I look after all your design needs” arrangement. It sounds like a strong relationship and it is an uncapped liability with a capped price, which is the definition of a deal that gets worse the better it goes.
The conversation that converts, and when to have it
Timing is most of it. The instinct is to raise a retainer at handover, when the project is finished and you are saying goodbye. That is the worst moment: the client's attention has moved on, their budget for this thing is closed, and the proposal arrives as a request rather than as a continuation.
Raise it while the project is still running and going well — around the point the last milestone is in sight and the client is visibly pleased. At that moment you have three things you will never have again in combination: their attention, demonstrated competence, and a live budget conversation. You are not asking for a favour; you are naming something they are about to need.
And the way in is not a pitch, it is an observation about what happens next. The strongest version is specific to their situation and slightly inconvenient for them to ignore.
Once this goes live, a few things will need doing every month — plugin and security updates, the product photos you mentioned rotating seasonally, and someone to look at it when something breaks. I can take that on for a fixed monthly fee so you are not finding someone each time. Want me to put a simple proposal together, or would you rather handle it in-house and call me when something comes up?
Three things make that work. It names real, specific ongoing needs rather than offering vague availability. It positions the retainer as solving their recurring problem, not filling your calendar. And it gives them a genuine and unembarrassing way to say no, which is exactly why more of them say yes — an offer with no exit attached invites a polite deferral instead of a decision.
Pricing from what the last engagement actually took
You have something most people pricing a retainer do not: evidence. You just finished a project for this client, so you know how they behave — how often they message, how many revision rounds they need, how long their approvals take, whether their requests arrive as clear briefs or as voice notes on a Sunday.
Use it. Go back over the last engagement and count the real monthly load: hours on deliverables, plus hours on communication, plus the invisible time on coordination and rework. Then price from your own floor rate rather than by guessing at a round number — the arithmetic for that floor, and why it has to be based on realistic billable hours rather than theoretical ones, is in setting your freelance rates.
Two adjustments. Add a margin for the fact that reserved capacity has a genuine cost: turning down other work to hold space for this client is worth something, and a retainer priced identically to ad-hoc project work is a discount you are giving for no reason. Then set the quantity slightly below what you measured rather than at it — if the real load was about 18 hours a month, sell 15 with a stated rate for anything beyond it. A retainer you can comfortably deliver renews for years; one that runs slightly over every month becomes something you resent by month four, and resentment is what ends these arrangements, not price.
Review it quarterly, and exit it cleanly if you must
Every retainer drifts. The scope you agreed in January is not what you are doing in July, usually through nobody's fault — their business changed, or you started absorbing adjacent requests because it was easier than a conversation. So put a review in the arrangement from the start: “we will look at this every three months and adjust if the shape of the work has changed.” Having agreed the review in advance turns an awkward renegotiation into a scheduled routine, and it is far easier to raise a price at a review you announced in month one than to raise it out of nowhere in month nine.
Bring evidence to the review rather than a feeling — the log of what you actually did each month, which is also the thing that makes the case obvious. A habit of tracking it as you go is worth building anyway, and it belongs with the other systems in staying productive as a solo freelancer.
And sometimes a retainer should end. The work has shrunk to nothing but the invoicing continues; the client has become the one whose messages you dread; the scope has grown past what the fee can justify and they will not adjust it. End it deliberately and in writing: give proper notice, offer to document everything and hand over cleanly, and if it is a fit problem rather than a relationship problem, say so honestly. “I do not think I am the right person for where this has gone — I would rather tell you now than do it at half my attention” is a message people respect. Handled that way you keep the reference and the review, and the client will often come back for a project later. If you need to refill that slot, the selection discipline in which projects to bid on is how to do it without wasting a month of bids, and the projects board is where to start.
The takeaway: a retainer is the same client with the sales cost removed, so it is worth more than its rate. Decide whether you are selling availability, outcomes or a block of scope, name it in one sentence, and never combine them. Raise it while the project is still running and going well, not at handover, and frame it around their recurring need with a genuine way to say no. Price from what the last engagement actually took, including communication and rework, then sell slightly less capacity than you measured. Write the scope boundary and the rollover rule before month one, and review it every quarter.