By Mehdi HassanGrowing SaaS teams reach the same fork sooner or later: keep commissioning design projects one at a time, or pay a team every month to handle whatever comes next. Both models work. They fail in predictable ways when used at the wrong stage. This comparison sets out what each covers, where each breaks and which to choose for your stage. It's part of our guide to SaaS product design.
What is a product design retainer?
A product design retainer is a monthly agreement where a designer or studio works on your product continuously, handling a rolling queue of features, fixes and experiments, for a fixed monthly fee. You're buying capacity and accumulated context rather than a single defined deliverable.
Retainers differ in what they include. Some cap the number of requests or active tasks. Some bill against a bank of hours. Some include front-end development, others are design only. Ours is $6,000 a month for design and development together: the team joins customer calls when useful, and we don't track hours. For how other studios structure fees, see our breakdown of design retainer pricing.
What is a fixed design project?
A fixed design project is an engagement with an agreed scope, deliverables and price, such as designing an MVP, redesigning onboarding or creating a new billing flow. It ends when the deliverables are handed over.
Projects are easy to approve because the cost is known up front, and they force a clear definition of done. The weakness is everything outside the scope. New ideas mid-project become change requests, and when the project ends, the context leaves with the team. If the next project starts months later with someone else, they relearn your product from zero.
How does a design retainer compare with a project?
A design retainer and a project differ mainly in what you're paying for: a project pays for a defined result, a retainer pays for a team's ongoing attention. That one difference changes cost predictability, speed, flexibility and how much your product benefits from accumulated knowledge.
Factor | Fixed project | Monthly retainer |
|---|---|---|
You pay for | A defined deliverable | Ongoing capacity and context |
Best for | New product, redesign, one big feature | Weekly shipping, a steady roadmap |
Cost predictability | Known total up front | Known monthly cost, open-ended total |
Flexibility mid-stream | Low: changes become change requests | High: reprioritise the queue anytime |
Context over time | Resets with each project | Builds month on month |
Speed to start new work | Slow: scope, quote, sign | Fast: add it to the queue |
Risk if poorly used | Scope creep, or a gap after handoff | Paying for idle weeks |
Neither model is cheaper in the abstract. A retainer looks expensive per month and cheap per shipped feature when the queue is full. A project looks cheap per engagement and expensive once you add the scoping, onboarding and handoff time repeated across many small projects.
When is a fixed project the right choice?
A fixed project is the right choice when the work has a clear start and end and you don't yet have a steady stream of design work behind it. That's usually before launch or at a moment of major change.
- Designing an MVP from a clear brief, as in our step-by-step guide on how to design a SaaS app.
- A redesign of a product or a single area, such as onboarding or settings.
- A brand and product exploration before raising or relaunching.
- A defined feature your in-house team will build and maintain.
Our version of this is the $3,000 brand and design sprint: a brand refresh or redesign plus 10 website or product explorations, delivered as Figma files. It's design only and fixed in scope, which makes it a good first step before deciding whether you need more.
When is a monthly product design retainer better?
A monthly product design retainer is better once you have users, a roadmap that keeps moving and features shipping every week or two. At that point, the cost of re-scoping each piece of work, and of losing context between projects, outweighs the predictability of fixed quotes.
Pros
- The team knows your product, users and components, so each feature starts faster
- You can reprioritise weekly as customer feedback comes in
- Design and build stay consistent because the same people own both
- No change requests for small additions
Cons
- You pay every month, including slow months
- Needs someone on your side to set priorities
- Less useful without a roadmap of real product work
- Easy to drift into low-value tasks if nobody reviews the queue
Retainers that include development are the stronger choice for teams without a full front-end team, because the people who design a feature also ship it. A design-only retainer still leaves the translation to your engineers. Our guide on web app UI design explains why that translation is where quality usually leaks.
For example, suppose a seed-stage SaaS is choosing between models
For example, suppose a seed-stage SaaS has just launched and has a roadmap for the next quarter: team invites, a billing upgrade flow, an integrations page and a steady stream of fixes from early customers. Commissioning each as a project means four scopes, four quotes and four handoffs, with fixes falling between them. A retainer handles all of it as one queue, with the same team that knows how invites affect billing. The same company a year earlier, with only an idea and a deck, would have been better off with one fixed sprint.
This is a hypothetical example to illustrate the trade-off, not a real client.
Which design model fits your SaaS stage?
The design model that fits your SaaS stage depends mainly on how steady your product work is. Use a project when the work is a defined block, a retainer when it's a continuous flow, and in-house hiring once that flow is large and stable enough to justify full-time roles.
Stage | Typical work | Best model |
|---|---|---|
Idea or pre-seed | Concept, brand, first flows | Fixed sprint |
Building the MVP | Core flows, UI, specs | Fixed project |
Just launched | Fixes, onboarding, early features | Retainer, or trial week first |
Growing, shipping weekly | Features, experiments, billing, teams | Retainer |
Scaling, multiple squads | Parallel workstreams, a design system | In-house team, with outside help for peaks |
If you're comparing outside partners at this point, our guides to what a SaaS product design agency costs and Eleken alternatives set out the options, and app design cost covers project budgets in more detail.
