Who actually builds websites — designer, developer, agency, freelancer

The four words in this cluster’s title are used loosely enough across the industry that none of them reliably tells you what you are buying. A “web designer” business might do full development; a “web developer” might mostly do design; an “agency” of two people exists alongside an “agency” of fifty. Knowing what each term is supposed to mean, and how often practice diverges from it, is what lets you ask the right question instead of trusting the label.

The four web design roles, as the terms are supposed to work

Term	What it’s supposed to mean	Where the label commonly diverges
Web designer	Visual layout, user experience, information architecture — the look and the flow	Many “designers” also code the build, especially on template-based platforms
Web developer	The code that makes a design function — front-end, back-end, integrations	Many “developers” also make significant design decisions, particularly on smaller projects
Design agency or development agency	A business employing more than one person across some combination of design, development, content and project management	Size varies from two people to fifty-plus; the word says nothing reliable about scale
Freelancer	A single independent person, contracted directly	May in practice subcontract parts of the work to others without always disclosing it

Why web designer and web developer words blur in practice

Most small-business website work does not require a specialised team, and a single competent person doing both design and development is common, efficient, and often perfectly appropriate for the scope. The blur becomes a problem only when the label implies a capability that is not actually there — a “full-service agency” that is one person working across every discipline they are only moderately strong in, or a “developer” quoting confidently on design decisions with no design training behind them.

The question that cuts through the label

Rather than relying on what a business calls itself, ask directly: who, by name, will be doing the design, and who will be doing the build? If it is the same person for both, ask to see examples of each discipline separately, because strength in one does not imply strength in the other. If it is different people, ask how many, because “agency” attached to a two-person operation is not dishonest, but it does change what continuity and specialisation you can actually expect.

What a web designer, developer, agency and freelancer should each be strong at

A designer should be able to show layout and user-experience decisions and explain the reasoning behind them, not just present finished visuals. A developer should be able to speak concretely about performance, accessibility and how the site will be maintained after launch, not only “it will work.” An agency should be able to name who specifically will work on your project, not describe the team in the abstract. A freelancer should be direct about what parts of a brief sit outside their core skill, rather than agreeing to everything.

Where this distinction actually matters for a small business decision

If your project is a straightforward business site, the distinction between designer and developer matters less than the distinction covered on freelancer vs agency for your website — namely, who you are contracting with and what happens if that person is unavailable. If your project has unusual technical requirements — custom functionality, integrations, non-standard performance needs — the designer/developer distinction becomes more practically important, because a design-strong generalist may not be the right fit regardless of how good their portfolio looks.

What “full service” is supposed to mean, and often doesn’t

A related and equally loose term is covered in more depth on what “full service” actually means — worth reading alongside this page if a supplier is using that phrase in their pitch.

A two-minute way to test a designer’s or developer’s claim

Ask to see one example each of pure design work (a wireframe, a mockup, an explanation of a layout decision) and pure development work (a technical explanation of how a feature was built, or a discussion of page speed). A supplier strong in both will answer both comfortably. A supplier strong in only one will visibly default back to their comfort area regardless of which question was asked — which tells you, honestly, what you are actually hiring.

How to spot which web design role you’re actually talking to

A supplier’s job title on a proposal is a weaker signal than how they answer specific questions. Ask someone who calls themselves a “web designer” to walk you through how a contact form actually submits data, or how a page’s load speed is optimised — a genuine developer answers concretely; a designer without development depth will describe it in visual or conceptual terms rather than technical ones. The reverse test works too: ask a “developer” to explain a layout decision on their own portfolio piece, and listen for whether the answer is about user experience or purely about implementation.

Why the blur is worse for small projects than large ones

A large, well-resourced project usually has enough budget to engage distinct specialists for each role, which keeps the boundaries relatively clear. A small business project — the majority of what this site covers — is far more often handled by one or two people covering multiple roles at once, which is exactly where the blur described above causes the most confusion, because the same person is being asked to wear several hats with genuinely different skill requirements. This isn’t a reason to avoid a small or solo supplier; it’s a reason to ask more specifically what they’re actually strong at within that combined role.

What changes once you know which web design role you actually need

Knowing whether your project is design-heavy, development-heavy, or genuinely balanced changes how you should read a portfolio. A design-heavy project — mostly about how the site looks, reads and guides a visitor — should be assessed against a supplier’s layout, typography and content-structure work. A development-heavy project — custom functionality, integrations, performance — should be assessed against technical case studies and specifics a supplier can speak to in detail, not just finished screenshots.

What to do next when hiring a web designer or developer

Before engaging anyone, write down which of the four roles your project actually needs — design-heavy, development-heavy, or genuinely both — and ask directly who at the business will be doing which part. The broader set of questions worth asking once you’ve identified the right role is on questions to ask a web designer before you sign.

What a business calling itself any of these four things actually is as a going concern is covered on what a website design company actually is.