In-house vs agency for a design system: when each wins
A dedicated in-house design system hire runs $145k to $185k a year loaded; an agency retainer $5k to $15k a month. Here is when each one wins.
The choice between an in-house team and an agency for your design system is a decision about who owns the system after launch, not just who builds it. A design system is the shared library of tokens, components, and rules that keeps a product consistent as it grows. Building the first version is a project. Keeping it alive is a job. The right model depends on which of the two you are actually staffing for.
Here is the short version. Go in-house when the system feeds several products, changes weekly, and needs an owner who sits in your standups. Hire an agency when you need it built once, built well, and handed over, or when your design load is too lumpy to justify a salary yet. Most teams that get this right land on a hybrid: an agency builds the foundation, one internal owner keeps it from rotting.
What the two models actually cost
Cost is where this decision usually starts, so start there honestly.
An in-house design system needs at least one dedicated person, and usually more. Nielsen Norman Group's research found most design-system teams run 2 to 5 people, climbing to 9 to 11 in large organizations and rarely past 25 (NN/g, lean design-system teams). A single mid-to-senior product designer in the US costs roughly $145,000 to $185,000 a year once you load salary with benefits, payroll tax, tooling, and recruiting. Add an engineer to maintain the coded components and you pass $300,000 in fully loaded annual cost before the system ships a single button.
An agency or studio bills differently. Mid-market design retainers in 2026 sit around $5,000 to $15,000 a month, and a fixed-scope build of a system foundation typically runs $15,000 to $80,000 depending on component count and platform coverage. You pay for output, not for a chair. When the build is done, the meter stops.
Stretch that over three years and the shape flips. A designer plus a maintenance engineer at a blended $320,000 a year is close to $1 million across three years. An agency that builds the foundation for $50,000 and then holds a $6,000-a-month maintenance retainer lands near $270,000 over the same window. The in-house model only wins the three-year math when the internal team is also shipping product design, not just tending the system. That is the real question hiding under the cost debate: are you buying a design system, or a design function that happens to own one.
In-house vs agency across the axes that matter
Six dimensions decide this more than price does.
- Ownership. In-house keeps the roadmap inside the building. An agency owns the system during the engagement, then hands it over. If nobody internal is ready to catch it, the handover is where systems die.
- Speed to first version. An agency ships faster. It has done this before and does not wait on a hiring cycle. Approving headcount and onboarding a lead often takes longer than the entire agency build.
- Cost shape. In-house is a fixed annual cost whether the workload is heavy or idle. An agency is variable: you pay when there is work to do.
- Product context. An in-house owner sits in standups and absorbs edge cases an external team never sees. Depth of context is the in-house model's real edge.
- Breadth. An agency brings patterns from dozens of systems: accessibility, theming, and token architecture decisions a first-time internal hire would learn on your budget.
- Continuity. One internal person is a single point of failure; if they leave, the system stalls. An agency carries redundancy, but can also walk away at contract end.
Where an in-house team wins
Go in-house when the design system is load-bearing infrastructure, not a one-time asset.
Several products consume it. A system feeding three or more apps generates a constant stream of new components, deprecations, and version bumps. That is a full-time job. NN/g's data shows even lean teams need a dedicated owner once support and maintenance pass half of someone's week.
It changes weekly. Fast-moving products break their own systems constantly. An external team on a monthly cadence cannot keep pace with daily drift. Component drift is how systems decay when nobody owns them day to day.
Adoption is the hard part. The failure mode of most systems is not the build, it is adoption. One 2026 analysis of adoption metrics found installation dashboards showing 92% adoption while developer sentiment slid from 67% to 23% positive over six months (DNSK, adoption metrics). Closing that gap needs someone in the room doing outreach, not a vendor on a statement of work.
The horizon is long. Past product-market fit, with the system running for years, the salary amortizes. Development teams save 31% to 47% of build time once a system is established (Sparkbox, Carbon study). Capturing that compounding return needs a permanent owner.
Where an agency wins
Bring in an agency when you need the system built right once, or when your load will not fill a salary.
You are starting from zero. A studio has built token architectures and component libraries before. Figma's internal experiment found designers on a mature system worked 34% faster than those starting from scratch (Figr, design system ROI). You buy that head start instead of funding a first-timer's learning curve on your product.
Your load is lumpy. A launch here, a rebrand there. Paying $170,000 a year for work that arrives in bursts is worse economics than a retainer you scale up and down.
Speed matters now. If the system blocks a launch this quarter, an agency ships before a job posting closes.
You want a clean handover. A good engagement ends with a system your team can run: documented tokens, governance rules, a contribution model. The pricing model you choose (project, retainer, or shared ownership) decides how much of that handover you actually get.
The hybrid most teams land on
The strongest setups are rarely pure. An agency builds the foundation in weeks, sets the token architecture and the first component set, and writes the governance rules. Then one internal owner, usually a senior designer or a design engineer, takes the handover and keeps the system honest: reviews contributions, kills duplicates, runs adoption. The agency stays on a light retainer for audits and heavy lifts. You get the agency's breadth up front and the in-house context over time, without paying for two full teams. The pattern is consistent across the systems we build and hand over: the ones that survive have a named owner from day one, not month six.
A 20-minute test to decide
Answer four questions honestly.
- How many products consume the system? One product on a slow roadmap points to an agency. Three or more active products point in-house.
- How often does it change? Weekly change needs a daily owner. Quarterly change does not.
- Do you have an internal owner ready? If nobody can catch a handover, an agency build with no in-house owner rots inside a year. Settle the owner question first.
- Is the workload steady or lumpy? Steady, year-round load justifies a salary. Bursty load favors a retainer.
Two or more answers pointing the same way is your model. When they split, default to the hybrid: buy the build, hire the owner.
Sources
Frequently asked questions
Is it cheaper to build a design system in-house or with an agency?
It depends on the time horizon and how steady the work is. In year one an agency is almost always cheaper: a fixed-scope foundation runs $15,000 to $80,000, versus $145,000 to $185,000 for a single loaded in-house hire who also has to learn the domain. Past year two, if the workload is steady and feeds several products, an in-house owner amortizes and pulls ahead. Lumpy or one-time work keeps the agency cheaper indefinitely.
How many people do you need to maintain a design system?
One dedicated owner is the floor. Nielsen Norman Group's research puts most design-system teams at 2 to 5 people, rising to 9 to 11 in large organizations. The trigger to add headcount is workload, not company size: when support and maintenance consume more than half of the current owner's week, or the component backlog stretches past six months, you are understaffed. Below that, one senior designer or design engineer can hold a system for two or three consuming products.
What happens to a design system after an agency hands it over?
Without an internal owner, it decays. Tokens drift, components get duplicated, and accessibility rules fall behind, often unnoticed until the system slows the very teams it was meant to speed up. A clean handover reduces the risk but does not remove it: the system still needs someone inside the company to review contributions and enforce governance. This is why we recommend naming that owner before the build starts, not after the invoice.
Can a freelancer build a design system instead of an agency or an in-house team?
Yes, for a narrow scope. A skilled freelancer can build a solid foundation or a focused component set, often at a lower rate than an agency. The risk is continuity and breadth: one contractor is a single point of failure, rarely covers both design and coded components, and disappears when the contract ends. For a one-product system with a clear brief, a freelancer works. For a system several teams will depend on for years, the redundancy of an agency or an in-house owner is worth the premium.
Related articles
Studio
Start a project.
One partner for the whole build. Faster delivery, a modern stack, lower cost.