What does a web designer actually do?
The short answer
Most of the value is decisions, not pixels. Working out what the site needs to achieve, which questions it must answer, what goes first, what gets left out, and how the parts fit together — then producing something that reflects those choices. The visual work is real, but it is downstream of judgement, and judgement is what separates a site that earns from one that merely looks finished.
On this page
What you are actually buying
People assume they are buying appearance. Appearance is the visible part, and it is the smallest part.
Deciding what the site is for. Bookings, enquiries, orders, or simply answering questions so the phone rings less. Different goals produce genuinely different sites, and a designer who does not ask is guessing.
Deciding what goes first. Every page has an order, and the order determines what people read and do. This is the highest-leverage decision on the whole project and it is invisible in the finished result.
Deciding what to leave out. The hardest part, and the one clients resist. A page that says three things well outperforms one that says nine.
Deciding how the parts connect. Which pages exist, what links to what, what someone does next from anywhere on the site.
Then producing it. Layout, typography, colour, images, and code — real craft, downstream of the decisions above.
Why the decisions cost more than the drawing
Anyone can produce a competent-looking page now. Templates are good, tools are good, and generated layouts are increasingly good.
What is not automated is knowing that this café should lead with its set lunch because that is the margin, or that this clinic should publish prices because the anxiety about cost is what stops people booking.
That knowledge comes from asking, from experience, and from having been wrong before. It is what you are paying for, and it is the part that is worth paying for.
What a good one asks you
If someone starts with "how many pages do you want", the process is upside down. A good brief is a conversation about the business first:
- What do you actually want a visitor to do?
- Who are your best customers, and how did they find you?
- What do people ask you every week?
- What do you want to stop doing manually?
- What has to be updated often, and by whom?
- What would make this a failure?
That last question is the one that surfaces the real requirement, and it is rarely asked.
What is not their job
Being clear about this prevents most disagreements:
Writing your content, unless agreed. They can shape and edit; they cannot know your prices, your story, or what makes you different.
Marketing. Building the site and driving people to it are different jobs, sometimes done by the same person, never by default.
Ongoing maintenance, unless it is in the agreement. This is the most common gap between what a client assumed and what was sold.
Guaranteeing rankings. Nobody can.
The questions that reveal quality
Ask any designer these before hiring:
"What will I be able to change myself?" The answer tells you whether you will be emailing them for a price change in eight months.
"What happens to my site if we stop working together?" You want to hear that you keep the domain, the files and the ability to carry on.
"Can I see something you built that is still live and still maintained?" A portfolio of launches is easy. A site still working well three years later is evidence.
"What would you tell me not to build?" The most revealing question there is. Anyone who says yes to everything is selling hours rather than judgement — and judgement was the thing worth buying.
The question that has replaced "can you build it"
Building a site is no longer the scarce skill, which changes what you should be buying. The judgement described above is the scarce part, and there is now a second question worth as much as any on that list:
"After launch, what can I change without you?"
A designer who has thought about this has an answer ready, and it is usually specific — you edit text, images, prices and hours; I handle structure and design. A designer who has not will describe a process that runs through them for everything, which is a business model dressed as a service level.
Neither answer is disqualifying. The one that costs you is the vague one, because it becomes an invoice every time your opening hours change. Helm exists to make the first answer easy to give: the designer builds a custom site, and the client gets a branded dashboard for the things that move, so nobody is queuing behind anybody for a phone number.