Design subscription or full-time hire?
Your first design hire is a big bet on one person. How to weigh a full-time designer against a senior design partner: the seniority you can reach, the range you need, what a hire really costs, and when hiring is the right call.
- Published
- 15 July 2026
- Reading time
- 10 min
- Topic
- Process
Chapters
Somewhere around a raise, most founders hit the same question. The product needs a designer, the website needs one, and so does the next deck. Do you hire someone, or bring in a design partner?
Jake and I have both been the only designer inside a fast-growing startup, so we know the hire's side of this from the inside. Now we sit on the other side of it as well. Neither answer is right for every company, and the wrong one is expensive either way. This is how I'd think it through if I were the founder, including the cases where I'd tell you to hire.
Senior, before you can afford senior
Most founders know they need senior design. The decisions you make in the first couple of years are the hardest ones to undo: how the product is structured, the information architecture everything else hangs off, what the brand stands for, what an investor sees when they open the deck on their own. Every screen, page and slide you make afterwards inherits those choices.
The budget usually says something else. At seed, a design salary tends to stretch to a junior or mid-level designer, so that's who gets hired. It's an understandable call. It also means the most important design decisions the company will ever make are made by the least experienced person who will ever hold that seat.
It's worth being specific about what seniority buys you at this stage, because it isn't polish. It's knowing which problem to solve first. It's saying no to the feature request that would clutter the product for everyone else. It's spotting the flow that will break the day you add a second type of user, and designing a component once so engineering doesn't build it five slightly different ways. It's knowing when shipping at 90% is the right call and when it will cost you a rebuild. And it's being able to push back on a founder with a reason, not a preference.
A junior designer can learn all of that, and plenty do. It's just an expensive classroom when the place they learn it is your product, with engineers waiting on them and nobody senior reviewing the work. There's a quieter difference too. A junior designer on their own tends to design what they're asked for. A senior one asks why you're asking, and at the early stage the why is often where the real problem is.
So the honest comparison isn't a designer against a design partner. It's the level of designer your budget reaches as a hire against the level you'd actually want making those decisions. A partner lets you have the second at the stage when you can only afford the first.
One person, one range
This is the part I think founders underestimate most. When you hire a designer, you hire one person's range.
Design at an early-stage startup isn't one job. In a single month you might need a new onboarding flow, a pricing page, an investor deck and social templates for a launch. That's product, web, presentation and brand, and they're different crafts with different instincts. Product designers think in systems, states and edge cases. Brand designers think in meaning, tone and how to look like nobody else in the category. Web designers think in story and in getting a visitor to the next step. Deck designers think about how a slide reads when nobody is in the room to present it. They overlap, but very few people are senior at all four.
I know this from my own career. I trained as a graphic designer and moved into product design, and I'm glad I did both. But a brilliant senior product designer isn't automatically someone you'd trust with your identity, and a strong brand designer can get lost in a data-heavy dashboard. Whoever you hire, part of your design work will land on their weaker side, and you often won't find out which side that is until it has shipped.
If you do hire, look hard at the work they've done for the surface you'll need most in the first year, not the project that looks best in the portfolio. A beautiful brand case study tells you very little about how someone will handle your permissions model.
The usual patch is freelancers for the gaps: one for the brand, another for the website, someone else for the deck. Each of them is good at their piece. None of them owns how the pieces fit together, so the website drifts away from the product, the deck drifts away from both, and the founder ends up as the art director holding it all together.
Range in one place fixes two things at once. The right person works on each problem, and the same people work across all of them. At Unlimity, Jake's and my combined experience adds up to real depth across every kind of design work a startup needs: product, brand, web and decks. And because the same two people design your brand, your site and your app, nothing feels jarring when someone goes from your homepage into the product.
Hiring isn't wrong at that stage. It's a big bet on one person at the moment you most need range.
What a hire really costs
When founders compare the two, they usually put a monthly fee next to a salary and stop there. The salary is real, but it's the least surprising cost of the whole thing.
Before a hire is useful, someone has to find them. That means writing the role, sifting portfolios, running calls, setting a design task and sitting on the panel. At a company without a designer that someone is usually a founder, judging work they don't feel qualified to judge, with time that should be going on selling and raising. Then there's a notice period, and then the ramp: learning the product, the customers, the codebase and how decisions really get made. Nobody does their best work in that stretch, however good they are.
While they work, someone has to manage them. If nobody senior in the company has done design, that's a founder setting direction, reviewing work and running career conversations for a discipline they've never practised.
And the biggest cost is the one nobody budgets for: hiring the wrong person. The designer who interviewed brilliantly but can't handle how complex your product is, or who's excellent at product and lost on brand. By the time that's clear, you've paid for the search, the notice period and the ramp, and you're starting again while the roadmap waits.
A partner takes most of that away, though not all of it. You still have to brief clearly, give honest feedback and make the decisions only you can make. No setup removes that, and you shouldn't want one that does.
When the need runs hot and cold
A full-time designer is a fixed amount of design, whatever the month looks like. The need for design at a startup isn't fixed. It runs hot around launches, raises and big releases, and cold in the stretches in between.
With a hire, the cold months turn into polishing things that don't need polishing, and the hot months are nowhere near enough, because one person can't suddenly become two. A partner can scale up while things run hot and back down when they cool, without a second hire to recruit or anyone to let go.
If your need for design really is constant and full time, this point matters less. If it runs hot and cold, it may matter more than anything else here.
Context, the hire's strongest argument
The best case for an in-house designer is context. They sit in every meeting, they know why the product looks the way it does, and they remember the decisions that got you here. One CEO told us on a call that outside teams had burned them before for exactly this reason: they never understood the business well enough to make good calls.
It's a fair worry, and it's the right thing to test any partner on, us included. Do they work inside your tools, or send files over the wall? Is it the same people every time, so knowledge builds up, or whoever is free that week? Do they write decisions down where your team can find them? Do they ask about the business before they open Figma?
The hire has a context risk of their own, which is that it all lives in one head. When they're on holiday, design stops. When they hand in their notice, a lot of what they knew leaves with them. Context that's written down in your own tools survives a change of people. Context in one person's memory doesn't.
When hiring is the right call
None of this means you should never hire a designer. Sometimes it's clearly the right move, and we'd tell you so on a call.
If design is your product, hire. If the interface is what customers pay for and it changes every day, you want designers in the building full time, in every product conversation.
If you can afford a lead, hire a lead. The pattern that works is a senior design lead who sets the direction, with a team growing around them. The pattern that struggles is one junior or mid-level designer on their own, expected to cover everything.
And if you're ready to build a design team and a design culture for the long term, that's a job for people on your payroll.
It doesn't have to be one or the other, either. We've worked alongside junior designers while they find their feet, leading the design and leaving them a component library, clear files and ways of working to build on. For a lot of startups the honest answer is a design partner now and a design lead later, and the lead inherits a foundation instead of a mess.
How to decide
If you're weighing it up, these are the questions we'd ask you on a first call.
What would they actually work on? Write down the requests you'd hand a new hire first. If they span product, web, brand and decks, you need range more than you need a role.
Can you afford senior? If the budget only stretches to a junior, ask who makes the big design decisions in the meantime.
Does your need run hot and cold? A constant flow suits either. Hot stretches around launches and raises, with quiet ones between, suit something that can flex.
Who would manage them? If the answer is a founder with no design background, be honest about how much time that takes.
What happens if they leave? If the answer is that design stops, that's a risk worth pricing in.
Is design the product? If your interface is what customers pay for, start building the team.
For most of the founders we talk to, somewhere between pre-seed and Series B with a lean team and design spread across four surfaces, a senior design partner is the better fit. Hiring isn't wrong at that stage. It's a big bet on one person at the moment you most need range. When design grows into a team of its own, hire, and we'll help set that person up to do their best work.
Keep reading.
All posts →Early stage, scaling or established?
Let's talk.
Most of our work is with fast-moving startups, but we work with teams of every size. Tell us what you're building and we'll tell you honestly how we'd help.