This might be an odd thing for a design agency to say, but here it is. If you're a founder with a small team and no design hire yet, your first move probably shouldn't be to hire one.

We've watched a lot of early founders go through this exact decision, and the pattern is consistent enough that it's worth writing down. Hiring too early, before you know what you actually need, tends to cost more than it saves.

The math nobody runs before hiring

A decent product designer at a startup costs real money, and salary is only part of it. There's the recruiting time, often two to three months of a founder's attention that could have gone into the product itself. There's the ramp-up period, where a new hire is learning your users, your codebase constraints, and your roadmap before they're producing much of value. And there's the risk that the person you hire isn't actually the right fit for the stage you're at, which you often only discover four or five months in.

Add it up, and a single early design hire can easily cost six to eight months of runway before you see consistent, high quality output. For a pre-seed or seed company, that's a significant chunk of the time you have to find product market fit.

What you actually need at this stage

Most early startups don't need a full-time designer. They need consistent design decisions made quickly, without becoming a full-time job for the founder or a distraction from building the product.

This is where a fractional or extended design arrangement earns its keep. Instead of one person who may or may not have the range to cover everything from onboarding flows to your first pitch deck, you get access to a small team with different strengths, available for however many hours a week the stage actually demands. Early on that might be ten hours a week. Closer to a launch, it might be forty.

The key difference from a full-time hire is that you're not paying for idle capacity, and you're not betting your design quality on a single person's skillset covering everything you'll need in the next twelve months.

What this actually looks like week to week

In practice, an extended or fractional design arrangement runs a lot like having an internal hire, minus the overhead. You get a point of contact who understands your product and shows up to your planning sessions. Design requests get triaged and prioritized the way any other workstream would. Work gets reviewed and shipped on a schedule you agree on together, weekly or biweekly depending on your pace.

What's different is that you're drawing on a wider bench. If your immediate need is a landing page that converts, you get someone who's good at that specifically. If the next sprint needs a complex dashboard reworked, someone with product design depth picks that up instead. You're not stuck hoping one generalist hire happens to be strong in the exact area you need help with this month.

When the math flips

This arrangement isn't meant to be permanent, and it shouldn't be sold to you as one. There's a point where bringing design in-house makes more sense, and it usually shows up as a combination of three things.

The first is volume. If design requests are coming in faster than a part-time or shared team can turn them around, and that's a consistent pattern rather than a one-off spike, it's a signal.

The second is need for deep context. Once your product has enough surface area that someone needs to live inside it full time, tracking every edge case and historical decision, an in-house hire starts to outperform an external team on speed of decision making.

The third is culture and ownership. At some point you want a person who feels ownership over the product's design the way your engineers feel ownership over the codebase. That kind of ownership is hard to fully replicate from outside, no matter how embedded the arrangement is.

When you see two or three of these signs together, usually somewhere between your Series A and B, that's the point to start hiring a design lead. And ideally, you hire that lead while you still have design support running, so they can walk into a system that already works rather than starting from zero under pressure.

The actual point

None of this is an argument against ever hiring designers in-house. It's an argument against doing it on a timeline set by anxiety rather than evidence. Founders often hire early because it feels like the responsible thing to do, the same way people feel they should have a lawyer and an accountant from day one. But design, unlike legal or financial risk, can be handled well on a flexible basis for a long time without real downside, as long as the person or team you're working with actually understands your stage.

If you're a founder trying to figure out whether you're at the "not yet" stage or the "hire now" stage, run the numbers honestly. Look at how much design work is actually queued up, how deep the context requirements really are, and whether the constraint is talent or simply time. Most early companies are short on time, not talent, and that's a problem an extended team solves better than a single new hire ever will.