By Mehdi HassanWhat terms should a design retainer agreement include?
A design retainer agreement should cover eight terms: the fee and scope of services, the minimum commitment, the notice period, how requests are made and prioritized, response times, unused capacity, ownership, and exit and handover. Together they define what you get each month and how easily you can stop.
A retainer contract for design is different from a project contract. There's no fixed list of deliverables, because the work changes month to month. That makes the agreement's structure more important, not less: it has to describe a working relationship rather than an output. For the project-contract clauses, see our web design contract checklist.
Retainers typically run about $2k to $12k a month in the ranges we see quoted, and they vary widely with team size and whether development is included. The price matters, but the terms decide whether that money is well spent. Use the checklist below before you sign.
What is the design retainer agreement checklist?
The checklist below covers every term to read before signing a design retainer agreement, in the order we'd check them. Work through it with the agency's draft open beside you.
- Fee and services. The monthly price, and which services it covers: design only, or design, copy and development.
- Minimum commitment. How many months you're committed to before you can end it.
- Notice period. How much notice either side must give to stop, and whether it can start mid-month.
- Capacity. What a typical month can include, described as team time, active requests or example outputs.
- Requests and priorities. How you submit work, who sets priorities and how often you review them.
- Response and turnaround. When you can expect replies and first drafts, in working days.
- Unused capacity. Whether quiet months roll over, and what a pause looks like.
- Ownership. That each month's paid work belongs to you, with files and code in your accounts.
- Exit and handover. What you receive when the retainer ends, and how open work is wrapped up.
Is a 12-month retainer minimum commitment reasonable?
A 12-month retainer minimum commitment is reasonable only if you're certain you'll need the same level of work all year and the price reflects the commitment. For most startups, whose priorities change every quarter, a long minimum is a risk you don't need to take.
Agencies ask for long minimums because steady revenue lets them staff a team and plan. That's a fair interest. The problem is the mismatch with how startups work: funding changes, products pivot, and an in-house hire may take over part of the work. Twelve months of fixed fees then become a cost you can't adjust. Some established agencies publish retainers that require exactly this kind of 12-month commitment.
If an agency insists on a minimum, negotiate the shape of it. A shorter initial term, a mid-term review with an exit option, or a step-down to a smaller plan all reduce the risk. A month-to-month retainer puts pressure on the agency to earn the renewal, which is usually the healthier incentive for you.
What should a month-to-month retainer look like?
A good month-to-month retainer bills in advance for each month, can be ended with a short written notice, describes a typical month's capacity, and hands over all work and access cleanly when it ends. Flexibility only works if the rest of the terms are clear.
Term | Long lock-in retainer | Month-to-month retainer |
|---|---|---|
Commitment | Fixed minimum, often months | One month at a time |
Ending it | Paid out or negotiated | Written notice, short period |
Price | Sometimes discounted for commitment | Standard monthly fee |
Agency incentive | Keep you inside the term | Earn the next month |
Best for | Stable, predictable workloads | Startups with shifting priorities |
Month-to-month doesn't mean casual. A good one still has a weekly or fortnightly priorities review, agreed turnaround expectations and a monthly summary of what shipped. If you're comparing how retainers are priced in the first place, our guide to design retainer pricing breaks down the common models.
How should retainer requests and priorities be managed?
Retainer requests should go through one shared channel, with one person on your side setting priorities and a regular review where both teams agree what's next. Without that, a retainer turns into a busy inbox where the urgent pushes out the important.
The agreement should say how this works, at least in outline. Where requests live, for example a shared board. Who can submit them and who decides priority. How often you review the list together. Whether the team joins your own meetings and customer calls, which is where much of the useful context comes from. And how bigger initiatives, like a new section of the site, are scoped inside the monthly capacity.
Clear priorities are also your best defense against retainer drift, where small requests absorb the month and the important project never starts. The same discipline as on a project applies; our guide to preventing scope creep in web design covers it.
What happens to ownership and files when a retainer ends?
When a retainer ends, you should already own everything produced and paid for, with files, code and accounts in your company's name. Ownership should transfer month by month as each invoice is paid, not wait for a final handover that depends on the relationship ending well.
This matters more for retainers than for projects, because retainers often end with work in progress. The agreement should say what happens to it: finished and delivered in the final month, handed over as-is, or billed separately. It should also say how long the agency keeps access after the end, and that access is removed on request.
Our guide to who owns the website design and code covers the transfer language. Ask for the same wording in a retainer, applied to each month's deliverables.
Hypothetical example: a clean retainer exit
Hypothetical example: a startup ends a retainer after eight months because it has hired an in-house designer. The agreement has a short notice period, so the final month is used to finish open work and document the design system. All Figma files and the code repository already live in the startup's own accounts, so the handover is a call and a document rather than a transfer.
The new designer starts with the full history of the work. Nothing is held back, and no one has to chase files. That's what a fair exit clause is designed to produce.
Should you choose a retainer or a care plan?
Choose a retainer when you need ongoing design and development output, such as new pages, product screens and experiments. Choose a care plan when you mainly need maintenance: updates, small fixes and monitoring on a site that's otherwise stable.
The two are often confused because both are monthly. A care plan is about keeping things working; a retainer is about making new things. Paying for a retainer when you only need maintenance wastes money, and running growth work through a care plan stalls it. Our comparison of a website care plan vs a retainer goes through the differences, and if your monthly work is mostly conversion testing, CRO agency pricing explains how that's usually priced.
If you're not sure which you need, a short paid trial on real work is the fastest way to find out. It shows how the team handles your priorities before any monthly commitment.
