In-house designer or freelancer: when to outsource design work

I get hired for projects that in-house teams could do themselves. That sounds like a strange thing to admit, but it’s true, and understanding why it happens is probably more useful than a pros-and-cons list. The short answer is that in-house teams are built for throughput, not for one-off problems. A rebrand, a pitch deck for a funding round, a product that needs to look different before launch. These are projects with a start and an end. Hiring someone permanently to do a job that finishes in eight weeks doesn’t make sense, and most design leads know that. The question is usually when to pull the trigger, not whether to.

The actual trade-off

An in-house designer knows your product. They sit in the same meetings, absorb the same context, and can move fast because they already know where things are. That’s worth a lot. Tan Nguyen at PHMG put it well in an It’s Nice That piece: in-house designers ‘produce more meaningful work’ because they live inside the brand long enough to understand it properly. You can’t replicate that by sending a freelancer a brand guidelines PDF and hoping for the best.

But that same familiarity comes at a cost. In-house designers sit in a lot of meetings. Timothy Goodman nailed it: ‘As a creative person, I loathe meetings. Yet, as a business owner, I need to be in them a lot.’ That tension is even worse when you’re salaried. Your in-house designers are in standups, retros, alignment sessions, feedback rounds. The hours they actually spend designing are fewer than you think. Adding a side project on top of that doesn’t give them more time. It just takes the time they had left.

There’s also the familiarity problem. In-house designers get close to the work. They stop seeing what’s wrong because they’ve been staring at it for months. I’ve been brought into projects where the team knew something wasn’t working but couldn’t articulate what. They weren’t bad designers. They just couldn’t see the building from inside it.

A freelancer walks in cold. That distance is the whole point.

When it makes sense to bring someone in

Your designers are busy and a rebrand needs to happen before the conference in October. You could ask the team to squeeze it in, but ‘squeeze it in’ usually means ‘do it badly between other things’. Hiring someone whose only job is the rebrand tends to produce better work and fewer resentful designers. Or your team has developed a house style, which is natural, but now the homepage looks like everyone else’s homepage and nobody can see it because they’ve been too close for too long. Fresh eyes aren’t a luxury. They’re diagnostic.

Or the project sits outside your team’s skill set. Your UI designers are brilliant, but nobody has done a brand identity from scratch. You could let someone learn on the job. Or you could hire someone who has done twenty of them and knows where the hard parts hide.

Then there’s the work that’s temporary by nature. Event branding, a launch campaign, a one-off presentation for the board. These don’t justify a permanent hire. A freelancer picks it up, finishes it, and leaves.

When it doesn’t

If the work is ongoing and deeply embedded in your product, keep it in-house. A freelancer designing your core product screens every sprint is a bad idea. They’ll never have enough context, and the handoff overhead eats whatever time you saved.

If your team needs to grow, hire. Don’t use freelancers as a permanent substitute for headcount you actually need. I’ve seen companies do this for years, cycling through external designers instead of committing to a full time role, and the institutional knowledge just leaks out quietly.

If the budget is tight and the timeline is loose, do it internally. Freelancers cost more per hour than salaried designers. That math only works when speed or specialism justifies it.

What to look for

I’m biased, obviously. But a few things I think matter.

Look at how they organise their work, not just the final output. A portfolio of pretty screenshots tells you almost nothing about what it’s like to actually work with someone. Ask to see a Figma file. If the layers are named ‘Rectangle 42’ and the pages are called ‘Page 1’, that’s information. I wrote about how I structure mine here.

Ask about handoff. Where do the assets end up? What does the developer get? If the answer is ‘I send a PDF’, keep looking.

Check if they handle their own admin. Hannah Valentine, a freelance designer, described the reality honestly: a chunk of your time goes to invoicing, emails, and chasing things that aren’t design. If a freelancer can’t manage that without handholding, you’ll feel it. You’re hiring them to take work off your plate, not add to it.

Check if they’ve worked with teams before. Working alongside an in-house team is different from working with a founder who says ‘make it look good’. You need someone who can slot into existing workflows without being managed like a junior.

The part nobody says out loud

Most design leads already know when they need external help. The delay is usually internal. Getting budget approval. Convincing someone that ‘our team can handle it’ isn’t the same as ‘our team should handle it’. Worrying that hiring a freelancer signals the team isn’t enough.

It doesn’t signal that. It means the team is busy doing their actual job, and this other thing also needs to get done. The best briefs I’ve received from design leads all say some version of the same thing: ‘We need someone to own this so our team can stay focused’. That’s not a failure of the team. That’s a lead doing their job well.