Subscription Billing for Freelancers: Retainers vs Packages vs Subscriptions
Recurring revenue is the closest thing freelancing has to a salary. But "recurring billing" isn't one thing — it's three different models, and picking the wrong one causes most of the pain: retainers that turn into unlimited-access deals, packages that clients treat as all-you-can-eat, or subscriptions nobody understands. This guide explains retainers vs packages vs subscriptions, when each fits, how to price them, and how to invoice them without scope creep.
The three models, side by side
Retainers: reserved time or capacity
A retainer is a fixed fee the client pays — usually monthly — for guaranteed access to a set amount of your time or capacity. Example: a web developer keeps a client on a $1,200/month retainer for up to 20 hours of maintenance and small fixes. The client pays whether they use the hours or not, which is the entire point: they're paying for availability, not for tasks completed.
Best when: clients need ongoing, unpredictable work — maintenance, consulting, design tweaks, marketing support. The workload varies month to month, so a flexible-but-committed model beats per-project pricing.
Packages: a fixed bundle for a fixed price
A package is a defined set of deliverables for a fixed recurring price. Example: a copywriter sells a $900/month package of four blog posts and one newsletter. Same work, same schedule, same price every month. Nothing varies except the topics.
Best when: your service is repeatable — content, social media management, bookkeeping, SEO reporting. The work is predictable, so you can productize it and sell the same package to many clients.
Subscriptions: productized access or output
True subscriptions are closer to SaaS pricing: the client pays a recurring fee for an outcome or access, not for your hours. Example: a designer sells a $750/month "unlimited design requests, one at a time" subscription, or a freelancer sells a monthly reporting dashboard. The price is tied to the deliverable, and hours are your problem, not the client's.
Best when: you've systemized delivery enough that your time per client is predictable. This is the most scalable model — but also the one where underpricing hurts the most, because the client never sees your hours.
Which model fits your work?
Ask three questions:
- Does the workload vary? If some months need 5 hours and others need 25, choose a retainer. If it's the same every month, a package or subscription works.
- Does the client need availability or output? Lawyers on retainer sell availability ("call me when something breaks"). Content agencies sell output ("four posts a month"). Match the model to what the client actually buys.
- Can you deliver without constant scoping? Subscriptions only work when you can say no — or charge extra — for out-of-scope requests. If every month needs negotiation, use a retainer with clear boundaries instead.
A common path: start with retainers to learn what clients actually ask for, then productize the recurring requests into packages once the pattern is obvious. Many freelancers run both — packages for the repeatable work, retainers for the clients who want flexibility.
How to price each model
Retainers: start from your hourly or day rate, then discount slightly for the commitment. A $100/hour freelancer might price a 20-hour retainer at $1,800/month instead of $2,000 — the client gets a ~10% discount, you get guaranteed income. Set the retainer below your comfortable capacity (20 hours of retainer capacity for a 40-hour week is plenty) so spikes don't drown you. See our retainer invoicing guide for the full structure.
Packages: price on value and market position, not hours — though you should know your hours to make sure the package is profitable. If four blog posts take you 12 hours and you want an effective rate of $75/hour, the package floor is $900. Price against competitors selling the same package, then differentiate on scope or extras, not on being cheaper.
Subscriptions: price by the outcome, and build in your efficiency gains. If your system lets you deliver a design subscription at 6 hours a month and the market will pay $750, your effective rate is $125/hour — higher than project work, which is the reward for systemizing. The risk is a client who submits 30 requests in a week; the fix is a fair-use clause (see below).
Across all three: charge enough that the recurring income is worth the commitment. A recurring contract that pays your project rate with a small discount is normal. One that pays half your rate in exchange for "stability" is a discount you keep paying forever.
The contract terms that prevent the common failures
Every recurring agreement needs five clauses, whatever the model:
- Scope, in writing. What is included — and what isn't. A retainer for "up to 20 hours of maintenance" should say maintenance means bug fixes and small updates, not new features.
- Rollover policy. Do unused hours or deliverables roll to next month? Most freelancers say no — use-it-or-lose-it is the standard, and it's fair because the client was paying for availability. If you allow rollover, cap it (e.g. one month, up to 50%).
- Response time and boundaries. A retainer doesn't mean instant replies. State your response window (e.g. one business day) and your working hours.
- Payment timing and failure. Bill in advance — recurring fees are for the coming period, not the past one. State what happens if a payment fails: work pauses after a stated grace period (e.g. 7 days). Don't chase recurring invoices by hand; set up the schedule once — our guide to setting up recurring invoices walks through a workflow that works anywhere.
- Termination notice. 30 days' notice, in writing, is the standard. It protects you from a client disappearing mid-month and protects them from being locked in.
How to invoice each model (practically)
Retainers: invoice on the 1st of the month for the coming month — "Retainer fee, November 2026 — up to 20 hours maintenance and support." Add a line item each month only if something varies (extra hours at the agreed rate, reimbursed expenses). Keep invoice numbering sequential across the year like any other invoice.
Packages: same cadence — monthly, in advance. The line item stays identical each month, which makes reconciliation easy for both sides. If the client adds one-off extras, put them on a separate invoice so the package invoice never changes.
Subscriptions: identical invoicing to packages — monthly in advance, fixed line item. The difference is commercial, not administrative: the client is buying access or output, so the line item should describe the service tier ("Design subscription — Standard tier, monthly") rather than hours.
A practical tip: send recurring invoices on the same day each month and include the service period in the line item ("1–30 November 2026"). Clients process regular, predictable invoices faster than irregular ones, and the period reference prevents "wait, what month was this for?" emails. Generate them free with our invoice generator and keep the formatting identical month to month.
Transitioning project clients to recurring
Don't pitch "want to switch to a retainer?" out of nowhere. Look for the trigger: a client who's bought three one-off projects in six months is spending inefficiently and knows it. Say so: "We've done three projects this year at $2,000 each. A $500/month package would cover what you actually use and save you $500 a month." You're selling convenience and savings, not asking for commitment.
Start with a 3-month minimum term, not 12. It's easier to sell, and by month three the client has built their workflow around you — renewal is the path of least resistance.
FAQ
Is a retainer better than project pricing? For income stability, yes — a full roster of retainer clients is the closest freelancing gets to a salary. For total earnings, not always: project pricing lets you raise rates with every new client, while retainers lock rates for the contract term. Many freelancers mix both: retainers for baseline income, projects for growth.
Should unused retainer hours roll over? The standard answer is no. The client paid for your availability during that month — you turned down other work to keep capacity free. Rolling hours over turns a retainer into a prepaid bank of hours, which defeats the model. If a client pushes, offer a limited rollover (e.g. up to 25% of hours, for one month) rather than full rollover.
How many retainer clients should I take? Fewer than you think. Total your committed retainer hours and keep them under 60–70% of your working capacity. The rest is for project work, business development, and the inevitable month when every retainer client needs something urgent at once.
What happens if a subscription client abuses the "unlimited" model? Pause and renegotiate. Your contract's fair-use clause is the enforcement mechanism: "subscription covers reasonable request volume; sustained usage above [X] requests per week will be quoted separately." In practice, a direct conversation fixes most cases — clients rarely intend to abuse the model, they just don't see your queue.
Can I raise prices on recurring clients? Yes — with notice. Standard practice is an annual review with 30 days' written notice. Grandfathering existing clients at old rates forever is a common mistake; inflation and rising demand are legitimate reasons, and clients who value you will accept a reasonable increase. Price the increase into the renewal conversation, not mid-contract.
Retainer vs milestone billing — which for a 6-month project? For a defined project with a clear end, use milestone billing — payments tied to phases, with a deposit up front. Retainers are for open-ended ongoing relationships. If the "project" keeps growing new phases, that's the sign to convert it to a retainer.
---
Ready to send your first recurring invoice? Use our free invoice generator — no sign-up, no watermark — or check your effective rates with the freelance rate calculator before you set the price.