How a designer or developer bills a retainer client
Most designers and developers spend the early part of their careers trading invoices for projects — a logo here, a build there, a check that arrives three weeks after the work is done. The retainer model changes all of that. It converts your expertise from a transaction into a standing relationship, and your income from an irregular series of receipts into something you can plan around. Getting there requires understanding not just what a retainer is, but how to price it, what clauses actually protect you, how to handle the friction points that break most retainer arrangements, and how to ensure the money actually lands when the month turns over. That is what this article covers.
What a retainer actually is — and what it is not
A freelance retainer is a contract agreement between a freelancer and a client that guarantees an agreed-upon amount of work for a set rate. The agreement can include a set amount of hours or a predetermined number of deliverables and usually occurs on a monthly basis. That sounds simple. In practice, there is an important distinction that most freelancers blur, and it costs them.
A retainer is not a prepaid project. It is not a discount package. It is not a subscription where the client buys access to you and then squeezes you for everything they can get. A freelance retainer is a way of pricing your work on an ongoing basis, instead of transactionally after each project is completed. Clients are paying to retain your services — they are essentially reserving a time slot with you for whatever work they may need done. That distinction — reserving your capacity — is the conceptual foundation the whole model rests on. When a client pays a retainer, they are not buying completed deliverables at a discount. They are buying priority access to your skills, your calendar, and your context about their business.
Retainer agreements should not be work-for-hire or employment contracts. You should retain your independence and status as an independent creative. Clients cannot tell you how, when, or where you do the work. This matters legally and practically. If a retainer agreement starts to look like employment — specific working hours, a required workspace, daily supervision — you have a classification problem. Write the contract to reflect what a retainer actually is: a guaranteed output or capacity commitment, fulfilled on your schedule.
The three retainer structures designers and developers actually use
Hours-based retainers
This is the most common freelancing rate structure for retainers and arguably the most flexible. You agree on a set number of hours per month at your standard or slightly discounted hourly rate. If the client uses 5 hours, they still pay for 10.
This works well when work volume is genuinely variable month to month — a growing startup whose design needs spike around product releases, a SaaS company that calls on you for front-end work whenever a sprint demands it. The client gets a predictable monthly cost. You get a floor.
The risk here is invisible scope creep. One real danger of retainers is scope creep. Since many retainers are set on billable hours and not projects, it’s common for freelancers working on retainer to be slowly given more work over time. Their initial agreement to do no more than 12 hours of work a month, for example, may become burdensome as they become more efficient at their job and the client wants more. The answer is not to avoid hours-based retainers — it is to build the overage structure into the contract from day one, and to track hours with the same discipline you would use if you were billing hourly from scratch.
Deliverables-based retainers
Rather than selling hours, you sell a defined set of outputs each month. Four UI screens. Two rounds of review on new landing page copy. Monthly plugin updates plus performance testing. One component library addition per sprint cycle. This model works beautifully for content marketing retainers, bookkeeping arrangements, and ongoing graphic design requests where a standard deliverable set can be packaged cleanly.
The advantage for you is that as you get faster and more familiar with a client’s systems, your effective hourly rate rises without any renegotiation. This is where you start building real profit margins because efficiency becomes one of your best revenue drivers. As you get faster at delivering the agreed-upon work, your effective hourly rate for that retainer goes up automatically — without raising prices or renegotiating.
The risk is underestimating the scope of what the deliverables actually require. A “monthly newsletter design” sounds clean until the client wants a full redesign of the template every quarter. Define not just what the deliverable is, but what it includes: number of revision rounds, whether strategy calls count toward the deliverable, what constitutes a new request versus an iteration.
Hour-block retainers
The IT industry popularized this contract approach to reduce surprise billings from unexpected hardware and software updates. In this unique agreement, the client buys “blocks” of hours ahead of time — for example, 10 hours at $850. Then they use that block until the time runs out, almost like a gas tank.
This structure suits clients who have irregular but recurring needs and who are uncomfortable committing to a monthly ongoing fee. It is particularly useful as a bridge into a full retainer: propose hour-blocks first, let the client see how quickly they burn through capacity, then use the usage data to convert them to a monthly arrangement with predictable volume. Blocks are an easy and non-committal way for clients to understand your relationship.
Pricing a retainer correctly
Most freelancers underprice their first retainer because the security of guaranteed income feels like compensation in itself. It is not. You are giving the client something concrete — priority access, calendar reservation, institutional knowledge of their product — and that has real value above your standard rate, not below it.
Retainer pricing guarantees a fixed monthly fee in exchange for a set number of hours or deliverables, giving the freelancer predictable income and the client priority access. A $3,000/month retainer for 20 hours of design work provides $36,000 in annual guaranteed revenue from a single client. Work from that math backwards. What is your current effective hourly rate on project work? How many months per year do you run short on work? If you have three slow months where your utilization drops to 60%, a retainer at a 5-10% effective discount versus your project rate still produces more total annual revenue than the same hours sold at full rate with that gap.
As a freelance designer, adding a 20% flexibility window — for example, $4,000 a month for approximately 44–56 hours per month — lowers the average hourly rate modestly and gives the client flex time for increased need. Any work in excess of those hours is billed hourly. The monthly rate is collected in advance of the month where the work exists, almost like rent on an apartment.
That “like rent” framing matters. Rent is paid before you occupy the space. Your retainer should work the same way. Retainers are paid in advance of service. This means that you receive payment from the client up front and then perform the work for that month. If you allow payment-in-arrears on a retainer, you have eliminated the primary structural protection the model provides. You are back to chasing money at the end of the month.
Discounting: when it makes sense and when it doesn’t
Some experienced freelancers choose not to discount their rates at all with retainers. Instead they offer a flat monthly fee in exchange for a set amount of time, roll over unused hours, use change orders for time over the set amount, and guarantee availability to the client. The main thing retainer clients receive is priority over other clients.
This is a defensible position, particularly if your pipeline is consistently full. If the pipeline has gaps — and most freelance pipelines do — a retainer at a 10% discount still produces higher annual income than the same hours sold at full rate with two or three slow months per year. The calculation is empirical. Track your actual utilization for three months before you decide whether the volume guarantee is worth a rate concession.
What you should never do is use retainer discounts as a sales tactic without understanding the math. Underpricing is a real danger — starting too low because you are excited about guaranteed income. Price based on data, not desperation.
What goes in the contract
A retainer contract does not need to be a 20-page legal document. It does need to address five specific things clearly.
Scope definition. Not just “design work” or “development support.” The retainer contract should specify the types of work covered: a “20 hours of design work” retainer needs to clarify whether that includes strategy calls, revisions on past deliverables, and rush requests, or only net-new creative production. The more specific this is, the easier it is to enforce the overage structure.
Unused hours policy. This is where most retainer disputes originate. If the client uses 5 hours, they still pay for 10. Unused hours roll over for up to two months in most contracts, which gives the client breathing room while keeping your baseline income intact. Decide your rollover policy before the conversation starts. Two months is reasonable. Indefinite rollover is a liability because it creates a phantom obligation that can suddenly come due.
Overage rate. Unused hours should be tracked and rolled over into the next month. Hours over the monthly number in your contract scope should be billed in addition to the retainer. The overage rate is typically your standard project rate, sometimes with a 10-20% premium to account for the disruption of unplanned work. Set it at something you’re comfortable defending in a conversation.
Minimum commitment and termination. Long-term contracts for retainer packages commonly include a minimum commitment — for example, three months — and define exit clauses. This prevents sudden cancellations and ensures payment for time already booked. Thirty-day written notice is the standard. Without this, a client can cancel on the 29th of the month after you’ve declined other work to hold their capacity.
Single point of contact. You don’t want to give everyone in the client company the freedom to contact you. Get the client to appoint one person who is allowed to speak to you on behalf of the entire client company. When there is no single contact, you end up serving four people who each believe their request is within scope. Requests multiply, hours disappear, and the retainer becomes unprofitable.
Converting a project client into a retainer client
The cleanest path to a retainer is through a project you’ve already delivered. A retainer starts out as a regular project. You design or write something for a client and deliver it. That first one-off project is critical — you get to evaluate the client, and they get to evaluate you. You figure out how well you really work together.
After delivery is exactly when to raise the retainer conversation. The client knows your work, trusts your process, and still has the product fresh in mind. They also know — even if they haven’t articulated it — that the website needs maintenance, the brand needs new touchpoints, the codebase will need updates. Converting a project client to a retainer client happens naturally when the project ends and the client asks about ongoing support.
Freelance retainers are particularly well-suited to web design because websites need constant maintenance. Rather than springing into action every time a client needs a bug fix, you might suggest a retainer agreement. You could offer the client a set amount of updates along with monthly AB testing, analytics analysis, or SEO work to add value to their site.
For developers, the same logic applies to any application in active use. As a website developer, you could provide ongoing website maintenance to ensure that your client’s website is up-to-date and continues to perform well. Security patches, dependency updates, performance monitoring, feature iterations — this is not padding the retainer, it is accurately describing what responsible stewardship of a codebase requires.
The framing matters in this conversation. Do not present a retainer as a discount. Present it as a structural improvement to how you work together. By presenting it as an easier way to work together — eliminating much of the administration that hourly work can require — it can be the selling point you need to land that ongoing arrangement.
Managing the ongoing relationship
The single biggest operational mistake: not tracking time
Even if your retainer is deliverables-based, track your time. You need the data to price the next retainer renewal accurately, to identify scope creep before it becomes a problem, and to make an informed case for rate increases. Not tracking time is a genuine risk. If your retainer is hours-based, you need accurate time tracking. Without it, you will either over-deliver and lose money, or under-deliver and lose the client.
Run a monthly internal reconciliation: hours committed versus hours used, overage billable, and pattern of requests. If a client is consistently burning 130% of their monthly allocation, raise the base before the resentment sets in. If they are consistently using 50%, have a conversation about restructuring — either reducing the retainer or expanding the scope so the value is more visible.
Rate increases on retainer clients
Retainers create stability, but they can limit the way you do business. You are agreeing to a set amount of work at a set price. Once you’re locked into that price, it can be difficult to raise rates.
The solution is to build a rate review mechanism into the contract from the start. Annual increases tied to the contract renewal are standard and unremarkable to a sophisticated client. What is harder to navigate is a mid-contract rate request. If you find yourself in that position, anchor the conversation in scope change — the nature of what you are doing has shifted, the complexity has increased, the volume has grown. Lead with data from your time tracking.
When a retainer client asks for more than the contract allows
This is where most retainer arrangements start to erode. The client sends a request that sits ambiguously at the edge of what the agreement covers. The instinct for many freelancers is to absorb it rather than have a friction-generating conversation. That instinct is expensive.
A practical approach is to agree the extra services upfront in writing, make sure you can fit them into the timeframe necessary, and then invoice the extra as an additional payment at the end of the month rather than mixing it up with the retainer invoices. This keeps the retainer amount clean and predictable, makes the overage visible as a separate line, and trains the client — gradually, without drama — that the retainer has real boundaries.
The payment mechanics that actually work
Bill before the month, not after
The single most important mechanical decision in retainer billing is timing. Bill on the first of the month for the month ahead, not at the end of the month for work completed. If the client does not pay the retainer, you do not do the work. If the client pays late, you do not do the work until they pay, and you can also charge a late fee if it is included in your contract.
This sounds firm. It is. It is also the only way the retainer model provides what it promises. If you are waiting to be paid after performing work, you have an accounts receivable problem. If you are paid in advance and then deliver, you have a retainer.
Automating collection
Recurring invoices handle retainer billing automatically, so the same invoice generates on the first of each month without manual re-creation. Set this up once in your invoicing system and let it run. The invoice should be identical every month unless the overage from the previous period has been calculated — in which case a separate overage invoice keeps the base retainer amount clean and readable.
The payment method matters more than most freelancers realize. Bank transfers have clearing delays that mean a client who pays on the 1st might not have funds in your account until the 3rd or 4th. Card payments have chargeback exposure. For retainer relationships that run month over month with significant dollar amounts, you want payment that is immediate, final, and not subject to reversal.
That is precisely where onchain payment infrastructure changes the equation. When a retainer has multiple recipients — say, you and a subcontractor you work with, or you and a business partner — Shaka lets you set the split at the contract level so that when the client’s monthly payment lands, it routes to each wallet instantly, in one transaction, without a secondary disbursement step. The month turns over, the payment moves, everyone is made whole in the same moment. No clearing window, no float, no chasing anyone.
Late payment handling
You might also charge interest if a monthly retainer payment is late by a certain amount. Whether you actually collect late fees is a judgment call based on the relationship and the dollar value. What matters is that the clause exists. Its presence changes how clients prioritize payment. An invoice with no consequence for lateness invites lateness.
The practical escalation is: invoice on the 1st, follow up on the 5th if unpaid, hold work on the 8th. These thresholds should be in the contract. When they are, the conversation is never personal — it is procedural. “The contract specifies work holds until the retainer is current. Let’s get you reinstated.”
When a retainer is the wrong structure
Not every client relationship belongs in a retainer. Retainers can leave a bad taste in the mouths of smaller clients who are poised for growth. A one-off client who just wanted you to design a logo may not see retainer potential.
The right retainer candidate is a client with a confirmed pattern of ongoing work — not a hope or a projection, but a track record. Clients who need 10 to 30 hours of work per month on an ongoing basis are ideal retainer candidates. Social media management, website maintenance, content production, and design support all generate recurring, predictable work.
If you are pitching a retainer to a client who has never bought more than one project from you, the conversation may be premature. Do the project. Do it well enough that they ask what ongoing support looks like. Then you have a retainer conversation with demand already established.
Retainer agreements can be time-based, project-based, or type-of-work based, and are used when providing creative services for a prolonged period of time. When a project involves months of work, a retainer can be a better option than hourly or progressive billing. But if the engagement has a natural end point — a product launch, a rebrand, a specific build — a milestone-based project structure is almost always cleaner. Retainers are for the ongoing relationship that follows.
Building a retainer-anchored practice
Experienced freelancers with a strong reputation and recurring client relationships shift toward retainers for baseline income and value-based pricing for high-impact projects. The retainer covers monthly operating costs. Value-based engagements produce outsized income on projects where the business outcome is measurable.
This is the architecture of a mature freelance practice: a base layer of retainer income that is stable and predictable, and a project layer on top that is higher-margin and higher-variability. Neither layer depends on the other. The retainers do not constrain the projects; the projects do not substitute for the retainers.
For example, with four retainer clients each contracted at $3,000 per month, you can guarantee $12,000 total for the month. When you know how much money you’ll bring in each month, you can plan for taxes, set aside money for savings, and figure out how much to pay yourself without worrying about where the money is going to come from or how many more clients you need to bring in to reach your goal.
The professionals who build practices like this — with retainer income predictable enough to plan against — are not doing anything exotic. They are applying the same discipline to their billing structure that they apply to their craft: define the scope clearly, hold the boundary, deliver at a level that makes the relationship worth renewing every month. The mechanics of getting paid are the last thing that should introduce uncertainty into that relationship. When the contract is solid, the scope is clear, the invoice goes out on the first, and the payment lands the same day — you stop thinking about billing and go back to doing the work.
