Almost every founder we talk to eventually asks some version of the same question. Should we hire a designer, bring in an agency, or find some middle ground between the two? There's no universal answer here. There's only the right answer for where your company happens to be right now, and that changes as you grow.

We've worked across all three models, sometimes with the same client at different stages of their journey. Here's what fifteen years of doing this has taught us about when each one actually works, and where founders tend to get it wrong.

The traditional agency model

This is the model most people picture when they hear "design agency." You come to us with a defined project, a rebrand, a new marketing site, a pitch deck that needs to hold up in front of investors, and we deliver it within a scoped timeline.

It works best when the need is finite. You know what you want, you have a start and end date in mind, and once it's delivered, you don't need ongoing support for a while. The upside is speed. You get a senior team without the six month hiring cycle, and without adding anyone to payroll.

The downside is context. Every time a new project starts, someone has to get reacquainted with your brand, your product, your users. If you're commissioning agency work every few months for unrelated projects, that ramp-up cost adds up.

The exclusive design team model

This is less common but incredibly useful for a specific kind of company: startups that need consistent, ongoing design output but aren't ready to build an internal team from scratch.

Think of it as a dedicated pod, people who work only on your product, sit in on your standups, understand your roadmap, but are employed and managed by us rather than by you. You get continuity without the overhead of recruiting, onboarding, and managing a design function you don't yet have the experience to run.

We've seen this work particularly well for founders between seed and Series B, where hiring an experienced design lead is still six to twelve months away, but the product can't wait that long for design decisions to get made. The team acts as your design department until you're ready to build one internally, and in some cases, help you hire and hand off when that time comes.

The extended team model

This one is for companies a stage further along, usually scale-ups with a small internal design team that's stretched thin. You already have a design lead who sets direction and reviews quality. What you're short on is hands.

An extended team plugs into your existing process rather than replacing it. We join your sprint planning, work inside your design system, and report to your internal lead the same way a full-time hire would. The difference is flexibility. You can scale the extended team up during a big product push and scale back down afterward, without the awkwardness of layoffs or idle headcount.

A simple way to decide

If you're not sure which model fits, three questions usually clarify it fast.

First, how much context does this work actually need over time? A one-off deliverable doesn't need a team that lives inside your product. Ongoing product design does.

Second, do you already have someone internally who can direct design decisions and hold quality to a standard? If yes, you likely need extra hands, not a whole function. If no, you need something closer to an exclusive team that can operate with more autonomy.

Third, what's your actual runway to hiring, if hiring is even the end goal? Founders often assume they need to hire a senior in-house designer immediately, when what they really need is six more months of design output while they figure out the rest of the org.

Where founders get this wrong

The most common mistake we see is hiring a single senior designer too early, before there's anyone internally to manage or challenge their thinking. That designer either ends up making every call alone, without a second opinion, or burns out trying to be both an individual contributor and a de facto design lead. Neither outcome is good for the product or the person.

The second most common mistake is the opposite problem: commissioning agency work for a big one-off project when what the company actually needed was ongoing coverage. Six months later, they're back to square one, briefing a new team from scratch on a brand and product that has moved on since the last engagement.

The model isn't the point

Getting good design work done consistently, without overpaying for capacity you don't need or under-resourcing a function that's core to your product, is the actual goal. The label on the arrangement matters far less than whether it gets you there.

We built our own studio around this idea because clients rarely need just one of these things. A startup that starts with us as an exclusive design team often brings on their first internal design lead a year later, at which point the relationship naturally shifts into an extended team model. Some enterprise clients start as a traditional agency engagement for a single campaign and end up keeping us on retainer for ongoing design support across multiple product lines.

If you're trying to figure out which model fits your company today, the honest starting point is to be clear about what stage you're at and what you actually have in place internally, not what you think you're supposed to have by now. The right design partner should be able to meet you at any of these stages, and move with you as you outgrow them.