You need a designer before a developer when you have no brand yet, or when the look is what sells, like a consumer brand or premium service. If you already have a brand and need a working website or product, many developers design the page layouts as part of the build. If you do hire a designer, finish the designs before development starts.
This question usually comes from a sensible worry: if a developer builds first, will it look amateur? Sometimes. But waiting weeks for a designer when the job is a booking site for an existing business can be just as costly. The answer depends on what you already have and what your customers judge you on. Below: how to decide, three ways to get the design done, real projects with and without design files, what a good handoff looks like, and the mistakes that slow builds down.
Designer or developer first: the short answer
Hire a designer first when
The look is the job
- You have no logo, colours, or fonts yet
- The look is what sells: a consumer brand or premium service
- The product's value is in how easy it feels to use
- Several people must approve the look before anything is built
Start with a developer when
Working is the job
- You already have a brand, even a simple one
- The job is a working site or product: bookings, sales, logins
- A clean, fast layout matters more than a unique look
- It's a first version you'll change after real users try it
The cut
Most service businesses fall on the right: a clean, fast site that makes the next step obvious wins more work than a striking one that hides it. Consumer brands, luxury products, and creative businesses often fall on the left, because the look is part of what they sell. If you're unsure which side you're on, look at your best competitors' sites.
What a designer does vs a web developer
The titles overlap, which is part of the confusion. There are really three kinds of design work, and they need different people:
- Brand design: the logo, colours, fonts, and overall personality. Done by a brand or graphic designer.
- Page and screen design: how each page is laid out, what goes where, and how it adapts to phones. Done by a web or UI designer, and often by an experienced developer too.
- User experience: how easy it is to complete a task, like booking or checking out. Shared between the designer and the developer, and tested with real users.
A developer turns all of that into a working site: the code, speed, forms, payments, search visibility, and hosting. If your brand already exists, the middle item is the only design work left, and that's the part a developer can often take on. Ask to see sites they designed, not just built, before you rely on it.
Three ways to get a website or app designed
| Approach | Works best when | Watch out for |
|---|---|---|
| Designer first, then a developer | You need a brand, or the look is what sells | Designs a developer can't build well, or no phone layouts |
| A developer who designs the layouts | You have a brand and need a working site fast | Check their past sites look like what you want |
| An agency doing both | Brand, design, and build all start from zero | Higher cost, and more people between you and the work |
The agency option is covered in more depth in freelance developer or agency. Whichever route you pick, ask to see live work from the person who will actually design your pages, not just a portfolio of screenshots. Live sites show whether the design still holds up on a phone, with real content, after launch. That's where the difference between a good-looking mockup and a good website becomes obvious, and it's the fastest way to judge a designer and a developer alike.
Real projects built with and without a designer
My own projects split roughly both ways, which is a good sign that neither answer is always right.
Started from the client's Figma designs
A technology consulting firm and an aviation company both arrived with finished Figma files. The visual design stayed as designed. My job was making it responsive, fast, and set up for Google: the consulting site went from about 3 seconds to 450ms, and the aviation catalog from about 8 seconds to 676ms. Because the design was already approved, the weeks went into building rather than debating layouts.
Designed as part of the build
Easy Pawsy, a vet clinic, had no design files. The site was built around the clinic's services and the booking path rather than a template, in six weeks. Bookings went from about 20 to 120 a week. Authentic Urban, a food brand, was designed from scratch as part of a 12-week build, leading with the brand's story and proof rather than a generic store layout. The lesson from both sides: design files save time when they're finished and approved, and they aren't required when the business already knows what it sells and to whom. What slows projects down isn't the absence of a designer, it's design decisions that are still open once building starts.
What a good design handoff to a developer includes
If you do hire a designer, the handoff decides how smoothly the build goes. A developer should be able to build from the file without guessing. Before you pay the designer's final invoice, check that the file includes:
- Every key page on both phone and desktop
- Real content, or close to it, not placeholder text
- Colours, fonts, and spacing defined once and reused
- Buttons, forms, and menus in all their states
- Empty pages, error messages, and loading states
- Images and icons exported, with the right to use them
- Notes on anything that moves or behaves differently
Missing phone layouts and missing error states are the two gaps I see most. Each one means the developer designs it on the fly, which is fine if agreed, and a source of friction if not. Ask the designer to walk the developer through the file on a short call before the build starts. Twenty minutes of questions at that point saves days of back-and-forth later.
Do apps and SaaS products need a designer first?
For a first version, usually not. The goal of version one is to learn whether people use it, and plain, consistent screens built from a well-made component library do that job well. Money spent perfecting screens that change after the first users try them is often wasted. More on what belongs in version one is in what to put in a first version.
The exception is a product where ease of use is the whole point, like a consumer app competing on feel, or a tool replacing something people already find painful. There, a product designer early is worth it. If you're not sure whether you're building a site or a product, start with website or web product. Either way, agree on colours, fonts, and one set of buttons and form styles before the first screen is built. That small foundation keeps a product looking consistent even without a designer, and makes it easy for one to join later without starting over.
Design mistakes that slow down development
None of these are about talent. They're about timing and handoff, and each one adds weeks: Most can be avoided with one rule: the design is approved, on phone and desktop, with real content, before the build begins.
- Designing while building. Changing the look after pages are coded means building them twice.
- Desktop only. Most visitors arrive on a phone, and phone layouts designed late are rarely good.
- Designing without content. Layouts made for short placeholder text break when the real, longer text arrives.
- Forty screens for version one.Designing features that won't be built for months.
- Nobody makes the final call. Rounds of feedback from several people, with no one deciding.
- Treating AI mockups as final. Generated screens look finished but often skip phone layouts, real content, and error states.
If you're already in the middle of one of these, pause the build for a few days and settle the design. It feels slower, but it's almost always faster than building pages twice.
What to have ready before you hire either
Whichever you hire first, having these ready makes the quote more accurate and the project faster:
With this list, a developer can tell you quickly whether they can design the layouts or you need a designer first. Prices for either route are in what a custom website costs. Or send me what you have, and I'll tell you where to start. If a designer should come first, I'll say so, and explain what to ask them for so the build goes smoothly afterwards. And if you already have a designer you like, I'm happy to work alongside them.
