Website Design: Three Different Jobs Under One Phrase, and How to Choose

What "website design" actually refers to

The market uses "website design" for three different jobs, and confusing them is the main source of mismatched expectations. The first is styling: taking an existing structure and making it tidy. The second is designing: deciding which screens the site consists of, what matters most on each, and where a visitor goes next. The third is a system: components and rules that let the site grow without a designer.

Price and timeline differ several times over precisely because one phrase covers three scopes. When a client asks for website design and receives styling, both sides feel cheated: the supplier delivered exactly what they named, and the client expected something else.

The conversation becomes useful the moment the brief states which one is wanted: restyle what exists, design it properly, or build a system that will grow. Everything else — price, timeline, what arrives at the end — follows from that choice.

What follows sets out each level: what it contains, when it is enough, and how to tell you have bought the wrong one.

Level one: styling

This is the most common and the cheapest job. The structure already exists — from a template, a previous supplier, or years of accumulation. The designer's task is to put it in order: typography, spacing, grid, button states, one consistent visual language.

That scope is right when the site broadly works: people reach the pages they need, enquiries arrive, but everything looks assembled from different sources. Styling removes the homemade feel and barely touches the logic.

What styling does not do is fix structure. If a visitor cannot find a section or cannot tell what you offer, careful typography will not repair that. It will make the unclear thing handsome and still unclear.

The sign that this is the level you need: you can name every page on the site, you agree with that set, and your complaint is about how they look.

Level two: designing

Here the work starts before the first screen. The designer establishes who arrives, with what question, what should happen, and only then decides which pages exist and what leads on each of them.

The main output of this level is not pictures but decisions: which sections are needed, which are surplus, what appears first, where the target action sits, how a service page differs from a product page. The visuals follow from those.

This level is required when a site is being made for the first time, when the business has changed, or when the old site stopped answering the questions people actually arrive with. The symptom is simple: you keep answering things in email that the site should have said.

Designing costs more than styling because it includes work before any drawing. It is also what usually pays back, since most site problems live in the structure rather than in the surface.

Level three: the system

A system is a set of components and rules that let new pages be assembled without a designer. Grid, type scale, cards, forms, states, behaviour across screen sizes.

It is needed when the site will grow: new services, new sections, campaign landing pages. Without one, every new page is a separate commission, and within a year the site looks assembled from different sources again.

A system does not have to be large. For a ten-page site, a description of the grid, the scale, three card types and the rules for forms is enough. A hundred-page guideline for that project is overspend.

The test of a working system is the same as for an identity: someone who did not build it can assemble a page from it.

What affects the result most

First, clarity of the offer. A site cannot explain what has not been articulated. If the company does not agree internally on how it differs from the business next door, design will not resolve that and will honestly expose it.

Second, material. Real photographs of work, figures, what a service includes and what it costs move trust further than any visual idea. A site with mediocre design and genuine evidence usually collects more than a beautiful one full of generalities.

Third, speed. Heavy images and fonts delay the text, and someone on a phone does not wait. This is not a separate technical topic: decisions about the size and number of images are made during design.

Fourth, accessibility. Text contrast, type size, legibility in sunlight and on a small screen. This is not charity: the same requirements make the site clearer for everyone, including people in a hurry.

It is worth agreeing separately on who writes the copy. A layout built on placeholder text is almost always rebuilt once the real words arrive: genuine headings run longer, genuine lists run shorter, and the paragraph somebody promised sometimes turns out not to exist at all.

How the process runs

The sensible order is the same at every level. First the task and the material: what should change, who arrives, what already exists. Then structure: the list of pages and what leads on each.

Then the key screens in two states — wide and phone. Not every page: the ones that decide, which are usually the home page, a service page and a form. The rest is assembled to their pattern.

Then states and the details people skip: empty lists, form errors, long headings, missing images. Those are exactly what spoils the impression once real content arrives.

And handover: files, rules, what to do about new pages. Without that last step a site starts drifting within two or three updates.

What belongs in the handover: "" is three different scopes of work, not one.

At minimum: editable source layouts, exported images in the formats and sizes required, fonts with their licence stated, and a description of the grid and the type scale.

Separately, component states: how a button looks on hover and press, how a form looks with an error, what happens when a list is empty. A developer without those will invent them, and will invent them differently in different places.

It helps to record in writing what was not part of the work. That removes most acceptance disputes and makes the project's boundaries visible to both sides.

And a note on which images may be used and on what terms: original photography, licensed stock or generated material each carry different constraints.

Choosing the level for your task

Three questions answer this faster than any discussion. First: do you agree with the current set of pages? If not, you need designing, and styling will not help.

Second: how many new pages will appear this year? If it is more than five, or different people will build them, you need a system, or the site will diverge within a year.

Third: what exactly is failing now — people do not arrive, do not understand, or do not trust? The first is fixed by structure, the second by structure and copy, the third by evidence and finish.

At VITON13 the design service starts at $70 for a single logo route, includes a focused scope at $120, a launch-ready page level at $290 and a system at $540, and runs one to eight working days depending on volume.

And finally, agree in advance who is responsible for turning the layout into code. A design nobody intends to implement precisely survives exactly until the first change made on the development side, after which it becomes decoration nobody consults.