--- title: "Outsource UX Design to a Dedicated Team | Azendo" description: "Outsource UX design to a product designer assigned to your roadmap. Ongoing design capacity in your sprint rhythm, on one monthly agreement." url: "https://azendo.co/services/ux-ui-design/" --- [← All services](https://azendo.co/services/) # Outsource UX design without losing the designer next quarter. Most teams outsource UX design to a freelancer on a retainer. It works until they take a holiday, win a bigger client, or stop replying. An assigned designer at Azendo comes with a service delivery manager, a design system that outlives any one person, and a fee that does not move month to month. [Contact us](https://azendo.co/services/ux-ui-design/#team-builder) [Talk to a service delivery manager](https://azendo.co/get-in-touch/) How the role joins your team Added to delivery \+ capacity Product Designer Assigned capacity * [Figma](https://azendo.co/skills/figma/) * [User research](https://azendo.co/skills/user-research/) * [Design systems](https://azendo.co/skills/design-systems/) Capacity 160 h committed monthly ## What does it mean to outsource UX design? Outsourcing UX design means contracting product design capacity externally: research, interaction design, interface design and design system ownership. It differs from commissioning an agency project in that a design system needs continuous ownership. A brand refresh finishes; the decisions about how the next feature should behave do not. ## What an outsourced design team covers. Skills and scope are agreed before delivery starts, so the first sprint is productive rather than a ramp-up month. The work runs to the same backlog, the same design files and the same definition of done as your own team’s. Design capacity behaves differently from engineering capacity. It runs a sprint ahead, so developers are never waiting on a screen, and it produces artefacts your team keeps using long after a particular feature ships. The design system is the clearest example. It is the part of this list that compounds, because the fiftieth screen costs a fraction of the fifth once the components and tokens exist and someone is maintaining them. * Product design Flows, wireframes and interface design against your roadmap. * Design systems Components and tokens built once, maintained as the product grows. * Research and testing Usability sessions and interviews where the answer is not obvious. * Developer handover Specs and assets your engineers can build from without a meeting. * Sprint participation In your rhythm, your tools, alongside product and engineering. ## Assigned to fit the stack you already run. Figma for design and handover, FigJam and Miro for workshops, Maze and Hotjar for testing, Storybook where the design system meets the codebase. Files stay in your workspace throughout. That matters more than it sounds when an engagement ends or a designer changes, because design work that lives in a vendor's account is design work you do not fully own. Where a design system already exists, even an implicit one, we audit before proposing anything. Most products have more consistency than their team believes and need curation rather than a rebuild. Design * [Figma](https://azendo.co/skills/figma/) * [Sketch](https://azendo.co/skills/sketch/) * [Adobe XD](https://azendo.co/skills/adobe-xd/) * [Framer](https://azendo.co/skills/framer/) * [InVision](https://azendo.co/skills/invision/) * \+ more on request Research * [Maze](https://azendo.co/skills/maze/) * [UserTesting](https://azendo.co/skills/usertesting/) * [Dovetail](https://azendo.co/skills/dovetail/) * [Hotjar](https://azendo.co/skills/hotjar/) * [Optimal Workshop](https://azendo.co/skills/optimal-workshop/) * \+ more on request Handover * [Zeplin](https://azendo.co/skills/zeplin/) * [Storybook](https://azendo.co/skills/storybook/) * [Design tokens](https://azendo.co/skills/design-tokens/) * [Figma Dev Mode](https://azendo.co/skills/figma-dev-mode/) * [Notion](https://azendo.co/skills/notion/) * \+ more on request ## A retainer with a company behind it. Priced as committed monthly capacity, the same as every other discipline. The difference from a freelance retainer is that the design system has an owner who is still there next year. The fee does not move month to month either. 160 h Typical monthly capacity for one product designer Fixed Monthly price, unaffected by leave or holidays 4–6 weeks From signed scope to delivery starting Monthly Cycle to raise or lower committed hours Design work happens next to the engineers who build it, not in a separate agency. Bangkok, Thailand — five hours ahead of Northern Europe ## The UX/UI design roles we assign. Take one role, or several as one delivery team. Each role below has its own page describing what it delivers under a service agreement. [UX Designer Flows, structure and usability Read about the role →](https://azendo.co/services/ux-ui-design/ux-designer/)[UI Designer Interface craft and visual systems Read about the role →](https://azendo.co/services/ux-ui-design/ui-designer/)[Product Designer Research through to interface Read about the role →](https://azendo.co/services/ux-ui-design/product-designer/)[UX Researcher Interviews, testing and analysis Read about the role →](https://azendo.co/services/ux-ui-design/ux-researcher/) ## Building in-house, a local agency, or Azendo. Each fits a different situation. An in-house role makes sense when the work is permanent and local; a local agency suits a one-off project with a clear end date. Azendo sits between the two — ongoing capacity for work that keeps coming, with the team, the workplace and the administration behind it handled on our side. | Comparison | Building it in-house | Local agency | Azendo | | ------------------------------- | ---------------------------------- | ----------------------------------------- | ----------------------------------------- | | Time to productive output | Months — recruit, onboard, ramp up | Fast to start, slow to learn your product | 4–6 weeks | | Continuity of context | Resets when someone leaves | Rebuilt with each new project | Held by the same delivery team, for years | | Continuity of product knowledge | Lost when the hire leaves | Ends with the project | Held by the assigned team | | Who answers for delivery | You do | Account manager, between projects | A service delivery manager, continuously | | Cost profile | Fixed, whatever the workload | Priced per project | One monthly fee, adjustable each cycle | | Scaling a discipline | A new hire each time | Re-scoped each engagement | Capacity up or down at the monthly cycle | ## Common questions before you outsource UX design. Why outsource UX design rather than hire a freelancer? For a short piece of work, a freelancer is often the right call and cheaper. The trade comes when design becomes continuous, because a freelance retainer has no second opinion and no continuity if that person moves on. Can a designer work with our existing product team? That is the usual arrangement. The assigned designer joins your sprint rhythm and works alongside your product owner and engineers. Do you work in our Figma or your own? Yours. Files, components and history stay in your workspace. Can a dedicated design team cover more than one product? Yes, though we will usually suggest one designer per product where roadmaps are active, because context switching costs more than it saves. ## Often assigned alongside a product designer. A specialist rarely works alone on a roadmap. These disciplines cover the ground around the role and can be added to the same service agreement. [Software development Web platforms, APIs and integrations](https://azendo.co/services/software-development/)[Mobile development Native and cross-platform apps](https://azendo.co/services/mobile-development/)[QA and test automation Test strategy and automated coverage](https://azendo.co/services/qa-engineering-and-test-automation/)[AI engineering LLM features, retrieval and evaluation](https://azendo.co/services/ai-engineering/) ## Outsourced design capacity across a roadmap rather than a project Design is the discipline most often bought as a project and most damaged by it. A brand refresh finishes, the designer leaves, and eighteen months later the product is a patchwork of decisions nobody can explain. Continuous assignment exists to prevent exactly that: the same designer owns the system, so the system stays coherent. Where the open question is what to build rather than how it should look, a [UX researcher](https://azendo.co/services/ux-ui-design/ux-researcher/) answers it more cheaply than a build does. Where design and delivery need one person holding both, a [product designer](https://azendo.co/services/ux-ui-design/product-designer/) is the usual assignment. Work happens in your Figma workspace, not ours. Files, components and version history stay with you, which matters more than it sounds when the engagement eventually changes shape. Design capacity is most useful when it sits next to the team building the thing, so it is commonly assigned alongside [outsource software development services](https://azendo.co/services/software-development/) on one agreement and one [committed monthly capacity](https://azendo.co/pricing/). ## Tell us what ux/ui design capacity your roadmap needs. Tell us about your project and the capacity you have in mind. A service delivery manager will get back to you.