Retainer billing is when a client pays your agency a fixed, recurring fee — almost always monthly — for an agreed amount of work, capacity or access over that period. Instead of quoting and invoicing every job separately, you agree one number and one cycle, and it repeats until somebody changes it.
That's the definition. Now the bit nobody puts in the definition.
The retainer is the invoice you think about least. Same client, same number, same date — it just goes out. Which is exactly why it's usually the one quietly losing you money. The fee is fixed. The hours aren't. One month the client goes quiet and you're miles up. Next month it's three rounds of revisions, a deck they need by Friday and a "quick favour" that eats a day... and you're eleven hours over without noticing, because nothing in your process was watching.
I ran an agency for years and this was the trap every time. Not the dramatic non-paying client. The retainer that ran itself right into a loss while I congratulated myself on how low-maintenance it was.
So: the models, how to actually invoice them, what to do with leftover hours, and how to get the loop running without you.
What are the main retainer models?
There are three that actually turn up in agency contracts: a fixed-scope (deliverables) retainer, a rolling hours retainer, and a value or access retainer. They differ in what the client is really buying — output, time, or availability. That one difference changes how you price it, how you invoice it, and which way it goes wrong.
The fixed-scope (deliverables) retainer
A set fee each month for a set list of things. Four blog posts, one campaign, a monthly report. Output in, money out.
Where it's good: easiest one to sell, because the client can see exactly what they get. Easiest to defend at renewal too — you point at the list and the list happened.
Where it hurts: the list says "four blog posts". It doesn't say how many rounds of revisions, and that's where your margin lives. Two clients on the identical retainer can be twice as profitable as each other purely on how fussy they are. Put the revision count in the agreement, not in your head.
Fits: content, SEO, social, anything with a repeatable monthly output shape.
The rolling hours retainer
The client buys a block of time each month — 20 hours, 40 hours — and you spend it on whatever they need. The most honest of the three in a way, because you're selling the thing you're actually consuming.
Where it's good: flexible for the client, fair for you, and overage is unambiguous. You went over, here's the hours.
Where it hurts: it turns you into a timesheet business and invites the client to think in hours rather than outcomes. It also punishes you for getting faster — the better you get, the less you bill. And you must track properly, because here the tracking isn't admin, it's the product.
Fits: dev support, ongoing maintenance, "we need a marketing person two days a week" arrangements.
The value / access retainer
Not a deliverable, not a block of hours. The client is buying you being there — strategic input, priority in your queue, a call when something breaks.
Where it's good: highest-margin of the three by a distance, because it's priced on what your availability is worth rather than what it costs you.
Where it hurts: hardest to sell, hardest to keep. In a quiet month the client sees a big invoice and no obvious pile of work, and starts doing sums. Make the value visible or the renewal conversation gets awkward fast.
Fits: senior consulting, fractional exec work, long-term clients who trust you already.
Most agencies run a hybrid without calling it one — a deliverables retainer with an hours cap under it. That's fine. Just write down which one you're actually running, because the invoicing has to match the model. A rolling-hours retainer billed like a subscription is how you give away a day a month for free.
How do I invoice clients for monthly retainers?
Invoice on the same date every cycle, in advance rather than arrears where you can, with the period covered and what's included printed on the invoice itself. Then automate it — because the hard part isn't knowing how to raise the invoice, it's raising it on time, every time, for years.
Here's the loop end to end:
- Agree the fee, the cycle and what's included — in writing. Fee, billing date, included hours or deliverables, revision count, what happens to unused hours, what overage costs. If it isn't in the agreement it becomes a negotiation later, and you'll lose it. Use the retainer agreement template if you don't have one.
- Set the billing date and stick to it religiously. Pick a date — 1st, 15th, whatever — and never move it. Invoicing on the 3rd, then the 7th, then the 2nd trains the client's accounts team that your invoice is a surprise. A retainer that lands on the 1st every month becomes furniture, and furniture gets paid.
- Raise the invoice on the same day each cycle, in advance not arrears. You're being paid for the coming month's capacity, so bill for the coming month. The money then arrives near the start of the work rather than 45 days after it finished.
- Track delivered hours against the fee as the month runs. Not at the end. As it runs. You want to know you're at 22 of 25 hours on the 18th, while you can still do something about it — not on the 3rd of next month when the options are eat it or start an argument.
- Bill overage the same month it happens, never "next time". Extra hours in March go on the March invoice, as their own line. Park it for later and it stops being a line item and becomes a favour you did.
- Automate the whole loop. Invoice raises itself, hours reconcile against the fee on their own, reminders chase without you deciding to be the bad guy. Anything in that list that depends on you remembering will eventually not happen — usually in the month you're busiest.
That's the process. There's a hands-on version with a worked example and the invoice layout in how to invoice clients for monthly retainers, with a template.
What should you do with unused retainer hours?
Pick one of three policies and write it into the agreement before month one: use-it-or-lose-it, capped rollover, or bank-and-review. There's no universally right answer — but there is a universally wrong one, which is having no policy and improvising when the client asks in month four.
Use-it-or-lose-it. Hours reset at the end of each cycle. Clean, and it's what the client is really buying with an access retainer — reserved capacity, which costs you whether they use it or not. The catch is it feels harsh after a genuinely quiet month, and if you enforce it silently you'll hear about it at renewal. Say it out loud when you sign, and again the first time it bites.
Capped rollover. Unused hours carry into the next cycle up to a limit — say 20% of the block, expiring after one month. The one I'd default to for most agencies. Fair, stops the client feeling robbed for a slow month, and the cap and expiry stop the horror scenario.
Bank-and-review. Hours accumulate and you look at the balance together every quarter. Sounds generous and collaborative. In practice it's the one that gets agencies in real trouble, because a client can bank 30 hours over a quiet summer and cash the lot in during your busiest week. If you do it: cap the bank, put an expiry on it, and make the quarterly review an actual meeting.
The honest take — which policy you pick matters less than you think, and having one matters more. Any of the three works if it's written down and applied consistently. None of them work if the first time the client hears about it is the month you decide to enforce it.
When does a retainer beat milestone billing?
A retainer wins when the work is ongoing and continuous with no natural finish line — support, maintenance, always-on marketing, being available. Milestone billing wins when the work has a defined outcome and a shape: a build, a rebrand, a site, anything you could draw a finish line under.
The test is simple. Can you describe "done"? If yes, that's a project, and it should be billed against stages that get signed off. If the honest answer is "it's never done, it just continues"... that's a retainer.
Getting it backwards is expensive both ways. A project forced onto a retainer drifts — no stage gates, no sign-offs, and the thing takes nine months because nothing forced it to finish. A continuous relationship chopped into fake milestones means inventing deliverables to justify invoices, which is admin theatre clients see straight through.
Plenty of agencies run both at once for the same client. Build it on milestones, move to a retainer for support after launch. That's not a compromise, it's matching the billing to the work.
How do you automate retainer invoicing?
Three things have to happen without you touching them: the invoice raises itself on the cycle, delivered hours reconcile against the fee automatically, and payment reminders escalate on their own. Automate one and you've saved some admin. Automate all three and the retainer actually runs itself instead of just feeling like it does.
Most tools only do the first.
The invoice should raise itself. Set the fee and the date once, it goes out every cycle without a human deciding to do it. Nearly every invoicing tool manages this — it's the easy bit, and where most of them stop.
Hours should reconcile against the fee automatically. This is the one that matters and the one almost nothing does. Your time data lives in one place, your invoice in another, so hours delivered and hours sold never meet. That gap is the retainer trap. It needs closing during the month, with a flag when you're getting close and a louder one when you're past it.
Reminders should escalate without you. A retainer that doesn't clear shouldn't wait for you to work up the nerve. Polite heads-up, then a nudge, then something firmer — on a schedule, identically for every client, so it never reads as personal.
That's what Handl's retainer billing is built to do. Invoices raise automatically on the retainer cycle. Hours get pulled from the tools your team already uses — Harvest, Toggl, Clockify, Hubstaff, or straight out of Monday, Asana, Jira, ClickUp or Linear — and tracked against the retainer fee, with a flag when delivered hours run past what's included, so scope creep shows up while you can still bill it. The AI billing agent sends the scheduled, escalating reminders when a retainer doesn't clear. Clients pay by link — no login, no portal account to create — and the money lands in your own Stripe account. Invoices sync to Xero (QuickBooks rolling out; MYOB coming soon), and your upcoming invoices become a cash-flow forecast instead of a guess.
I built it that way because my retainer failures were never invoicing failures. The invoice always went out. What never happened was anyone noticing, on the 18th, that we were about to give away a day and a half.
FAQ
What is the best software for retainer management and invoicing?
Depends entirely on where the pain actually is, and it's worth being honest about that before you buy anything. If the pain is delivery — briefs, tasks, who's doing what — that's a PM tool problem and no billing tool fixes it. If it's the books, that's your accounting platform. If it's the money side of the retainer — invoice not going out on time, hours quietly exceeding the fee, chasing payment every month — that's the lane Handl is built for, from $29/mo with a 7-day free trial. Pricing is by plan, not per seat, which matters for retainer work: most tools that track hours properly charge per user, so the bill grows with every account manager you add.
What should a monthly retainer invoice include?
Six things: the retainer fee; the period it covers (spell out the dates — that one line prevents most retainer payment queries); what's included for the fee, in hours or deliverables; delivered hours if you're giving the client billing visibility; any overage as its own line rather than folded into the total; and a payment link with your terms and due date.
Should retainers be invoiced in advance or arrears?
In advance for anything about capacity or access, in arrears only where the retainer is purely hours-based and the hours genuinely can't be known until the period ends. Advance protects both sides, which is the part people miss. You get paid near the start of the work you're committing capacity to, not 30-plus days after it finished — and the client gets a predictable amount on a predictable date they can plan around, rather than a variable number arriving after the fact. Arrears billing also has a habit of drifting later and later, until you're financing your client's operations for free.
The bottom line
Pick the model that matches what the client is actually buying. Write the fee, the cycle, the inclusions and the rollover policy down before month one. Invoice the same day, every cycle, in advance. Watch hours against the fee while the month is still running, and bill overage in the month it happens. Then take yourself out of the loop, because the only part of this that ever fails is the part that needs you to remember.
Hands-on version — worked example, invoice layout, common mistakes — is in how to invoice clients for monthly retainers, with a template. Setting a new one up from scratch, start with the retainer agreement template and get the awkward bits agreed while everyone's still friendly.