Why projects fall short for products
Products are never finished. New features, changing users, and growing complexity create design work every week. A project engagement ends and the knowledge leaves with it. Teams then spend time re-explaining the product to the next provider.
What ongoing support covers
- Designing new features and improving existing flows.
- Research and testing to guide decisions.
- Maintaining and extending the design system.
- Supporting engineers during build and QA.
- Reviewing work from other teams for consistency.
How a healthy retainer runs
Agree priorities
A shared list of the most important design work, reviewed regularly.
Work in cycles
Weekly or two-weekly cycles with clear outputs.
Review together
A short review where decisions are made and feedback is given.
Report outcomes
What shipped, what was learned, and what is next.
Signs it is working
| Sign | What it shows |
|---|---|
| Faster turnaround on requests | Context is building |
| Fewer surprises at handoff | Design and engineering are aligned |
| Consistent UI across releases | A system is being used |
| Proactive suggestions | The partner understands the product |
Choose well
Ask how work is prioritized, who you work with, how quickly you can scale capacity up or down, and what happens to your files and knowledge if you leave. The best arrangements are flexible and transparent.



