Skip to content
Blog

In-house designer, agency or embedded design partner: which should you choose?

Hire in-house when design is a permanent, full-time need and you can give a designer the support to do it well. Choose a defined project when the work has a clear outcome and end. Choose an embedded partner when you need senior design continuously, but not necessarily as a full-time hire, or not yet.

Author
Luke Dalton
Topic
Design resourcing
Published
Length
6 min read

In practice these options overlap, and the right one can change as the company grows.

What the terms actually mean

In-house means employing a designer as part of your team, managed by you.

Agency describes a company that provides design as a service. Agencies work in different ways: some take on defined projects with a fixed scope, some provide ongoing support, and many do both.

Embedded describes a way of working, not a type of provider. An embedded designer works inside your team’s rhythm: joining planning, using your tools and channels, and designing features as the roadmap moves. That can be delivered by an agency, a studio or an independent designer.

So the decision is less “agency or embedded” than two separate questions. Do you want to employ the designer? And do you need a defined project, or continuing involvement?

How the options compare

In-house, project-based and embedded product design compared
In-house hireDefined projectEmbedded partner
ContinuityHigh, for as long as the person stays.Ends with the project. Context has to be handed over.Continues for as long as the engagement runs.
Scope flexibilityWorks on whatever the business prioritises.Agreed in advance. Changes are renegotiated.Priorities agreed regularly, within the agreed level of support.
Internal managementYou recruit, manage, review and develop the designer.You own the brief and approvals. The provider manages the work.You set priorities. The partner manages how the work gets done.
Product contextBuilds deep context over time.Builds context for the scope at hand.Builds context over time, alongside your team.
CapacityOne person’s working time, minus everything else they are asked to do.Planned around the project.As agreed in the engagement. Not necessarily full-time or dedicated.
Cost structureSalary, employment costs, recruitment, equipment and management time.A fee for the agreed scope.A recurring fee, usually monthly.

An ongoing partner is not a full-time employee

Some providers offer a dedicated designer who works only on your product for a full working week. Others work on your product as an agreed priority alongside other clients. Both can work well. They are different arrangements.

Before signing, find out which one you are getting: how much time is committed, how quickly requests are picked up, and what happens when you have more work than the engagement covers. A monthly fee does not mean you are buying a full-time person, and comparing it directly with a salary can mislead in either direction.

Four common situations

These scenarios are illustrative. They describe typical situations rather than specific companies.

You have a defined redesign

You know which part of the product needs to change, such as onboarding or a reporting area, and you want it designed and handed over within a known timeframe. A defined project usually fits. You get a clear deliverable and cost without creating a permanent role you may not need afterwards. How to scope a SaaS redesign without rebuilding everything explains how to define the work.

You have a continuing roadmap

You ship new features regularly and need design throughout: shaping requirements, designing flows and reviewing what gets built. An embedded arrangement fits better than a series of separate projects, because the designer keeps context from one feature to the next. Exalt’s work with Scout is one example: more than two years embedded alongside Scout’s lead designer as the product developed. The two models also combine. Openlane began with a full UI refactor and continued as an ongoing partnership.

Your design team needs support

You already have designers, but the signs of strain are visible: features reach engineering before design has looked at them, the design system stalls behind feature work, or a complex workflow needs more focused time than anyone can give it. An external partner can add capacity or specific experience. This works best when the partner adopts your team’s conventions and your designers keep ownership of design decisions.

You are ready for a first permanent designer

Design work is constant, the product direction is stable enough to plan around, and someone in the business can support a designer’s work and growth. This is often the point to hire. An external partner can still help before the hire starts, for example by establishing a component library the new designer will inherit.

When an in-house hire is the strongest choice

  • Design is needed full-time for the foreseeable future, not in bursts.
  • The product is central to the business and you want design knowledge to stay inside the company.
  • Good design decisions depend on daily contact with customers, sales and support.
  • You can give the role a clear remit, the right tools and a manager who understands design.
  • You can wait for a hiring process, and for the new person to learn the product.

The last two points are easy to underestimate. A first designer hired without a clear remit or support can end up producing screens to order without the authority to shape the product. If you hire, give the role access to customers and a real say in product decisions.

Comparing total cost

A salary and a monthly fee are rarely like for like, so avoid converting one into the other. Instead, list what each option involves over the period you actually need design support:

  • A hire: salary and benefits, employer taxes and contributions where you operate, recruitment fees or time, software and equipment, management time, and the months before the person is fully effective. Add the cost of the role sitting empty if they leave.
  • A defined project: the fee, your team’s time for briefing and reviews, and anything excluded from scope, such as implementation.
  • An ongoing engagement: the monthly fee, any minimum term or notice period, the internal time spent setting priorities, and what happens to work beyond the agreed level.

Then compare like periods. A permanent hire makes more sense the longer and steadier the need. For a redesign expected to take a few months, the relevant comparison is a few months of each option, not a year of salary against a year of fees.

Questions to ask any provider

  1. Who will do the work day to day, and how experienced are they?
  2. How much of their time is committed to us each week or month?
  3. How many other clients or projects will they be working on at the same time?
  4. How do we request work, and how quickly is it usually picked up?
  5. What happens when we have more work than the engagement covers?
  6. How do you hand work to our engineers, and will you review what gets built?
  7. Who owns the design files, components and any code produced?
  8. How do we pause or end the engagement, and how much notice is needed?
  9. What will you leave behind so our team, or a future hire, can carry on?

Clear answers to these questions tell you more than the label a provider uses for itself.

How Exalt works

Exalt offers both a defined project and an ongoing partnership. In both, you work directly with Luke Dalton, Exalt’s founder, supported by a senior product designer.

  • Fixed-Price Project, from $6,000 per project. For defined work, from new features to full product redesigns, with the scope, timeline and fee agreed before kickoff.
  • Embedded Design Partner, from $7,000 per month. Ongoing product strategy, UX and UI against agreed priorities, with weekly planning and Slack collaboration, on a flexible monthly renewal.

Both are starting prices, not quotes. In an ongoing engagement, how much gets done in a month depends on the size of each request: we estimate requests before starting them and flag early if priorities need to shift. Scope, availability and terms are confirmed before work begins, and larger front-end builds are quoted separately. The details are in the pricing section of our site.