How the web design industry works

Why how the web design industry works matters to a buyer

Because almost every confusing part of buying a website comes from the web design industry describing itself inconsistently. Two suppliers use the same job title for different work, quote the same word for different deliverables, and cite standards that one of them follows and the other has only heard of. Knowing which questions are answerable is most of what makes a supplier conversation productive.

What the pages in this section cover

The roles, and where the boundaries between designer, developer, agency and freelancer really sit. What “standards compliant” means and what it does not. White-label and reseller arrangements, which are common and rarely disclosed, and which explain why the person you hired may not be the person doing the work. And the measurement pages: how this site gathers demand figures, why Google volume and AI-assistant volume are different measurements that must not be added together, and what the limits of both are.

What is here

Who actually builds websites: designer, developer, agency, freelancer — the boundary between the roles, and why a job title predicts less than a buyer assumes.

What “full service” actually means — the claim on almost every agency homepage, and what it commits a supplier to in practice.

In-house, outsourced or marketplace web work — three different production models behind the same quote.

How web design work is actually priced — the real cost drivers underneath a single headline figure.

Offshore production and what changes — what moves and what does not when part of the work is produced overseas.

What “web standards compliant” actually means — a phrase used to sound rigorous, and what it is supposed to actually guarantee.

WCAG as an industry standard, separate from the law — a technical standard and a legal obligation are not the same thing, though suppliers often conflate them.

How this site measures demand — the tool, the date, the location setting and the query, stated rather than assumed.

Google search volume vs AI assistant volume — two different measurements of demand that must not be added together.

Why published web design statistics are usually unsourced — how a number without a date or a method survives being repeated for years.

The Australian financial year and when websites get commissioned — the seasonal pattern behind when Australian businesses actually brief a project.

How the industry sells SEO alongside a build — where a build ends and an ongoing SEO service begins, and why the two get bundled.

The roles: designers, web designers and developers, described from outside

Job titles in web work are inconsistent to the point of being unhelpful. Two suppliers will use “web designer” for different scopes, quote the same word for different deliverables, and describe arrangements that differ substantially in who actually does the work. “Designer” alone tells a buyer very little — it can mean someone who works entirely in a visual tool and hands off a static mockup, or someone who also writes the front-end code that turns that mockup into a working page.

These pages describe the trade as a buyer encounters it: what the roles cover in practice, what a full-service claim usually means, and how in-house, outsourced and marketplace production differ in ways that show up in the result.

Where design skills come from, and why that varies so much

Web designers reach the job by different routes — a design degree or bachelor’s degree, a shorter course, or self-taught coding and visual work — and the route shapes the skill set — and the career that follows it — more than the title does. Someone whose background is visual design and user research may hand off static screens; someone whose background includes front-end coding (HTML, CSS, and enough JavaScript to build the page) can deliver a working site rather than a picture of one. Neither path is wrong, but a buyer who does not ask which one their designer took can end up expecting a career’s worth of coding skill from someone trained purely in visual interaction design, or vice versa.

How this site measures its own industry claims

Several pages here explain how this site gathers the figures it publishes: which tool, which location setting, which date, and what the resulting number does and does not support. That is unusual enough to need justifying. This trade runs on statistics nobody can trace — a figure about page speed and conversion, or mobile traffic share, or how long visitors spend before forming a judgement, gets copied from one marketing page to another until the original study, if there ever was one, is unrecoverable. The number survives; the conditions it was measured under do not.

The pages state the tool, the date, the location setting and the query, so a reader can disagree with the method rather than only with the conclusion. So the position taken here is that a figure without a date, a source and a method is not evidence, and that includes figures this site would like to be true. Where a measurement has been taken, the pages say how. Where one has not, they say that instead. For what web design covers as a discipline, before you get to how the industry sells it, start with web design in Australia.