Working With a Design Agency After You Hire a Designer

When you hire your first in-house designer and keep an agency, split the work by time horizon rather than by page. Your designer owns everything that changes weekly and needs product context: the product itself, the design system, and the decisions that only make sense if you sit in the standups. The agency owns the work that arrives in bursts and needs more hands than you have: launches, campaign pages, a redesign, a second product. Divide it any other way, by page or by section, and the two will collide inside a month.

This is a real problem and almost nobody writes about it. Plenty has been written about whether to hire a designer or use a design partner. Far less about what happens the week after you have both, when your new designer opens a file the agency is already working in.

The first month is where this goes wrong

The usual failure is quiet. Your designer starts, and nobody tells the agency what changed. The agency keeps working the way it did when it was the only design resource, which means it keeps making decisions that are now your designer's to make. Your designer, three weeks in and still learning the product, does not want to start a fight, so they work around the agency instead of with it.

Two months later you have two versions of the button styles, two ideas about what the homepage is for, and a designer who is quietly updating their CV. The agency did nothing wrong. Nobody redrew the line.

Redraw it on day one, in writing, and tell both sides at the same time.

Split the work by time horizon

The cleanest rule we have seen hold up is this. If the work changes every week and depends on knowing the product, it belongs in house. If it arrives as a project with a start and an end, it belongs to the agency.

In house by that rule: the product interface, the design system, anything that needs a conversation with an engineer, and any decision where the right answer depends on what a customer said in a call last Tuesday. Your designer is the only one who hears that.

Agency by that rule: a launch site, a pricing page rebuild, a campaign microsite, a second product's marketing pages, a redesign your designer cannot absorb on top of their day job. These need three or four people for four weeks and then nobody for two months. That shape is bad for a salary and good for a project.

The rule is useful because it is easy to apply under pressure. When something new lands, ask one question: does this repeat every week? That is usually enough.

Who owns the design system

Your designer owns it. Not jointly, not by committee. One owner.

The reason is maintenance. A design system is not a file, it is a set of promises about spacing, type, and components that somebody has to keep true as the product changes. An agency that finishes a project in four weeks is not around in week nine when an engineer needs a new component and takes the nearest thing that looks close. Your designer is.

That does not mean the agency cannot touch it. It means the agency proposes and your designer approves. If the agency needs a new component for a campaign page, they build it, show the reasoning, and your designer decides whether it enters the system or stays local to that page. Most should stay local. A system that absorbs every one-off stops being a system.

Write down who approves. It is the single most common thing teams leave implicit and the one that causes the most damage.

What the agency should stop doing

Three things, and it is your job to say so rather than wait for them to notice.

Stop setting direction on the product. Before the hire, the agency probably had opinions about onboarding and the dashboard, and you probably wanted them. Now those opinions go to your designer, not to you, and not into a deck.

Stop being the default answer to every design question. If your team still messages the agency for a quick favour, your designer is not actually the design lead, whatever the title says. Route design questions to your designer for a month even when the agency would be faster. Speed is worth less than a clear owner.

Stop reporting only to you. The agency should be in a working relationship with your designer, including the awkward parts. If every piece of feedback travels through the founder, you have made yourself a permanent bottleneck and you will not be able to step out of it later.

The one meeting that keeps this working

One thirty minute call a week, your designer and the agency lead, no founder in the room.

The agenda is three items. What is the agency shipping this week, what does it need approved, and what did it learn that should change the system. That is it. No status theatre, no slides.

Leaving yourself out is the important part. If you are there, both sides perform for you and neither says the honest thing. If you are not, they have to actually talk to each other, which is the relationship you are trying to build. Ask for two lines in a channel afterwards so you know it happened.

How to tell it is working

Three signs, and you can check all of them in a few minutes.

Your designer can tell you what the agency is working on without looking it up. Agency work ships without you approving it first. And the design system has changed in the last month, in a way your designer can explain in a sentence.

If instead you are still the router for every decision, or the agency's work keeps needing rework after your designer sees it, the line is wrong. Usually it is wrong in the same direction: the agency is still doing work that changes weekly. Move that work in house and give the agency the next project instead. It is also worth running the same quality checks you used before the hire on agency work, because a designer in the building is not a substitute for judging the work itself.

When to end it

Not automatically, and usually later than founders expect.

End it when your in-house team is big enough that project work no longer spikes, which for most companies means two or three designers, not one. One designer plus an agency is a stable arrangement and often a better one than two designers, because the second salary is fixed and the agency is not.

The honest reason to keep an agency after the first hire is capacity that turns on and off. The honest reason to end one is that you are paying a monthly fee for work that no longer arrives in bursts. Look at the last three months. If the agency was busy in one of them and idle in two, change the shape of the deal before you change the relationship.

Where to go next

If you are still choosing the agency half of this, our shortlist of design retainer agencies for teams hiring their first designer compares ten on public criteria, and design retainer agencies for companies scaling product teams covers the stage after that. If your designer is already underwater, design retainer agencies for overloaded design teams is the closer fit. And if the hire has not happened yet, design partner vs hiring an in-house designer works through that decision first.

Studio Maydit is a web and product design studio working with AI founders in the US, UK, and Europe. We work both ways: as the only design resource for founders with nobody in house, and alongside an in-house designer on launches and redesigns that would otherwise pull that person off the product. If you are drawing this line right now and want a second opinion on where it should sit, book a 30 minute call.