Retainers Explained: When They Beat Hourly Billing for Freelancers

A retainer beats hourly billing when a client needs you regularly and you would rather have predictable income than bill in fits and starts. Below is what a retainer actually is, when it pays off, and when hourly is still the smarter call.

Quick answer

A freelance retainer is a fixed fee a client pays in advance — usually every month — to reserve your time or a set of deliverables. Instead of counting every hour after the fact, you both agree up front on what the fee covers. The trade-off is simple: a retainer gives you steady, predictable revenue and the client a specialist on call, while hourly billing keeps things flexible when the work is one-off or hard to scope. Retainers win when the relationship is ongoing; hourly wins when it isn't.

How it actually works

A retainer agreement is a contract whose defining feature is that the client pays in advance for work to be specified later. The fee reserves your future availability, and it can be a one-time payment or, more commonly for freelancers, a recurring monthly one.

In practice, retainers come in three shapes:

• Hours-based. The client buys a block of hours each month — say 20 hours at a $75 rate, for $1,500 a month — and assigns work within your skill set up to that limit.
• Deliverable-based. The client pays a flat monthly fee for a defined output, like four articles or a set of design updates. The fee stays the same regardless of how long each piece takes.
• Access-based. The client pays mainly for priority availability — you keep capacity reserved so they can reach you quickly when something comes up.

The reason retainers appeal to freelancers comes down to cash flow. Freelance income is naturally lumpy: if you wait until a project wraps to invoice, you can go weeks between payments. Spreading work across recurring monthly billing, as Stripe's freelance billing guide notes, makes earnings far more predictable. A few reliable retainers become the baseline that covers your fixed costs, so project work and new clients add to a floor instead of replacing it.

When to use it (and when to skip it)

Reach for a retainer when the work is ongoing and roughly steady — a client who needs the same kind of help most months, where you can predict the demand well enough to price it. It rewards relationships: the client gets a dependable specialist, you get income you can plan around, and the constant re-quoting of one-off jobs disappears.

Skip the retainer when the scope is genuinely undefined or the work is a single project with a clear end. As Stripe's overview of billing types puts it, hourly billing is transparent and fair precisely when scope keeps shifting — you bill for what you actually do, and neither side guesses. For a brand-new client you haven't worked with, a few hourly or project-based engagements first let you learn the real workload before you commit to a fixed monthly number.

Be honest about the trade-offs, because retainers have two failure modes. The first is the unused allotment: a client who pays for 20 hours but only uses five starts to feel they're wasting money, and the arrangement gets cancelled. The second is scope creep — when "a quick favor" quietly expands the work without expanding the fee. The fix for both is a written scope. An effective retainer agreement spells out what the fee covers, the billing cycle, and how out-of-scope work is handled, which heads off disputes before they start.

If you're torn, a hybrid works well: a smaller retainer base for the predictable work, plus an hourly rate for anything beyond it. You keep the steady floor and still get paid fairly for the busy months. Whichever model you pick, knowing what counts as billable hours and how to set your freelance rate is what makes the number defensible.

How Pomlo fits in

Retainers only work if you can see where the hours actually go — otherwise the unused-allotment and scope-creep problems above are invisible until a client is unhappy. That visibility is exactly what Pomlo is built for, and it's the simplest way to keep a retainer honest.

With Pomlo you start and stop a timer in one tap, then organize that time by projects and clients, so you always know how many of this month's retained hours a given client has used. The reports turn those logs into a clear picture of where your week went, which tells you whether a retainer is priced right or quietly bleeding hours. And when a client goes over their block, Pomlo's invoicing turns the tracked overflow into an invoice in one tap — no reconstructing the month from memory. It stays in sync across iOS, Android, and the web, and your data is never sold or used to train models.

If you're moving clients onto retainers, track your time with Pomlo so every agreement stays profitable. Download it on the App Store or Google Play.

Frequently asked questions

How many hours should a retainer cover?

Base it on a few months of real data, not a guess. Track how long the recurring work actually takes, then set the block slightly above the average so normal months fit comfortably. Starting too high invites the unused-allotment problem; starting too low means you eat the overflow.

What happens to unused retainer hours?

That's a term you set in the agreement. Some freelancers let a small amount roll over to the next month; others treat the fee as payment for reserved availability that doesn't roll over. Either is fine — just state it in writing so the client isn't surprised.

Is a retainer better than hourly for a brand-new client?

Usually not at first. Run a project or a few hourly engagements to learn the real workload and whether the relationship fits, then convert to a retainer once the demand is predictable. Committing to a fixed monthly number before you know the rhythm is how retainers end up mispriced.

How do I stop scope creep on a retainer?

Define what the fee covers in writing, then track time against it so you can see when a client is drifting past the agreed scope. A short, factual conversation backed by real hours is far easier than a vague sense that you're doing too much.