Retainer structures for ongoing design work generally fall into a handful of recognisable formats, each suited to different project rhythms and team setups. A fixed hour arrangement allocates a set number of working hours per month, regardless of how those hours get distributed across tasks. Firms listed across any UX Agency Directory some variation of this model, since it gives both sides a predictable baseline to plan around from the outset.
This structure works well when the workload stays fairly consistent month to month, since unused hours often don’t roll over, and heavier months can push a team past the allocated cap without warning.
A few characteristics define this model:
- A fixed monthly hour block agreed upon in advance.
- Rate consistency regardless of task complexity within that block.
- Limited flexibility when demand spikes unexpectedly.
- Clear tracking through timesheets or project management tools.
Teams choosing this format usually value predictability over flexibility, accepting the tradeoff that comes with a rigid hour ceiling. Billing cycles align neatly with calendar months, which simplifies internal budgeting on the client side even when actual design output varies week to week.
Scope-based retainers
Scope-based retainers shift the focus away from hours and toward a defined set of deliverables completed within a recurring period. Rather than tracking time spent, this model outlines specific outputs, wireframe sets, prototype rounds, or usability test cycles that must be delivered each cycle, regardless of how long they take to produce.
This structure suits teams with clearly defined recurring needs, such as monthly design system updates or scheduled feature audits. It removes the pressure of hour tracking but requires precise scope definition upfront, since ambiguity here tends to create disputes about what counts as included work versus a separate request.
Agencies favouring this model often build in buffer capacity for minor revisions, keeping the core deliverable list stable while allowing some flexibility around smaller adjustments. Disagreements under this model usually trace back to scope creep rather than time overruns, which makes upfront documentation particularly important.
Hybrid capacity models
Hybrid arrangements blend elements of both fixed hours and scope-based structures, typically anchoring a baseline of guaranteed deliverables while allowing additional hours to flex based on need. This format suits teams whose workload fluctuates significantly across a product cycle, moving between quiet maintenance stretches and intense release periods.
A baseline retainer might cover core maintenance and incremental updates, with capacity for larger initiatives, a full redesign sprint or major research push, negotiated separately as they arise. This keeps the ongoing relationship stable without locking either party into rigid boundaries during quieter or busier periods.
Some teams pair this model with quarterly reviews, adjusting baseline capacity as product needs shift over longer timeframes rather than renegotiating every month. This review rhythm tends to catch mismatches between allocated capacity and actual demand before they become a recurring point of friction.
Each structure trades certainty for flexibility in different proportions, and the right fit generally depends on whether the workload stays steady, follows a defined cycle, or shifts unpredictably across a longer engagement.