07846 432491 Start a project

Website development

Web Designer or Web Developer: Who Do You Need?

The two job titles get used as if they meant the same thing, and plenty of people in the trade use whichever sounds better on the day. They are different skills, though, and hiring the wrong one is a common reason projects go over budget or stall. A developer asked to make something look good, or a designer asked to connect a booking system to an accounts package, is being set up to struggle.

Here is the web designer vs web developer question in plain terms, and how to match the right person to your project.

What a web designer does

A web designer decides how a website looks and how people move through it. That covers the layout of each page, colours and typefaces, which information comes first, where the buttons go and how it all rearranges itself on a phone. A good one starts from what a visitor is trying to do and works backwards.

Many designers also build what they design, using tools such as WordPress with a page builder, Wix or Squarespace. For a typical business website, that is the whole job.

What a web developer does

A web developer writes code to make a website do things. The work is usually described in two halves.

  • Front end is everything that runs in the visitor’s browser: turning a design into working pages, menus, forms and animations.
  • Back end is everything that happens on the server: storing customer records, taking payments, checking logins, sending data to other systems.

Someone who does both is called a full-stack developer. Developers are who you need when a site must do something no ready-made tool offers.

Where the two overlap

In practice the line is blurred. Modern website platforms let designers build fairly capable sites without writing code. Many developers have a decent eye. Small studios often have people who do both, or a designer and a developer working side by side.

So the useful question is not which job title someone has. It is whether the work you need is mainly about presentation, mainly about function, or a real mixture.

Which one does your project need?

What you want Who you mainly need
A brochure website: services, about, contact, gallery A designer who builds, or a small studio
A new look for an existing site on the same platform A designer
An online shop with standard products and delivery A designer who knows the shop platform well
A shop with unusual pricing, stock links or trade accounts Designer and developer together
Online booking tied to your own diary or staff rota A developer, with design input
A customer portal or login area A developer
Connecting the website to your accounts, CRM or other software A developer
A site that has become slow or keeps breaking A developer

If your project sits in the top three rows, you are buying a website. Further down, you are buying software with a website on the front. The difference affects cost, timescale and who you should be talking to.

Signs you have moved into developer territory

Owners often do not realise they have crossed the line. Listen for yourself saying any of these:

  • “It needs to talk to the system we already use.”
  • “Customers should be able to log in and see their own orders.”
  • “The price depends on several things they choose.”
  • “We type the same details into three places at the moment.”
  • “There is a plugin that nearly does it, but not quite.”

Each of these is ordinary work for a developer and a headache for someone working only with page-building tools. We look at this turning point in when a business needs more than a brochure website.

What it means for cost

Design-led websites can usually be priced up front, because the work is predictable. That is why packages exist. Development is priced on the time it takes to build and test a particular feature, so a proper quote needs a clear description of what the feature must do.

Be cautious of a fixed price for custom functionality given after a five-minute chat. Either the supplier has not understood it, or the price includes a wide margin for surprises. A short written specification protects both sides.

Questions that reveal who you are talking to

  1. Will this be built with an existing theme and plugins, or will code be written for it?
  2. Who on your side does the design, and who does the build?
  3. Have you built this particular feature before? May I see it working?
  4. If a plugin you rely on stops being supported, what happens?
  5. Who will I contact for changes in a year’s time?

Honest answers are a good sign even when they include “we would bring someone in for that part”. The broader checks in our guide to choosing a web designer apply to developers too.

One team or two?

For most small businesses, one supplier who covers both is simpler: a single conversation, and nobody blaming the other when something does not fit. What matters is that they are straightforward about where their strengths lie.

We work across both. Standard business sites come under our website design and development service, and projects that need portals, bookings or bespoke features are handled as web application development, with a quote based on what the system has to do. We are based in Manchester and work with businesses across the UK.

Call Start a project