Design Retainer
An ongoing agreement that reserves a fixed amount of design capacity each month instead of scoping and pricing each project separately.
Business & EngagementA retainer buys availability. The company gets a predictable amount of senior design time and the agency gets predictable revenue, so neither side spends the first week of every piece of work negotiating scope. It suits products that ship continuously — where the next month's priorities genuinely are not known yet — better than one-off builds with a fixed deliverable.
The failure mode is a retainer used as a discount on an unbounded backlog. Without a written definition of what the capacity covers, who prioritises it and what happens to unused hours, it turns into either an on-call arrangement or an invoice nobody can justify. The alternative model, an embedded design team, trades flexibility for deeper product context.
In practice
A Web3 product cycled through four freelancers in a year, re-explaining its token mechanics each time. Before: each engagement spent its first two weeks on context. After moving to a monthly retainer with the same two designers, new features started shipping in week one. The catch — the retainer had to specify a notice period, or capacity planning broke on both sides.
Learn more
You may ask
Frequently Asked Questions
Is a retainer cheaper than project work?
Per hour, usually slightly. The larger saving is in ramp-up: a team that already knows your product, users and codebase does not rebuild that context every engagement, which is often several weeks of billable time per project.
What happens to unused hours?
That has to be written down before signing. Common answers are roll over for one month, expire monthly, or convert to a defined backlog. Any of them works; leaving it unstated is what causes the argument.
Related terms
All terms- Embedded Design TeamAn external design team that works inside a client's rituals and tools — standups, sprints, backlog — rather than delivering from the outside.
- Product-Market FitThe point at which a product satisfies a real market demand strongly enough that usage and revenue grow without being pushed.
- Design SprintA time-boxed process, classically five days, that takes a team from a hard product question to a tested prototype without building anything.
- Product DesignThe end-to-end design of a digital product — deciding what to build, how it should work, and how it should look, against business constraints.
Let's talk about your product.
Happy to look at what you're building and say where design would move the needle.
Contact Us