WRITTEN BYJamal Akbar Alam
· 4 min read

Web designer vs. web developer: who does your project need?

READING NOTES09 / 23

A web designer decides how the site looks and how a visitor moves through it. A web developer builds it so it loads, works on a phone, and can be edited later. If you're hiring for a business website, you usually need both jobs done, but not always by two different people.

I do both, so take this with that bias. I'll also tell you where it stops being the right setup.

What each one actually hands you

A designer's output is decisions. Which page comes first, what the headline says, where the contact button sits, which colors and type make the business look like itself. The files they give you are layouts, usually in Figma.

A developer's output is a working site. Pages that open fast, forms that send to the right inbox, a way for your team to change a price without calling anyone. The thing they give you is a URL you can send to a customer.

Neither job is "just the visual part" or "just the code". A good layout that nobody can build within your budget is a drawing. A fast site with confusing pages is a fast way to lose a visitor.

Which one do you need first?

  • You have no site and no brand direction. Start with design. Building before you know what the pages should say means paying for the same page twice.
  • You have a design or a clear reference and it needs to ship. Start with a developer. Check that they will build what's in the file, not their own version of it.
  • You have a site that looks fine but is slow, broken on phones, or hard to edit. That's a developer problem. A redesign won't fix it.
  • You have a site that works but visitors don't know what to do. That's a design problem. New code won't fix it.

If you can't tell which of the last two you have, open your own site on a phone and try to contact the business. Where you got stuck tells you who to hire.

The handoff is where projects leak

When design and development are two people, there's a handoff in the middle. The designer draws a menu that opens with a nice animation. The developer finds it adds a second of delay on a mid-range phone and quietly simplifies it. Nobody tells the client, and the site ships looking slightly different from what was approved.

Good teams manage this with a lot of conversation. That conversation costs time, and on a small project it can cost more than the part it protects.

With one person doing both, the question "can we build this?" gets answered while the layout is still cheap to change. I'll say a design is too heavy before I draw the next five pages around it.

When I'd tell you to hire two people

One person has limits, and you should know them:

  • Large builds on a deadline. A big store or a platform with many features needs more hands than one person has.
  • Ongoing design work. If you need a steady stream of campaigns, illustrations, and brand pieces, a dedicated designer will serve you better than someone who also writes code.
  • You already have a design team. Then you need a developer who respects the files, and that's a narrower job.

For a company website, a landing page, or a small store, one person who designs and builds is usually the shorter path, and there are fewer meetings between your idea and the live page.

How to decide in ten minutes

Write down what the site must do in one sentence, for example "let a new customer see our work and book a call". Then write what is stopping it today. If the blocker is what the pages say and show, hire for design. If it's speed, errors, or how hard it is to change, hire for development. If it's both, ask whether one person can cover both and look at their work first.

I'm Jamal Akbar Alam, a developer and designer in Bandung. If you're deciding between hiring one person or two, send me your site and what you want it to do and I'll tell you honestly which setup fits. If you need a business website, the business website page shows how I work and what it covers.

Have something in mind?

Let’s talk